[Desktop-packages] [Bug 1851824] Re: gnome shell freezes when too many notifications appear

[Daniel van Vugt]

Please also check if uninstalling these extensions avoids the bug:

'area-screens...@dasprids.de'
'dash-to-d...@micxgx.gmail.com'
'screenshotlocations.ti...@linux.com'
'gnome-shell-screens...@ttll.de'
'caffe...@patapon.info'
'un...@hardpixel.eu'

We need to check this since so many bugs are caused by extensions.

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

Title:
  gnome shell freezes when too many notifications appear

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I'm using 20.04. When I receive some notifications immediately one
  after the other, the shell sometimes freezes.

  I usually make it start again moving to a vt and doing `killall -3
  gnome-shell`.

  This makes it work again (except it makes some apps like PyCharm and
  Chrome to crash).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  8 13:26:49 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-02-03 (277 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2019-07-21 (109 days ago)

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

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

[Desktop-packages] [Bug 1854371] Re: Input lag with Razer Naga Trinity mouse

[Daniel van Vugt]

This might be the same issue as bug 1799679. Do you find it happens on
any particular applications? Or with zero applications?

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

** Package changed: 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/1854371

Title:
  Input lag with Razer Naga Trinity mouse

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  When pressing multiple keys on my keyboard (Roccat isku FX) and pressing 
repetitively the buttons on the "numpad" (side buttons) of my mouse (Razer Naga 
Trinity) at the same time, the system freeze while doing this. All become 
normal again when I stop doing this.
  While freezing, I can see the Xorg process going up to 60/70% of the CPU.

  Not sure if it is a Xorg or driver related problem, or anything else.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/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 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 28 15:25:50 2019
  DistUpgraded: 2019-10-25 11:21:07,314 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.3.0-22-generic, x86_64: installed
   nvidia, 435.21, 5.3.0-23-generic, x86_64: installed
   openrazer-driver, 2.6.0, 5.3.0-23-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-22-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GM206 [GeForce GTX 960] 
[19da:1385]
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=eabe8e30-c27a-4b40-8af2-38ffd8bcbcc9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-10-25 (34 days ago)
  dmi.bios.date: 02/28/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1801:bd02/28/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  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.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  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/xorg-server/+bug/1854371/+subscriptions

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

[Desktop-packages] [Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset

[hugh chao]

@Robert,

Is there any chance you can review this mp in #15? many thanks

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

Title:
  [18.04]Not able to adjust Audio input UI volume after connecting
  headset

Status in gnome-control-center:
  New
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  Summary:Not able to adjust Audio input UI volume, it's gray

  Steps to reproduce:
  1. Plug 3 ring earphone with mic to appropriate jack

  Expected result:
  System can be recording audio from external mic

  Actual result:
  Not able to adjust Audio input UI volume, it's gray, and no volume detected 
in UI, but I can recording the input audio by checkbox

  Failure rate:100%

  Note.
  1. There is no internal mic, just a mic jack on the machine, this issue will 
happen
  2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2

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

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

[Desktop-packages] [Bug 1854371] Re: Input lag with Razer Naga Trinity mouse

[Daniel van Vugt]

To test for sure, please uninstall the Nvidia proprietary driver and
boot with the default 'nouveau' driver. Does the bug then go away?

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

Title:
  Input lag with Razer Naga Trinity mouse

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  When pressing multiple keys on my keyboard (Roccat isku FX) and pressing 
repetitively the buttons on the "numpad" (side buttons) of my mouse (Razer Naga 
Trinity) at the same time, the system freeze while doing this. All become 
normal again when I stop doing this.
  While freezing, I can see the Xorg process going up to 60/70% of the CPU.

  Not sure if it is a Xorg or driver related problem, or anything else.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/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 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 28 15:25:50 2019
  DistUpgraded: 2019-10-25 11:21:07,314 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.3.0-22-generic, x86_64: installed
   nvidia, 435.21, 5.3.0-23-generic, x86_64: installed
   openrazer-driver, 2.6.0, 5.3.0-23-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-22-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GM206 [GeForce GTX 960] 
[19da:1385]
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=eabe8e30-c27a-4b40-8af2-38ffd8bcbcc9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-10-25 (34 days ago)
  dmi.bios.date: 02/28/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1801:bd02/28/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  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.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  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/xorg-server/+bug/1854371/+subscriptions

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

[Desktop-packages] [Bug 1853351] Re: Object St.Button has already been deallocated

[Daniel van Vugt]

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

This looks like bug 1848119, which was fix-released within hours of this
bug being created.

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

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

** This bug has been marked a duplicate of bug 1848119
   gnome-shell infinite error loop when closing app in activities overview: 
Object St.Button (0x55aeadeca4a0), has been already deallocated ... 
[workspace.js:695]

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

Title:
  Object St.Button has already been deallocated

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

Bug description:
  I don't know what causes it but frequently I see my journalctl being
  spammed with gnome-shell errors (see attached journalctl snippet). If
  I do nothing about it, then within a few hours gnome-shell is slow and
  may eventually freeze. So I end up rebooting to reset the system and
  avoid a freeze.

  I'll keep my eye out for reproducers but in the mean time I wanted to
  record this somewhere in case others see it.

  This happens every couple of days on both my laptop and workstation
  and both systems are running 19.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 20 11:36:37 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-13 (67 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-19 (62 days ago)

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

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

[Desktop-packages] [Bug 956120] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a()

[Daniel van Vugt]

Please open a new bug for Ubuntu 18.04 by finding the .crash file and
then run:

  ubuntu-bug /path/to/file.crash

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a()

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Shell crash right after closing an application window (Synaptic).

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: gnome-shell 3.3.90-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
  Uname: Linux 3.2.0-18-generic-pae i686
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  CrashCounter: 1
  Date: Thu Mar 15 17:36:50 2012
  ExecutablePath: /usr/bin/gnome-shell
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 
(20120211)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0xb7241ad0 :   testb  
$0x4,0xe(%edi)
   PC (0xb7241ad0) ok
   source "$0x4" ok
   destination "0xe(%edi)" (0xc009fa22) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/gnome-shell/libgnome-shell.so
   g_simple_async_result_complete () from 
/usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a()
  UpgradeStatus: Upgraded to precise on 2012-03-13 (2 days ago)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1853440] Re: Volume either 0 or 100% on Lenovo X1 Carbon G7

[Daniel van Vugt]

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

apport-collect 1853440

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

** Tags added: eoan

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

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

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

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

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

Title:
  Volume either 0 or 100% on Lenovo X1 Carbon G7

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Volume increasing or decreasing doesn't work. 
  I can only toggle sound on (= 100%) and off (= 0%).

  What I found out is that the Master channel seems to have no effect
  for volume adjustments, but the PCM channel does. If the sound is
  muted, PCM is set to 0 and therefore the sound is toggled off, but
  when I increase the sound a bit, PCM jumps straight to 100, causing
  the speakers to be very load.

  I have attached alsa-info output.

  System environment:
  Pop!_OS 19.10
  Release: 19.10

  Alsa-Version:
  alsa-base: 1.0.25

  Sound Card:
  HDA-Intel
  Codec: Realtek ALC285

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

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

[Desktop-packages] [Bug 1854386] Re: Stuck on show applications overlay (can't close it)

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1854386

Title:
  Stuck on show applications overlay (can't close it)

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

Bug description:
  Hello,

  I've upgraded my ubuntu 19.04 to 19.10 this morning and I came across
  this very annoying bug.

  Whenever I click on 'show applications' or press win key (shortcut),
  the menu with the applications show, but it's empty - you can search
  through it and it works fine (applications show, one can trigger
  application launch), but then after you select an application, the
  menu doesn't disappear at all.

  It doesn't go away when pressing any application on the dash panel,
  nor when clicking esc key, it only goes away after you click on the
  dash icon again, BUT...

  It doesn't really go away - it just becomes invisible, but still it
  overlaps all the items that are launched (with exception of dash
  panel, because it's not being overlapped), and you can't do anything
  on any launched application. Sometimes when you try to move some
  windows, you can see them getting transformed into a miniature, as if
  the system wanted to insert application into the suggestions on the
  'show applications'.

  The only thing that worked for me was restarting my computer.

  Here is a movie of this happening:
  
https://photos.google.com/share/AF1QipNA94MOXY4iH8rm01coSkZcH6ILYas9n2oXNs9Swxo16ijABFqz71VaRpO59tGpPg/photo/AF1QipOqVIZXLZW-Z_7zCIy8eeBGQgJQkPLY-OKfgy0Y?key=MTJBa2pRUl9VU2lmMXdEZGxYX3ZiSDRSTjJxWjdn

  I couldn't record screen because apparently the hotkeys were also
  intercepted and I couldn't save the video.

  It makes programming right now super dangerous, as if you press the
  'win' button then it's basically 'adios'.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15.3
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 28 18:00:54 2019
  InstallationDate: Installed on 2018-11-09 (383 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to eoan on 2019-11-27 (0 days ago)
  VarLogDistupgradeTermlog:

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

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

[Desktop-packages] [Bug 1855065] [NEW] Thumbnail graphics of open file dialogue are impossibly tiny

[klfytklfyt]

Public bug reported:


It's unfortunately impossible to understand what you see
due to the small size of thumbnail graphics. I would
make them at least 4 times larger.

:))

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

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

Title:
  Thumbnail graphics of open file dialogue are impossibly tiny

Status in nautilus package in Ubuntu:
  New

Bug description:
  
  It's unfortunately impossible to understand what you see
  due to the small size of thumbnail graphics. I would
  make them at least 4 times larger.

  :))

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

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

[Desktop-packages] [Bug 1853961] Re: Nautilus segfaults while transferring files via SFTP

[Bug Watch Updater]

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

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

Title:
  Nautilus segfaults while transferring files via SFTP

Status in gvfs:
  New
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  Every time I try to transfer a large file (or several small files) via
  Nautilus/SFTP, it ends up failing after a minute or so (connection
  closed).

  For example, I tried the same transfer twice, and got the following
  log:

  [505587.786931] gvfsd-sftp[23481]: segfault at 1 ip 0001 sp 
7ffe3e316a58 error 14 in gvfsd-sftp[559f94955000+6000]
  [505587.786958] Code: Bad RIP value.
  [505856.692209] gvfsd-sftp[23767]: segfault at 559d000a ip 
7fa35323bc04 sp 7ffc3f4d7d90 error 4 in 
libc-2.30.so[7fa3531c8000+178000]
  [505856.692233] Code: c9 0f 11 4b 20 48 89 ee 66 48 0f 6e c0 48 83 ce 01 0f 
16 44 24 08 48 89 73 08 0f 11 43 10 49 89 2c 24 48 85 d2 74 8f 48 89 d3 <48> 8b 
43 08 89 c2 c1 ea 04 83 ea 02 49 8d 54 d7 10 49 39 d5 0f 85

  If I try the same transfer using Filezilla, it completes flawlessly.
  Also, before Ubuntu 19.10 / Nautilus 3.34, I didn't have any problems
  with the same server either.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Nov 26 07:48:38 2019
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'209'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 538)'
  InstallationDate: Installed on 2018-05-14 (560 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (38 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1854439] Re: gnome-control-center won't open even after reinstalling

[Sebastien Bacher]

Can you try to obtain a backtrace following the instructions at 
http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an 
attachment) to the bug report?
Also can you include a 'journalctl -b 0' log after getting the issue?

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

Title:
  gnome-control-center won't open even after reinstalling

Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  When I try to open the cursor is just spinning and it won't open.
  When i tried to open in terminal i got this:
  $ sudo gnome-control-center
  **
  ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: 
assertion failed: (valid)
  Bail out! 
ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: 
assertion failed: (valid)
  Aborted

  Someone help me..
  thanks in advance

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

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

[Desktop-packages] [Bug 1855065] Re: Thumbnail graphics of open file dialogue are impossibly tiny

[Sebastien Bacher]

The bug report lacks basic details like the scree resolution, the Ubuntu
version used or the desktop environment. Can you make a screenshot
showing the problem?

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

Title:
  Thumbnail graphics of open file dialogue are impossibly tiny

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  
  It's unfortunately impossible to understand what you see
  due to the small size of thumbnail graphics. I would
  make them at least 4 times larger.

  :))

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

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

[Desktop-packages] [Bug 1836462] Re: Renaming Templates to # Templates fixes speed issues present in wide range of desktop applications

[klfytklfyt]

** Changed in: xdg-user-dirs (Ubuntu)
   Status: Incomplete => New

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

Title:
  Renaming Templates to # Templates fixes speed issues present in wide
  range of desktop applications

Status in xdg-user-dirs package in Ubuntu:
  New
Status in xdg-user-dirs package in Fedora:
  Unknown

Bug description:
  
  Renaming "Templates" to "# Templates" fixes a lot of speed issues
  in a range of desktop applications, e.g.
  file managers, text editors, etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1836462/+subscriptions

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

[Desktop-packages] [Bug 1855065] Re: Thumbnail graphics of open file dialogue are impossibly tiny

[Sebastien Bacher]

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

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

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

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

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

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

Title:
  Thumbnail graphics of open file dialogue are impossibly tiny

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  
  It's unfortunately impossible to understand what you see
  due to the small size of thumbnail graphics. I would
  make them at least 4 times larger.

  :))

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

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

[Desktop-packages] [Bug 1515539] Re: letters stop being displayed

[Daniel van Vugt]

** Tags removed: wily

** Changed in: xorg-server
   Importance: High => Unknown

** Changed in: xorg-server
 Remote watch: freedesktop.org Bugzilla #88584 => 
gitlab.freedesktop.org/xorg/driver/xf86-video-intel/issues #41

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

Title:
  letters stop being displayed

Status in X.Org X server:
  Unknown
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  From time to time, some letters are just not displayer anymore. Only a
  restart will fix the problem temporarily. See the Screenshots that I
  attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nautilus 1:3.14.2-0ubuntu12
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov 12 10:59:44 2015
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2015-08-13 (90 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to wily on 2015-10-27 (15 days ago)

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

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

[Desktop-packages] [Bug 1839716] Re: There is infinite loop in address bar

[klfytklfyt]

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

** Also affects: chromium-browser
   Importance: Undecided
   Status: New

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

Title:
  There is infinite loop in address bar

Status in Chromium Browser:
  New
Status in chromium-browser package in Ubuntu:
  Invalid
Status in chromium package in Fedora:
  Invalid

Bug description:
  There seems to be infinite loop in the address bar
  if you fill it with letter f

  
https://bugs.launchpad.net/ubuntu/+source/nautilus/+filebug

  then scrolling and page loading becomes faster.

  :))

  
  two spaces
  https://bugzilla.redhat.com/show_bug.cgi?id=1754300#c5

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

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

[Desktop-packages] [Bug 1672822] Re: sound only coming from left speaker on acer predator (fresh install)

[Daniel van Vugt]

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

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

Title:
  sound only coming from left speaker on acer predator (fresh install)

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu version: Ubuntu  16.10 and a fresh install of 17.04 and even
  fedora F25-WORK-x86_64-20170228 via live usb

  Device: acer predator: G9-593-7757 15,6"/i7-7700/32 GB RAM/512 GB
  SSD/1 TB HDD/GTX1070

  expected: sound comes out of both left and right speaker and the
  subwoofer

  what happened instead:
  Sound only comes out of the left speaker or subwoofer.

  More system information:

  $ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0

  audio chip (on motherboard): VGA Chip nVidia N17E-G2-A1 GP104-725-A1

  note that that is only 1 device, one would expect several here.

  I attempted to fix this by modifying the /etc/pulse/deamon.conf into the 
following:
  # This file is part of PulseAudio.
  #
  # PulseAudio is free software; you can redistribute it and/or modify
  # it under the terms of the GNU Lesser General Public License as published by
  # the Free Software Foundation; either version 2 of the License, or
  # (at your option) any later version.
  #
  # PulseAudio is distributed in the hope that it will be useful, but
  # WITHOUT ANY WARRANTY; without even the implied warranty of
  # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
  # General Public License for more details.
  #
  # You should have received a copy of the GNU Lesser General Public License
  # along with PulseAudio; if not, see .

  ## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
  ## more information. Default values are commented out.  Use either ; or # for
  ## commenting.

  ; daemonize = no
  ; fail = yes
  ; allow-module-loading = yes
  ; allow-exit = yes
  ; use-pid-file = yes
  ; system-instance = no
  ; local-server-type = user
  ; enable-shm = yes
  ; enable-memfd = yes
  ; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
  ; lock-memory = no
  ; cpu-limit = no

  ; high-priority = yes
  ; nice-level = -11

  ; realtime-scheduling = yes
  ; realtime-priority = 5

  ; exit-idle-time = 20
  ; scache-idle-time = 20

  ; dl-search-path = (depends on architecture)

  ; load-default-script-file = yes
  ; default-script-file = /etc/pulse/default.pa

  ; log-target = auto
  ; log-level = notice
  ; log-meta = no
  ; log-time = no
  ; log-backtrace = 0

  ; resample-method = speex-float-1
  ; enable-remixing = yes
   enable-lfe-remixing = yes
  ; lfe-crossover-freq = 0

  flat-volumes = no

  ; rlimit-fsize = -1
  ; rlimit-data = -1
  ; rlimit-stack = -1
  ; rlimit-core = -1
  ; rlimit-as = -1
  ; rlimit-rss = -1
  ; rlimit-nproc = -1
  ; rlimit-nofile = 256
  ; rlimit-memlock = -1
  ; rlimit-locks = -1
  ; rlimit-sigpending = -1
  ; rlimit-msgqueue = -1
  ; rlimit-nice = 31
  ; rlimit-rtprio = 9
  ; rlimit-rttime = 20

  ; default-sample-format = s16le
  ; default-sample-rate = 44100
  ; alternate-sample-rate = 48000
  default-sample-channels = 3
  default-channel-map = front-left,front-right,lfe

  ; default-fragments = 4
  ; default-fragment-size-msec = 25

  ; enable-deferred-volume = yes
  deferred-volume-safety-margin-usec = 1
  ; deferred-volume-extra-delay-usec = 0

  but this did not work. I also tried various other permutations to see
  if changing the order of  front-left,front-right,lfe would work but it
  did not. I also tried to see if it would work in fedora but the same
  problem occurred there. When on ubuntu 16.10 at first only the
  subwoofer seemed to be working and altering the file only the left
  speaker was working. On ubuntu 17.04 only the left speaker was working
  regardless of how I altered the above file.

  
  Note that the speakers work perfectly fine on windows 10. 

  Looking around online there seem to be a lot of problems with acer
  predator laptops and sound on ubuntu.

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

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

[Desktop-packages] [Bug 921321]

[Martin-peres-n]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/20.

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

Title:
  nouveau: dark screen after suspend/resume

Status in Nouveau Xorg driver:
  Unknown
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  Nouveau works fine with brightness controls working fine after initial
  boot, but I do S3 suspend, and then resume via power button, and
  brightness controls don't work at all, and backlight is on, but set at
  extremely low level.

  hardware is Quadro 770M on HP 8530w laptop

  /sys/.../brightness control does nothing when in this state,
  suspend resume cycles after this first cycle all have the same problem.

  I'll test if a full hibernate has the issue or not after this and
  report back.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: xorg 1:7.6+7ubuntu7
  Uname: Linux 3.3.0-rc1+ x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,move,compiztoolbox,grid,vpswitch,gnomecompat,place,session,snap,mousepoll,regex,resize,imgpng,unitymtgrabhandles,wall,animation,workarounds,expo,fade,ezoom,scale,unityshell]
  CompositorRunning: None
  Date: Tue Jan 24 15:57:58 2012
  DistUpgraded: Log time: 2011-10-20 21:20:49.957387
  DistroCodename: oneiric
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GraphicsCard:
   nVidia Corporation G96M [Quadro FX 770M] [10de:065c] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:30e7]
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  MachineType: Hewlett-Packard HP EliteBook 8530w
  PccardctlIdent:
   Socket 0:
 product info: "RICOH", "Bay8Controller", "", ""
 manfid: 0x, 0x
 function: 254 (unknown)
  PccardctlStatus:
   Socket 0:
 3.3V 16-bit PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.3.0-rc1+ 
root=UUID=824346e6-fd2f-4916-a2c9-e883c1fe860c ro splash quiet vga=771 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to oneiric on 2011-10-21 (95 days ago)
  Xrandr: Screen 0: minimum 0 x 0, current 3200 x 1200, maximum 4096 x 4096
  dmi.bios.date: 12/13/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PDV Ver. F.13
  dmi.board.name: 30E7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 90.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PDVVer.F.13:bd12/13/2010:svnHewlett-Packard:pnHPEliteBook8530w:pvrF.13:rvnHewlett-Packard:rn30E7:rvrKBCVersion90.27:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8530w
  dmi.product.version: F.13
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu6
  version.ia32-libs: ia32-libs 20090808ubuntu26
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
  version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20110811.g93fc084-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.15.901-1ubuntu2.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110411+8378443-1

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

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

[Desktop-packages] [Bug 1111884]

[Martin-peres-n]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/50.

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

Title:
  10de:0611 nouveau fails at suspend/resume - PAGE_NOT_PRESENT

Status in Linux:
  Invalid
Status in Nouveau Xorg driver:
  Unknown
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Triaged

Bug description:
  Happens when resuming from standby. Can be reproduced. Every time.

  nouveau E[ PFB][:05:00.0] trapped read at 0x002001a020 on channel 
0x0001fae9 SEMAPHORE_BG/PFIFO_READ/00 reason: PAGE_NOT_PRESENT
  nouveau E[ PFB][:05:00.0] trapped write at 0x002001a020 on channel 
0x0001fae9 PFIFO/PFIFO_READ/SEMAPHORE reason: PAGE_NOT_PRESENT
  nouveau E[  PGRAPH][:05:00.0] TRAP_TPDMA_2D - TP 0 - Unknown fault at 
address 00449b
  nouveau E[  PGRAPH][:05:00.0] TRAP_TPDMA_2D - TP 0 - e0c: , e18: 
, e1c: , e20: 0011, e24: 0c03
  nouveau E[  PGRAPH][:05:00.0]  TRAP
  nouveau E[  PGRAPH][:05:00.0] ch 2 [0x001fae9000] subc 2 class 0x502d 
mthd 0x060c data 0x04b0
  nouveau E[ PFB][:05:00.0] trapped write at 0x00449b on channel 
0x0001fae9 PGRAPH/PROP/DST2D reason: PAGE_NOT_PRESENT
  nouveau E[  PGRAPH][:05:00.0] magic set 0:
  nouveau E[  PGRAPH][:05:00.0] 0x00408904: 0x20087701
  nouveau E[  PGRAPH][:05:00.0] 0x00408908: 0x00449b00
  nouveau E[  PGRAPH][:05:00.0] 0x0040890c: 0x8432
  nouveau E[  PGRAPH][:05:00.0] 0x00408910: 0x9b00
  nouveau E[  PGRAPH][:05:00.0] TRAP_TEXTURE - TP0: Unhandled ustatus 
0x0003
  nouveau E[  PGRAPH][:05:00.0]  TRAP

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-core 2:1.13.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4
  Uname: Linux 3.8.0-2-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.8-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CrashCounter: 1
  Date: Thu Jan 31 22:17:49 2013
  DistUpgraded: 2013-01-30 03:34:50,679 DEBUG enabling apt cron job
  DistroCodename: raring
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G92 [GeForce 8800 GT] [10de:0611] (rev a2) (prog-if 00 
[VGA controller])
     Subsystem: XFX Pine Group Inc. Device [1682:2330]
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp 
vt7 -novtswitch -background none
  ProcEnviron:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-2-generic 
root=UUID=615f02d8-8bf1-4c07-bf26-9f8b2230d6d6 ro pcie_aspm=force
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/xorg/modules/libexa.so
   ?? () from /usr/lib/xorg/modules/libexa.so
   ?? () from /usr/lib/xorg/modules/libexa.so
   ?? () from /usr/lib/xorg/modules/libexa.so
   ?? () from /usr/lib/xorg/modules/libexa.so
  Title: Xorg crashed with SIGABRT
  UpgradeStatus: Upgraded to raring on 2013-01-30 (1 days ago)
  UserGroups:

  dmi.bios.date: 12/24/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0806
  dmi.board.name: P5WD2-Premium
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0806:bd12/24/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WD2-Premium:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.9~daily13.01.25-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.41-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.19-0ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu2
  xserver.bootTime: Thu Jan 31 22:30:57 2013
  xserver

[Desktop-packages] [Bug 921321] Re: nouveau: dark screen after suspend/resume

[Bug Watch Updater]

** Changed in: nouveau
   Status: Incomplete => Unknown

** Bug watch added: 
gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues #20
   https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/20

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

Title:
  nouveau: dark screen after suspend/resume

Status in Nouveau Xorg driver:
  Unknown
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  Nouveau works fine with brightness controls working fine after initial
  boot, but I do S3 suspend, and then resume via power button, and
  brightness controls don't work at all, and backlight is on, but set at
  extremely low level.

  hardware is Quadro 770M on HP 8530w laptop

  /sys/.../brightness control does nothing when in this state,
  suspend resume cycles after this first cycle all have the same problem.

  I'll test if a full hibernate has the issue or not after this and
  report back.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: xorg 1:7.6+7ubuntu7
  Uname: Linux 3.3.0-rc1+ x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,move,compiztoolbox,grid,vpswitch,gnomecompat,place,session,snap,mousepoll,regex,resize,imgpng,unitymtgrabhandles,wall,animation,workarounds,expo,fade,ezoom,scale,unityshell]
  CompositorRunning: None
  Date: Tue Jan 24 15:57:58 2012
  DistUpgraded: Log time: 2011-10-20 21:20:49.957387
  DistroCodename: oneiric
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GraphicsCard:
   nVidia Corporation G96M [Quadro FX 770M] [10de:065c] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:30e7]
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  MachineType: Hewlett-Packard HP EliteBook 8530w
  PccardctlIdent:
   Socket 0:
 product info: "RICOH", "Bay8Controller", "", ""
 manfid: 0x, 0x
 function: 254 (unknown)
  PccardctlStatus:
   Socket 0:
 3.3V 16-bit PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.3.0-rc1+ 
root=UUID=824346e6-fd2f-4916-a2c9-e883c1fe860c ro splash quiet vga=771 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to oneiric on 2011-10-21 (95 days ago)
  Xrandr: Screen 0: minimum 0 x 0, current 3200 x 1200, maximum 4096 x 4096
  dmi.bios.date: 12/13/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PDV Ver. F.13
  dmi.board.name: 30E7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 90.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PDVVer.F.13:bd12/13/2010:svnHewlett-Packard:pnHPEliteBook8530w:pvrF.13:rvnHewlett-Packard:rn30E7:rvrKBCVersion90.27:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8530w
  dmi.product.version: F.13
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu6
  version.ia32-libs: ia32-libs 20090808ubuntu26
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
  version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20110811.g93fc084-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.15.901-1ubuntu2.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110411+8378443-1

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

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

[Desktop-packages] [Bug 1111884] Re: 10de:0611 nouveau fails at suspend/resume - PAGE_NOT_PRESENT

[Bug Watch Updater]

** Changed in: nouveau
   Status: Confirmed => Unknown

** Bug watch added: 
gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues #50
   https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/50

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

Title:
  10de:0611 nouveau fails at suspend/resume - PAGE_NOT_PRESENT

Status in Linux:
  Invalid
Status in Nouveau Xorg driver:
  Unknown
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Triaged

Bug description:
  Happens when resuming from standby. Can be reproduced. Every time.

  nouveau E[ PFB][:05:00.0] trapped read at 0x002001a020 on channel 
0x0001fae9 SEMAPHORE_BG/PFIFO_READ/00 reason: PAGE_NOT_PRESENT
  nouveau E[ PFB][:05:00.0] trapped write at 0x002001a020 on channel 
0x0001fae9 PFIFO/PFIFO_READ/SEMAPHORE reason: PAGE_NOT_PRESENT
  nouveau E[  PGRAPH][:05:00.0] TRAP_TPDMA_2D - TP 0 - Unknown fault at 
address 00449b
  nouveau E[  PGRAPH][:05:00.0] TRAP_TPDMA_2D - TP 0 - e0c: , e18: 
, e1c: , e20: 0011, e24: 0c03
  nouveau E[  PGRAPH][:05:00.0]  TRAP
  nouveau E[  PGRAPH][:05:00.0] ch 2 [0x001fae9000] subc 2 class 0x502d 
mthd 0x060c data 0x04b0
  nouveau E[ PFB][:05:00.0] trapped write at 0x00449b on channel 
0x0001fae9 PGRAPH/PROP/DST2D reason: PAGE_NOT_PRESENT
  nouveau E[  PGRAPH][:05:00.0] magic set 0:
  nouveau E[  PGRAPH][:05:00.0] 0x00408904: 0x20087701
  nouveau E[  PGRAPH][:05:00.0] 0x00408908: 0x00449b00
  nouveau E[  PGRAPH][:05:00.0] 0x0040890c: 0x8432
  nouveau E[  PGRAPH][:05:00.0] 0x00408910: 0x9b00
  nouveau E[  PGRAPH][:05:00.0] TRAP_TEXTURE - TP0: Unhandled ustatus 
0x0003
  nouveau E[  PGRAPH][:05:00.0]  TRAP

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-core 2:1.13.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4
  Uname: Linux 3.8.0-2-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.8-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CrashCounter: 1
  Date: Thu Jan 31 22:17:49 2013
  DistUpgraded: 2013-01-30 03:34:50,679 DEBUG enabling apt cron job
  DistroCodename: raring
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G92 [GeForce 8800 GT] [10de:0611] (rev a2) (prog-if 00 
[VGA controller])
     Subsystem: XFX Pine Group Inc. Device [1682:2330]
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp 
vt7 -novtswitch -background none
  ProcEnviron:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-2-generic 
root=UUID=615f02d8-8bf1-4c07-bf26-9f8b2230d6d6 ro pcie_aspm=force
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/xorg/modules/libexa.so
   ?? () from /usr/lib/xorg/modules/libexa.so
   ?? () from /usr/lib/xorg/modules/libexa.so
   ?? () from /usr/lib/xorg/modules/libexa.so
   ?? () from /usr/lib/xorg/modules/libexa.so
  Title: Xorg crashed with SIGABRT
  UpgradeStatus: Upgraded to raring on 2013-01-30 (1 days ago)
  UserGroups:

  dmi.bios.date: 12/24/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0806
  dmi.board.name: P5WD2-Premium
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0806:bd12/24/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WD2-Premium:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.9~daily13.01.25-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.41-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.19-0ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu2
  xserver.bootTime: Thu Jan 31 22:30:57 2013
  xserver.configfile: /etc/X11/xorg.conf
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   

[Desktop-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

[r.fabb...@gmail.com]

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Triaged
Status in xserver-xorg-video-intel source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Triaged
Status in xserver-xorg-video-intel source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Triaged
Status in xserver-xorg-video-intel source package in Disco:
  Invalid

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm

[Daniel van Vugt]

** Tags added: eoan

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

Title:
  Can't lock screen with keyboard shortcuts when using lightdm

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen.
  Additionally, if I wait a very long time the screen does not lock
  either.

  Switching from LightDM to GDM3 fixes the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  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: GNOME
  Date: Wed Sep  6 09:17:35 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2016-01-22 (592 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1853571] Re: autopkgtests sometimes hang on armhf

[Olivier Tilloy]

This is not actually fixed, merely mitigated by the reduced timeout.

** Changed in: firefox (Ubuntu)
   Status: Fix Released => Triaged

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

Title:
  autopkgtests sometimes hang on armhf

Status in firefox package in Ubuntu:
  Triaged

Bug description:
  This has been most recently observed with firefox
  70.0.1+build1-0ubuntu2 on focal, but I believe this is not new, it has
  been observed in the past with older versions of firefox.

  I cannot reproduce the problem consistently, but I've observed it at
  least once in a test environment (focal/armhf lxd container running on
  a bionic/arm64 cloud instance), and it has happened quite a few times
  lately on the ubuntu autopkgtest infrastructure.

  The html5test hangs indefinitely, and only times out after more than 5
  hours (=2 seconds, which is the test timeout hardcoded in the
  infrastructure).

  When I reproduced the hang, this was the list of (relevant) running
  processes:

  root  5554  5545  0 05:55 ?00:00:02 /usr/bin/python3 
/tmp/autopkgtest.xdq8Z8/build.Zik/real-tree/debian/tests/html5test
  root  5561  5554  0 05:55 ?00:00:00 geckodriver --port 42963
  root  5569  5561  0 05:55 ?00:00:17 /usr/lib/firefox/firefox 
-marionette -headless -foreground -no-remote -profile /tmp/rust_mozprofileA720rs
  root  5611  5569  0 05:55 ?00:00:05 /usr/lib/firefox/firefox 
-contentproc -childID 1 -isForBrowser -prefsLen 1 -prefMapSize 198008 …
  root  5632  5569  0 05:55 ?00:00:14 /usr/lib/firefox/firefox 
-contentproc -childID 2 -isForBrowser -prefsLen 62 -prefMapSize 198008 …
  root  5676  5569  0 05:55 ?00:00:00 /usr/lib/firefox/firefox 
-contentproc -childID 3 -isForBrowser -prefsLen 8264 -prefMapSize 198008 …

  
  I straced them all and the geckodriver process is the one that appeared 
blocked:

  root@focal-armhf:~# strace -p 5561
  strace: Process 5561 attached
  futex(0xf7a79288, FUTEX_WAIT, 5562, NULL

  Here is the test output when it hangs:

  autopkgtest [07:14:56]: test firefox-version:  - - - - - - - - - - results - 
- - - - - - - - -
  firefox-version  PASS
  autopkgtest [07:14:59]: test html5test: preparing testbed
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Starting pkgProblemResolver with broken count: 0
  Starting 2 pkgProblemResolver with broken count: 0
  Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up autopkgtest-satdep (0) ...
  (Reading database ... 59615 files and directories currently installed.)
  Removing autopkgtest-satdep (0) ...
  autopkgtest [07:15:29]: test html5test: [---
  127.0.0.1 - - [22/Nov/2019 07:15:45] "GET / HTTP/1.1" 200 -
  127.0.0.1 - - [22/Nov/2019 07:15:47] "GET /css/main.css HTTP/1.1" 200 -
  127.0.0.1 - - [22/Nov/2019 07:15:47] "GET /scripts/base.js HTTP/1.1" 200 -
  127.0.0.1 - - [22/Nov/2019 07:15:47] "GET /scripts/8/engine.js HTTP/1.1" 200 -
  127.0.0.1 - - [22/Nov/2019 07:15:47] "GET /scripts/8/data.js HTTP/1.1" 200 -
  127.0.0.1 - - [22/Nov/2019 07:15:52] "GET /images/html5.png HTTP/1.1" 200 -
  127.0.0.1 - - [22/Nov/2019 07:15:53] "GET /images/sponsors/cloudvps.png 
HTTP/1.1" 200 -
  127.0.0.1 - - [22/Nov/2019 07:15:53] "GET /fonts/html5test.woff HTTP/1.1" 200 
-
  127.0.0.1 - - [22/Nov/2019 07:15:53] "GET 
/fonts/leaguegothic-regular-webfont.woff HTTP/1.1" 200 -
  127.0.0.1 - - [22/Nov/2019 07:15:53] "GET /assets/detect.html?twt5r HTTP/1.1" 
200 -
  127.0.0.1 - - [22/Nov/2019 07:15:53] "GET /assets/detect.html?k44ge HTTP/1.1" 
200 -
  127.0.0.1 - - [22/Nov/2019 07:15:53] "GET /assets/detect.html?flslr HTTP/1.1" 
200 -
  127.0.0.1 - - [22/Nov/2019 07:15:53] "GET /assets/detect.html?2l0zy HTTP/1.1" 
200 -
  127.0.0.1 - - [22/Nov/2019 07:15:53] "GET /images/icons/favicon-196x196.png 
HTTP/1.1" 200 -
  127.0.0.1 - - [22/Nov/2019 07:15:53] "GET /images/icons/favicon-16x16.png 
HTTP/1.1" 200 -

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

-- 
Mailing list: https://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 1850651] Autopkgtest regression report (thunderbird/1:60.9.1+build1-0ubuntu0.19.04.1)

[Gyula]

Befaore I got your messages I reinstalled the thunderbird in synaptic. 
Interesting reinstalled because the synapric wrote that the newest was 
installed. But after reinstalled I have the newest version and it's 
working. But in Software center stay the old version if I searching.

2019. 12. 04. 2:55 keltezéssel, Ubuntu SRU Bot írta:
> All autopkgtests for the newly accepted thunderbird 
> (1:60.9.1+build1-0ubuntu0.19.04.1) for disco have finished running.
> The following regressions have been reported in tests triggered by the 
> package:
>
> enigmail/2:2.0.9+ds1-2 (i386, arm64, amd64, ppc64el, armhf)
>
>
> Please visit the excuses page listed below and investigate the failures, 
> proceeding afterwards as per the StableReleaseUpdates policy regarding 
> autopkgtest regressions [1].
>
> https://people.canonical.com/~ubuntu-archive/proposed-
> migration/disco/update_excuses.html#thunderbird
>
> [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
>
> Thank you!
>

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

Title:
  [SRU] Authentication constantly re-requested for Google

Status in Mozilla Thunderbird:
  Fix Released
Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Xenial:
  Fix Committed
Status in thunderbird source package in Bionic:
  Fix Committed
Status in thunderbird source package in Disco:
  Fix Committed
Status in thunderbird source package in Eoan:
  Fix Committed
Status in thunderbird source package in Focal:
  Fix Released

Bug description:
  [Impact]

  A recent server-side change with google e-mail accounts (gmail) means that 
thunderbird consistently fails to authenticate, prompting for the user's e-mail 
address and password over and over, without ever succeeding.
  This has been fixed upstream and is tracked by 
https://bugzilla.mozilla.org/show_bug.cgi?id=1592407.

  
  [Test Case]

  In a clean environment, launch thunderbird and add an existing gmail account.
  Thunderbird should auto-detect all the relevant parameters, and then an 
external webview should pop up to prompt for your e-mail address (it's not 
auto-filled, that's a separate issue that's also known upstream) and your 
password. After filling this in and authorizing thunderbird to access your 
e-mails, your account should be set up and thunderbird should start fetching 
e-mails from your inbox. Instead it fails to authenticate and displays the 
authentication pop up again.

  [Regression Potential]

  Low, as this is an official upstream point release that addresses only this 
regression (see 
https://www.thunderbird.net/en-US/thunderbird/60.9.1/releasenotes/).
  The fix is minimal and self-contained 
(https://hg.mozilla.org/releases/comm-esr60/rev/56b6d1b50647143c25efe642b37b02f65f9c4343),
 if the bug is indeed confirmed to be fixed then it should be safe.

  
  [Original Bug Description]

  When I use Thunderbird, it keeps failing to connect with my Google
  (Gmail) accounts. It keeps asking for authentication via the web
  portal, I seem to successfully give Thunderbird authentication, but no
  messages come in and, soon afterwards, the web portal comes up asking
  for login again.

  I am using OAuth2 (so this ( https://support.mozilla.org/en-
  US/questions/1201406 ) doesn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: thunderbird 1:60.9.0+build1-0ubuntu0.19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adam   3444 F pulseaudio
   /dev/snd/pcmC0D0p:   adam   3444 F...m pulseaudio
  BuildID: 20191007090404
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 30 14:56:50 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-08-03 (817 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600
   10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown
   169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown
   172.29.0.0/16 dev ztnfad2dd7 proto kernel scope link src 172.29.35.74
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.11 metric 600
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - 
/usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so 
(browser-plugin-freshplayer-pepperflash)
  PrefSources: pre

[Desktop-packages] [Bug 1731420] Re: gnome-shell hangs (goes into key repeat runaway) when key repeat is used on chromium-browser's address bar

[Daniel van Vugt]

This bug is closed because it was only known to affect 17.10. If you are
still affected then please open a new bug by running:

  ubuntu-bug gnome-shell

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

Title:
  gnome-shell hangs (goes into key repeat runaway) when key repeat is
  used on chromium-browser's address bar

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  GNOME Shell running in Wayland completely hangs when the key repeat
  rate is sufficiently high and used inside Chromium and/or Google
  Chrome. Then GNOME Shell, at-spi's dbus-daemon, ibus-daemon, and
  chromium-browser all get stuck at 100% CPU. GNOME Shell's RSS also
  quickly increases to >2GB and continues climbing.

  Attempting to kill chromium-browser in a separate TTY either causes one of 
two things:
   - gnome-shell, dbus-daemon and ibus-daemon remain at 100% CPU and stuck; or
   - gnome-shell temporarily recovers, then crashes, taking the entire session 
with it and returning to the login screen.

  
  Steps to reproduce:

  1. Set key repeat rates to a high value (these are my actual
  settings):

  $ gsettings set org.gnome.desktop.peripherals.keyboard repeat-interval 3
  $ gsettings set org.gnome.desktop.peripherals.keyboard repeat true
  $ gsettings set org.gnome.desktop.peripherals.keyboard delay 180

  2. Start chromium-browser
  3. Focus the location bar in chromium-browser
  4. Press and hold a key (e.g. a) for a few seconds (~10 should do)
  5. Observe that gnome-shell probably has hung by this point. If it hasn't, 
proceed to step 6.
  6. Press and hold the backspace button until the location bar has cleared, 
then continue for another few seconds (~10 seconds should do)

  
  This also affected GNOME Shell 3.24, but I was able to reduce the chances of 
it happening by renicing my chromium processes to +10, thereby giving GNOME 
Shell a greater chance at the CPU.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  Uname: Linux 4.13.4-hyper2+ x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov 10 16:50:13 2017
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-11-04 (5 days ago)

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

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

[Desktop-packages] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg

[Daniel van Vugt]

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

** Changed in: nvidia-graphics-drivers-430 (Ubuntu)
   Status: New => Confirmed

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

** Changed in: nvidia-graphics-drivers-435 (Ubuntu)
   Status: New => Confirmed

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

Title:
  nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external
  monitors detected by Xorg

Status in gdm3 package in Ubuntu:
  Opinion
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

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

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

[Desktop-packages] [Bug 1854534] Re: [radeon] Wayland sessions including the login screen are just static noise

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1775881
   [radeon] Wayland sessions including the login screen are just static noise

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

Title:
  [radeon] Wayland sessions including the login screen are just static
  noise

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Whenever I boot Ubuntu following installation from the official
  install ISO, the boot screen appears, but the login manager appears as
  static, scrambled graphics, making me unable to login without opening
  the VT and installing lightdm and switching to that login manager.

  Expected Results:
  Login manager appears with login field, background, and menu while I am able 
to find, click, and enter information into the login text fields.

  Actual Results:
  Scrambled noise appeared on my screen and I am unable to leave without 
force-shutting down my Gateway PC, or opening a VT and disabling Wayland via 
editing GDM's custom.conf file.

  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  xwayland:
Installed: 2:1.19.6-1ubuntu4.3
Candidate: 2:1.19.6-1ubuntu4.3
Version table:
   *** 2:1.19.6-1ubuntu4.3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2:1.19.6-1ubuntu4.2 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   2:1.19.6-1ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu4.3
  ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
  Uname: Linux 4.15.0-70-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  Date: Fri Nov 29 13:26:56 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 
OEM] [1682:3207]
  MachineType: Gateway DX4860
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic 
root=UUID=751019b9-8693-494c-ad69-17ddf9e51235 ro splash quiet vt.handoff=1
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/01/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02-A1
  dmi.board.name: IPISB-VR
  dmi.board.vendor: Gateway
  dmi.board.version: 1.01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr:
  dmi.product.family: Gateway Desktop
  dmi.product.name: DX4860
  dmi.sys.vendor: Gateway
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  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/1854534/+subscriptions

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

[Desktop-packages] [Bug 1732245] Re: [wayland] Fullscreen games offset after returning from alt-tab

[Bug Watch Updater]

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

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

Title:
  [wayland] Fullscreen games offset after returning from alt-tab

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Impact
  ==
  Using Alt-Tab to leave a fullscreen game and then return breaks the game by 
offsetting the display by the size of the GNOME Shell top bar (and the Ubuntu 
Dock if running).

  Test Case
  =
  1. Log into the default Ubuntu session. (Make sure that Wayland is running by 
running this command. If you have output, you are running Wayland.

  env | grep -i wayland

  2. Run a game full screen.

  I installed Steam and used Team Fortress 2 because it's free (but a
  very large download)

  3. Press Alt-Tab to switch to another window and then press Alt-Tab to
  switch back to the game.

  The game should display and function normally.

  Workaround
  ==
  Open the Activities Overview and click the game window instead of using 
Alt-Tab to switch back to the game.

  Other Info
  ==
  This bug is split from LP: #1725649 where the problem was seen and fixed for 
the Xorg session. This bug is for the Wayland sessions.

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

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

[Desktop-packages] [Bug 1766775] Re: Notifications do not disappear

[Daniel van Vugt]

** Tags added: eoan

** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/issues #240
   https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/240

** Project changed: gnome-shell => gnome-settings-daemon

** Changed in: gnome-settings-daemon
   Importance: Low => Unknown

** Changed in: gnome-settings-daemon
   Status: Incomplete => Unknown

** Changed in: gnome-settings-daemon
 Remote watch: GNOME Bug Tracker #721170 => 
gitlab.gnome.org/GNOME/gnome-settings-daemon/issues #240

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

Title:
  Notifications do not disappear

Status in GNOME Settings Daemon:
  Unknown
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I frequently have notifications that do not disappear after being
  shown.  This is particularly prevalent with power management
  notifications.  Most of the time when I wake my computer from suspend,
  I see the following notification at the top: "Automatic suspend -
  Computer will suspend very soon because of inactivity." that never
  goes away.  Presumably, this was shown before my computer went to
  sleep, and should have disappeared but didn't.  I have to either click
  on the notification, or click on the time to open the notification
  menu to get it to disappear.  Occasionally, the same behaviour occurs
  with other, random notifications.

  This is a long-standing issue for me, that I'm just now getting around
  to reporting.  I'm on 17.10, gnome-shell 3.26.2-0ubuntu0.1, and
  running the gnome-session (not Ubuntu).  I don't know if the issue is
  present on Gnome 3.28, but plan to find out once 18.04 final is
  released.

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

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

[Desktop-packages] [Bug 1732245] Re: [wayland] Fullscreen games offset after returning from alt-tab

[Daniel van Vugt]

** Bug watch added: bugzilla.gnome.org/ #786305
   https://bugzilla.gnome.org/show_bug.cgi?id=786305

** Changed in: mutter
   Importance: Low => Unknown

** Changed in: mutter
   Status: Confirmed => Unknown

** Changed in: mutter
 Remote watch: GNOME Bug Tracker #786305 => bugzilla.gnome.org/ #786305

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

** Changed in: mutter
 Remote watch: bugzilla.gnome.org/ #786305 => 
gitlab.gnome.org/GNOME/mutter/issues #397

** Tags removed: artful
** Tags added: eoan

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

Title:
  [wayland] Fullscreen games offset after returning from alt-tab

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Impact
  ==
  Using Alt-Tab to leave a fullscreen game and then return breaks the game by 
offsetting the display by the size of the GNOME Shell top bar (and the Ubuntu 
Dock if running).

  Test Case
  =
  1. Log into the default Ubuntu session. (Make sure that Wayland is running by 
running this command. If you have output, you are running Wayland.

  env | grep -i wayland

  2. Run a game full screen.

  I installed Steam and used Team Fortress 2 because it's free (but a
  very large download)

  3. Press Alt-Tab to switch to another window and then press Alt-Tab to
  switch back to the game.

  The game should display and function normally.

  Workaround
  ==
  Open the Activities Overview and click the game window instead of using 
Alt-Tab to switch back to the game.

  Other Info
  ==
  This bug is split from LP: #1725649 where the problem was seen and fixed for 
the Xorg session. This bug is for the Wayland sessions.

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

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

[Desktop-packages] [Bug 1854371] Re: Input lag with Razer Naga Trinity mouse

[Foulques]

It does not seem to be the same issue as
https://bugs.launchpad.net/bugs/1799679.

I can reproduce the bug with nouveau, so it should not be related to the
driver.

There is no need to launch any application to reproduce it, it works
from the desktop. I originally discovered this bug while playing a game
though.

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

Title:
  Input lag with Razer Naga Trinity mouse

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  When pressing multiple keys on my keyboard (Roccat isku FX) and pressing 
repetitively the buttons on the "numpad" (side buttons) of my mouse (Razer Naga 
Trinity) at the same time, the system freeze while doing this. All become 
normal again when I stop doing this.
  While freezing, I can see the Xorg process going up to 60/70% of the CPU.

  Not sure if it is a Xorg or driver related problem, or anything else.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/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 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 28 15:25:50 2019
  DistUpgraded: 2019-10-25 11:21:07,314 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.3.0-22-generic, x86_64: installed
   nvidia, 435.21, 5.3.0-23-generic, x86_64: installed
   openrazer-driver, 2.6.0, 5.3.0-23-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-22-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GM206 [GeForce GTX 960] 
[19da:1385]
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=eabe8e30-c27a-4b40-8af2-38ffd8bcbcc9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-10-25 (34 days ago)
  dmi.bios.date: 02/28/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1801:bd02/28/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  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.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  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/xorg-server/+bug/1854371/+subscriptions

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

[Desktop-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation

[Daniel van Vugt]

This bug is closed, rightly or wrongly. So if you continue to experience
any problems then you will need to open a new bug by running:

  ubuntu-bug mutter

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

Title:
  [nvidia] Corrupted wallpaper after resuming from suspend or
  hibernation

Status in GNOME Shell:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Disco:
  Won't Fix
Status in mutter source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  The Nvidia (Xorg) driver corrupts the desktop wallpaper (by design
  (1)) upon resuming from suspend. This creates a poor user experience
  and gives the impression of severe memory corruption.

  (1)
  
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt

  [Test Case]

  0. Set up an Nvidia-only system using the proprietary Nvidia Xorg driver.
  1. Suspend and resume the machine.
  Expect: The wallpaper still looks like it did before suspending.

  [Regression Potential]

  Low. The exact same patch is in Gnome 3.34 (Ubuntu 19.10) already and
  has been used for a couple of months without issue.

  [Original Report]

  https://trello.com/c/i5hENxSO

  Every other wake from sleep presents a corrupted screen with no unlock
  app.  There's a dock and system menu on a black background with pixel
  garbage.  Some personal information in the dock's large window
  thumbnails.  Bitmap garbage flashes on the screen when interacting
  with anything.  Only workaround is doing another sleep-wake cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:4b:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.1
  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: Thu Dec 20 22:19:29 2018
  DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-11-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-12-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162]
  InstallationDate: Installed on 2018-10-28 (54 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic 
root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F24
  dmi.board.asset.tag: Default string
  dmi.board.name: X99P-SLI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  ver

[Desktop-packages] [Bug 1847639] Re: Podcast can't resume play once it was paused

[Paul White]

Hi Rob, I'm not seeing that problem here.

Can you let us know which podcast you are having a problem with? Please
also run

apport-collect 1847639

in a terminal to add debugging information to the bug report, thanks.


** Tags added: eoan

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

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

Title:
  Podcast can't resume play once it was paused

Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  I just installed a fresh Ubuntu 19.10 and added a Podcast. I
  downloaded an episode and pressed play. The podcast did not started to
  play. The timecode "jumps" to 00:00:00 but it simply does not start.
  When I pressed the pause button, it stopped, but once I pressed the
  play button again, it did not resume either. I tried this various
  times, it does not matter if the episode is downloaded or streamed.
  Overall system sound works just fine out of the box.

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

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

[Desktop-packages] [Bug 1854371] Re: Input lag with Razer Naga Trinity mouse

[Daniel van Vugt]

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

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

Title:
  Input lag with Razer Naga Trinity mouse

Status in xorg-server package in Ubuntu:
  New

Bug description:
  When pressing multiple keys on my keyboard (Roccat isku FX) and pressing 
repetitively the buttons on the "numpad" (side buttons) of my mouse (Razer Naga 
Trinity) at the same time, the system freeze while doing this. All become 
normal again when I stop doing this.
  While freezing, I can see the Xorg process going up to 60/70% of the CPU.

  Not sure if it is a Xorg or driver related problem, or anything else.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/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 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 28 15:25:50 2019
  DistUpgraded: 2019-10-25 11:21:07,314 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.3.0-22-generic, x86_64: installed
   nvidia, 435.21, 5.3.0-23-generic, x86_64: installed
   openrazer-driver, 2.6.0, 5.3.0-23-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-22-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GM206 [GeForce GTX 960] 
[19da:1385]
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=eabe8e30-c27a-4b40-8af2-38ffd8bcbcc9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-10-25 (34 days ago)
  dmi.bios.date: 02/28/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1801:bd02/28/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  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.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  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/xorg-server/+bug/1854371/+subscriptions

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

[Desktop-packages] [Bug 1825626] Re: nvLock: client timed out, taking the lock

[Daniel van Vugt]

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

** Changed in: nvidia-graphics-drivers-430 (Ubuntu)
   Status: New => Confirmed

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

Title:
  nvLock: client timed out, taking the lock

Status in gnome-desktop:
  New
Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed

Bug description:
  While launching an app or performing an operation, the screen has a
  certain chance to freeze for a few seconds and then recover.

  [ System Info ]
  Version : Ubuntu 19.04
  Kernel : x86_64 Linux 5.0.0-13-generic
  GPU : NVIDIA GeForce GTX 1050
  Xorg version : 1:7.7+19ubuntu12
  Product Name : Aspire VX5-591G (Acer)

  [ Log File ]
  Uploaded as an attachment

  *Sorry for my not-good English.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 17:19:29 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
   virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127]
 Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:1128]
  MachineType: Acer Aspire VX5-591G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Wish_KLS
  dmi.board.vendor: KBL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.06
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06:
  dmi.product.family: Aspire VX 15
  dmi.product.name: Aspire VX5-591G
  dmi.product.sku: 
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  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.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1825842] Re: [vmware] Background goes white when using scaling (200%, 300% or 400%)

[Daniel van Vugt]

** Tags added: eoan

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

Title:
  [vmware] Background goes white when using scaling (200%, 300% or 400%)

Status in mutter package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-vmware package in Ubuntu:
  Confirmed

Bug description:
  As soon as I set my display to scaled (any percentage) via Settings ->
  Displays -> Scale, the background image disappears and become all
  white. When I choose a different background image via Settings ->
  Background initially nothing happens. As soon as I switch back to 100%
  scaling, the image I choose before now appears.

  This problem started right after updating to 19.04. No such issues
  with either 18.04 or 18.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 22 15:35:49 2019
  DistUpgraded: 2019-04-21 17:34:15,063 DEBUG icon theme changed, re-reading
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2019-03-01 (51 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: VMware, Inc. VMware Virtual Platform
  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.0.0-13-generic 
root=UUID=c8dc93a3-fd95-4152-9c04-0211309b2dc7 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-21 (0 days ago)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1850702] Re: [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is faint and distorted (but works fine in Windows)

[Daniel van Vugt]

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

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

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

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9

[Desktop-packages] [Bug 78524] Re: Podcast download mechanism isn't robust enough and often fails

[Paul White]

The upstream report has moved to:
https://gitlab.gnome.org/GNOME/rhythmbox/issues/301
but has seen no activity

Is this still an issue or have the updates to rhythmbox over the years
rendered this bug report obsolete as the problem has been fixed?


** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/issues #301
   https://gitlab.gnome.org/GNOME/rhythmbox/issues/301

** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/issues #301
   https://gitlab.gnome.org/GNOME/rhythmbox/issues/301

** Changed in: rhythmbox
   Importance: Medium => Unknown

** Changed in: rhythmbox
   Status: Expired => Unknown

** Changed in: rhythmbox
 Remote watch: GNOME Bug Tracker #395733 => 
gitlab.gnome.org/GNOME/rhythmbox/issues #301

** Changed in: rhythmbox (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  Podcast download mechanism isn't robust enough and often fails

Status in Rhythmbox:
  Unknown
Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: rhythmbox

  I have subscribed to a few radio podcasts in RB.
  I have broadband so it's fast, and it used to work just fine, however, in the 
past couple of months, the quality of my internet connection (blame crappy ISP 
here!) has decreased significantly (takes ages to connect to a server, transfer 
speed is highly unstable, and sometimes plain stops, then resumes when it feels 
like it, a second later, or a minute... depends on the mood and server !).
  This revealed a serious weakness/problem in RB: 99% of the time, RB fails to 
download the podcasts ! Most of the time it just says "Waiting", and sometimes 
it downloads 5% of the file then sits there forever and won't move an inch even 
if I let it run for 3 days.
  Thing is, if I try to download these podcasts in a terminal, using the "wget" 
command, it works just fine, and in the worse case, it takes 3 minutes to grab 
an episode and that's it.
  That's why I think the problem lies within RB...
  I suspect that the problem might be that RB times out way too easily, and 
most importantly, when it does time out, it gives up for good, and won't insist.
  So the solution is probably to do as wget likely does (from what I can see) : 
increase the time out greatly when connecting initially to the server. Say a 2 
minute time out, not less. 
  Then once it starts downloading the file, and in the event that transfer 
speed drops to zero : DO NOT time out, and just patiently wait for transfer to 
resume.

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

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

[Desktop-packages] [Bug 1832426] Re: "Program" is not responding when debugging in gdb

[Daniel van Vugt]

** Tags added: eoan

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

Title:
  "Program" is not responding when debugging in gdb

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I believe this is a regression for ​​bug 1740869:
   is not responding window is constantly showing when debugging a 
program

  I'm debugging my c++ sdl2 program in gdb and when I hit a breakpoint
  this window shows up and I can't get it to stop asking me to close the
  program.

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

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  gnome-shell:
    Installed: 3.32.1-1ubuntu1~19.04.1
    Candidate: 3.32.1-1ubuntu1~19.04.1
    Version table:
   *** 3.32.1-1ubuntu1~19.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu disco-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.32.0+git20190410-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages

  3) What you expected to happen
  When I hit a breakpoint in gdb, the program should stop.

  4) What happened instead
  The program stops and ubuntu asks me if i want to kill the program.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 11 22:03:44 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-08 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1834967] Re: Windows in Activities might be partially off screen

[Daniel van Vugt]

The upstream bug report (https://gitlab.gnome.org/GNOME/gnome-
shell/issues/1826) suggests this is not a gnome-shell bug. So to avoid
confusing people with a spurious "Fix Released" I will just remove the
task.

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

** No longer affects: gnome-shell

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

Title:
  Windows in Activities might be partially off screen

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

Bug description:
  Details in my screenshot: https://photos.app.goo.gl/BR6H56eug7JFMGU37

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  1 20:38:43 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (0 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 265143] Re: Seeking using the mouse wheel or right cursor causes song to restart sometimes

[Paul White]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner.

The upstream report has moved to:
https://gitlab.gnome.org/GNOME/rhythmbox/issues/660
but has seen no activity

If this is still an issue using a maintained version of Ubuntu please
let us know otherwise this report can be left to expire in approximately
60 days time.

Paul White
[Ubuntu Bug Squad]

** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/issues #660
   https://gitlab.gnome.org/GNOME/rhythmbox/issues/660

** Changed in: rhythmbox
   Importance: Medium => Unknown

** Changed in: rhythmbox
   Status: Expired => Unknown

** Changed in: rhythmbox
 Remote watch: GNOME Bug Tracker #560813 => 
gitlab.gnome.org/GNOME/rhythmbox/issues #660

** Changed in: rhythmbox (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  Seeking using the mouse wheel or right cursor causes song to restart
  sometimes

Status in Rhythmbox:
  Unknown
Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: rhythmbox

  When moving the "seek" bar in Rhythmbox to go forward in the song
  using the right cursor keys or the mouse wheel, sometimes the slider
  is positioned at the beginning of the bar.

  This is very easy to reproduce for me, no matter what file format I'm
  playing or what backend I'm using (I've tested with Pulseaudio and
  ALSA): play a few seconds of the song, and then press *and hold* the
  right cursor key. After a few forward "skips", the slider will return
  to the beginning of the bar, will advance a little and will return
  again. I can do this forever withouth the slider ever getting to the
  end of the bar.

  With the mouse, after a few rotations of the mouse wheel the slider
  goes back to the beginning.

  If I allow a few seconds between cursor key presses or mouse wheel
  rotations, everything works fine.

  To resume, "What I expected to happen":

  I expect that the slider goes to the right if I press the right cursor
  or move the mouse wheel.

  "What happened instead":

  The slider went back to the beginning (left) of the seek bar.

  I'm using Ubuntu Hardy with Rhythmbox 0.11.5

  Raúl

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

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

[Desktop-packages] [Bug 328008] Re: Rhythmbox overloads memory with Jamendo

[Paul White]

Upstream report was closed "RESOLVED OBSOLETE" on 2012-03-28
stating "We now use the jamendo search API via grilo, so this is not an issue 
any more."
This bug report was specifically about the Jamendo plgin so is no longer valid

** Changed in: rhythmbox (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  Rhythmbox overloads memory with Jamendo

Status in Rhythmbox:
  Expired
Status in rhythmbox package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: rhythmbox

  Step to Reproduce the bug:

  1- Open Rhythmbox
  2- Open Jamendo Store
  3- Wait until it finishes loading (from there memory loads goes up)
  4- 0 artist to show (something missing in the script?)
  5- unable to browse Jamendo Store

  ~

  I used it in Hardy, "stock" install (i386), Worked Fine,
  Switched to Intrepid, "stock" install (amd64), doesn't work anymore...

  
  ~
  System:
  Ubuntu 8.10 Intrepid, 
  Rhythmbox v.0.11.6svn20081008

  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 8.10
  ExecutablePath: /usr/bin/rhythmbox
  NonfreeKernelModules: fglrx
  Package: rhythmbox 0.11.6svn20081008-0ubuntu4.2
  ProcEnviron:
   SHELL=/bin/bash
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_CA.UTF-8
  SourcePackage: rhythmbox
  Uname: Linux 2.6.27-11-generic x86_64

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

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

[Desktop-packages] [Bug 1221954] Re: Rythmbox: Poor Grammar: 80s and 90s under radio

[Paul White]

Upstream report was closed "RESOLVED OBSOLETE" on 2014-03-28
stating "These streams are no longer in the default list."
Confirmed to be the case with rhythmbox 3.4.3 in Ubuntu 20.04
So closing as this bug report is no longer valid

** Changed in: hundredpapercuts
   Status: Triaged => Invalid

** Changed in: rhythmbox (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  Rythmbox: Poor Grammar: 80s and 90s under radio

Status in One Hundred Papercuts:
  Invalid
Status in Rhythmbox:
  Expired
Status in rhythmbox package in Ubuntu:
  Invalid

Bug description:
  I'd expect the apostrophe should be before the 80 or 90, showing contraction 
('80s or '90s).
  Sorry this is such a small thing.

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

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

[Desktop-packages] [Bug 909803] Re: Spelling errors in radio genre names ('80s, '90s and Rock 'n' Roll)

[Paul White]

Upstream report was closed "RESOLVED OBSOLETE" on 2014-03-28
stating "These streams are no longer in the default list."
Confirmed to be the case with rhythmbox 3.4.3 in Ubuntu 20.04
So closing as this bug report is no longer valid

** Changed in: rhythmbox (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Spelling errors in radio genre names ('80s, '90s and Rock 'n' Roll)

Status in Rhythmbox:
  Expired
Status in rhythmbox package in Ubuntu:
  Invalid

Bug description:
  The Genre list on the Radio view has genres called "80's", "90's" and
  "Rock'n'Roll".

  They should be "The '80s", "The '90s" and "Rock 'n' Roll",
  respectively.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: rhythmbox 2.90.1~2026.89c872b0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7
  Uname: Linux 3.2.0-7-generic x86_64
  ApportVersion: 1.90-0ubuntu1
  Architecture: amd64
  CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Thu Dec 29 18:57:59 2011
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/rhythmbox
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  LocalLibraries: /usr/local/lib/librtmp.so.0
  SourcePackage: rhythmbox
  UpgradeStatus: Upgraded to precise on 2011-12-22 (7 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2011-07-06 (1013 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110531.1)
  Package: rhythmbox 3.0.2-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

[Efthimios Chaskaris]

This bug is so annoying if you have your screen turn off due to
inactivity that I'm inclined to press 1. for a fix and 2. to write
something about it in the known issues section for 19.10.

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Triaged
Status in pulseaudio source package in Eoan:
  Triaged
Status in pulseaudio source package in Focal:
  Triaged

Bug description:
  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  I would be good if it would remember this choice so that I have
  to do it only once.

  Or maybe (if that is technically possible)
  just output on both output devices by default - this would be
  even more user friendly for newbies who will have a hard time
  finding the right place to change this (or maybe have UI in the
  volume slider to select outputs if there are more than one?
  But anyway, my immediate concern is that it should just remember
  my choice :)

  Please let me know if I can provide more information. Happy to
  dig into code if needed but I will need some pointers.

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

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

[Desktop-packages] [Bug 1393189] Re: extra plugin not installable

[Paul White]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner.

Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019.

This release of Ubuntu is no longer receiving maintenance updates. If
this is still an issue using a maintained version of Ubuntu please let
us know otherwise this report can be left to expire in approximately 60
days time.

Paul White
[Ubuntu Bug Squad]

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

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

Title:
  extra plugin not installable

Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  On a 64bits architecture, Rhythmbox tries (and fails) to install the
  32 bits version of gstreamer1.0-plugins-bad (i386) even if the 64 bits
  version is already installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: rhythmbox 3.0.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov 16 15:16:16 2014
  InstallationDate: Installed on 2014-05-24 (175 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1325834] Re: extra plugin not installable

[Paul White]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner.

Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019.

This release of Ubuntu is no longer receiving maintenance updates. If
this is still an issue using a maintained version of Ubuntu please let
us know otherwise this report can be left to expire in approximately 60
days time.

Paul White
[Ubuntu Bug Squad]

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

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

Title:
  extra plugin not installable

Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  I have some midi files in my sound library.

  After upgrading to Ubuntu 14.04 Rhythmbox complains about missing plug-ins 
and when I click on the "install plug-in" button it proposes  
  Gstreamer1.0-plugins-bad (i386) 
  which is not installable because I already have Gstreamer1.0-plugins-bad for 
I64 architecture.

  May be a discrepancy in the software lists used by Rhythmbox and the
  Ubuntu ones

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: rhythmbox 3.0.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jun  3 09:09:48 2014
  InstallationDate: Installed on 2014-05-24 (9 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 406587] Re: Rhythmbox freezes after playing one song

[Paul White]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner.

This release of Ubuntu is no longer receiving maintenance updates.

The upstream report has moved to:
https://gitlab.gnome.org/GNOME/rhythmbox/issues/767
but has seen no activity 

If this is still an issue using a maintained version of Ubuntu please
let us know otherwise this report can be left to expire in approximately
60 days time.

Paul White
[Ubuntu Bug Squad]

** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/issues #767
   https://gitlab.gnome.org/GNOME/rhythmbox/issues/767

** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/issues #767
   https://gitlab.gnome.org/GNOME/rhythmbox/issues/767

** Changed in: rhythmbox
   Importance: Critical => Unknown

** Changed in: rhythmbox
   Status: Expired => Unknown

** Changed in: rhythmbox
 Remote watch: GNOME Bug Tracker #587285 => 
gitlab.gnome.org/GNOME/rhythmbox/issues #767

** Changed in: rhythmbox (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  Rhythmbox freezes after playing one song

Status in Rhythmbox:
  Unknown
Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: rhythmbox

  Ubuntu 9.10 karmic, Linux 2.6.31-4-generic-pae i686 GNU/Linux
  Rhythmbox 0.12.3-1ubuntu1

  When track end playing, rhythmbox freezes.

  Here is gdb from attached to PID:

  (gdb) bt full
  #0 0xb807b430 in __kernel_vsyscall ()
  No symbol table info available.
  #1 0xb7d24c79 in __lll_lock_wait () from /lib/tls/i686/cmov/libpthread.so.0
  No symbol table info available.
  #2 0xb7d20109 in _L_lock_89 () from /lib/tls/i686/cmov/libpthread.so.0
  No symbol table info available.
  #3 0xb7d1fa12 in pthread_mutex_lock () from /lib/tls/i686/cmov/libpthread.so.0
  No symbol table info available.
  #4 0xb70d716e in g_static_rec_mutex_lock () from /usr/lib/libglib-2.0.so.0
  No symbol table info available.
  #5 0xb8034970 in _threads_enter () at rb-util.c:355
  No locals.
  #6 0xb774e078 in ?? () from /usr/lib/libgdk-x11-2.0.so.0
  No symbol table info available.
  #7 0xb70afa91 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
  No symbol table info available.
  #8 0xb70b023c in ?? () from /usr/lib/libglib-2.0.so.0
  No symbol table info available.
  #9 0xb70b095f in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
  No symbol table info available.
  #10 0xb78f7a49 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
  No symbol table info available.
  #11 0x08062f3e in main (argc=1, argv=0xbf91feb4) at main.c:332
  _save = 0x88e7928
  session_bus = 
  error = 0x0
  rb_shell = 0x8691020
  accel_map_file = 0x8686e50 "/home/oivasyuv/.gnome2/accels/rhythmbox"
  context = 
  options = {{long_name = 0x80d7a53 "debug", short_name = 100 'd', 
flags = 0, arg = G_OPTION_ARG_NONE, arg_data = 0x80ef0c8, description = 
0x80c5d10 "Enable debug output", arg_description = 0x0}, {
  long_name = 0x80c5d24 "debug-match", short_name = 68 'D', flags = 
0, arg = G_OPTION_ARG_STRING, arg_data = 0x80ef0cc, description = 0x80c5edc 
"Enable debug output matching a specified string",
  arg_description = 0x0}, {long_name = 0x80c5d30 "no-update", 
short_name = 0 '\0', flags = 0, arg = G_OPTION_ARG_NONE, arg_data = 0x80ef0e4,
  description = 0x80c5f0c "Do not update the library with file 
changes", arg_description = 0x0}, {long_name = 0x80c5d3a "no-registration", 
short_name = 110 'n', flags = 0,
  arg = G_OPTION_ARG_NONE, arg_data = 0x80ef0d0, description = 
0x80c5d4a "Do not register the shell", arg_description = 0x0}, {long_name = 
0x80c5d64 "dry-run", short_name = 0 '\0', flags = 0,
  arg = G_OPTION_ARG_NONE, arg_data = 0x80ef0e0, description = 
0x80c5f38 "Don't save any data permanently (implies --no-registration)", 
arg_description = 0x0}, {
  long_name = 0x80c5d6c "rhythmdb-file", short_name = 0 '\0', flags 
= 0, arg = G_OPTION_ARG_STRING, arg_data = 0x80ef0dc, description = 0x80c5d7a 
"Path for database file to use",
  arg_description = 0x0}, {long_name = 0x80c5d98 "playlists-file", 
short_name = 0 '\0', flags = 0, arg = G_OPTION_ARG_STRING, arg_data = 0x80ef0d8,
  description = 0x80c5f74 "Path for playlists file to use", 
arg_description = 0x0}, {long_name = 0x80c7048 "quit", short_name = 113 'q', 
flags = 0, arg = G_OPTION_ARG_NONE, arg_data = 0x80ef0d4,
  description = 0x80c5da7 "Quit Rhythmbox", arg_description = 0x0}, 
{long_name = 0x80cc91e "", short_name = 0 '\0', flags = 0, arg = 
G_OPTION_ARG_STRING_ARRAY, arg_data = 0x80ef0e8,
  description = 0x0, arg_description = 0x80c5db6 "[URI...]"}, 
{long_name = 0x0, short_name = 0 '\0', flags = 0, arg = G_OPTION_ARG_NONE, 
arg_data = 0x0, description =

[Desktop-packages] [Bug 452929] Re: lyrics download fails

[Paul White]

Upstream report was closed "RESOLVED FIXED" on 2009-09-12
Fixed in Ubuntu as per comment #3 so closing

** Changed in: rhythmbox (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  lyrics download fails

Status in Rhythmbox:
  Fix Released
Status in rhythmbox package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: rhythmbox

  instead of song text, the user is presented with an html page that
  starts like this:

  
  
  
MediaWiki API
  
  
  
  
  



**
**  **
**  This is an auto-generated MediaWiki API documentation page  **
**  **
**  Documentation and Examples: **
**   http://www.mediawiki.org/wiki/API";>http://www.mediawiki.org/wiki/API  
**
**  **
**

Status:  All features shown on this page should be working, but the 
API
 is still in active development, and  may change at any 
time.
 Make sure to monitor our mailing list for any updates.

  
  I suspect the MediaWiki API has changed.

  ProblemType: Bug
  Architecture: i386
  Date: Fri Oct 16 11:55:08 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/rhythmbox
  Package: rhythmbox 0.12.5-0ubuntu3
  ProcEnviron:
   PATH=(custom, user)
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  ProcVersionSignature: Ubuntu 2.6.31-14.47-generic
  SourcePackage: rhythmbox
  Uname: Linux 2.6.31-14-generic i686

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

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

[Desktop-packages] [Bug 1258367] Re: Atom feed is not readable in Rhythmbox

[Paul White]

** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/issues #1690
   https://gitlab.gnome.org/GNOME/rhythmbox/issues/1690

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

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

Title:
  Atom feed is not readable in Rhythmbox

Status in Rhythmbox:
  Unknown
Status in rhythmbox package in Ubuntu:
  Triaged

Bug description:
  The following feed either crashes or doesn't work in Rhythmbox:
  http://gdata.youtube.com/feeds/api/users/TimesSquareChurch/uploads

  As you can see, it's valid:
  
http://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fgdata.youtube.com%2Ffeeds%2Fapi%2Fusers%2FTimesSquareChurch%2Fuploads

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: rhythmbox 2.99.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Thu Dec  5 18:21:09 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-11-23 (12 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1609700] Re: username is not saved in openconnect connection dialog

[Jerome Covington]

Confirmed this bug is an issue for me in Ubuntu 19.10 as well.
 
Package: network-manager-openconnect
Architecture: amd64
Version: 1.2.4-2ubuntu1

Package: network-manager-openconnect-gnome
Version: 1.2.4-2ubuntu1

However perhaps network-manager-openconnect-gnome is deprecated?

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

Title:
  username is not saved in openconnect connection dialog

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager-openconnect package in Ubuntu:
  Fix Released
Status in Fedora:
  Fix Released

Bug description:
  
  Hi,

  I clicked on "save passwords" but only the password is filled in
  automatically when I open the connection dialog. The "Username" field
  is empty!

  This happens for a SSLVPN configuration.

  For another VPN config (don't know which type) everything is ok.

  
  openconnect: 7.06-2build2

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

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

[Desktop-packages] [Bug 1264901] Re: package starts with grey screen

[Paul White]

Bug report did not expire due to bug watch
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014
Upstream report was closed "RESOLVED INCOMPLETE" on 2014-10-28
as the reporter (here and upstream) did not provide the requested information
The last comment from the reporter here was over 6 years ago so closing

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

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

Title:
  package starts with grey screen

Status in Rhythmbox:
  Expired
Status in rhythmbox package in Ubuntu:
  Invalid

Bug description:
  When Started Rhythmbox starts but show a grey screen with nothing on
  it. I am using Ubuntu 13.04 and Rhythmbox 2.98-0ubuntu5. I expected to
  have the interface and be able to start playing music but I instead
  got the grey screen that I can't do anything with.

  ALSO SUBMITTED ON: https://bugzilla.gnome.org/show_bug.cgi?id=721221

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: rhythmbox 2.98-0ubuntu5
  ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12
  Uname: Linux 3.8.0-34-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: amd64
  Date: Sun Dec 29 19:21:38 2013
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2013-10-12 (78 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rhythmbox
  UpgradeStatus: Upgraded to raring on 2013-12-08 (21 days ago)
  XsessionErrors:
   (nautilus:2289): GLib-GObject-CRITICAL **: g_object_set: assertion 
`G_IS_OBJECT (object)' failed
   (nautilus:2289): GLib-GObject-CRITICAL **: g_object_set: assertion 
`G_IS_OBJECT (object)' failed

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

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

[Desktop-packages] [Bug 457292] Re: [karmic] Rhythmbox: can't login to Last.fm

[Paul White]

Report was raised over 10 years ago
Bug report did not expire due to assignment
No response to comment #18 after over 5 years
Not a problem here with rhythmbox 3.4.3 and Ubuntu 20.04 (dev)
As 14 people say they were affected any issue must have been fixed


** Changed in: rhythmbox (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  [karmic] Rhythmbox: can't login to Last.fm

Status in rhythmbox package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: rhythmbox

  I enter my username and password into Last.fm preferences, but I am
  never able to login. It always returns "incorrect username or
  password" under "status."

  ProblemType: Bug
  Architecture: amd64
  Date: Thu Oct 22 00:49:43 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/rhythmbox
  NonfreeKernelModules: nvidia
  Package: rhythmbox 0.12.5-0ubuntu4
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: rhythmbox
  Uname: Linux 2.6.31-14-generic x86_64

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

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

[Desktop-packages] [Bug 1341452] Re: Rhythmbox won't encode to ogg vorbis. Insists it needs additional software.

[Paul White]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner.

The 14.04 and 14.10 releases of Ubuntu are no longer receiving
maintenance updates. If this is still an issue using a maintained
version of Ubuntu please let us know otherwise this report can be left
to expire in approximately 60 days time.

Paul White
[Ubuntu Bug Squad]

** Changed in: rhythmbox
   Status: New => Incomplete

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

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

Title:
  Rhythmbox won't encode to ogg vorbis. Insists it needs additional
  software.

Status in Rhythmbox:
  Incomplete
Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  Since I upgraded to 14.04, I cannot export CD tracks in Rhythmbox. It
  told me "Unabel to transfer tracks. Additional software is required to
  encode media in your preferred format: Vorbis encoder" My options are
  "Cancel the transfer" or "Install" I click install, and get the
  following error.

  Invalid commandline

  The parameters passed to the application had an invalid format. Please
  file a bug!

  The parameters were:
  --transient-for=56623111
  gstreamer|1.0|rhythmbox|Vorbis encoder|encoder-audio/x-vorbis

  I click OK on the error and it loops back to "Unabel to transfer
  tracks".

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-codec-install 0.4.7+nmu1ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jul 13 22:49:34 2014
  ExecutablePath: /usr/bin/gnome-codec-install
  InstallationDate: Installed on 2014-01-13 (182 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-codec-install
  UpgradeStatus: Upgraded to trusty on 2014-07-14 (0 days ago)

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

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

[Desktop-packages] [Bug 1766775] Re: Notifications do not disappear

[Bug Watch Updater]

** Changed in: gnome-settings-daemon
   Status: Unknown => 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/1766775

Title:
  Notifications do not disappear

Status in GNOME Settings Daemon:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I frequently have notifications that do not disappear after being
  shown.  This is particularly prevalent with power management
  notifications.  Most of the time when I wake my computer from suspend,
  I see the following notification at the top: "Automatic suspend -
  Computer will suspend very soon because of inactivity." that never
  goes away.  Presumably, this was shown before my computer went to
  sleep, and should have disappeared but didn't.  I have to either click
  on the notification, or click on the time to open the notification
  menu to get it to disappear.  Occasionally, the same behaviour occurs
  with other, random notifications.

  This is a long-standing issue for me, that I'm just now getting around
  to reporting.  I'm on 17.10, gnome-shell 3.26.2-0ubuntu0.1, and
  running the gnome-session (not Ubuntu).  I don't know if the issue is
  present on Gnome 3.28, but plan to find out once 18.04 final is
  released.

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

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

[Desktop-packages] [Bug 1258367] Re: Atom feed is not readable in Rhythmbox

[Bug Watch Updater]

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

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

Title:
  Atom feed is not readable in Rhythmbox

Status in Rhythmbox:
  New
Status in rhythmbox package in Ubuntu:
  Triaged

Bug description:
  The following feed either crashes or doesn't work in Rhythmbox:
  http://gdata.youtube.com/feeds/api/users/TimesSquareChurch/uploads

  As you can see, it's valid:
  
http://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fgdata.youtube.com%2Ffeeds%2Fapi%2Fusers%2FTimesSquareChurch%2Fuploads

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: rhythmbox 2.99.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Thu Dec  5 18:21:09 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-11-23 (12 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 265143] Re: Seeking using the mouse wheel or right cursor causes song to restart sometimes

[Bug Watch Updater]

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

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

Title:
  Seeking using the mouse wheel or right cursor causes song to restart
  sometimes

Status in Rhythmbox:
  New
Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: rhythmbox

  When moving the "seek" bar in Rhythmbox to go forward in the song
  using the right cursor keys or the mouse wheel, sometimes the slider
  is positioned at the beginning of the bar.

  This is very easy to reproduce for me, no matter what file format I'm
  playing or what backend I'm using (I've tested with Pulseaudio and
  ALSA): play a few seconds of the song, and then press *and hold* the
  right cursor key. After a few forward "skips", the slider will return
  to the beginning of the bar, will advance a little and will return
  again. I can do this forever withouth the slider ever getting to the
  end of the bar.

  With the mouse, after a few rotations of the mouse wheel the slider
  goes back to the beginning.

  If I allow a few seconds between cursor key presses or mouse wheel
  rotations, everything works fine.

  To resume, "What I expected to happen":

  I expect that the slider goes to the right if I press the right cursor
  or move the mouse wheel.

  "What happened instead":

  The slider went back to the beginning (left) of the seek bar.

  I'm using Ubuntu Hardy with Rhythmbox 0.11.5

  Raúl

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

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

[Desktop-packages] [Bug 406587] Re: Rhythmbox freezes after playing one song

[Bug Watch Updater]

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

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

Title:
  Rhythmbox freezes after playing one song

Status in Rhythmbox:
  New
Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: rhythmbox

  Ubuntu 9.10 karmic, Linux 2.6.31-4-generic-pae i686 GNU/Linux
  Rhythmbox 0.12.3-1ubuntu1

  When track end playing, rhythmbox freezes.

  Here is gdb from attached to PID:

  (gdb) bt full
  #0 0xb807b430 in __kernel_vsyscall ()
  No symbol table info available.
  #1 0xb7d24c79 in __lll_lock_wait () from /lib/tls/i686/cmov/libpthread.so.0
  No symbol table info available.
  #2 0xb7d20109 in _L_lock_89 () from /lib/tls/i686/cmov/libpthread.so.0
  No symbol table info available.
  #3 0xb7d1fa12 in pthread_mutex_lock () from /lib/tls/i686/cmov/libpthread.so.0
  No symbol table info available.
  #4 0xb70d716e in g_static_rec_mutex_lock () from /usr/lib/libglib-2.0.so.0
  No symbol table info available.
  #5 0xb8034970 in _threads_enter () at rb-util.c:355
  No locals.
  #6 0xb774e078 in ?? () from /usr/lib/libgdk-x11-2.0.so.0
  No symbol table info available.
  #7 0xb70afa91 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
  No symbol table info available.
  #8 0xb70b023c in ?? () from /usr/lib/libglib-2.0.so.0
  No symbol table info available.
  #9 0xb70b095f in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
  No symbol table info available.
  #10 0xb78f7a49 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
  No symbol table info available.
  #11 0x08062f3e in main (argc=1, argv=0xbf91feb4) at main.c:332
  _save = 0x88e7928
  session_bus = 
  error = 0x0
  rb_shell = 0x8691020
  accel_map_file = 0x8686e50 "/home/oivasyuv/.gnome2/accels/rhythmbox"
  context = 
  options = {{long_name = 0x80d7a53 "debug", short_name = 100 'd', 
flags = 0, arg = G_OPTION_ARG_NONE, arg_data = 0x80ef0c8, description = 
0x80c5d10 "Enable debug output", arg_description = 0x0}, {
  long_name = 0x80c5d24 "debug-match", short_name = 68 'D', flags = 
0, arg = G_OPTION_ARG_STRING, arg_data = 0x80ef0cc, description = 0x80c5edc 
"Enable debug output matching a specified string",
  arg_description = 0x0}, {long_name = 0x80c5d30 "no-update", 
short_name = 0 '\0', flags = 0, arg = G_OPTION_ARG_NONE, arg_data = 0x80ef0e4,
  description = 0x80c5f0c "Do not update the library with file 
changes", arg_description = 0x0}, {long_name = 0x80c5d3a "no-registration", 
short_name = 110 'n', flags = 0,
  arg = G_OPTION_ARG_NONE, arg_data = 0x80ef0d0, description = 
0x80c5d4a "Do not register the shell", arg_description = 0x0}, {long_name = 
0x80c5d64 "dry-run", short_name = 0 '\0', flags = 0,
  arg = G_OPTION_ARG_NONE, arg_data = 0x80ef0e0, description = 
0x80c5f38 "Don't save any data permanently (implies --no-registration)", 
arg_description = 0x0}, {
  long_name = 0x80c5d6c "rhythmdb-file", short_name = 0 '\0', flags 
= 0, arg = G_OPTION_ARG_STRING, arg_data = 0x80ef0dc, description = 0x80c5d7a 
"Path for database file to use",
  arg_description = 0x0}, {long_name = 0x80c5d98 "playlists-file", 
short_name = 0 '\0', flags = 0, arg = G_OPTION_ARG_STRING, arg_data = 0x80ef0d8,
  description = 0x80c5f74 "Path for playlists file to use", 
arg_description = 0x0}, {long_name = 0x80c7048 "quit", short_name = 113 'q', 
flags = 0, arg = G_OPTION_ARG_NONE, arg_data = 0x80ef0d4,
  description = 0x80c5da7 "Quit Rhythmbox", arg_description = 0x0}, 
{long_name = 0x80cc91e "", short_name = 0 '\0', flags = 0, arg = 
G_OPTION_ARG_STRING_ARRAY, arg_data = 0x80ef0e8,
  description = 0x0, arg_description = 0x80c5db6 "[URI...]"}, 
{long_name = 0x0, short_name = 0 '\0', flags = 0, arg = G_OPTION_ARG_NONE, 
arg_data = 0x0, description = 0x0, arg_description = 0x0}}
  __FUNCTION__ = "main"
  (gdb)

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

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

[Desktop-packages] [Bug 78524] Re: Podcast download mechanism isn't robust enough and often fails

[Bug Watch Updater]

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

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

Title:
  Podcast download mechanism isn't robust enough and often fails

Status in Rhythmbox:
  New
Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: rhythmbox

  I have subscribed to a few radio podcasts in RB.
  I have broadband so it's fast, and it used to work just fine, however, in the 
past couple of months, the quality of my internet connection (blame crappy ISP 
here!) has decreased significantly (takes ages to connect to a server, transfer 
speed is highly unstable, and sometimes plain stops, then resumes when it feels 
like it, a second later, or a minute... depends on the mood and server !).
  This revealed a serious weakness/problem in RB: 99% of the time, RB fails to 
download the podcasts ! Most of the time it just says "Waiting", and sometimes 
it downloads 5% of the file then sits there forever and won't move an inch even 
if I let it run for 3 days.
  Thing is, if I try to download these podcasts in a terminal, using the "wget" 
command, it works just fine, and in the worse case, it takes 3 minutes to grab 
an episode and that's it.
  That's why I think the problem lies within RB...
  I suspect that the problem might be that RB times out way too easily, and 
most importantly, when it does time out, it gives up for good, and won't insist.
  So the solution is probably to do as wget likely does (from what I can see) : 
increase the time out greatly when connecting initially to the server. Say a 2 
minute time out, not less. 
  Then once it starts downloading the file, and in the event that transfer 
speed drops to zero : DO NOT time out, and just patiently wait for transfer to 
resume.

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

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

[Desktop-packages] [Bug 299158] Re: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place

[Paride Legovini]

Maintainer of the fonts-hack Debian package here. I can't reproduce the
issue with fonts-hack 3.003-3 on Eoan, I get the expected result, i.e.:

* Two grapheme clusters are displayed: Latin small letter a with acute
accent, Latin small letter e.

On which Ubuntu release are you observing it?

** Changed in: fonts-hack (Ubuntu)
   Status: New => Incomplete

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

Title:
  DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream
  Vera Mono: Combining diacritics out of place

Status in fonts-dejavu package in Ubuntu:
  Confirmed
Status in fonts-droid package in Ubuntu:
  Won't Fix
Status in fonts-hack package in Ubuntu:
  Incomplete
Status in fonts-liberation package in Ubuntu:
  Confirmed
Status in fonts-noto package in Ubuntu:
  New
Status in fonts-tlwg package in Ubuntu:
  New
Status in fonts-ubuntu package in Ubuntu:
  New
Status in msttcorefonts package in Ubuntu:
  Won't Fix
Status in oxygen-fonts package in Ubuntu:
  New
Status in ttf-bitstream-vera package in Ubuntu:
  New

Bug description:
  In the Liberation Mono font, combining diacritical marks are drawn
  over the following character rather than the preceding.

  According to the Unicode standard since at least version 3.0, chapter
  3.6, verse D56, combining characters apply to the preceding base
  character. However, this font renders them on the following base
  character.

  Version info:
  Ubuntu Intrepid
  ttf-liberation 1.04~beta2-2

  To reproduce:
  1. Open gedit.
  2. Type the following three code points: U+0061 U+0301 U+0065 (Latin small 
letter a, Combining acute accent, Latin small letter e).
  3. Via Edit|Preferences|Font & Colors|Font, select the Liberation Mono font.

  Expected:
  * Two grapheme clusters are displayed: Latin small letter a with acute 
accent, Latin small letter e.

  Observed:
  * The grapheme clusters displayed are: Latin small letter a, Latin small 
letter e with acute accent.

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

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

[Desktop-packages] [Bug 1852069] Re: Failed to backup to google drive on ubuntu 19.10

[Bug Watch Updater]

** Changed in: deja-dup (Debian)
   Status: New => Fix Released

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

Title:
  Failed to backup to google drive on ubuntu 19.10

Status in Déjà Dup:
  Invalid
Status in deja-dup package in Ubuntu:
  Confirmed
Status in deja-dup package in Debian:
  Fix Released

Bug description:
  On Ubuntu 19.10 can't do backup to Google Drive anymore with the
  following error message:

  BackendException: PyDrive backend requires PyDrive installation.  Please read 
the manpage for setup details.
  Exception: No module named 'apiclient'

  I also could not find pydrive package or don't know how it properly
  called.

  $ lsb_release -d
  Description:Ubuntu 19.10

  $ dpkg-query -W deja-dup duplicity
  deja-dup40.1-1ubuntu2
  duplicity   0.8.04-2ubuntu1

  The logfile for following command is empy:
  DEJA_DUP_DEBUG=1 deja-dup --backup | tail -n 1000 > /tmp/deja-dup.log

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1852069/+subscriptions

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

[Desktop-packages] [Bug 893031] Re: Empathy is not working behind the proxy servers SINCE Ubuntu 11.10

[Bug Watch Updater]

Launchpad has imported 9 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=47960.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2012-03-27T12:39:23+00:00 Ken VanDine wrote:

Created attachment 59127
WOCKY_DEBUG=xmpp with contact info stripped out

In my test scenario, I have a local squid proxy properly configured to
handle HTTP CONNECT, tested with pidgin and it works.  MS Live accounts
works as well using telepathy-haze.  However attempting to connect to
gtalk or jabber.org accounts, according to the squid access log, never
attempts to connect to the configured proxy.


Downstream bug report: 
https://bugs.launchpad.net/ubuntu/precise/+source/telepathy-gabble/+bug/893031

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/893031/comments/18


On 2012-03-28T08:01:24+00:00 Nicilas wrote:

Can you provide your system configuration, and the returned
configuration as seen by libproxy:

proxy xmpp-client://myserfer
proxy https://myserfer

HTTP Connect for bare jabber is currently not supported by libproxy (not
support fro any non https:// protocols). Also, be aware that Pidgin
erroneously reads the HTTP_PROXY rather then SECURE_PROXY gnome setting
for doing HTTP Connect.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/893031/comments/20


On 2012-03-28T11:59:38+00:00 Ken VanDine wrote:

proxy xmpp-client://myserfer
direct://
proxy https://myserfer
http://localhost:3128

Looking through the gabble source, I don't see anywhere that it uses
libproxy, not even an includes for proxy.h.  How does it interact with
libproxy?

Previously it had been suggested that it wasn't working because our
version of libproxy in Ubuntu was too old, 0.3.x.  We now have the
0.4.7, the latest and it still doesn't work.

So this isn't a bug so much as it is not supported yet?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/893031/comments/21


On 2012-03-28T12:30:14+00:00 Nicilas wrote:

(In reply to comment #2)
> proxy xmpp-client://myserfer
> direct://
> proxy https://myserfer
> http://localhost:3128
> 
> Looking through the gabble source, I don't see anywhere that it uses libproxy,
> not even an includes for proxy.h.  How does it interact with libproxy?
> 
> Previously it had been suggested that it wasn't working because our version of
> libproxy in Ubuntu was too old, 0.3.x.  We now have the 0.4.7, the latest and
> it still doesn't work.
> 
> So this isn't a bug so much as it is not supported yet?

Gabble uses a library called Wocky which is base on GIO. And GIO has a
libproxy and gnome plugin. I usually suggest using libproxy for distro
that can run both KDE and Gnome on the same install, the Gnome plugin
ignores the environment.

Currently the support for HTTP Connect is very restricted because the
GIO developers did not agree it was a correct way of doing generic
socket proxying. Here is how you can make it work. First thing to know
is that wocky will do HTTP Connect only when you are running in Old SSL
mode. Which mean the first thing you do is an TLS handshake (so it
cannot be differentiated from a HTTPS connection). Then you need a
correct configuration, which you have.

If you are using a google account configured with older version of Empathy, I 
suggest to remove it and re-create it. This will add the fallback-servers 
parameter to your account. Note that HTTP Connect is never the first, so 
connection may take a little while depending on how fat the other attempts 
fails. You can check the params using mc-tool show ... Here's what you should 
see:
(GStrv) fallback-servers = ["talkx.l.google.com", 
"talkx.l.google.com:443,oldssl", "talkx.l.google.com:80"]

Unless someone broke the fallbacks, wocky will try the server
talk.google.com (use to do SRV, but was changed recently). In case of
failure, it will fallback to talkx.l.google.com using normal TLS, if it
fails again, it will try talkx.l.google.com:443 using OLD SSL mode, and
if that still fails it will try cleartext on port 80 (I think this one
always fails these days, not sure).

In the future, libproxy should try HTTP Connect for any type of
connection, and have a direct fallback, but that couldn't be done
without changing libproxy internals a lot. Also, the HTTP Connect GLIB
plugin should be provided by libsoup. Feel free to contribute if you
have time.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/893031/comments/22


On 2012-03-28T12:4

[Desktop-packages] [Bug 1842167] Re: Default list of stations entry for "WSUM 91.7 FM (University of Wisconsin) has an outdated URL

[Dabian]

Upstream posted a patch, which I have included here.

As far as I can tell, this should fix the issue with this particular
station. I don't know why it hasn't been applied upstream, but I see no
reason why we can't apply it while we wait for upstream.

** Patch added: "Patch file with diff for plugins/iradio/iradio-initial.xsp"
   
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1842167/+attachment/5309775/+files/rhythmbox.735111.diff

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

Title:
  Default list of stations entry for "WSUM 91.7 FM (University of
  Wisconsin) has an outdated URL

Status in Rhythmbox:
  New
Status in rhythmbox package in Ubuntu:
  Confirmed

Bug description:
  The stock URL does no longer have an DNS-record.

  (Stock URL is "http://vu.wsum.wisc.edu/wsumlive.m3u";).

  The new URL appears to be:

  http://stream.studio.wsum.wisc.edu/wsum128

  A workaround, is to rightclick the station, choose "properties", which
  will popup a window with information about the station. Click the
  "details" tab in the popup window, and replace the URL with the one
  above, and close the the popup window.

  I think at least one of the other URL's might need an update, but I
  haven't looked into that yet.

  Additional information per request:

  (1)
  $ lsb_release -rd
  Description:  Ubuntu 19.04
  Release:  19.04

  (2)
  $ rhythmbox --version
  rhythmbox 3.4.3

  $ apt-cache policy rhythmbox
  rhythmbox:
Installeret: 3.4.3-1ubuntu1
Kandidat:3.4.3-1ubuntu1
Versionstabel:
   *** 3.4.3-1ubuntu1 500
  500 http://ny-mirrors.evowise.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status
   3.3-1ubuntu7 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  (3) I obviously expected the URL to up to date.

  (4) I found that the URL was out of date.

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

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

[Desktop-packages] [Bug 1855106] [NEW] Turn based [should you avoid focus effect in an icon?]

[klfytklfyt]

Public bug reported:


Perfect rule for desktop icons looks like actually being
turn based graphics.

Unfortunately I have no example of difference how real
time differs from turn based icon.

:))

** Affects: yaru-theme (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Turn based  [should you avoid focus effect in an icon?]

Status in yaru-theme package in Ubuntu:
  New

Bug description:
  
  Perfect rule for desktop icons looks like actually being
  turn based graphics.

  Unfortunately I have no example of difference how real
  time differs from turn based icon.

  :))

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1855106/+subscriptions

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

[Desktop-packages] [Bug 1842167] Re: Default list of stations entry for "WSUM 91.7 FM (University of Wisconsin) has an outdated URL

[Dabian]

** Description changed:

+ Update:  A patch has been posted - who can apply it?
+ 
  The stock URL does no longer have an DNS-record.
  
  (Stock URL is "http://vu.wsum.wisc.edu/wsumlive.m3u";).
  
  The new URL appears to be:
  
  http://stream.studio.wsum.wisc.edu/wsum128
  
  A workaround, is to rightclick the station, choose "properties", which
  will popup a window with information about the station. Click the
  "details" tab in the popup window, and replace the URL with the one
  above, and close the the popup window.
  
  I think at least one of the other URL's might need an update, but I
  haven't looked into that yet.
  
  Additional information per request:
  
  (1)
  $ lsb_release -rd
  Description:  Ubuntu 19.04
  Release:  19.04
  
  (2)
  $ rhythmbox --version
  rhythmbox 3.4.3
  
  $ apt-cache policy rhythmbox
  rhythmbox:
-   Installeret: 3.4.3-1ubuntu1
-   Kandidat:3.4.3-1ubuntu1
-   Versionstabel:
-  *** 3.4.3-1ubuntu1 500
- 500 http://ny-mirrors.evowise.com/ubuntu disco/main amd64 Packages
- 100 /var/lib/dpkg/status
-  3.3-1ubuntu7 500
- 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+   Installeret: 3.4.3-1ubuntu1
+   Kandidat:3.4.3-1ubuntu1
+   Versionstabel:
+  *** 3.4.3-1ubuntu1 500
+ 500 http://ny-mirrors.evowise.com/ubuntu disco/main amd64 Packages
+ 100 /var/lib/dpkg/status
+  3.3-1ubuntu7 500
+ 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  
  (3) I obviously expected the URL to up to date.
  
  (4) I found that the URL was out of date.

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

Title:
  Default list of stations entry for "WSUM 91.7 FM (University of
  Wisconsin) has an outdated URL

Status in Rhythmbox:
  New
Status in rhythmbox package in Ubuntu:
  Confirmed

Bug description:
  Update:  A patch has been posted - who can apply it?

  The stock URL does no longer have an DNS-record.

  (Stock URL is "http://vu.wsum.wisc.edu/wsumlive.m3u";).

  The new URL appears to be:

  http://stream.studio.wsum.wisc.edu/wsum128

  A workaround, is to rightclick the station, choose "properties", which
  will popup a window with information about the station. Click the
  "details" tab in the popup window, and replace the URL with the one
  above, and close the the popup window.

  I think at least one of the other URL's might need an update, but I
  haven't looked into that yet.

  Additional information per request:

  (1)
  $ lsb_release -rd
  Description:  Ubuntu 19.04
  Release:  19.04

  (2)
  $ rhythmbox --version
  rhythmbox 3.4.3

  $ apt-cache policy rhythmbox
  rhythmbox:
    Installeret: 3.4.3-1ubuntu1
    Kandidat:3.4.3-1ubuntu1
    Versionstabel:
   *** 3.4.3-1ubuntu1 500
  500 http://ny-mirrors.evowise.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status
   3.3-1ubuntu7 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  (3) I obviously expected the URL to up to date.

  (4) I found that the URL was out of date.

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

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

[Desktop-packages] [Bug 1515539] Re: letters stop being displayed

[Bug Watch Updater]

** Changed in: xorg-server
   Status: Unknown => New

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

Title:
  letters stop being displayed

Status in X.Org X server:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  From time to time, some letters are just not displayer anymore. Only a
  restart will fix the problem temporarily. See the Screenshots that I
  attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nautilus 1:3.14.2-0ubuntu12
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov 12 10:59:44 2015
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2015-08-13 (90 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to wily on 2015-10-27 (15 days ago)

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

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

[Desktop-packages] [Bug 1854386] Re: Stuck on show applications overlay (can't close it)

[Damian]

I have gnome-shell 3.34.1. It still has the 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/1854386

Title:
  Stuck on show applications overlay (can't close it)

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

Bug description:
  Hello,

  I've upgraded my ubuntu 19.04 to 19.10 this morning and I came across
  this very annoying bug.

  Whenever I click on 'show applications' or press win key (shortcut),
  the menu with the applications show, but it's empty - you can search
  through it and it works fine (applications show, one can trigger
  application launch), but then after you select an application, the
  menu doesn't disappear at all.

  It doesn't go away when pressing any application on the dash panel,
  nor when clicking esc key, it only goes away after you click on the
  dash icon again, BUT...

  It doesn't really go away - it just becomes invisible, but still it
  overlaps all the items that are launched (with exception of dash
  panel, because it's not being overlapped), and you can't do anything
  on any launched application. Sometimes when you try to move some
  windows, you can see them getting transformed into a miniature, as if
  the system wanted to insert application into the suggestions on the
  'show applications'.

  The only thing that worked for me was restarting my computer.

  Here is a movie of this happening:
  
https://photos.google.com/share/AF1QipNA94MOXY4iH8rm01coSkZcH6ILYas9n2oXNs9Swxo16ijABFqz71VaRpO59tGpPg/photo/AF1QipOqVIZXLZW-Z_7zCIy8eeBGQgJQkPLY-OKfgy0Y?key=MTJBa2pRUl9VU2lmMXdEZGxYX3ZiSDRSTjJxWjdn

  I couldn't record screen because apparently the hotkeys were also
  intercepted and I couldn't save the video.

  It makes programming right now super dangerous, as if you press the
  'win' button then it's basically 'adios'.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15.3
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 28 18:00:54 2019
  InstallationDate: Installed on 2018-11-09 (383 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to eoan on 2019-11-27 (0 days ago)
  VarLogDistupgradeTermlog:

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

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

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

[Dan Streetman]

Most of the failures are due to s390x kernel configuration setting
RFKILL=n

-- 
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:
  In Progress
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Bionic:
  In Progress
Status in network-manager source package in Disco:
  In Progress
Status in network-manager source package in Eoan:
  In Progress
Status in network-manager source package in Focal:
  In Progress

Bug description:
  [impact]

  most or 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

  [regression potential]

  TBD

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 1855009] Re: autopkgtests all fail on s390x

[Dan Streetman]

Re: RFKILL=n, wireless networking is specifically excluded on s390
systems:

menuconfig WIRELESS 


  
bool "Wireless" 


  
depends on !S390


  
default y   


  

so there's no sense in building RFKILL.  The wpa-dhclient tests fails
because it can't load cfg80211, which is due to s390 never including
wireless networking support.

-- 
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:
  In Progress
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Bionic:
  In Progress
Status in network-manager source package in Disco:
  In Progress
Status in network-manager source package in Eoan:
  In Progress
Status in network-manager source package in Focal:
  In Progress

Bug description:
  [impact]

  most or 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

  [regression potential]

  TBD

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 1854758] Re: duplicity crashes since upgraded to 19.10

[Kenneth Loafman]

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

** This bug has been marked a duplicate of bug 1852876
   AttributeError: '_io.BufferedReader' object has no attribute 'uc_name'

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

Title:
  duplicity crashes since upgraded to 19.10

Status in duplicity package in Ubuntu:
  New

Bug description:
  The following script is used to run duplicity for backup

  # Version  PA01/01  by T Pollák  on 2018-11-02
  # This script is used to create a full backup of this computer
  # and must be run as root.
  # The script will run the backup command duplicity to create
  # a full backup on My Book Live as IP 192.168.1.100 with ftp
  # into the directory 64HP in the share Tommy.
  # The script is developed from the script backup_duplicity_full64.
  # To create incremental backups run the script
  # /home/tpollak/bin/backup_duplicity_incrHP as root.
  # - - - - - -

  PASSPHRASE=***
  FTP_PASSWORD=
  export PASSPHRASE FTP_PASSWORD

  duplicity full --force --volsize 1000 --exclude /media/OS/Program\
  Files/WindowsApps --exclude /media/OS/Windows --exclude /boot
  --exclude /cdrom --exclude /dev --exclude /proc --exclude /sys
  --exclude /tmp --exclude /home/tpollak/.gvfs --exclude
  /run/user/1000/gvfs --exclude /home/tpollak/Downloads --exclude
  /home/tpollak/Trash / ftp://Tommy@192.168.1.100/Tommy/64HP

  This looks like the following in the terminal

  ~$ sudo bin/backup_duplicity_fullHP 
  LFTP version is 4.8.4
  Local and Remote metadata are synchronized, no sync needed.
  Last full backup date: Tue Oct  1 11:56:24 2019
  Traceback (innermost last):
File "/usr/bin/duplicity", line 107, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 93, in with_tempdir
  fn()
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1535, in 
main
  do_backup(action)
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1659, in 
do_backup
  full_backup(col_stats)
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 565, in 
full_backup
  globals.backend)
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 422, in 
write_multivol
  globals.volsize)
File "/usr/lib/python3/dist-packages/duplicity/gpg.py", line 393, in 
GPGWriteFile
  data = block_iter.__next__().data
File "/usr/lib/python3/dist-packages/duplicity/diffdir.py", line 542, in 
__next__
  result = self.process(next(self.input_iter))  # pylint: 
disable=assignment-from-no-return
File "/usr/lib/python3/dist-packages/duplicity/diffdir.py", line 680, in 
process
  data, last_block = self.get_data_block(fp)
File "/usr/lib/python3/dist-packages/duplicity/diffdir.py", line 707, in 
get_data_block
  buf = fp.read(read_size)
File "/usr/lib/python3/dist-packages/duplicity/diffdir.py", line 449, in 
read
  buf = self.infile.read(length)
File "/usr/lib/python3/dist-packages/duplicity/diffdir.py", line 417, in 
read
  log.Warn(_(u"Error %s getting delta for %s") % (str(ex), 
self.infile.uc_name))
   AttributeError: '_io.BufferedReader' object has no attribute 'uc_name'

  ~$

  Below is an excerpt from a listing of the backup directory

  ..
  ftp> open 192.168.1.100
  ftp> cd Tommy/64HP
  ftp> ls
  ..
  -rwxr-xr-x1 ftp  ftp  1048607916 Dec 01 23:38 
duplicity-full.20191201T135308Z.vol102.difftar.gpg
  -rwxr-xr-x1 ftp  ftp  1048616177 Dec 01 23:43 
duplicity-full.20191201T135308Z.vol103.difftar.gpg
  -rwxr-xr-x1 ftp  ftp  1048608039 Dec 01 23:47 
duplicity-full.20191201T135308Z.vol104.difftar.gpg
  -rwxr-xr-x1 ftp  ftp  504667096 Dec 01 23:49 
duplicity-full.20191201T135308Z.vol105.difftar.gpg
  -rwxr-xr-x1 ftp  ftp  1048619424 Dec 01 15:49 
duplicity-full.20191201T135308Z.vol11.difftar.gpg

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: duplicity 0.8.04-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Dec  2 15:16:02 2019
  InstallationDate: Installed on 2018-10-12 (415 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: duplicity
  UpgradeStatus: Upgraded to eoan on 2019-10-29 (33 days ago)

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

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

[Desktop-packages] [Bug 1855024] Re: Computer Stops Responding Shortly After Logging In

[Sebastien Bacher]

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

Title:
  Computer Stops Responding Shortly After Logging In

Status in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using Dell Precision M 4700. I was able to install Ubuntu 19.10
  using "safe graphics" mode, but after installing and rebooting into
  installed system, logging in was successful, but before showing my
  desktop, the screen continues showing violet or magenta (or whatever
  that color is), but it has some artifacts in it, and hard drive
  activity ceases, and nothing can be done except hold the power button
  until the machine powers off.

  I am therefore unable to run apport or other bug reporting utilities.
  Please let me know what I should do to make a better bug report.

  I searched and I don't think this is a "known issue" or an issue with
  a known workaround, but if I missed anything, that would be great.

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

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

[Desktop-packages] [Bug 1836462] Re: Renaming Templates to # Templates fixes speed issues present in wide range of desktop applications

[Sebastien Bacher]

Right, so it means that you declared your user dir as a template source,
which means it's building a list including every single of your files to
build the template which takes some time, that's not a bug but an user
error

** Changed in: xdg-user-dirs (Ubuntu)
   Status: New => Invalid

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

Title:
  Renaming Templates to # Templates fixes speed issues present in wide
  range of desktop applications

Status in xdg-user-dirs package in Ubuntu:
  Invalid
Status in xdg-user-dirs package in Fedora:
  Unknown

Bug description:
  
  Renaming "Templates" to "# Templates" fixes a lot of speed issues
  in a range of desktop applications, e.g.
  file managers, text editors, etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1836462/+subscriptions

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

[Desktop-packages] [Bug 1776711] Re: package gnome-software-common 3.20.5-0ubuntu0.16.04.10 failed to install/upgrade: no package named 'gnome-software-common' is installed, cannot configure

[Sebastien Bacher]

the issue looks like a corruption rather than a package bug


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

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

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

Title:
  package gnome-software-common 3.20.5-0ubuntu0.16.04.10 failed to
  install/upgrade: no package named 'gnome-software-common' is
  installed, cannot configure

Status in gnome-software package in Ubuntu:
  Invalid

Bug description:
  it is crashing everytime

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gnome-software-common 3.20.5-0ubuntu0.16.04.10
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Tue Jun 12 14:13:40 2018
  Dependencies:
   
  DuplicateSignature:
   package:gnome-software-common:3.20.5-0ubuntu0.16.04.10
   Setting up aptdaemon (1.1.1+bzr982-0ubuntu14) ...
   dpkg: error processing package gnome-software-common (--configure):
no package named 'gnome-software-common' is installed, cannot configure
  ErrorMessage: no package named 'gnome-software-common' is installed, cannot 
configure
  InstallationDate: Installed on 2018-06-12 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: gnome-software
  Title: package gnome-software-common 3.20.5-0ubuntu0.16.04.10 failed to 
install/upgrade: no package named 'gnome-software-common' is installed, cannot 
configure
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1777520] Re: package gnome-software-common 3.28.1-0ubuntu4.18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attem

[Sebastien Bacher]

the issue looks like a corruption rather than a package bug

** Changed in: gnome-software (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package gnome-software-common 3.28.1-0ubuntu4.18.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in gnome-software package in Ubuntu:
  Invalid

Bug description:
  Dont know.  tried to do update and got this automatically

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gnome-software-common 3.28.1-0ubuntu4.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Mon Jun 18 14:40:41 2018
  Dependencies:
   
  DuplicateSignature:
   package:gnome-software-common:3.28.1-0ubuntu4.18.04.1
   Unpacking wireless-regdb (2018.05.09-0ubuntu1~18.04.1) over 
(2016.06.10-0ubuntu1) ...
   dpkg: error processing package gnome-software-common (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2014-12-14 (1282 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: gnome-software
  Title: package gnome-software-common 3.28.1-0ubuntu4.18.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to bionic on 2018-05-04 (45 days ago)

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

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

[Desktop-packages] [Bug 1798213] Re: package gnome-software-common 3.30.2-0ubuntu4 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intenta

[Sebastien Bacher]

the issue looks like a corruption rather than a package bug


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

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

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

Title:
  package gnome-software-common 3.30.2-0ubuntu4 failed to
  install/upgrade: El paquete está en un estado grave de inconsistencia
  - debe reinstalarlo  antes de intentar su configuración.

Status in gnome-software package in Ubuntu:
  Invalid

Bug description:
  rocesando disparadores para hicolor-icon-theme (0.17-2) ...
  dpkg: problemas de dependencias impiden la configuración de ubuntu-software:
   ubuntu-software depende de gnome-software (>= 3.30.2-0ubuntu4); sin embargo:
   El paquete `gnome-software' no está configurado todavía.

  dpkg: error al procesar el paquete ubuntu-software (--configure):
   problemas de dependencias - se deja sin configurar
  dpkg: problemas de dependencias impiden la configuración de 
gnome-software-plugin-snap:
   gnome-software-plugin-snap depende de gnome-software (= 3.30.2-0ubuntu4); 
sin embargo:
   El paquete `gnome-software' no está configurado todavía.

  dpkg: error al procesar el paquete gnome-software-plugin-snap (--configure):
   problemas de dependencias - se deja sin configurar
  No se escribió un informe «apport» porque el mensaje de error indica que es 
un mensaje de error asociado a un fallo previo.

 No se escribió ningún informe 
«apport» porque ya se ha alcanzado el valor de «MaxReports»

  Se encontraron errores al procesar:
   gnome-software-common
   gnome-software
   ubuntu-software
   gnome-software-plugin-snap
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: gnome-software-common 3.30.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Oct 16 19:19:06 2018
  Dependencies:
   
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2018-10-15 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.30.2-0ubuntu4
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.0
  SourcePackage: gnome-software
  Title: package gnome-software-common 3.30.2-0ubuntu4 failed to 
install/upgrade: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1854633] Re: touchpad only works as mouse, no touchpad features

[joshua pritikin]

Ah ha! This is a bug, but it gets resolved after a laptop suspend-resume
cycle. That is, the touchpad is not detected after a reboot. However, it
is detected after the next suspend-resume.

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

Title:
  touchpad only works as mouse, no touchpad features

Status in xserver-xorg-input-libinput package in Ubuntu:
  Invalid

Bug description:
  I've never had a problem before. The touchpad worked great on all
  Ubuntu releases including Eoan until I installed the latest updates
  today. I generally use Wayland. I haven't tested the touchpad on X11.

  Description:  Ubuntu 19.10
  Release:  19.10

  xserver-xorg-input-libinput:
Installed: 0.29.0-1
Candidate: 0.29.0-1
Version table:
   *** 0.29.0-1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1854633/+subscriptions

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

[Desktop-packages] [Bug 1854590] Re: No ComposeKey sequence for ≈ (almost equal) and ≅ (approximately equal)

[Sebastien Bacher]

Thank you for your bug report, could you report it upstream on
https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/ ?

** Package changed: xorg (Ubuntu) => xkeyboard-config (Ubuntu)

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

Title:
  No ComposeKey sequence for ≈ (almost equal) and ≅ (approximately
  equal)

Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  I don't know much, so forgive me if I use the wrong terminology.

  Problem:
  There is no ComposeKey mapping for the symbols ≈ (Unicode 2248) and ≅ 
(Unicode 2248) in Compose Tables.

  Details:
  According to  https://help.ubuntu.com/community/ComposeKey  the files such as 
 /usr/share/X11/locale/en_US.UTF-8/Compose  have all ComposeKey combinations to 
type special symbols, characters and graphemes.
  Two standard graphemes (≈ and ≅) seem to be missing from multiple compose 
files although their negated versions (are present mapped to compositions

  Solution?!: I propose this (but wouldn't know how to commit it except by 
filing a bug - if it's straightforward to improve Linux, then please tell me 
how!  I'd love to commit something to the code!
  I added these lines to a copy of the  compose  file that I made at ~/.Xcompose
  I propose that they should be added to the multiple, original  Compose  files 
in:
/usr/share/X11/locale/en_US.UTF-8/Compose
/usr/share/X11/locale/iso8859-1/Compose
/usr/share/X11/locale/iso8859-15/Compose
   etc etc etc

  # _Added by Jackalux_
  : "≅"   U2245 # APPROXIMATELY OR 
ACTUALLY EQUAL TO
  : "≅"   U2245 # APPROXIMATELY OR 
ACTUALLY EQUAL TO
 : "≈"   U2248 # ALMOST EQUAL TO
  # End of Jackalux's additions

  
  Notes:
  The list at 
https://www.x.org/releases/X11R7.7/doc/libX11/i18n/compose/en_US.UTF-8.html 
also misses combinations for ≈ and ≅ .   Perhaps that should be updated too if 
it is a reference list.

  I also wanted to add:
   : "≇"   U2247 # NEITHER 
APPROXIMATELY NOR ACTUALLY EQUAL TO
   : "≇"   U2247 # NEITHER 
APPROXIMATELY NOR ACTUALLY EQUAL TO
   : "≇"   U2247 # NEITHER 
APPROXIMATELY NOR ACTUALLY EQUAL TO
   : "≇"   U2247 # NEITHER 
APPROXIMATELY NOR ACTUALLY EQUAL TO
  : "≉"   U2249 # NOT ALMOST 
EQUAL TO
  : "≉"   U2249 # NOT ALMOST 
EQUAL TO
  But I've realised that they create clashes with other compositions, as the 
composition forms before the ComposeKey is released.
  If this can be corrected and added at the same time, then that would be 
amazing as I don't know how to access the actual compositions listed for those 
characters.

  Co-operatively,
  Jackalux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1854590/+subscriptions

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

[Desktop-packages] [Bug 1609700] Re: username is not saved in openconnect connection dialog

[GeekSmith]

Not deprecated unless it happened very quietly.

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

Title:
  username is not saved in openconnect connection dialog

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager-openconnect package in Ubuntu:
  Fix Released
Status in Fedora:
  Fix Released

Bug description:
  
  Hi,

  I clicked on "save passwords" but only the password is filled in
  automatically when I open the connection dialog. The "Username" field
  is empty!

  This happens for a SSLVPN configuration.

  For another VPN config (don't know which type) everything is ok.

  
  openconnect: 7.06-2build2

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

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

[Desktop-packages] [Bug 1723758]

[Martin-peres-n]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/xorg/driver/xf86-video-
nouveau/issues/251.

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

Title:
  Xorg X11 nouveau video driver for NVIDIA graphics chipsets locks up
  (hangs)

Status in Nouveau Xorg driver:
  Unknown
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed
Status in Fedora:
  Confirmed

Bug description:
  This is an intermittent issue. Rumored to be fixed in Ubuntu 17.04
  according to comments in bug 1645375

  Oct 15 11:36:26 lakshmi kernel: nouveau :01:00.0: timeout at
  /build/linux-
  
Pcn0xK/linux-4.4.0/drivers/gpu/drm/nouveau/nvkm/engine/fifo/chang84.c:111/g84_fifo_chan_engine_fini()!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-nouveau 1:1.0.12-1build2
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  .tmp.unity_support_test.0:

  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Oct 15 12:27:28 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   iscsitarget, 1.4.20.3+svn502, 4.4.0-96-generic, x86_64: installed
   iscsitarget, 1.4.20.3+svn502, 4.4.0-97-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GT218 [GeForce 210] 
[1462:2011]
  InstallationDate: Installed on 2016-01-13 (641 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  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=/vmlinuz-4.4.0-97-generic 
root=/dev/mapper/vg0-lv0 ro
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3029
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A89GTD-PRO/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3029:bd07/05/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Oct 12 15:08:58 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputMicrosoft Comfort Curve Keyboard 2000 KEYBOARD, id 8
   inputMicrosoft Comfort Curve Keyboard 2000 KEYBOARD, id 9
   inputMicrosoft Comfort Optical Mouse 1000 MOUSE, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.6
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1723758] Re: Xorg X11 nouveau video driver for NVIDIA graphics chipsets locks up (hangs)

[Bug Watch Updater]

** Changed in: nouveau
   Status: Confirmed => Unknown

** Bug watch added: 
gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues #251
   https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/251

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

Title:
  Xorg X11 nouveau video driver for NVIDIA graphics chipsets locks up
  (hangs)

Status in Nouveau Xorg driver:
  Unknown
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed
Status in Fedora:
  Confirmed

Bug description:
  This is an intermittent issue. Rumored to be fixed in Ubuntu 17.04
  according to comments in bug 1645375

  Oct 15 11:36:26 lakshmi kernel: nouveau :01:00.0: timeout at
  /build/linux-
  
Pcn0xK/linux-4.4.0/drivers/gpu/drm/nouveau/nvkm/engine/fifo/chang84.c:111/g84_fifo_chan_engine_fini()!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-nouveau 1:1.0.12-1build2
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  .tmp.unity_support_test.0:

  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Oct 15 12:27:28 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   iscsitarget, 1.4.20.3+svn502, 4.4.0-96-generic, x86_64: installed
   iscsitarget, 1.4.20.3+svn502, 4.4.0-97-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GT218 [GeForce 210] 
[1462:2011]
  InstallationDate: Installed on 2016-01-13 (641 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  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=/vmlinuz-4.4.0-97-generic 
root=/dev/mapper/vg0-lv0 ro
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3029
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A89GTD-PRO/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3029:bd07/05/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Oct 12 15:08:58 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputMicrosoft Comfort Curve Keyboard 2000 KEYBOARD, id 8
   inputMicrosoft Comfort Curve Keyboard 2000 KEYBOARD, id 9
   inputMicrosoft Comfort Optical Mouse 1000 MOUSE, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.6
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1855165] Re: gvfsd-dav crashed with SIGSEGV

[Praveen B]

How can I provide more useful debugging information? Are there any dbg /
symbols packages that I can download?

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

Title:
  gvfsd-dav crashed with SIGSEGV

Status in gvfs package in Ubuntu:
  New

Bug description:
  Setup
  Lubuntu 19.10

  Steps to Reproduce
  * Using the file manager, pcmanfm-qt, perform a secure webdav mount using 
'Go' -> 'Connect to server' option
  * After mounting the remote dav folder, attempt to perform a copy of a large 
file (> 500M) from local machine to remote folder

  Expected behavior
  File copy should succeed

  Observed behavior
  file manager crashes and the mount is no longer present

  Additional Information
  When I attempted to gather more information by attaching gdb to the gfvsd-dav 
process, I was unable to reproduce the problem. Without gdb, problem readily 
reproduces at my end.

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

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

[Desktop-packages] [Bug 1855165] [NEW] gvfsd-dav crashed with SIGSEGV

[Praveen B]

Public bug reported:

Setup
Lubuntu 19.10

Steps to Reproduce
* Using the file manager, pcmanfm-qt, perform a secure webdav mount using 'Go' 
-> 'Connect to server' option
* After mounting the remote dav folder, attempt to perform a copy of a large 
file (> 500M) from local machine to remote folder

Expected behavior
File copy should succeed

Observed behavior
file manager crashes and the mount is no longer present

Additional Information
When I attempted to gather more information by attaching gdb to the gfvsd-dav 
process, I was unable to reproduce the problem. Without gdb, problem readily 
reproduces at my end.

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


** Tags: webdav

** Attachment added: "Crash file from /var/crash"
   
https://bugs.launchpad.net/bugs/1855165/+attachment/5309816/+files/_usr_lib_gvfs_gvfsd-dav.999.crash

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

Title:
  gvfsd-dav crashed with SIGSEGV

Status in gvfs package in Ubuntu:
  New

Bug description:
  Setup
  Lubuntu 19.10

  Steps to Reproduce
  * Using the file manager, pcmanfm-qt, perform a secure webdav mount using 
'Go' -> 'Connect to server' option
  * After mounting the remote dav folder, attempt to perform a copy of a large 
file (> 500M) from local machine to remote folder

  Expected behavior
  File copy should succeed

  Observed behavior
  file manager crashes and the mount is no longer present

  Additional Information
  When I attempted to gather more information by attaching gdb to the gfvsd-dav 
process, I was unable to reproduce the problem. Without gdb, problem readily 
reproduces at my end.

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

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

[Desktop-packages] [Bug 1843695] Re: Freeze after suspend to RAM nvidia kernel 5.0.0.x

[Michal Siatkowski]

Yey it works with 440!
Thanks a lot!

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

Title:
  Freeze after suspend to RAM nvidia kernel 5.0.0.x

Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed

Bug description:
  The computer is a notebook model PB71RD from Clevo. The problem happens in 
all Clevo models:
  P960E*, P970E*, P960R*, P970R*, P960RC*, P970RC, PB51E*, PB71E*, PB51R*, 
PB71R*
  with mainboard identifiers (cat /sys/devices/virtual/dmi/id/board_name):
  - P95_96_97Ex_Rx
  - PB50_70EF_ED_EC
  - PB50_70RF_RD_RC
  - P9XXRC

  and NVIDIA GPU (in this case: GeForce RTX 2060 and also on GeForce GTX
  1660 Ti).

  The problem only happens with kernel >= 5.0.0 and using the NVIDIA 
proprietary driver.
  On kernel 4.18 suspend works without problems on both GPU's (NVIDIA and Intel)
  When using the Intel GPU or the nouveau driver then suspend works without 
problems.
  With kernel 4.18 suspend works without problems on both GPU's.

   | NVIDIA proprietary | Intel GPU | nouveau |
  | kernel 4.18| works  | works | works   |
  | kernel 5.0.0.x | no suspend | works | works   |

  I have tried different proprietary drivers, official Ubuntu Versions
  and from PPA: 418 430.26 435.21

  The notebook has a hybrid GPU configuration with NVIDIA and Intel
  GPUs.

  The notebook goes into suspend when pressing the suspend button (Fn-
  suspend).

  When pressing the suspend button again, the power button light goes on
  and nothing else happens.

   | power button | power LED | Battery LED | HD LED
  Notebook on  | on   | on| on  | sporadic
  suspend  | off  | blinking  | on  | off
  freeze after | on   | on| on  | off
  activated
  from STR

  
  The system is a Ubuntu 18.04.3

  cat /etc/issue:
  Ubuntu 18.04.3 LTS \n \l

  uname -a:
  Linux test-notebook 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 
03:00:32 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  I first thought that it could be an ACPI-Problem. I reluctantly tried
  acpi_osi=linux and all other OS's (as listed in: strings
  /sys/firmware/acpi/tables/DSDT | grep -i windows | sort) for
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub

  Also acpi_os_name=linux

  Also tried to blacklist the nouveau driver.

  Nothing helped.

  Then i found out that a driver from pop-os launchpad worked. I posted
  a possible solution on the button of this message.

  LOGFILES:
  I will attach now the logfiles as required on the Ubuntu Website 
DebuggingKernelSuspend (https://wiki.ubuntu.com/DebuggingKernelSuspend)

  dmesg.txt from: sh -c "sync && echo 1 > /sys/power/pm_trace && pm-
  suspend"

  I think the problem might be this:
  [2.797119]   Magic number: 2:1:0
  [2.797623] memory memory48: hash matches

  Answers to DebuggingKernelSuspend:
  1. the system freezes when comming back from STR
  2. suspend was activated by pressing: Fn+suspendButton
  3. resume was activated by pressing: Fn+suspendButton
  4. As required i installed the newest non-daily mainline kernel (v5.3-rc8)
  now the notebook refuses to go into freeze at all, it just returns to the 
desktop
  As the fix described below works only on kernel 5.0.0.x i will continue with 
information gathered with the kernel 5.0.0.27-generic

  The logs are all attached to this message.

  POSSIBLE SOLUTION:

  The solution i found was a patch for nvidia-kernel-source-435

  pop-os included the patch into nvidia-dkms-435:

  diff --git a/nvidia/nv.c b/nvidia/nv.c
  index b6dc6f3..ed250c8 100644
  --- a/nvidia/nv.c
  +++ b/nvidia/nv.c
  @@ -4200,8 +4200,6 @@ nv_power_management(
   nv_kthread_q_stop(&nvl->bottom_half_q);

   nv_disable_pat_support();
  -
  -pci_save_state(nvl->pci_dev);
   break;
   }
   case NV_PM_ACTION_RESUME:

  
  I testet it with different notebook models from Clevo with a different 
hardware than mentioned above . It had no adverse effects so far.

  Is this a possible solution? Could this be sent upstream? I would
  gladly provide more information if necessary.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-driver-430 430.26-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 12 11:52:09 2019
  InstallationDate: Installed on 2019-09-12 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: nvidia-graphics-drivers-430
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Desktop-packages] [Bug 1855172] [NEW] Synaptics s3203 touchpad on Dell Inspiron 15 5547 has no working after recent upgrade

[Fabrício Pereira]

Public bug reported:

I upgraded my Ubuntu 18.04 with the `apt upgrade` command, and the kernel 
upgrade to 4.15.0-72.
After a reboot, the touchpad stopped working. And the external USB mouse kept 
working fine.

Looking for this issue, I found these reports about similar problems
(https://sangams.com.np/fix-ubuntu-18-4-touchpad-not-working-properly/
and https://askubuntu.com/questions/1041820/touchpad-not-working-on-
ubuntu-18-04), and I checked the package `xserver-xorg-input-synaptics`
wasn't installed.

Then I tried to install with the command: `apt install 
xserver-xorg-input-synaptics`.
I rebooted the computer, but the problem continues.

After I ran a diagnostic test with BIOS from Dell Notebook, and on
interacting with the diagnostic system, I was able to use the touchpad
without problems.

Then I suppose this problem is from SO kernel upgraded.

=
Follow some info's system:

$uname -a
Linux myinspiron155547 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

$ xinput
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ Synaptics s3203   id=11   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Video Bus id=7[slave  keyboard (3)]
↳ Power Button  id=8[slave  keyboard (3)]
↳ Sleep Button  id=9[slave  keyboard (3)]
↳ Integrated_Webcam_HD: Integrate   id=10   [slave  keyboard (3)]
↳ Dell WMI hotkeys  id=12   [slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=13   [slave  keyboard (3)]

** Affects: xserver-xorg-input-synaptics (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: synaptics touchpad

** Description changed:

  I upgraded my Ubuntu 18.04 with the `apt upgrade` command, and the kernel 
upgrade to 4.15.0-72.
- After a reboot, the touchpad stopped working. And the external USB mouse 
works fine.
+ After a reboot, the touchpad stopped working. And the external USB mouse kept 
working fine.
  
  Looking for this issue, I found these reports about similar problems
  (https://sangams.com.np/fix-ubuntu-18-4-touchpad-not-working-properly/
  and https://askubuntu.com/questions/1041820/touchpad-not-working-on-
  ubuntu-18-04), and I checked the package `xserver-xorg-input-synaptics`
  wasn't installed.
  
  Then I tried to install with the command: `apt install 
xserver-xorg-input-synaptics`.
  I rebooted the computer, but the problem continues.
  
  After I ran a diagnostic test with BIOS from Dell Notebook, and on
  interacting with the diagnostic system, I was able to use the touchpad
  without problems.
  
  Then I suppose this problem is from SO kernel upgraded.
  
  =
  Follow some info's system:
  
  $uname -a
  Linux myinspiron155547 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
  
  $ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Synaptics s3203 id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
- ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
- ↳ Power Buttonid=6[slave  
keyboard (3)]
- ↳ Video Bus   id=7[slave  
keyboard (3)]
- ↳ Power Buttonid=8[slave  
keyboard (3)]
- ↳ Sleep Buttonid=9[slave  
keyboard (3)]
- ↳ Integrated_Webcam_HD: Integrate id=10   [slave  
keyboard (3)]
- ↳ Dell WMI hotkeysid=12   [slave  
keyboard (3)]
- ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
+ ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
+ ↳ Power Buttonid=6[slave  
keyboard (3)]
+ ↳ Video Bus   id=7[slave  
keyboard (3)]
+ ↳ Power Buttonid=8[slave  
keyboard (3)]
+ ↳ Sleep Buttonid=9[slave  
keyboard (3)]
+ ↳ Integrated_Webcam_HD: Integrate id=10   [slave  
keyboard (3)]
+ ↳ Dell WMI hotkeysid=12   [slave  
keyboard (3)]
+ ↳ AT Translated Set 2 keyboard 

[Desktop-packages] [Bug 1855168] [NEW] Keep only numbers in the url

[klfytklfyt]

Public bug reported:

.

If you delete everything except numbers in the url
browser becomes faster - can you confirm?  :))

Additional information:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839716

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

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

Title:
  Keep only numbers in the url

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  .

  If you delete everything except numbers in the url
  browser becomes faster - can you confirm?  :))

  Additional information:
  https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839716

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

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

[Desktop-packages] [Bug 1855065] Re: Thumbnail graphics of open file dialogue are impossibly tiny

[klfytklfyt]

R you kidding me?  o_O(it's the open file dialogue)

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

Title:
  Thumbnail graphics of open file dialogue are impossibly tiny

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  
  It's unfortunately impossible to understand what you see
  due to the small size of thumbnail graphics. I would
  make them at least 4 times larger.

  :))

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

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

[Desktop-packages] [Bug 1855168] Re: Keep only numbers in the url

[klfytklfyt]

** Description changed:

+ .
  
  If you delete everything except numbers in the url
  browser becomes faster - can you confirm?  :))
  
- 
  Additional information:
  https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839716

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

Title:
  Keep only numbers in the url

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  .

  If you delete everything except numbers in the url
  browser becomes faster - can you confirm?  :))

  Additional information:
  https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839716
  https://bugs.launchpad.net/ubuntu/+source/chromium/+bug/1854615

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

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

[Desktop-packages] [Bug 1839716] Re: There is infinite loop in address bar

[klfytklfyt]

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


< https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1855168

>:]

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

Title:
  There is infinite loop in address bar

Status in Chromium Browser:
  New
Status in chromium-browser package in Ubuntu:
  Invalid
Status in chromium package in Fedora:
  Invalid

Bug description:
  There seems to be infinite loop in the address bar
  if you fill it with letter f

  
https://bugs.launchpad.net/ubuntu/+source/nautilus/+filebug

  then scrolling and page loading becomes faster.

  :))

  two spaces
  https://bugzilla.redhat.com/show_bug.cgi?id=1754300#c5

  delete numbers
  https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1855168

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

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

[Desktop-packages] [Bug 1839716] Re: There is infinite loop in address bar

[klfytklfyt]

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


It's even better if you delete everything except numbers
(I start from the end and use Shift+Left key combo and delete symbols including 
letters with delete key),
can you confirm?

>:]  https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1855106


** Description changed:

  There seems to be infinite loop in the address bar
  if you fill it with letter f
  
  
https://bugs.launchpad.net/ubuntu/+source/nautilus/+filebug
  
  then scrolling and page loading becomes faster.
  
  :))
  
- 
  two spaces
  https://bugzilla.redhat.com/show_bug.cgi?id=1754300#c5
+ 
+ delete numbers
+ https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1855106

** Description changed:

  There seems to be infinite loop in the address bar
  if you fill it with letter f
  
  
https://bugs.launchpad.net/ubuntu/+source/nautilus/+filebug
  
  then scrolling and page loading becomes faster.
  
  :))
  
  two spaces
  https://bugzilla.redhat.com/show_bug.cgi?id=1754300#c5
  
  delete numbers
- https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1855106
+ https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1855168

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

Title:
  There is infinite loop in address bar

Status in Chromium Browser:
  New
Status in chromium-browser package in Ubuntu:
  Invalid
Status in chromium package in Fedora:
  Invalid

Bug description:
  There seems to be infinite loop in the address bar
  if you fill it with letter f

  
https://bugs.launchpad.net/ubuntu/+source/nautilus/+filebug

  then scrolling and page loading becomes faster.

  :))

  two spaces
  https://bugzilla.redhat.com/show_bug.cgi?id=1754300#c5

  delete numbers
  https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1855168

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

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

[Desktop-packages] [Bug 1855168] Re: Keep only numbers in the url

[klfytklfyt]

** Description changed:

  .
  
  If you delete everything except numbers in the url
  browser becomes faster - can you confirm?  :))
  
  Additional information:
  https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839716
+ https://bugs.launchpad.net/ubuntu/+source/chromium/+bug/1854615

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

Title:
  Keep only numbers in the url

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  .

  If you delete everything except numbers in the url
  browser becomes faster - can you confirm?  :))

  Additional information:
  https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839716
  https://bugs.launchpad.net/ubuntu/+source/chromium/+bug/1854615

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

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

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

[Dan Streetman]

** Description changed:

  [impact]
  
- most or all autopkgtests fail on s390x
+ 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]
  
- TBD
+ 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]
+ 
+ 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.

** Description changed:

  [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]
  
- 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.
+ 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.

** Description changed:

  [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 i

[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10

[Owen Williams]

I have very inconsistent copy/paste under Wayland.  Usually switching
windows and trying again fixes it, but I'd give the success rate of a
copy command working at 75%.

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

Title:
  [X11] copy/paste (clipboard) is broken in Ubuntu 19.10

Status in LibreOffice:
  Confirmed
Status in Mutter:
  New
Status in libreoffice package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in libreoffice source package in Eoan:
  Triaged
Status in mutter source package in Eoan:
  Triaged

Bug description:
  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

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

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

  There is some discussion of the problem here:

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

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

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

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

  It seems like that could be related.

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

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

[Desktop-packages] [Bug 1855183] [NEW] autopkgtest fails on i386 because linux-headers-generic no longer built for i386

[Dan Streetman]

Public bug reported:

[impact]

the kernel is no longer built for i386, starting with Eoan.  However
some of the autopkgtests depend on linux-headers-generic, which isn't
available for i386, so the test fails with bad dependency.

[test case]

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

Broken autopkgtest-satdep:i386 Depends on linux-headers-generic:i386 < none @un 
H >
  Removing autopkgtest-satdep:i386 because I can't find 
linux-headers-generic:i386

[regression potential]

test case fix only, regressions would involve more/continued test
failure

** Affects: network-manager (Ubuntu)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

** Affects: network-manager (Ubuntu Eoan)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

** Affects: network-manager (Ubuntu Focal)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

** Also affects: network-manager (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: network-manager (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: network-manager (Ubuntu Eoan)
   Status: New => In Progress

** Changed in: network-manager (Ubuntu Focal)
   Status: New => In Progress

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

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

** Changed in: network-manager (Ubuntu Eoan)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: network-manager (Ubuntu Focal)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

Title:
  autopkgtest fails on i386 because linux-headers-generic no longer
  built for i386

Status in network-manager package in Ubuntu:
  In Progress
Status in network-manager source package in Eoan:
  In Progress
Status in network-manager source package in Focal:
  In Progress

Bug description:
  [impact]

  the kernel is no longer built for i386, starting with Eoan.  However
  some of the autopkgtests depend on linux-headers-generic, which isn't
  available for i386, so the test fails with bad dependency.

  [test case]

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

  Broken autopkgtest-satdep:i386 Depends on linux-headers-generic:i386 < none 
@un H >
Removing autopkgtest-satdep:i386 because I can't find 
linux-headers-generic:i386

  [regression potential]

  test case fix only, regressions would involve more/continued test
  failure

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

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

[Desktop-packages] [Bug 1855168] Re: Keep only numbers in the url

[Olivier Tilloy]

Do you have actual measurements to back up this theory?

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

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

Title:
  Keep only numbers in the url

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  .

  If you delete everything except numbers in the url
  browser becomes faster - can you confirm?  :))

  Additional information:
  https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839716
  https://bugs.launchpad.net/ubuntu/+source/chromium/+bug/1854615

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

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

[Desktop-packages] [Bug 1845385] Re: Touchpad click-drag action broken after close-lid suspend, Lenovo X1C5, Bionic

[Launchpad Bug Tracker]

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

** Changed in: xserver-xorg-input-libinput (Ubuntu)
   Status: New => Confirmed

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

Title:
  Touchpad click-drag action broken after close-lid suspend, Lenovo
  X1C5, Bionic

Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  - observe touchpad click-drag* working normally (i.e. can click touchpad and 
drag an icon, or select text in any direction)
  - close lid to suspend (need to wait some time until red Thinkpad light above 
'i' on lid starts to flash
  - open lid to resume
  - observe touchpad click-drag NOT working. Can click but not drag, or can 
only drag very short distance/awkwardly

  *depressing the touchpad surface until it clicks, with one finger (usually 
index) and with the touchpad clicked down, dragging on the touchpad with 
another finger (middle) to move the item selected via the click.
  typical uses to test: click a window titlebar and move it using drag
  click a desktop icon and move it using drag
  click to being select in text area of an app and drag to extend selection

  
  Also note:
  - sudo moidprobe -r psmouse
  - sudo modprobe psmouse
  restores expected functionaly

  Similar symptoms to several related bugs (see below) but reporting 
separately, since:
  - issue still present on later hardware and software than previously reported
  - issue still present despite full firmware updates
  - slightly different experience with workaround (i.e modprobe -r psmouse / 
modprobe psmouse does restore functionality

  Related bugs:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427
  https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1727130
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1728778

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-input-libinput 0.27.1-1
  ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18
  Uname: Linux 4.15.0-64-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 25 21:29:07 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  InstallationDate: Installed on 2018-11-22 (306 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 138a:0097 Validity Sensors, Inc.
   Bus 001 Device 003: ID 13d3:5682 IMC Networks
   Bus 001 Device 002: ID 8087:0a2b Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20HRCTO1WW
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-64-generic 
root=/dev/mapper/system-root ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-input-libinput
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/16/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET54W (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET54W(1.39):bd04/16/2019:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  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/xserver-xorg-input-libinput/+bug/1845385/+subscriptions

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

[Desktop-packages] [Bug 1855065] Re: Thumbnail graphics of open file dialogue are impossibly tiny

[Sebastien Bacher]

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

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

Title:
  Thumbnail graphics of open file dialogue are impossibly tiny

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  
  It's unfortunately impossible to understand what you see
  due to the small size of thumbnail graphics. I would
  make them at least 4 times larger.

  :))

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

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

[Desktop-packages] [Bug 1511473]

[Martin-peres-n]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/xorg/driver/xf86-video-
nouveau/issues/227.

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

Title:
  nouveau E[PBUS][:01:00.0] MMIO read of 0x FAULT at
  0x002140 [ !ENGINE ]

Status in Nouveau Xorg driver:
  Unknown
Status in xorg package in Ubuntu:
  Won't Fix

Bug description:
  dmesg:
  [  163.227218] nouveau E[PBUS][:01:00.0] MMIO read of 0x 
FAULT at 0x002140 [ !ENGINE ]

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.360
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Oct 29 02:22:19 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Device [144d:c650]
   NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Samsung Electronics Co Ltd Device [144d:c650]
  LiveMediaBuild: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. Q470C/500P4C
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper quiet splash ---
  SourcePackage: xserver-xorg-video-nouveau
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P02RAB
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP500P4C-S02CL
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP02RAB:bd08/29/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pnQ470C/500P4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP500P4C-S02CL:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: Q470C/500P4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Thu Oct 29 02:14:13 2015
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13897 
   vendor SEC
  xserver.version: 2:1.17.1-0ubuntu3

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

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

[Desktop-packages] [Bug 1511473] Re: nouveau E[ PBUS][0000:01:00.0] MMIO read of 0x00000000 FAULT at 0x002140 [ !ENGINE ]

[Bug Watch Updater]

** Changed in: nouveau
   Status: Confirmed => Unknown

** Bug watch added: 
gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues #227
   https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/227

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

Title:
  nouveau E[PBUS][:01:00.0] MMIO read of 0x FAULT at
  0x002140 [ !ENGINE ]

Status in Nouveau Xorg driver:
  Unknown
Status in xorg package in Ubuntu:
  Won't Fix

Bug description:
  dmesg:
  [  163.227218] nouveau E[PBUS][:01:00.0] MMIO read of 0x 
FAULT at 0x002140 [ !ENGINE ]

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.360
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Oct 29 02:22:19 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Device [144d:c650]
   NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Samsung Electronics Co Ltd Device [144d:c650]
  LiveMediaBuild: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. Q470C/500P4C
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper quiet splash ---
  SourcePackage: xserver-xorg-video-nouveau
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P02RAB
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP500P4C-S02CL
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP02RAB:bd08/29/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pnQ470C/500P4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP500P4C-S02CL:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: Q470C/500P4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Thu Oct 29 02:14:13 2015
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13897 
   vendor SEC
  xserver.version: 2:1.17.1-0ubuntu3

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

-- 
Mailing list: https://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 1855172] Synaptics s3203 touchpad on Dell Inspiron 15 5547 has no working after recent upgrade

[A. Richard Miller]

This one-line fix (which was in your askubuntu... link) has worked well 
for us on various notebook touchpads from Ubuntu 18.04 through

|
> 19.10:Installing below package will resolve the touchpad issues on 
> |Ubuntu 18.04|.
> |sudo apt install xserver-xorg-input-synaptics ||


Cheers from
--Dick Miller, Partner, MMS mailto:themill...@millermicro.com>>
Co-Leader, FOSS User Group at Natick Community-Senior Center 



On 12/4/19 2:43 PM, Fabrício Pereira wrote:
> Public bug reported:
>
> I upgraded my Ubuntu 18.04 with the `apt upgrade` command, and the kernel 
> upgrade to 4.15.0-72.
> After a reboot, the touchpad stopped working. And the external USB mouse kept 
> working fine.
>
> Looking for this issue, I found these reports about similar problems
> (https://sangams.com.np/fix-ubuntu-18-4-touchpad-not-working-properly/
> and https://askubuntu.com/questions/1041820/touchpad-not-working-on-
> ubuntu-18-04), and I checked the package `xserver-xorg-input-synaptics`
> wasn't installed.
>
> Then I tried to install with the command: `apt install 
> xserver-xorg-input-synaptics`.
> I rebooted the computer, but the problem continues.
>
> After I ran a diagnostic test with BIOS from Dell Notebook, and on
> interacting with the diagnostic system, I was able to use the touchpad
> without problems.
>
> Then I suppose this problem is from SO kernel upgraded.
>
> =
> Follow some info's system:
>
> $uname -a
> Linux myinspiron155547 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 
> UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
>
> $ xinput
> ⎡ Virtual core pointerid=2[master pointer  (3)]
> ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
>  (2)]
> ⎜   ↳ Synaptics s3203 id=11   [slave  pointer 
>  (2)]
> ⎣ Virtual core keyboard   id=3[master keyboard (2)]
>  ↳ Virtual core XTEST keyboardid=5[slave  
> keyboard (3)]
>  ↳ Power Button   id=6[slave  
> keyboard (3)]
>  ↳ Video Bus  id=7[slave  
> keyboard (3)]
>  ↳ Power Button   id=8[slave  
> keyboard (3)]
>  ↳ Sleep Button   id=9[slave  
> keyboard (3)]
>  ↳ Integrated_Webcam_HD: Integrateid=10   [slave  
> keyboard (3)]
>  ↳ Dell WMI hotkeys   id=12   [slave  
> keyboard (3)]
>  ↳ AT Translated Set 2 keyboard   id=13   [slave  
> keyboard (3)]
>
> ** Affects: xserver-xorg-input-synaptics (Ubuntu)
>   Importance: Undecided
>   Status: New
>
>
> ** Tags: synaptics touchpad
>
> ** Description changed:
>
>I upgraded my Ubuntu 18.04 with the `apt upgrade` command, and the kernel 
> upgrade to 4.15.0-72.
> - After a reboot, the touchpad stopped working. And the external USB mouse 
> works fine.
> + After a reboot, the touchpad stopped working. And the external USB mouse 
> kept working fine.
>
>Looking for this issue, I found these reports about similar problems
>(https://sangams.com.np/fix-ubuntu-18-4-touchpad-not-working-properly/
>and https://askubuntu.com/questions/1041820/touchpad-not-working-on-
>ubuntu-18-04), and I checked the package `xserver-xorg-input-synaptics`
>wasn't installed.
>
>Then I tried to install with the command: `apt install 
> xserver-xorg-input-synaptics`.
>I rebooted the computer, but the problem continues.
>
>After I ran a diagnostic test with BIOS from Dell Notebook, and on
>interacting with the diagnostic system, I was able to use the touchpad
>without problems.
>
>Then I suppose this problem is from SO kernel upgraded.
>
>=
>Follow some info's system:
>
>$uname -a
>Linux myinspiron155547 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 
> 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
>
>$ xinput
>⎡ Virtual core pointer id=2[master pointer  (3)]
>⎜   ↳ Virtual core XTEST pointer   id=4[slave  pointer 
>  (2)]
>⎜   ↳ Synaptics s3203  id=11   [slave  pointer 
>  (2)]
>⎣ Virtual core keyboardid=3[master keyboard (2)]
> - ↳ Virtual core XTEST keyboard   id=5[slave  
> keyboard (3)]
> - ↳ Power Button  id=6[slave  
> keyboard (3)]
> - ↳ Video Bus id=7[slave  
> keyboard (3)]
> - ↳ Power Button  id=8[slave  
> keyboard (3)]
> - ↳ Sleep Button  id=9[slave  
> keyboard (3)]
> - ↳ Integrated_Webcam_HD: Integrate   id=10   [slave  
> keyboard (3)]
> - ↳ Dell WMI