date:20190808

** Tags added: eoan

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

Title:
  LucidSound LS31 only outputs mono sound

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  LucidSound LS31 only outputs mono sound.

  The usb vendor:prod = 2f12:0109.

  The fix is incoming.

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

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

[Desktop-packages] [Bug 1839580] Re: LucidSound LS31 only outputs mono sound

2019-08-08 Thread Dave Chiluk

Upstream merge request.
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/merge_requests/143

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

Title:
  LucidSound LS31 only outputs mono sound

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  LucidSound LS31 only outputs mono sound.

  The usb vendor:prod = 2f12:0109.

  The fix is incoming.

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

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

[Desktop-packages] [Bug 225361] Re: .gvfs can't be stat'd by root causing backup tools to fail

2019-08-08 Thread windowsguy

.gvfs can't be removed on a 18.04-equivalent OS.

$ sudo rm -rf .gvfs 
[sudo] password for me:  
rm: cannot remove '.gvfs': Device or resource busy

$ uname -a
Linux me 4.15.0-54-lowlatency #58-Ubuntu SMP PREEMPT Mon Jun 24 11:45:10 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

$ cat /etc/lsb-release 
DISTRIB_ID=LinuxMint
DISTRIB_RELEASE=19.2
DISTRIB_CODENAME=tina
DISTRIB_DESCRIPTION="Linux Mint 19.2 Tina"

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

Title:
  .gvfs can't be stat'd by root causing backup tools to fail

Status in gvfs:
  Expired
Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs package in ALT Linux:
  Expired

Bug description:
  Problem
  ===
  For security reasons ( possible DoS ), other users (esp. root) cannot access 
a fuse filesystem, and not even stat the mountpoint:

  $ sudo stat .gvfs
  stat: cannot stat `.gvfs': Permission denied
  $ sudo ls -la
  ls: cannot access .gvfs: Permission denied
  d?   ? ? ? ?? .gvfs

  This means "rsync --one-file-system" (and similar options for find,
  tar...) cannot know this is a different file system they actually want
  to exclude, and fail on the permission denied error.

  Please note that it is GOOD AND CORRECT that root cannot copy the
  .gvfs directory. The real problem is that the stat fails.

  Workarounds
  ===
  * bind-mount the file system you want to backup beforehand (see comment #67)

  See also
  ===
  * Excellent description of the problem in bug 227724
  * fuse-devel mailing list saying this will all be solved someday using 
"private namespaces"
  http://thread.gmane.org/gmane.comp.file-systems.fuse.devel/3497/focus=3502
  http://thread.gmane.org/gmane.comp.file-systems.fuse.devel/7169/focus=7236
  http://thread.gmane.org/gmane.comp.file-systems.fuse.devel/6197 (no answer at 
all)
  * Kernel documentation explaing the DoS
  http://www.kernel.org/doc/Documentation/filesystems/fuse.txt

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

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

[Desktop-packages] [Bug 1839580] [NEW] LucidSound LS31 only outputs mono sound

2019-08-08 Thread Dave Chiluk

Public bug reported:

LucidSound LS31 only outputs mono sound.

The usb vendor:prod = 2f12:0109.

The fix is incoming.

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Assignee: Dave Chiluk (chiluk)
 Status: In Progress

** Changed in: pulseaudio (Ubuntu)
   Status: New => In Progress

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

Title:
  LucidSound LS31 only outputs mono sound

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  LucidSound LS31 only outputs mono sound.

  The usb vendor:prod = 2f12:0109.

  The fix is incoming.

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

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

[Desktop-packages] [Bug 1831995] Re: Bluetooth earphone is connected but disconnected immediately. [Intel 3165]

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

** Changed in: linux-firmware (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Bluetooth earphone is connected but disconnected immediately. [Intel
  3165]

Status in bluez package in Ubuntu:
  Expired
Status in linux-firmware package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:

  I have erased and reinstalled Pulseaudio.
  It seems like this can not be done since.

  I tried the following.
  sudo apt-get remove alsa-base pulseaudio
  sudo apt-get install alsa-base pulseaudio

  I did this again.
  sudo apt-get --purge remove linux-sound-base alsa-base alsa-utils
  sudo apt-get install linux-sound-base alsa-base alsa-utils

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: bluetooth 5.50-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Fri Jun  7 20:33:05 2019
  InstallationDate: Installed on 2019-04-04 (64 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 7559
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=5f78f31f-69d5-4c72-9eb4-b8c535f89c9f ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.9
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.9:bd09/03/2018:svnDellInc.:pnInspiron7559:pvr1.2.9:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7559
  dmi.product.sku: 0706
  dmi.product.version: 1.2.9
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 58:FB:84:C1:51:50  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:125274 acl:68 sco:0 events:1720 errors:0
TX bytes:15000 acl:64 sco:0 commands:861 errors:0

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

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

[Desktop-packages] [Bug 1831995] Re: Bluetooth earphone is connected but disconnected immediately. [Intel 3165]

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

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

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

Title:
  Bluetooth earphone is connected but disconnected immediately. [Intel
  3165]

Status in bluez package in Ubuntu:
  Expired
Status in linux-firmware package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:

  I have erased and reinstalled Pulseaudio.
  It seems like this can not be done since.

  I tried the following.
  sudo apt-get remove alsa-base pulseaudio
  sudo apt-get install alsa-base pulseaudio

  I did this again.
  sudo apt-get --purge remove linux-sound-base alsa-base alsa-utils
  sudo apt-get install linux-sound-base alsa-base alsa-utils

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: bluetooth 5.50-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Fri Jun  7 20:33:05 2019
  InstallationDate: Installed on 2019-04-04 (64 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 7559
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=5f78f31f-69d5-4c72-9eb4-b8c535f89c9f ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.9
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.9:bd09/03/2018:svnDellInc.:pnInspiron7559:pvr1.2.9:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7559
  dmi.product.sku: 0706
  dmi.product.version: 1.2.9
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 58:FB:84:C1:51:50  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:125274 acl:68 sco:0 events:1720 errors:0
TX bytes:15000 acl:64 sco:0 commands:861 errors:0

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

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

[Desktop-packages] [Bug 1831995] Re: Bluetooth earphone is connected but disconnected immediately. [Intel 3165]

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

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

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

Title:
  Bluetooth earphone is connected but disconnected immediately. [Intel
  3165]

Status in bluez package in Ubuntu:
  Expired
Status in linux-firmware package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:

  I have erased and reinstalled Pulseaudio.
  It seems like this can not be done since.

  I tried the following.
  sudo apt-get remove alsa-base pulseaudio
  sudo apt-get install alsa-base pulseaudio

  I did this again.
  sudo apt-get --purge remove linux-sound-base alsa-base alsa-utils
  sudo apt-get install linux-sound-base alsa-base alsa-utils

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: bluetooth 5.50-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Fri Jun  7 20:33:05 2019
  InstallationDate: Installed on 2019-04-04 (64 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 7559
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=5f78f31f-69d5-4c72-9eb4-b8c535f89c9f ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.9
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.9:bd09/03/2018:svnDellInc.:pnInspiron7559:pvr1.2.9:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7559
  dmi.product.sku: 0706
  dmi.product.version: 1.2.9
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 58:FB:84:C1:51:50  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:125274 acl:68 sco:0 events:1720 errors:0
TX bytes:15000 acl:64 sco:0 commands:861 errors:0

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

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

[Desktop-packages] [Bug 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)

2019-08-08 Thread Hui Wang

please install headers first:

sudo apt install linux-headers-5.0.0-24
sudo apt install linux-headers-5.0.0-24-generic

Then install the dkms.

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

Title:
  Alsa not detecting internal microphone [ALC255] (Realtek)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)

2019-08-08 Thread Kreaninw

@Hui Wang

Last time, I installed the file by double click it, as I see it's a .deb
file. The installation process went with no issue at all.

Now this time, I am trying to install the file via terminal. But it
never finish the building, as shown my terminal like this...

(Reading database ... 161794 files and directories currently installed.)
Preparing to unpack oem-audio-hda-daily-dkms_0.1_all.deb ...

 Uninstall Beginning 
Module:  oem-audio-hda-daily
Version: 0.1
Kernel:  5.0.0-24-generic (x86_64)
-

Status: Before uninstall, this module version was ACTIVE on this kernel.

snd-hda-codec-ca0132.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.0.0-24-generic/
rmdir: failed to remove '': No such file or directory
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


snd-hda-codec-realtek.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.0.0-24-generic/
rmdir: failed to remove '': No such file or directory
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


snd-hda-codec-ca0110.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.0.0-24-generic/
rmdir: failed to remove '': No such file or directory
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


snd-hda-codec-si3054.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.0.0-24-generic/
rmdir: failed to remove '': No such file or directory
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


snd-hda-codec-idt.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.0.0-24-generic/
rmdir: failed to remove '': No such file or directory
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


snd-hda-codec-analog.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.0.0-24-generic/
rmdir: failed to remove '': No such file or directory
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


snd-hda-codec.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.0.0-24-generic/
rmdir: failed to remove '': No such file or directory
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


snd-hda-intel.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.0.0-24-generic/
rmdir: failed to remove '': No such file or directory
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


snd-hda-codec-cmedia.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.0.0-24-generic/
rmdir: failed to remove '': No such file or directory
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


snd-hda-codec-via.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.0.0-24-generic/
rmdir: failed to remove '': No such file or directory
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


snd-hda-codec-cirrus.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.0.0-24-generic/
rmdir: failed to remove '': No such file or directory
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


snd-hda-codec-hdmi.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.0.0-24-generic/
rmdir: failed to remove '': No such file or directory
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


snd-hda-codec-conexant.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.0.0-24-generic/
rmdir: failed to remove '': No such file or directory
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


snd-hda-codec-generic.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.0.0-24-generic/
rmdir: failed to remove '': No such file or directory
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

depmod

DKMS: uninstall

[Desktop-packages] [Bug 1839576] [NEW] cannot print any document

2019-08-08 Thread Hanura Diarjo

Public bug reported:

Additional software needed, but when i click it and open ubuntu software
center there is nothing in there i can install. and when i try to print
some document it is always canceled somehow.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.6
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug  9 09:58:41 2019
InstallationDate: Installed on 2019-08-01 (8 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Lpstat: device for Canon-iP1800-series: 
usb://Canon/iP1800%20series?serial=40DDFE
MachineType: Hewlett-Packard HP 14 Notebook PC
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Canon-iP1800-series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Canon-iP1800-series.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic 
root=UUID=ffe3c507-56e6-4dbf-aeee-da9a6d7c68d4 ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/18/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.36
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2335
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 05.24
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.36:bd12/18/2014:svnHewlett-Packard:pnHP14NotebookPC:pvr098F120600087:rvnHewlett-Packard:rn2335:rvr05.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
dmi.product.name: HP 14 Notebook PC
dmi.product.sku: K8U41PA#AR6
dmi.product.version: 098F120600087
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug bionic

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

Title:
  cannot print any document

Status in cups package in Ubuntu:
  New

Bug description:
  Additional software needed, but when i click it and open ubuntu
  software center there is nothing in there i can install. and when i
  try to print some document it is always canceled somehow.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.6
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  9 09:58:41 2019
  InstallationDate: Installed on 2019-08-01 (8 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lpstat: device for Canon-iP1800-series: 
usb://Canon/iP1800%20series?serial=40DDFE
  MachineType: Hewlett-Packard HP 14 Notebook PC
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Canon-iP1800-series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Canon-iP1800-series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic 
root=UUID=ffe3c507-56e6-4dbf-aeee-da9a6d7c68d4 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.36
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2335
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 05.24
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.36:bd12/18/2014:svnHewlett-Packard:pnHP14NotebookPC:pvr098F120600087:rvnHewlett-Packard:rn2335:rvr05.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 14 Notebook PC
  dmi.product.sku: K8U41PA#AR6
  dmi.product.version: 098F120600087
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1839555] [NEW] X server backports for PRIME render offloading

2019-08-08 Thread Daniel Dadap

Public bug reported:

Configuring PRIME render offloading requires changes to the X server
which have been accepted upstream but are not yet present in any
release. These changes do not break the driver ABI and should be safe to
backport to existing X servers shipped in distributions like Ubuntu.

The required commits are:

* 7f962c70b6d9c346477f23f6c15211e749110078 - xsync: Add resource inside of 
SyncCreate, export SyncCreate
* 37a36a6b5b887d5c5a17a6931ceba8ad5d1bb6d5 - GLX: Add a per-client vendor 
mapping
*  8b67ec7cc6fda243480a5a8ca118b66242f3eb2c- GLX: Use the sending client for 
looking up XID's
* 56c0a71fdd94a008e5d746261f70a713c4767f93 - GLX: Add a function to change a 
clients vendor list
* b4231d69028adc8123801a7552b40a15ea928d1b - GLX: Set 
GlxServerExports::{major,minor}Version

These commits must be backported to an X.org X server of at least
version 1.20, as this is the first version with support for server-side
GLVND.

** Affects: xorg-server (Ubuntu)
 Importance: Undecided
 Status: 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/1839555

Title:
  X server backports for PRIME render offloading

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Configuring PRIME render offloading requires changes to the X server
  which have been accepted upstream but are not yet present in any
  release. These changes do not break the driver ABI and should be safe
  to backport to existing X servers shipped in distributions like
  Ubuntu.

  The required commits are:

  * 7f962c70b6d9c346477f23f6c15211e749110078 - xsync: Add resource inside of 
SyncCreate, export SyncCreate
  * 37a36a6b5b887d5c5a17a6931ceba8ad5d1bb6d5 - GLX: Add a per-client vendor 
mapping
  *  8b67ec7cc6fda243480a5a8ca118b66242f3eb2c- GLX: Use the sending client for 
looking up XID's
  * 56c0a71fdd94a008e5d746261f70a713c4767f93 - GLX: Add a function to change a 
clients vendor list
  * b4231d69028adc8123801a7552b40a15ea928d1b - GLX: Set 
GlxServerExports::{major,minor}Version

  These commits must be backported to an X.org X server of at least
  version 1.20, as this is the first version with support for server-
  side GLVND.

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

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

[Desktop-packages] [Bug 1817225] Re: 18.04.2 breaks xrdp

2019-08-08 Thread Steve Langasek

** Changed in: xrdp (Ubuntu)
   Status: In Progress => Fix Committed

** Package changed: xrdp (Ubuntu) => xrdp-hwe-18.04 (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/1817225

Title:
  18.04.2 breaks xrdp

Status in linux package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xrdp-hwe-18.04 package in Ubuntu:
  Fix Committed

Bug description:
  I have observed the following on two different computers:

  On both computers, running Ubuntu 18.04, I am able to install xrdp and
  log in remotely using a third computer via Reminna or Windows RDP
  client without any problems.

  If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I
  update my working 18.04 installation by running

  sudo apt-get install --install-recommends linux-generic-hwe-18.04
  xserver-xorg-hwe-18.04

  then xrdp stops working. That is, when I login using an RDP client, I
  am presented with the xrdp login screen, but when I select xorg and
  try to login with my username and password, I see a blue screen for
  about a minute and then

  connecting to sesman ip 127.0.0.1
  sesman connect ok
  sending login info to session manager, please wait...
  login successful for display 10
  started connecting
  connection problem, giving up
  some problem

  The only difference between the working configuration and the broken
  one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above
  command).

  Out of the two computers I tried one has nvidia graphics and one has
  intel on-board graphics. For the nvidia computer, I tried both nvidia
  and nouveau drivers to no avail.

  Not sure if this is a problem with xrdp or xorg.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rushik 4016 F pulseaudio
   /dev/snd/controlC1:  rushik 4016 F pulseaudio
   /dev/snd/controlC0:  rushik 4016 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c
  InstallationDate: Installed on 2019-01-11 (41 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/04/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0802
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX Z390-E GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1817225] Re: 18.04.2 breaks xrdp

2019-08-08 Thread Steve Langasek

Hello Rushi, or anyone else affected,

Accepted xrdp-hwe-18.04 into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xrdp-
hwe-18.04/0.9.5-2~18.04.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags added: verification-needed verification-needed-bionic

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

Title:
  18.04.2 breaks xrdp

Status in linux package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xrdp-hwe-18.04 package in Ubuntu:
  Fix Committed

Bug description:
  I have observed the following on two different computers:

  On both computers, running Ubuntu 18.04, I am able to install xrdp and
  log in remotely using a third computer via Reminna or Windows RDP
  client without any problems.

  If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I
  update my working 18.04 installation by running

  sudo apt-get install --install-recommends linux-generic-hwe-18.04
  xserver-xorg-hwe-18.04

  then xrdp stops working. That is, when I login using an RDP client, I
  am presented with the xrdp login screen, but when I select xorg and
  try to login with my username and password, I see a blue screen for
  about a minute and then

  connecting to sesman ip 127.0.0.1
  sesman connect ok
  sending login info to session manager, please wait...
  login successful for display 10
  started connecting
  connection problem, giving up
  some problem

  The only difference between the working configuration and the broken
  one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above
  command).

  Out of the two computers I tried one has nvidia graphics and one has
  intel on-board graphics. For the nvidia computer, I tried both nvidia
  and nouveau drivers to no avail.

  Not sure if this is a problem with xrdp or xorg.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rushik 4016 F pulseaudio
   /dev/snd/controlC1:  rushik 4016 F pulseaudio
   /dev/snd/controlC0:  rushik 4016 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c
  InstallationDate: Installed on 2019-01-11 (41 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/04/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0802
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX Z390-E GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version

[Desktop-packages] [Bug 1838358] Re: Ibus causes gnome-shell to freeze when password fields are selected in Firefox

2019-08-08 Thread Matthew Ruffell

I enabled bionic-proposed and installed ibus, ibus-gtk, ibus-gtk3
versions 1.5.17-3ubuntu5.

I ran the test in a bionic VM which had VMware Horizon Agent for Linux
installed, version 7.9.0-13916467.

Running firefox with no environment variables caused long input delays
and small lockups with the affected gnome-shell library shipped by
VMware Horizon.

When enabling the following environment variables for ibus which are
implemented as part of this SRU:

$ env IBUS_DISCARD_PASSWORD=1 firefox
and
$ export IBUS_DISCARD_PASSWORD_APPS="firefox"
$ firefox

I could enter text into password fields in firefox with no problems at
all, and the problem is fixed.

The customer has also validated that the fix works in their VMware
Horizon environment, and the problem is solved.

I am happy to mark this as verified.

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  Ibus causes gnome-shell to freeze when password fields are selected in
  Firefox

Status in ibus package in Ubuntu:
  Fix Released
Status in ibus source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  The following has been seen in a VMware Horizon VDI. I cannot reproduce this
  issue myself.

  When a user interacts with any password field in Firefox, gnome-shell
  and Firefox both freeze and the system becomes unusable. If you ssh
  into the system and terminate Firefox, gnome-shell unfreezes.

  This only happens when the environment variable GTK_IM_MODULE is set to 
"ibus". If you unset the variable, or change it to
  GTK_IM_MODULE=gtk-im-context-simple and then start Firefox, everything works 
as intended.

  This has been seen before with gnome-shell 3.28.4-0ubuntu18.04.1, ibus
  1.5.17-3ubuntu4 and Firefox versions starting with 
68.0+build3-0ubuntu0.18.04.1

  Note: Chrome[ium] and other applications do not trigger it, and it cannot be
  reproduced in other desktop environments.

  This seems to be an interaction issue between ibus and gnome-shell.

  
  [Test Case]

  Launch firefox from within a gnome-session, making sure the
  GTK_IM_MODULE is set to "ibus". Note, this is the default value.

  $ env GTK_IM_MODULE="ibus" firefox

  Navigate to any website which has a password field. Wikipedia or
  Reddit will do.

  Click a password field and attempt to enter text. Firefox and gnome-
  shell both lock up and stay frozen for an extended period of time.

  Now, try it with the fix by enabling:

  $ env IBUS_DISCARD_PASSWORD=1 firefox

  When you enter text into a password field, ibus should directly pass through
  the text and the problem will be solved.

  We can also ask it to always apply for a specific application with:

  $ export IBUS_DISCARD_PASSWORD_APPS="firefox"
  $ firefox

  Again, when you enter text into a password input field, the problem will be
  solved.

  Test package is available here:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf235370-test

  Please test with the revised version,
  1.5.17-3ubuntu4+sf235370v20190731b1.

  [Regression Potential]

  This change has a low risk of regression, because the default behaviour is
  unchanged. To be able to use the password input field discard functionality, 
a user has to explicitly set an environment variable for the specific process, 
or set a regex that matches a process name.

  This means the fix is not enabled by default on any machines, and will
  only be utilised by those suffering problems and go and manually set
  environment variables or have their system administrator enable the
  environment variables permanently.

  This commit is present in upstream ibus from version ibus-1.5.19
  onward, and is currently present in cosmic, disco and eoan.

  If a regression occurs, users can ensure that the environment
  variables are unset and continue working.

  [Other info]

  * This patch is functionally the same as ibus-xx-f19-password.patch,
  but just hides the features behind environment variables.

  * When ibus is built with the patch ibus-xx-f19-password.patch which
  was dropped in ibus-1.5.17-2, the problem is solved.

  Instead of using ibus-xx-f19-password.patch, we will instead fix it with
  upstream commit f328fd67f479faa46ca87bf3c85eed7080ec5ec0:

  https://github.com/ibus/ibus/commit/f328fd67f479faa46ca87bf3c85eed7080ec5ec0

  Subject: client/gtk2: Add IBUS_DISCARD_PASSWORD for firefox and chrome
  Author: fujiwarat 

  This implements the password discard functionality found in
  ibus-xx-f19-password.patch and places it behind two environment variables,
  IBUS_DISCARD_PASSWORD and IBUS_DISCARD_PASSWORD_APPS.

  IBUS_DISCARD_PASSWORD is for a single process, and IBUS_DISCARD_PASSWORD_APPS
  lets you set a regex of process names to filter and enable the fix for.

  If IBUS_DISCARD_PASSWORD is set or

[Desktop-packages] [Bug 1835996] Re: Dell Precision 7730 - The screen will be flickering after resumed from "display sleep" (ONLY occurs on AUO UHD#8CJK2 panel)

2019-08-08 Thread Ho Cheung

I have this problem on a Precision 7740 with the same panel and AMD
Radeon Pro WX 7130 gpu too.

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

Title:
  Dell Precision 7730 - The screen will be flickering after resumed from
  "display sleep" (ONLY occurs on AUO UHD#8CJK2 panel)

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  [Summary]
  Dell Precision 7730 -  The screen will be flickering after resumed from 
"display sleep" (ONLY occurs on AUO UHD#8CJK2 panel)

  [Reproduce Steps]
  1. Install Ubuntu 16.04/18.04 on Precision 7730;
  2. Disable automatic system sleep;
  3. Wait for display to enter sleep;
  4. Resume from display sleep.

  [Results]
  Expected: The screen wakes up as normal;
  Actual: The screen is flickering.

  [Additional Information]
  1. This bug can be reproduced both Dell OEM Ubuntu 16.04 image and 
Canonical Ubuntu 16.04 image (Default video driver/firmware version is 390.25);
  2. This bug still can be reproduced on Ubuntu 18.04;
  3. "apt-get install nvidia current", the video driver/firmware version 
304.135 will be installed. This bug does not appear with this driver;
  4. Also tested version 331 (working properly) and version 384 (This bug 
can be reproduced.);
  5. This bug does not appear on external monitors (working properly via 
WD15 and directly attached);
  6 Same behavior with BIOS 1.4.2;
  7. Similar behavior with RHEL Enterprise Linux Developer Workstation 7.5 
64bit -> No video at all when attempting to resume from display sleep or system 
sleep;
  8. System is working properly using Windows 10 Pro 64bit;
  9. More information from customer:
  
https://www.dell.com/community/XPS/Precision-7730-display-lined-flickering-in-BIOS-DO-NOT-BUY/td-p/6219020

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

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

[Desktop-packages] [Bug 1838132] Re: file browser hangs system for several seconds on save/load/exit

2019-08-08 Thread Christopher Barrington-Leigh

Sorry, I suspect it's specific to whatever part of the OS supplies dialogues to 
save files, but I'm not sophisticated enough to know what that means.
Here's the journal:


Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
[1:14:0808/145734.092083:ERROR:data_channel.cc(44)] Accepting maxRetransmits = 
-1 for backwards compatibility
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
[1:14:0808/145734.092197:ERROR:data_channel.cc(49)] Accepting maxRetransmitTime 
= -1 for backwards compatibility
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
[1:1:0808/145734.297061:ERROR:webrtc_sdp.cc(412)] Failed to parse: "a=msid: ". 
Reason: Missing track ID in msid attribute.
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
[1:1:0808/145734.297423:ERROR:webrtc_sdp.cc(412)] Failed to parse: "a=msid: ". 
Reason: Missing track ID in msid attribute.
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
[1:1:0808/145734.297582:ERROR:webrtc_sdp.cc(412)] Failed to parse: "a=msid: ". 
Reason: Missing track ID in msid attribute.
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
[1:1:0808/145734.297750:ERROR:webrtc_sdp.cc(412)] Failed to parse: "a=msid: ". 
Reason: Missing track ID in msid attribute.
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
[1:1:0808/145734.297838:ERROR:rtc_peer_connection_handler.cc(2296)] Failed to 
create native session description. Type: offer SDP: v=0
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
o=- 7056755024856063948 2 IN IP4 127.0.0.1
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: s=-
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
t=0 0
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
a=group:BUNDLE 0
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
a=msid-semantic: WMS
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
m=application 9 UDP/TLS/RTP/SAVPF 119
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
c=IN IP4 0.0.0.0
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
b=AS:30
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
a=rtcp:9 IN IP4 0.0.0.0
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
a=ice-ufrag:XXX
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
a=ice-pwd:XXX
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
a=ice-options:trickle
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
a=fingerprint:sha-256 XXX
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
a=setup:actpass
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
a=mid:0
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
a=sendrecv
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
a=msid:
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
a=rtcp-mux
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
a=rtpmap:119 google-data/9
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
a=ssrc:1531460167 cname:XXX
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
a=ssrc:1531460167 msid:-
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
a=ssrc:1531460167 mslabel:-
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
a=ssrc:1531460167 label:
Aug 08 14:57:34 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: 
[1:1:0808/145734.297888:ERROR:rtc_peer_connection_handler.cc(1215)] Failed to 
parse SessionDescription. a=msid:  Missing track ID in msid attribute.
Aug 08 14:58:44 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: # 
_g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for 
‘gio-vfs’
Aug 08 14:58:44 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: # 
_g_io_module_get_default: Found default implementation dconf 
(DConfSettingsBackend) for ‘gsettings-backend’
Aug 08 14:58:44 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: # 
watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0)
Aug 08 14:58:44 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: # 
unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1)
Aug 08 14:58:44 T450s-high org.gnome.SettingsDaemon.MediaKeys.desktop[2678]: # 
watch_established: "/org/gnome/terminal/legacy/" (establishing: 0)
Aug 08 14:58:52 T450s-high /usr/lib/gdm3/gdm-x-session[2412]: [dix] 
EventToCore: Not implemented yet
Aug 08 14:58:53 T450s-high

[Desktop-packages] [Bug 1839545] [NEW] Graphic environment slows down and then returns to normal

2019-08-08 Thread El jinete sin cabeza

Private bug reported:

After updating the mesa, the management of my graphic environment is no
longer as fluid.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: libegl-mesa0 19.1.4-1ubuntu1
Uname: Linux 5.2.7-050207-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug  8 16:46:39 2019
DistUpgraded: 2018-12-02 16:59:40,473 DEBUG inhibit gnome-session idle
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus: virtualbox, 6.0.10, 5.2.7-050207-generic, x86_64: installed
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:8486]
InstallationDate: Installed on 2018-12-02 (249 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.7-050207-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: mesa
UpgradeStatus: Upgraded to eoan on 2018-12-02 (249 days ago)
dmi.bios.date: 04/29/2019
dmi.bios.vendor: Insyde
dmi.bios.version: F.34
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8486
dmi.board.vendor: HP
dmi.board.version: 72.23
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
dmi.product.sku: 3PX63LA#ABM
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.1.4-1ubuntu1
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-1
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

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


** Tags: amd64 apport-bug eoan regression single-occurrence ubuntu 
wayland-session

** Information type changed from Public to Private

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

Title:
  Graphic environment slows down and then returns to normal

Status in mesa package in Ubuntu:
  New

Bug description:
  After updating the mesa, the management of my graphic environment is
  no longer as fluid.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libegl-mesa0 19.1.4-1ubuntu1
  Uname: Linux 5.2.7-050207-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  8 16:46:39 2019
  DistUpgraded: 2018-12-02 16:59:40,473 DEBUG inhibit gnome-session idle
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.0.10, 5.2.7-050207-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:8486]
  InstallationDate: Installed on 2018-12-02 (249 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.7-050207-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (249 days ago)
  dmi.bios.date: 04/29/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.34
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri:

[Desktop-packages] [Bug 1839544] [NEW] power setting "display off" maximum is 15 minutes, used to have several hour increment values

2019-08-08 Thread Bill Turner, wb4alm

Public bug reported:

Just upgraded to Ubuntu 18.04.2 LTS from Ubuntu 16.04 LTS.

In the POWER settings for blanking the display, there used to be several
options that allowed selecting a time interval of 1 hour, 2 hours, 4
hours, etc.

Under Ubuntu 18.04.2 there are only 9 selectable time values:
i.e. 1 min, 2 min, 3 min, 4 min, 5 min, 8 min, 10 min, 12 min, 15 minutes, and
never.

This might be fine for a portable laptop running on batteries, but is
not acceptable for a desktop system.

The never option is not good, because then the monitor NEVER goes dark.

My preferred time is to set this to 1-hour because of the length of conference
calls.
It is a real nuisance to have the screen blank on you while you are reading
information displayed on the screen to a multi-person conference call...
...Especially if you lock your screen, requiring you to log back on.

I suggest adding some of the time values back to the pull down list, or
possibly adding a "other" fill-in value box where the user can specify
in minutes when he wants the screen to blank when idle.

I consider this to be a bug, and not a feature enhancement, because I
used to be able to say "1 hour".

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

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

Title:
power setting "display off" maximum is 15 minutes, used to have
several hour increment values

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

Bug description:
Just upgraded to Ubuntu 18.04.2 LTS from Ubuntu 16.04 LTS.

In the POWER settings for blanking the display, there used to be
several options that allowed selecting a time interval of 1 hour, 2
hours, 4 hours, etc.

Under Ubuntu 18.04.2 there are only 9 selectable time values:
i.e. 1 min, 2 min, 3 min, 4 min, 5 min, 8 min, 10 min, 12 min, 15 minutes,
and never.

This might be fine for a portable laptop running on batteries, but is
not acceptable for a desktop system.

The never option is not good, because then the monitor NEVER goes
dark.

My preferred time is to set this to 1-hour because of the length of
conference calls.
It is a real nuisance to have the screen blank on you while you are reading
information displayed on the screen to a multi-person conference call...
...Especially if you lock your screen, requiring you to log back on.

I suggest adding some of the time values back to the pull down list,
or possibly adding a "other" fill-in value box where the user can
specify in minutes when he wants the screen to blank when idle.

I consider this to be a bug, and not a feature enhancement, because I
used to be able to say "1 hour".

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

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

[Desktop-packages] [Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2

2019-08-08 Thread chris pollock

I can verify that here as well

uname -a
Linux localhost 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

chris@localhost:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.3 LTS
Release:18.04
Codename:   bionic

echo $DESKTOP_SESSION
gnome

journalctl -b 0 | grep -i fail | grep -i colord
Aug 07 17:47:57 localhost colord[1249]: failed to get session [pid 1062]: No 
data available
Aug 07 17:47:58 localhost colord[1249]: failed to get session [pid 1062]: No 
data available
Aug 08 00:06:43 localhost colord[1249]: failed to get session [pid 11911]: No 
data available
Aug 08 00:06:43 localhost colord[1249]: failed to get session [pid 11911]: No 
data available

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

Title:
  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged into journalctl

  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  9 11:57:02 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  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.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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

[Desktop-packages] [Bug 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish

** Bug watch added: Debian Bug tracker #912603
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912603

** Also affects: sane-backends (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912603
   Importance: Unknown
   Status: Unknown

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

Title:
  genesys_gl847 scanners produce a black band in scanned images on
  Ubuntu 17.10+,  18.04 LTS and 18.10 Cosmic cuttlefish

Status in sane-backends:
  Unknown
Status in sane-backends package in Ubuntu:
  In Progress
Status in sane-backends source package in Bionic:
  In Progress
Status in sane-backends source package in Disco:
  In Progress
Status in sane-backends package in Debian:
  Unknown

Bug description:
  [Impact]

  When using a Genesys GL847 scanner, the documents get disfigured by a
  discolored bar. The proposed uploads should fix the issue. They are
  available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends

  [Test case]

  1. Install the libsane (libsane1 in bionic), libsane-common
 and sane-utils packages from {bionic,disco]-proposed.

  2. Use an affected device to scan, and find that the issue is
 no longer present.

  [Regression risk]

  Upstream commit, focused bug fix => low regression risk

  [Original description]

  On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
  black band on scanned image. The scanner is Canon CanoScan LIDE100.
  Libsane version is 1.0.27-1~experimental2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1731459/+subscriptions

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

[Desktop-packages] [Bug 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish

Let's give it a try to get this fixed. I have put proposed uploads in a
PPA, and asked for sponsorship to have them uploaded.

There is a but, though: I don't have an affected device, so I can't
verify that the uploads fix the issue. The eoan upload will likely make
it, but if the disco and bionic uploads won't get stuck in -proposed,
some users who have access to an affected device need to help with the
verification.

So your help will be needed. You'll get notified when it's time to
verify.

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

Title:
  genesys_gl847 scanners produce a black band in scanned images on
  Ubuntu 17.10+,  18.04 LTS and 18.10 Cosmic cuttlefish

Status in sane-backends:
  Unknown
Status in sane-backends package in Ubuntu:
  In Progress
Status in sane-backends source package in Bionic:
  In Progress
Status in sane-backends source package in Disco:
  In Progress

Bug description:
  [Impact]

  When using a Genesys GL847 scanner, the documents get disfigured by a
  discolored bar. The proposed uploads should fix the issue. They are
  available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends

  [Test case]

  1. Install the libsane (libsane1 in bionic), libsane-common
 and sane-utils packages from {bionic,disco]-proposed.

  2. Use an affected device to scan, and find that the issue is
 no longer present.

  [Regression risk]

  Upstream commit, focused bug fix => low regression risk

  [Original description]

  On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
  black band on scanned image. The scanner is Canon CanoScan LIDE100.
  Libsane version is 1.0.27-1~experimental2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1731459/+subscriptions

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

[Desktop-packages] [Bug 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish

** Description changed:

+ [Impact]
+ 
+ When using a Genesys GL847 scanner, the documents get disfigured by a
+ discolored bar. The proposed uploads should fix the issue. They are
+ available in this PPA:
+ 
+ https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends
+ 
+ [Test case]
+ 
+ 1. Install the libsane (libsane1 in bionic), libsane-common
+and sane-utils packages from {bionic,disco]-proposed.
+ 
+ 2. Use an affected device to scan, and find that the issue is
+no longer present.
+ 
+ [Regression risk]
+ 
+ Upstream commit, focused bug fix => low regression risk
+ 
+ [Original description]
+ 
  On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
  black band on scanned image. The scanner is Canon CanoScan LIDE100.
  Libsane version is 1.0.27-1~experimental2ubuntu1

** Also affects: sane-backends (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: sane-backends (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: sane-backends (Ubuntu)
   Importance: Undecided => Medium

** Changed in: sane-backends (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: sane-backends (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: sane-backends (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: sane-backends (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: sane-backends (Ubuntu Disco)
   Importance: Undecided => Medium

** Changed in: sane-backends (Ubuntu Disco)
   Status: New => In Progress

** Also affects: sane-backends via
   https://gitlab.com/sane-project/backends/issues/7
   Importance: Unknown
   Status: Unknown

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

Title:
  genesys_gl847 scanners produce a black band in scanned images on
  Ubuntu 17.10+,  18.04 LTS and 18.10 Cosmic cuttlefish

Status in sane-backends:
  Unknown
Status in sane-backends package in Ubuntu:
  In Progress
Status in sane-backends source package in Bionic:
  In Progress
Status in sane-backends source package in Disco:
  In Progress

Bug description:
  [Impact]

  When using a Genesys GL847 scanner, the documents get disfigured by a
  discolored bar. The proposed uploads should fix the issue. They are
  available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends

  [Test case]

  1. Install the libsane (libsane1 in bionic), libsane-common
 and sane-utils packages from {bionic,disco]-proposed.

  2. Use an affected device to scan, and find that the issue is
 no longer present.

  [Regression risk]

  Upstream commit, focused bug fix => low regression risk

  [Original description]

  On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
  black band on scanned image. The scanner is Canon CanoScan LIDE100.
  Libsane version is 1.0.27-1~experimental2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1731459/+subscriptions

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

[Desktop-packages] [Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2

2019-08-08 Thread tomdean

Still in 18.04 LTS

> uname -a
Linux Meerkat 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

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

> echo $DESKTOP_SESSION
ubuntu

> journalctl -b 0 | grep -i fail | grep -i colord
Aug 07 16:25:47 Meerkat colord[981]: failed to get session [pid 847]: No data 
available
Aug 07 16:25:47 Meerkat colord[981]: failed to get session [pid 847]: No data 
available
Aug 08 00:08:17 Meerkat colord[981]: failed to get session [pid 9890]: No data 
available
Aug 08 00:08:17 Meerkat colord[981]: failed to get session [pid 9890]: No data 
available

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

Title:
  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged into journalctl

  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  9 11:57:02 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  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.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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

[Desktop-packages] [Bug 1839217] Re: Bad user experience choosing partition labels

2019-08-08 Thread Chris Graham

I can't reproduce anymore either :(. I wish I kept a record of the exact
error message. I just grepped through so many packages to try and source
the error and couldn't find anything.

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

Title:
  Bad user experience choosing partition labels

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  For FAT partitions, labels have to be upper case.

  FAT is the default for a new partition, but the default example label is 
mixed case.
  This means just going on recommendation, it's not going to work out, and the 
user will get an error message.

  A better user experience would be to simply tell the user that their
  label will be made upper case, and ask them to confirm with yes/no. Or
  just do it without asking TBH because I think upper-casing it by
  default is a pretty harmless thing.

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

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

[Desktop-packages] [Bug 1801161] Re: soffice.bin: ../../src/xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.

2019-08-08 Thread Vier Eck

I currently have it from time to time in Artix/ Arch Linux (libreoffice-
still 6.1.6-2), only using lcalc. It is triggered when I do some action,
but too seldomly that I can really test what in detail triggers it.

And it happens with SAL_USE_VCLPLUGIN=gtk3, as well.

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

Title:
  soffice.bin: ../../src/xcb_io.c:263: poll_for_event: Assertion
  `!xcb_xlib_threads_sequence_lost' failed.

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Using LibreOffice Calc I was editing a filter on a pivot table and all
  LibreOffice windows hung.  What appeared in /var/log/syslog was:

  Nov  1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Unknown 
sequence number while processing queue
  Nov  1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Most likely 
this is a multi-threaded client and XInitThreads has not been called
  Nov  1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Aborting, sorry 
about that.
  Nov  1 13:31:57 santiago org.gnome.Shell.desktop[8288]: soffice.bin: 
../../src/xcb_io.c:263: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  Nov  1 13:32:27 santiago gnome-shell[8288]: Some code accessed the property 
'WindowPreviewMenuItem' on the module 'windowPreview'. That property was 
defined with 'let' or 'const' inside the module. This was previously supported, 
but is not correct according to the ES6 standard. Any symbols to be exported 
from a module must be defined with 'var'. The property access will work as 
previously for the time being, but please fix your code anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libreoffice-calc 1:6.1.2-0ubuntu1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  1 13:39:03 2018
  InstallationDate: Installed on 2018-10-29 (3 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1838836] Re: network-manager needs to be restarted frequently

2019-08-08 Thread Chelmite

Here's the syslog, starting at the point where I have a connection to a
local wifi, and then I have a failed switch to the other local wifi. (I
am sending this after capturing the log, and restarting the network-
manager service.)

Aug  8 10:01:22 serval NetworkManager[14891]:   [1565283682.3253] device 
(wlp62s0): disconnecting for new activation request.
Aug  8 10:01:22 serval NetworkManager[14891]:   [1565283682.3253] device 
(wlp62s0): state change: activated -> deactivating (reason 'new-activation', 
sys-iface-state: 'managed')
Aug  8 10:01:22 serval NetworkManager[14891]:   [1565283682.3255] 
manager: NetworkManager state is now DISCONNECTING
Aug  8 10:01:22 serval whoopsie[2549]: [10:01:22] offline
Aug  8 10:01:22 serval NetworkManager[14891]:   [1565283682.3316] audit: 
op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" 
name="ATT964" pid=11238 uid=1010 result="success"
Aug  8 10:01:22 serval NetworkManager[14891]:   [1565283682.3317] device 
(wlp62s0): state change: deactivating -> disconnected (reason 'new-activation', 
sys-iface-state: 'managed')
Aug  8 10:01:22 serval gnome-shell[11238]: Object NM.ActiveConnection 
(0x556db1161660), has been already deallocated — impossible to get any property 
from it. This might be caused by the object having been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs.
Aug  8 10:01:22 serval org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x556db1607240 ==
Aug  8 10:01:22 serval org.gnome.Shell.desktop[11238]: #0   556db14b6d08 i   
resource:///org/gnome/shell/ui/status/network.js:1318 (7f9b93d73dc0 @ 56)
Aug  8 10:01:22 serval org.gnome.Shell.desktop[11238]: #1   556db14b6c70 i   
resource:///org/gnome/shell/ui/status/network.js:1335 (7f9b93d73e50 @ 113)
Aug  8 10:01:22 serval org.gnome.Shell.desktop[11238]: #2   556db14b6bd0 i   
resource:///org/gnome/shell/ui/status/network.js:2039 (7f9b93d771f0 @ 216)
Aug  8 10:01:22 serval org.gnome.Shell.desktop[11238]: #3   556db14b6b50 i   
resource:///org/gnome/shell/ui/status/network.js:1934 (7f9b93d75dc0 @ 80)
Aug  8 10:01:22 serval org.gnome.Shell.desktop[11238]: #4   7fff53218340 b   
self-hosted:979 (7f9b93f50a60 @ 440)
Aug  8 10:01:22 serval org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x556db1607240 ==
Aug  8 10:01:22 serval org.gnome.Shell.desktop[11238]: #0   556db14b6d18 i   
resource:///org/gnome/shell/ui/status/network.js:1318 (7f9b93d73dc0 @ 56)
Aug  8 10:01:22 serval org.gnome.Shell.desktop[11238]: #1   556db14b6c80 i   
resource:///org/gnome/shell/ui/status/network.js:1335 (7f9b93d73e50 @ 113)
Aug  8 10:01:22 serval org.gnome.Shell.desktop[11238]: #2   556db14b6be0 i   
resource:///org/gnome/shell/ui/status/network.js:2039 (7f9b93d771f0 @ 216)
Aug  8 10:01:22 serval gnome-shell[11238]: JS ERROR: TypeError: 
connection.get_setting_ip4_config is not a 
function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1322:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1335:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2039:52#012_syncNMState@resource:///org/gnome/shell/ui/status/network.js:1934:9
Aug  8 10:01:22 serval org.gnome.Shell.desktop[11238]: #3   556db14b6b50 i   
resource:///org/gnome/shell/ui/status/network.js:1842 (7f9b93d75790 @ 138)
Aug  8 10:01:22 serval org.gnome.Shell.desktop[11238]: #4   7fff53218340 b   
self-hosted:979 (7f9b93f50a60 @ 440)
Aug  8 10:01:22 serval org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x556db1607240 ==
Aug  8 10:01:22 serval org.gnome.Shell.desktop[11238]: #0   556db14b6bf8 i   
resource:///org/gnome/gjs/modules/overrides/GObject.js:468 (7f9bb45b90d0 @ 25)
Aug  8 10:01:22 serval org.gnome.Shell.desktop[11238]: #1   556db14b6b50 i   
resource:///org/gnome/shell/ui/status/network.js:1815 (7f9b93d75700 @ 111)
Aug  8 10:01:22 serval org.gnome.Shell.desktop[11238]: #2   7fff53218340 b   
self-hosted:979 (7f9b93f50a60 @ 440)
Aug  8 10:01:22 serval gnome-shell[11238]: Object NM.ActiveConnection 
(0x556db1161660), has been already deallocated — impossible to get any property 
from it. This might be caused by the object having been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs.
Aug  8 10:01:22 serval gnome-shell[11238]: JS ERROR: TypeError: 
connection.get_setting_ip4_config is not a 
function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1322:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1335:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2039:52#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1842:9
Aug  8 10:01:22 serval gnome-shell[11238]: Object NM.ActiveConnection 
(0x556db1161660), has been already deallocated — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
Aug  8

[Desktop-packages] [Bug 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path

2019-08-08 Thread El jinete sin cabeza

** Also affects: gtk+3.0 (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/1726129

Title:
  nautilus crashed with SIGSEGV in widget_needs_widget_path

Status in Nautilus:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/nautilus/issues/1190

  ---

  https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Budgie:GNOME
  Date: Sun Oct 22 15:30:05 2017
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-10-19 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  ProcCmdline: nautilus --new-window
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax
   PC (0x7fe0115bd2a4) ok
   source "0x380(%rax)" (0x0380) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: nautilus crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish

2019-08-08 Thread Amr Ibrahim

** Project changed: prj20071101 => sane-backends (Ubuntu)

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

Title:
  genesys_gl847 scanners produce a black band in scanned images on
  Ubuntu 17.10+,  18.04 LTS and 18.10 Cosmic cuttlefish

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
  black band on scanned image. The scanner is Canon CanoScan LIDE100.
  Libsane version is 1.0.27-1~experimental2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1731459/+subscriptions

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

[Desktop-packages] [Bug 1731459] [NEW] genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish

You have been subscribed to a public bug:

On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
black band on scanned image. The scanner is Canon CanoScan LIDE100.
Libsane version is 1.0.27-1~experimental2ubuntu1

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: patch
-- 
genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 
 18.04 LTS and 18.10 Cosmic cuttlefish
https://bugs.launchpad.net/bugs/1731459
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to sane-backends in Ubuntu.

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

[Desktop-packages] [Bug 1837821] Re: [HP Spectre x360 Convertible 15-df0xxx, Realtek ALC285, Black Mic, Left] Recording problem

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

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

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

Title:
  [HP Spectre x360 Convertible 15-df0xxx, Realtek ALC285, Black Mic,
  Left] Recording problem

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 18.04.2 LTS. The built in microphone is not displayed
  and not available to select. The webcam, touchscreen, and speakers all
  work fine. Plugging in a headset with a microphone does allow audio to
  be heard through the external microphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  carwyn 2521 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 24 20:57:51 2019
  InstallationDate: Installed on 2019-07-22 (3 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Mic, Left
  Symptom_Type: None of the above
  Title: [HP Spectre x360 Convertible 15-df0xxx, Realtek ALC285, Black Mic, 
Left] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.29
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8518
  dmi.board.vendor: HP
  dmi.board.version: 10.47
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.29:bd04/22/2019:svnHP:pnHPSpectrex360Convertible15-df0xxx:pvr:rvnHP:rn8518:rvr10.47:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-df0xxx
  dmi.product.sku: 6JY95UA#ABA
  dmi.sys.vendor: HP

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

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

[Desktop-packages] [Bug 1771185] Re: Secondary monitor not connecting in 18.04 LTS

2019-08-08 Thread reinhard zufall

I upgraded my system to the 5.0 kernel of 18.04.3 recently, but the
external monitor is still not detected and also xrandr still lists HDMI
as disconnected. I was hoping badly for an improvement, but so far it
does not seem as if someone is working on this bug.

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

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

Title:
  Secondary monitor not connecting in 18.04 LTS

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I have an Acer Aspire V Nitro VN7-592G-709V with Nvidia Geforce 960M
  (nvidia driver v390) and a Benq W1070 projector.

  I have upgraded from Ubuntu 16.04 to 18.04 and my projector connects
  for a split second and then gets disconnected. In Ubuntu 16.04
  projector was working fine as a mirror display and extended desktop.
  Here's what I already tried:

  - enable the nouveau driver instead of the nvidia driver -> no result
  - enable the on-board intel board with sudo prime-select intel -> no result
  - apt purge nvidia* & reinstall nvidia driver 390 (stable) or 396 (beta) -> 
no result
  - disable nouveau driver, disable nvidia driver from the repository and 
install nvidia driver from nvidia website (both 390 and 396) -> no result
  - installed CCSM (CompizConfig Settings Manager) and disabled display 
auto-detection -> no result
  - played around with the refresh rate (some forums say that the two outputs 
have to be in sync -> no result
  - deleted the whole Ubuntu 18.04 upgrade and installed a fresh 18.04 -> still 
the same issue
  - tried to manually enable the output with xrandr --output HDMI-1-2 --mode 
1920x1920 -> nothing
  - under settings -> devices -> displays I don't see a secondary display (just 
the main one)

  I have the latest libxrandr2, 2:1.5.1-1 under Ubuntu 18.04 (updated to
  day)

  Here is the output of xrandr the very second when I connect the
  projector (then HDMI-1-2 goes disconnected and no modes are
  displayed):

  ~$ xrandr
  Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x 
axis y axis) 345mm x 194mm
     1920x1080 60.02*+  60.0159.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 disconnected (normal left inverted right x axis y axis)
    1920x1080 (0x258) 148.500MHz +HSync +VSync
  h: width  1920 start 2008 end 2052 total 2200 skew0 clock  
67.50KHz
  v: height 1080 start 1084 end 1089 total 1125   clock  
60.00Hz
    1920x1080 (0x259) 148.500MHz +HSync +VSync
  h: width  1920 start 2448 end 2492 total 2640 skew0 clock  
56.25KHz
  v: height 1080 start 1084 end 1089 total 1125   clock  
50.00Hz
    1920x1080 (0x25a) 148.352MHz +HSync +VSync
  h: width  1920 start 2008 end 2052 total 2200 skew0 clock  
67.43KHz
  v: height 1080 start 1084 end 1089 total 1125   clock

[Desktop-packages] [Bug 1837098] Re: Can't print in monochrome, only in colour

The PPD you have now is completely different, it is not auto-generated
based on a get-printer-attributes IPP request but it is a generic PPD
which is part of the cups-filters package.

How did you set up your printer under Disco? How did you set it up under
Eoan? Does your printer actually print under Eoan?

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

Title:
  Can't print in monochrome, only in colour

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Printer is a Samsung C430W connected over wifi and using driverless
  printing.  Everything is discovered and I can print in colour just
  fine.

  In Bionic I was able to toggle in to monochrome, but in Disco I am
  not.  I now have to print everything in colour.

  $ lpoptions -l
  PageSize/Media Size: 4x6 8.5x13.5 *A4 A5 A6 B5 Executive FanFoldGermanLegal 
ISOB5 Legal Letter Custom.WIDTHxHEIGHT
  MediaType/Media Type: *Stationery StationeryHeavyweight StationeryLightweight 
StationeryBond StationeryColored Cardstock Labels Recycled Preprinted Cotton 
Archive
  ColorModel/Print Color Mode: *RGB
  cupsPrintQuality/Print Quality: *4
  print-scaling/Print Scaling: *auto auto-fit fill fit none

  I have also attached the output of ipptool.

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

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

[Desktop-packages] [Bug 1837098] Re: Can't print in monochrome, only in colour

** Attachment added: "E ipp output"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+attachment/5281623/+files/e_ipp.txt

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

Title:
  Can't print in monochrome, only in colour

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Printer is a Samsung C430W connected over wifi and using driverless
  printing.  Everything is discovered and I can print in colour just
  fine.

  In Bionic I was able to toggle in to monochrome, but in Disco I am
  not.  I now have to print everything in colour.

  $ lpoptions -l
  PageSize/Media Size: 4x6 8.5x13.5 *A4 A5 A6 B5 Executive FanFoldGermanLegal 
ISOB5 Legal Letter Custom.WIDTHxHEIGHT
  MediaType/Media Type: *Stationery StationeryHeavyweight StationeryLightweight 
StationeryBond StationeryColored Cardstock Labels Recycled Preprinted Cotton 
Archive
  ColorModel/Print Color Mode: *RGB
  cupsPrintQuality/Print Quality: *4
  print-scaling/Print Scaling: *auto auto-fit fill fit none

  I have also attached the output of ipptool.

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

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

[Desktop-packages] [Bug 1837098] Re: Can't print in monochrome, only in colour

** Attachment added: "E PPD"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+attachment/5281616/+files/C43x.ppd

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

Title:
  Can't print in monochrome, only in colour

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Printer is a Samsung C430W connected over wifi and using driverless
  printing.  Everything is discovered and I can print in colour just
  fine.

  In Bionic I was able to toggle in to monochrome, but in Disco I am
  not.  I now have to print everything in colour.

  $ lpoptions -l
  PageSize/Media Size: 4x6 8.5x13.5 *A4 A5 A6 B5 Executive FanFoldGermanLegal 
ISOB5 Legal Letter Custom.WIDTHxHEIGHT
  MediaType/Media Type: *Stationery StationeryHeavyweight StationeryLightweight 
StationeryBond StationeryColored Cardstock Labels Recycled Preprinted Cotton 
Archive
  ColorModel/Print Color Mode: *RGB
  cupsPrintQuality/Print Quality: *4
  print-scaling/Print Scaling: *auto auto-fit fill fit none

  I have also attached the output of ipptool.

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

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

[Desktop-packages] [Bug 1836979] Re: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed”

2019-08-08 Thread Alex Moldovan

Using Ubuntu 18.04.3 LTS with 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2
18:22:20 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Output:

libva info: VA-API version 1.1.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so
libva info: Found init function __vaDriverInit_1_1
libva info: va_openDriver() returns 0
kodi-x11: ../src/gallium/drivers/nouveau/nouveau_vp3_video.c:91: 
nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed.
Aborted (core dumped)
Traceback (most recent call last):
  File "/usr/bin/apport-unpack", line 74, in 
pr.extract_keys(f, bin_keys, dir)
  File "/usr/lib/python3/dist-packages/problem_report.py", line 270, in 
extract_keys
[item for item, element in b64_block.items() if element is False])
ValueError: ['UserGroups'] has no binary content
Crash report available at /home/calin/kodi_crashlog-20190808_093922.log


** Attachment added: "dpkg-l"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836979/+attachment/5281621/+files/dpkg.txt

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

Title:
  Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion
  `templat->interlaced' failed”

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Buggy as Kodi is, this seems to be a problem specifically with mesa-
  va-drivers.

  Kodi has worked just fine on my system, as recently as July 6th of
  this year, but yesterday (July 16) I tried Kodi again: I got a blank
  screen and a pause for a few moments, followed by an unceremonious
  crash-to-desktop. This happens every time I start Kodi, now.

  If I run it through the command-line, I get this:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so
  libva info: Found init function __vaDriverInit_1_1
  libva info: va_openDriver() returns 0
  kodi-x11: ../src/gallium/drivers/nouveau/nouveau_vp3_video.c:91: 
nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed.
  Aborted (core dumped)

  I’ve been using the same version of Kodi (“18.3 Git:20190621-89472b7”,
  package version 2:18.3+git20190621.1610-final-0bionic, from the Team-
  XBMC PPA) since its release in June, but in between July 6th and 16th,
  I did upgrade the Mesa packages, from 18.2.8-0ubuntu0~18.04.2
  19.0.2-1ubuntu1.1~18.04.1. If I downgrade the “mesa-va-drivers”
  package to 18.0.0~rc5-1ubuntu1 (the version in the base, non-updates
  Bionic repository), however, Kodi works again, without even requiring
  me to restart my machine. So, this is likely a problem with “mesa-va-
  drivers”.

  I tried looking in Xorg.0.log:

  [ 17185.557] (II) NOUVEAU(0): EDID vendor "SEC", prod id 12620
  [ 17185.557] (II) NOUVEAU(0): Printing DDC gathered Modelines:
  [ 17185.558] (II) NOUVEAU(0): Modeline "1366x768"x0.0   72.33  1366 1414 1446 
1526  768 770 775 790 -hsync -vsync (47.4 kHz eP)

  …that’s all that appears in the log when I try to load Kodi and a
  crash happens.

  I’m using Ubuntu MATE 18.04.2 LTS 64-bit on a Compaq Presario CQ60; if
  you need more information, I’ve attached a hardinfo report, too. I
  hope this bug can get fixed, soon. Thanks!

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

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

[Desktop-packages] [Bug 1836979] Re: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed”

2019-08-08 Thread Alex Moldovan

kodi_crashlog-20190808_093922.log

** Attachment added: "kodi_crashlog"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836979/+attachment/5281622/+files/kodi_crashlog-20190808_093922.log

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

Title:
  Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion
  `templat->interlaced' failed”

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Buggy as Kodi is, this seems to be a problem specifically with mesa-
  va-drivers.

  Kodi has worked just fine on my system, as recently as July 6th of
  this year, but yesterday (July 16) I tried Kodi again: I got a blank
  screen and a pause for a few moments, followed by an unceremonious
  crash-to-desktop. This happens every time I start Kodi, now.

  If I run it through the command-line, I get this:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so
  libva info: Found init function __vaDriverInit_1_1
  libva info: va_openDriver() returns 0
  kodi-x11: ../src/gallium/drivers/nouveau/nouveau_vp3_video.c:91: 
nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed.
  Aborted (core dumped)

  I’ve been using the same version of Kodi (“18.3 Git:20190621-89472b7”,
  package version 2:18.3+git20190621.1610-final-0bionic, from the Team-
  XBMC PPA) since its release in June, but in between July 6th and 16th,
  I did upgrade the Mesa packages, from 18.2.8-0ubuntu0~18.04.2
  19.0.2-1ubuntu1.1~18.04.1. If I downgrade the “mesa-va-drivers”
  package to 18.0.0~rc5-1ubuntu1 (the version in the base, non-updates
  Bionic repository), however, Kodi works again, without even requiring
  me to restart my machine. So, this is likely a problem with “mesa-va-
  drivers”.

  I tried looking in Xorg.0.log:

  [ 17185.557] (II) NOUVEAU(0): EDID vendor "SEC", prod id 12620
  [ 17185.557] (II) NOUVEAU(0): Printing DDC gathered Modelines:
  [ 17185.558] (II) NOUVEAU(0): Modeline "1366x768"x0.0   72.33  1366 1414 1446 
1526  768 770 775 790 -hsync -vsync (47.4 kHz eP)

  …that’s all that appears in the log when I try to load Kodi and a
  crash happens.

  I’m using Ubuntu MATE 18.04.2 LTS 64-bit on a Compaq Presario CQ60; if
  you need more information, I’ve attached a hardinfo report, too. I
  hope this bug can get fixed, soon. Thanks!

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

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

[Desktop-packages] [Bug 1839481] [NEW] Simplified Chinese localization incomplete

2019-08-08 Thread Olivier Tilloy

Public bug reported:

I can't speak/read Chinese, but I was testing "Non-English Installation
Full Network Support & CJK Input" in the QA ISO tracker, and the
livepatch screen in the initial setup wizard appears incompletely
translated.

See attached screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-initial-setup 3.28.0-2ubuntu6.16.04.4
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug  8 15:49:38 2019
InstallationDate: Installed on 2019-08-08 (0 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
SourcePackage: gnome-initial-setup
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic iso-testing

** Attachment added: "VirtualBox_ubuntu test_08_08_2019_15_34_39.png"
   
https://bugs.launchpad.net/bugs/1839481/+attachment/5281617/+files/VirtualBox_ubuntu%20test_08_08_2019_15_34_39.png

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

Title:
  Simplified Chinese localization incomplete

Status in gnome-initial-setup package in Ubuntu:
  New

Bug description:
  I can't speak/read Chinese, but I was testing "Non-English
  Installation Full Network Support & CJK Input" in the QA ISO tracker,
  and the livepatch screen in the initial setup wizard appears
  incompletely translated.

  See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-initial-setup 3.28.0-2ubuntu6.16.04.4
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  8 15:49:38 2019
  InstallationDate: Installed on 2019-08-08 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: gnome-initial-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1839402] Re: package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: попытка перезаписать общий «/lib/udev/

Excellent; thanks for letting us know.

Closing the bug then - please feel free to submit a new report if the
error repeats itself.

** Changed in: sane-backends (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified:
  lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: попытка
  перезаписать общий «/lib/udev/rules.d/60-libsane.rules», который
  отличается от других экземпляров пакета libsane:i386

Status in sane-backends package in Ubuntu:
  Fix Released

Bug description:
  package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified:
  lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: попытка
  перезаписать общий «/lib/udev/rules.d/60-libsane.rules», который
  отличается от других экземпляров пакета libsane:i386

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: 
lib/udev/rules.d/60-libsane.rules]
  ProcVersionSignature: Ubuntu 4.15.0-55.60~16.04.2-generic 4.15.18
  Uname: Linux 4.15.0-55-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  Date: Wed Jul 31 06:27:15 2019
  ErrorMessage: попытка перезаписать общий 
«/lib/udev/rules.d/60-libsane.rules», который отличается от других экземпляров 
пакета libsane:i386
  InstallationDate: Installed on 2017-03-04 (887 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.32
  SourcePackage: sane-backends
  Title: package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: 
lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: попытка 
перезаписать общий «/lib/udev/rules.d/60-libsane.rules», который отличается от 
других экземпляров пакета libsane:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1839402/+subscriptions

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

[Desktop-packages] [Bug 1837098] Re: Can't print in monochrome, only in colour

Could you post the PPD file of Eoan then, so tat I can compare?

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

Title:
  Can't print in monochrome, only in colour

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Printer is a Samsung C430W connected over wifi and using driverless
  printing.  Everything is discovered and I can print in colour just
  fine.

  In Bionic I was able to toggle in to monochrome, but in Disco I am
  not.  I now have to print everything in colour.

  $ lpoptions -l
  PageSize/Media Size: 4x6 8.5x13.5 *A4 A5 A6 B5 Executive FanFoldGermanLegal 
ISOB5 Legal Letter Custom.WIDTHxHEIGHT
  MediaType/Media Type: *Stationery StationeryHeavyweight StationeryLightweight 
StationeryBond StationeryColored Cardstock Labels Recycled Preprinted Cotton 
Archive
  ColorModel/Print Color Mode: *RGB
  cupsPrintQuality/Print Quality: *4
  print-scaling/Print Scaling: *auto auto-fit fill fit none

  I have also attached the output of ipptool.

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

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

[Desktop-packages] [Bug 1837098] Re: Can't print in monochrome, only in colour

Could you also attach the ipptool output of Eoan, to see whether this is
different?

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

Title:
  Can't print in monochrome, only in colour

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Printer is a Samsung C430W connected over wifi and using driverless
  printing.  Everything is discovered and I can print in colour just
  fine.

  In Bionic I was able to toggle in to monochrome, but in Disco I am
  not.  I now have to print everything in colour.

  $ lpoptions -l
  PageSize/Media Size: 4x6 8.5x13.5 *A4 A5 A6 B5 Executive FanFoldGermanLegal 
ISOB5 Legal Letter Custom.WIDTHxHEIGHT
  MediaType/Media Type: *Stationery StationeryHeavyweight StationeryLightweight 
StationeryBond StationeryColored Cardstock Labels Recycled Preprinted Cotton 
Archive
  ColorModel/Print Color Mode: *RGB
  cupsPrintQuality/Print Quality: *4
  print-scaling/Print Scaling: *auto auto-fit fill fit none

  I have also attached the output of ipptool.

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

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

[Desktop-packages] [Bug 1176548] Re: nut-server fails if modemmanager is scanning serial ports

2019-08-08 Thread Andreas Hasenack

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

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

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

Title:
  nut-server fails if modemmanager is scanning serial ports

Status in modemmanager package in Ubuntu:
  Incomplete
Status in nut package in Ubuntu:
  Incomplete

Bug description:
  Similar to whatPaavo Leinonen reported in
  031601ce2a49$20b2efe0$6218cfa0$@leinonen.fi on the NUT mailing list.
  See also my mail in reply.

  Ubuntu runs modemmanager as a native upstart service. nut-server ends
  up running in parallel (on my system, probably a matter of timing).
  When modemmanager scans the serial ports for modems, upsd is unable to
  open the port configured for an UPS. (It might be possible to exclude
  some ports from the scan, I didn't check because I have no modem it
  could configure, I just kicked the package.

  Please convert nut-server to a native upstart service to be able to
  have it wait for modemmanager. (I hope upstart is clever enough to
  have a service wait for an optional package and let it proceed if not
  installed.)

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

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

[Desktop-packages] [Bug 1839402] Re: package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: попытка перезаписать общий «/lib/udev/

2019-08-08 Thread Airat Halitov

I did it
`sudo apt install --reinstall libsane`

I have seen this error only once today.
If I will see the error again, I will write here.

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

Title:
  package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified:
  lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: попытка
  перезаписать общий «/lib/udev/rules.d/60-libsane.rules», который
  отличается от других экземпляров пакета libsane:i386

Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified:
  lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: попытка
  перезаписать общий «/lib/udev/rules.d/60-libsane.rules», который
  отличается от других экземпляров пакета libsane:i386

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: 
lib/udev/rules.d/60-libsane.rules]
  ProcVersionSignature: Ubuntu 4.15.0-55.60~16.04.2-generic 4.15.18
  Uname: Linux 4.15.0-55-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  Date: Wed Jul 31 06:27:15 2019
  ErrorMessage: попытка перезаписать общий 
«/lib/udev/rules.d/60-libsane.rules», который отличается от других экземпляров 
пакета libsane:i386
  InstallationDate: Installed on 2017-03-04 (887 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.32
  SourcePackage: sane-backends
  Title: package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: 
lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: попытка 
перезаписать общий «/lib/udev/rules.d/60-libsane.rules», который отличается от 
других экземпляров пакета libsane:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1839402/+subscriptions

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

[Desktop-packages] [Bug 1839402] Re: package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: попытка перезаписать общий «/lib/udev/

2019-08-08 Thread Airat Halitov

After rebooting the system, the error did not recur.
Perhaps reinstalling the package helped.

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

Title:
  package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified:
  lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: попытка
  перезаписать общий «/lib/udev/rules.d/60-libsane.rules», который
  отличается от других экземпляров пакета libsane:i386

Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified:
  lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: попытка
  перезаписать общий «/lib/udev/rules.d/60-libsane.rules», который
  отличается от других экземпляров пакета libsane:i386

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: 
lib/udev/rules.d/60-libsane.rules]
  ProcVersionSignature: Ubuntu 4.15.0-55.60~16.04.2-generic 4.15.18
  Uname: Linux 4.15.0-55-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  Date: Wed Jul 31 06:27:15 2019
  ErrorMessage: попытка перезаписать общий 
«/lib/udev/rules.d/60-libsane.rules», который отличается от других экземпляров 
пакета libsane:i386
  InstallationDate: Installed on 2017-03-04 (887 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.32
  SourcePackage: sane-backends
  Title: package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: 
lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: попытка 
перезаписать общий «/lib/udev/rules.d/60-libsane.rules», который отличается от 
других экземпляров пакета libsane:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1839402/+subscriptions

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

[Desktop-packages] [Bug 1839402] Re: package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: попытка перезаписать общий «/lib/udev/

Thanks for your report. It sounds as some kind of hardware glitch to me.

Can you please try to reinstall:

sudo apt install --reinstall libsane

and let us know if that helps.

** Changed in: sane-backends (Ubuntu)
   Status: New => Incomplete

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

Title:
  package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified:
  lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: попытка
  перезаписать общий «/lib/udev/rules.d/60-libsane.rules», который
  отличается от других экземпляров пакета libsane:i386

Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified:
  lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: попытка
  перезаписать общий «/lib/udev/rules.d/60-libsane.rules», который
  отличается от других экземпляров пакета libsane:i386

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: 
lib/udev/rules.d/60-libsane.rules]
  ProcVersionSignature: Ubuntu 4.15.0-55.60~16.04.2-generic 4.15.18
  Uname: Linux 4.15.0-55-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  Date: Wed Jul 31 06:27:15 2019
  ErrorMessage: попытка перезаписать общий 
«/lib/udev/rules.d/60-libsane.rules», который отличается от других экземпляров 
пакета libsane:i386
  InstallationDate: Installed on 2017-03-04 (887 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.32
  SourcePackage: sane-backends
  Title: package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: 
lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: попытка 
перезаписать общий «/lib/udev/rules.d/60-libsane.rules», который отличается от 
других экземпляров пакета libsane:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1839402/+subscriptions

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

[Desktop-packages] [Bug 127071] Re: system-config-printer does not save options into .cups/lpoptions for unprivileged users

2019-08-08 Thread Lasse Kliemann

Addendum: the KDE version shipped with Debian 10 allows to configure a
local default printer.

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

Title:
  system-config-printer does not save options into .cups/lpoptions for
  unprivileged users

Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: system-config-printer

  If I run system-config-printer as a privileged user (first user set up
  by Ubuntu, member of "lpadmin" group) all works as I expect it: PPD
  option settings are saved in the "*Default..." lines of the queue's
  PPD file (/etc/cups/ppd/.ppd and CUPS-specific in
  /etc/cups/printers.conf.

  If I run it as unprivileged user I would like that it saves the
  settings in the user's ~/.cups/lpoptions file.

  Or even better: For a privileged user ask whether the settings should
  be applied system-wide or personally (when clicking on "Apply").

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/127071/+subscriptions

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

[Desktop-packages] [Bug 1815550] Re: gnome-shell high memory and CPU usage when desktop files are constantly created or deleted

Fix proposed:

https://salsa.debian.org/gnome-team/shell-extensions/gnome-shell-
extension-desktop-icons/merge_requests/1

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

Title:
  gnome-shell high memory and CPU usage when desktop files are
  constantly created or deleted

Status in gnome-shell-extension-desktop-icons:
  New
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  In Progress
Status in gnome-shell-extension-desktop-icons source package in Disco:
  In Progress

Bug description:
  This *may* be an nvidia-specific problem, but the RSS of gnome-shell
  on my system grows without limit (over a couple of hours it's
  increased past 10G).

  At the same time, gnome-shell appears to become progressively less
  responsive.

  Restarting gnome-shell (via  restart) drops shell RSS down to
  ~400MB and improves system responsiveness a bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.30.2-2ubuntu2
  ProcVersionSignature: Ubuntu 4.20.0+bcachefs.git20190130.d1f70147-1.0-generic 
4.20.0
  Uname: Linux 4.20.0+bcachefs.git20190130.d1f70147-1-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 12 13:35:59 2019
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1839446] Re: When trying to print a test page CUPS crashes

I wasnt able to get a backtrace because there was "no stack".

This is what shows in gdb:


Program received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) 
Continuing.

Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
(gdb) 
The program is not being run.
(gdb) 
The program is not being run.
(gdb) backtrace full
No stack.

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

Title:
  When trying to print a test page CUPS crashes

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to get my printer working correctly and when I try and
  print test pages it seems like cups crashes and restarts in the
  background.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: cups 2.2.10-4ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  8 10:33:49 2019
  InstallationDate: Installed on 2019-07-03 (35 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lpstat: device for Samsung_C43x_Series_printer_: 
ipp://printer.local:631/ipp/print
  MachineType: LENOVO 20HN0016UK
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Samsung_C43x_Series_printer_.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Samsung_C43x_Series_printer_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=91a2a717-12eb-448f-8b5b-48dd8d3dc145 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0IET57W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HN0016UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET57W(1.35):bd03/25/2019:svnLENOVO:pn20HN0016UK:pvrThinkPadX270:rvnLENOVO:rn20HN0016UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X270
  dmi.product.name: 20HN0016UK
  dmi.product.sku: LENOVO_MT_20HN_BU_Think_FM_ThinkPad X270
  dmi.product.version: ThinkPad X270
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1837098] Re: Can't print in monochrome, only in colour

I tested E and that seems to work as expected.

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

Title:
  Can't print in monochrome, only in colour

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Printer is a Samsung C430W connected over wifi and using driverless
  printing.  Everything is discovered and I can print in colour just
  fine.

  In Bionic I was able to toggle in to monochrome, but in Disco I am
  not.  I now have to print everything in colour.

  $ lpoptions -l
  PageSize/Media Size: 4x6 8.5x13.5 *A4 A5 A6 B5 Executive FanFoldGermanLegal 
ISOB5 Legal Letter Custom.WIDTHxHEIGHT
  MediaType/Media Type: *Stationery StationeryHeavyweight StationeryLightweight 
StationeryBond StationeryColored Cardstock Labels Recycled Preprinted Cotton 
Archive
  ColorModel/Print Color Mode: *RGB
  cupsPrintQuality/Print Quality: *4
  print-scaling/Print Scaling: *auto auto-fit fill fit none

  I have also attached the output of ipptool.

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

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

[Desktop-packages] [Bug 1006895] Re: size of side pane can not be set to less than 220 pixels

Upstream bug was closed as a duplicate of 680953 which
was itself closed "RESOLVED FIXED" on 2013-08-26

Reporter did not reply to comment #4 but I have checked
with evince 3.28.4 and Ubuntu 18.04 and have found that
the side pane can now be set to around 130px or the size
of a thumbnail. Closing as fixed.

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

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

Title:
  size of side pane can not be set to less than 220 pixels

Status in evince package in Ubuntu:
  Fix Released

Bug description:
  in evince the side pane can not be set to smaller (but just larger).
  the minimum size of 220 pixels is quite large, especially when the
  side pane is switched into the "thumbnails" view, thumbs occupy less
  than 50% of width and the whole look is rather strange.

  imho, width of thumbnails should follow the width of the side pane and
  the side pane should be able to get minimal width much less than
  what's allowed now... kde's okular is much more like how the side pane
  should behave... i hope nobody will mind me saying it... ;)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: evince 3.4.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Thu May 31 14:59:18 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  KernLog:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   LC_PAPER=en_GB.UTF-8
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1839446] Re: When trying to print a test page CUPS crashes

Sorry, wrong bug, ignore that comment.

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

Title:
  When trying to print a test page CUPS crashes

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to get my printer working correctly and when I try and
  print test pages it seems like cups crashes and restarts in the
  background.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: cups 2.2.10-4ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  8 10:33:49 2019
  InstallationDate: Installed on 2019-07-03 (35 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lpstat: device for Samsung_C43x_Series_printer_: 
ipp://printer.local:631/ipp/print
  MachineType: LENOVO 20HN0016UK
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Samsung_C43x_Series_printer_.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Samsung_C43x_Series_printer_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=91a2a717-12eb-448f-8b5b-48dd8d3dc145 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0IET57W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HN0016UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET57W(1.35):bd03/25/2019:svnLENOVO:pn20HN0016UK:pvrThinkPadX270:rvnLENOVO:rn20HN0016UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X270
  dmi.product.name: 20HN0016UK
  dmi.product.sku: LENOVO_MT_20HN_BU_Think_FM_ThinkPad X270
  dmi.product.version: ThinkPad X270
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1839446] Re: When trying to print a test page CUPS crashes

I've tested this on E, and I can now print in B and Colour again.

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

Title:
  When trying to print a test page CUPS crashes

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to get my printer working correctly and when I try and
  print test pages it seems like cups crashes and restarts in the
  background.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: cups 2.2.10-4ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  8 10:33:49 2019
  InstallationDate: Installed on 2019-07-03 (35 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lpstat: device for Samsung_C43x_Series_printer_: 
ipp://printer.local:631/ipp/print
  MachineType: LENOVO 20HN0016UK
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Samsung_C43x_Series_printer_.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Samsung_C43x_Series_printer_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=91a2a717-12eb-448f-8b5b-48dd8d3dc145 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0IET57W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HN0016UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET57W(1.35):bd03/25/2019:svnLENOVO:pn20HN0016UK:pvrThinkPadX270:rvnLENOVO:rn20HN0016UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X270
  dmi.product.name: 20HN0016UK
  dmi.product.sku: LENOVO_MT_20HN_BU_Think_FM_ThinkPad X270
  dmi.product.version: ThinkPad X270
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1839446] Re: When trying to print a test page CUPS crashes

** Attachment added: "error_log"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1839446/+attachment/5281584/+files/error_log

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

Title:
  When trying to print a test page CUPS crashes

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to get my printer working correctly and when I try and
  print test pages it seems like cups crashes and restarts in the
  background.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: cups 2.2.10-4ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  8 10:33:49 2019
  InstallationDate: Installed on 2019-07-03 (35 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lpstat: device for Samsung_C43x_Series_printer_: 
ipp://printer.local:631/ipp/print
  MachineType: LENOVO 20HN0016UK
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Samsung_C43x_Series_printer_.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Samsung_C43x_Series_printer_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=91a2a717-12eb-448f-8b5b-48dd8d3dc145 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0IET57W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HN0016UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET57W(1.35):bd03/25/2019:svnLENOVO:pn20HN0016UK:pvrThinkPadX270:rvnLENOVO:rn20HN0016UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X270
  dmi.product.name: 20HN0016UK
  dmi.product.sku: LENOVO_MT_20HN_BU_Think_FM_ThinkPad X270
  dmi.product.version: ThinkPad X270
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 545778] Re: xul-ext-lightning is only available in English

2019-08-08 Thread Olivier Tilloy

I'm looking at how this works upstream, and in Debian.

Upstream: the xpi that can be downloaded from
https://addons.thunderbird.net/thunderbird/addon/lightning/ includes all
locales. I don't know how this xpi is built though, given that the
upstream build system insists on building a localized xpi that contains
only one language at a time.

Debian: the extension is unpacked and installed in /usr/share/lightning, and 
each langpack package installs the corresponding translations in 
/usr/share/lightning/chrome/lightning/AB_CD/…
This works only because the extension is installed unpacked. Note that in 
Debian there's a separate source tarball for lightning translations (see 
https://packages.debian.org/source/buster/thunderbird), but maybe that predates 
the inclusion of lightning in the central repository?

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

Title:
  xul-ext-lightning is only available in English

Status in One Hundred Papercuts:
  Triaged
Status in Mozilla Thunderbird:
  Invalid
Status in Ubuntu Translations:
  Triaged
Status in lightning-sunbird package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Change the user session language to other different than English.
  2. In Thunderbird, open the calendar

  EXPECTED BEHAVIOUR

  - The calendar interface to be in the session language.

  REAL BEHAVIOUR

  - The calendar is in English.

  RELEVANT DETAILS

  - None.

  **
   SOLUTION
  **

  WORK-AROUND

  - None known.

  FIX

  - .

  REGRESSION POTENTIAL

  - Since no code needs to be modified, the regression potential is very
  low.

  
   TECHNICAL INFO
  

  Binary package hint: lightning-extension

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

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

[Desktop-packages] [Bug 256736] Re: Printing to a pdf in portrait mode from evince fails if paper is wider than it is tall

Bug report did not expire due to bug watch.
Upstream report was closed "RESOLVED INCOMPLETE" on 2011-06-29
as further information was not provided.
No response to comment #7 over 4 years ago so closing.


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

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

Title:
  Printing to a pdf in portrait mode from evince  fails if paper is
  wider than it is tall

Status in Evince:
  Expired
Status in evince package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: evince

  If you create a custom paper type where the page width is larger than
  the page height evince will always orient the paper so that the longer
  dimension is the height. Switching the orientaion to lansdcape will
  make the dimensons correct but then the pdf file is sideways.

  To replicate:
  Try creating a custom paper type that is 5 in x 3 in. Print a document that 
is wider than it is tall. The resulting pdf file will have your content jammed 
at the top of a page that is 3 in x 5 in.

  This is in Hardy Heron evince-2.22.2-0ubuntu1

  ProblemType: Bug
  Architecture: i386
  Date: Sun Aug 10 14:31:08 2008
  DistroRelease: Ubuntu 8.04
  ExecutablePath: /usr/bin/evince
  NonfreeKernelModules: nvidia
  Package: evince 2.22.2-0ubuntu1
  PackageArchitecture: i386
  ProcEnviron:
   
PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  Uname: Linux 2.6.24-19-generic i686

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

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

[Desktop-packages] [Bug 1759591] Re: gnome-control-center assert failure: corrupted size vs. prev_size

I can reproduce this on E.  I was told by apport that this is the same
bug.


** Changed in: gnome-control-center (Ubuntu)
   Status: Expired => Confirmed

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

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

Title:
  gnome-control-center assert failure: corrupted size vs. prev_size

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

Bug description:
  was setting the printer

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu4
  Uname: Linux 4.16.0-041600rc7-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  AssertionMessage: corrupted size vs. prev_size
  CurrentDesktop: GNOME
  Date: Wed Mar 28 16:23:37 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-02-06 (49 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcCmdline: gnome-control-center printers
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fa0d6dcdb9a 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7fa0d6dcbc9d "corrupted size vs. 
prev_size") at malloc.c:5350
   _int_realloc (av=av@entry=0x7fa0d7002c40 , 
oldp=oldp@entry=0x55f7d56c5400, oldsize=oldsize@entry=912, nb=nb@entry=928) at 
malloc.c:4564
   __GI___libc_realloc (oldmem=0x55f7d56c5410, bytes=912) at malloc.c:3230
   g_realloc () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center assert failure: corrupted size vs. prev_size
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

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

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

[Desktop-packages] [Bug 667515] Re: jamendo intro page does not fit netbook screen

Upstream report was closed "RESOLVED OBSOLETE" on 2012-03-28 as
the Jamendo plugin no longer exists. Closing this too as report
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/667515

Title:
  jamendo intro page does not fit netbook screen

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

Bug description:
  Binary package hint: rhythmbox

  Neither does ubuntu one for that manner. I'll try to add some screen
  shots. I'm using netbook 10.10

  Seems like it could be fixed with some sort of text wrapping.

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

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

[Desktop-packages] [Bug 1839446] Re: When trying to print a test page CUPS crashes

Could you follow the instructions of the section "CUPS error_log" on
https://wiki.ubuntu.com/DebuggingPrintingProblems to get an error_log in
debug mode from the CUPS crash?

Also some form of backtrace of the crashing CUPS daemon would be great
(apport record? cupsd run in a way that one can capture a core file,
...).

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

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

Title:
  When trying to print a test page CUPS crashes

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to get my printer working correctly and when I try and
  print test pages it seems like cups crashes and restarts in the
  background.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: cups 2.2.10-4ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  8 10:33:49 2019
  InstallationDate: Installed on 2019-07-03 (35 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lpstat: device for Samsung_C43x_Series_printer_: 
ipp://printer.local:631/ipp/print
  MachineType: LENOVO 20HN0016UK
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Samsung_C43x_Series_printer_.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Samsung_C43x_Series_printer_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=91a2a717-12eb-448f-8b5b-48dd8d3dc145 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0IET57W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HN0016UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET57W(1.35):bd03/25/2019:svnLENOVO:pn20HN0016UK:pvrThinkPadX270:rvnLENOVO:rn20HN0016UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X270
  dmi.product.name: 20HN0016UK
  dmi.product.sku: LENOVO_MT_20HN_BU_Think_FM_ThinkPad X270
  dmi.product.version: ThinkPad X270
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 584529] Re: Thunderbird complains there is no connection on resume from suspend, when there is a connection

Bug report won't expire due to bug watches
No reply to comment #57 after 40 days so closing as fixed


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

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

Title:
  Thunderbird complains there is no connection on resume from suspend,
  when there is a connection

Status in Mozilla Thunderbird:
  Invalid
Status in thunderbird package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: thunderbird

  When I resume from suspend, network manager quickly re-establishes a
  WiFi internet connection.  With an active connection, I try to check
  my mail with Thunderbird, but it complains that it can't connect to
  the IMAP server.  This seems to happen after longer suspend periods
  because if I try to replicate the behaviour by quickly suspending and
  resuming (suspend of a few seconds), I get no warning.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: thunderbird 3.0.4+nobinonly-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic x86_64
  Architecture: amd64
  Date: Sun May 23 12:26:28 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100412)
  ProcEnviron:
   LANG=en_GB.utf8
   SHELL=/bin/bash
  SourcePackage: thunderbird

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

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

[Desktop-packages] [Bug 1839446] [NEW] When trying to print a test page CUPS crashes

Public bug reported:

I'm trying to get my printer working correctly and when I try and print
test pages it seems like cups crashes and restarts in the background.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: cups 2.2.10-4ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
Uname: Linux 5.0.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug  8 10:33:49 2019
InstallationDate: Installed on 2019-07-03 (35 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lpstat: device for Samsung_C43x_Series_printer_: 
ipp://printer.local:631/ipp/print
MachineType: LENOVO 20HN0016UK
Papersize: letter
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Samsung_C43x_Series_printer_.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Samsung_C43x_Series_printer_.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=91a2a717-12eb-448f-8b5b-48dd8d3dc145 ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/25/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0IET57W (1.35 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HN0016UK
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET57W(1.35):bd03/25/2019:svnLENOVO:pn20HN0016UK:pvrThinkPadX270:rvnLENOVO:rn20HN0016UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X270
dmi.product.name: 20HN0016UK
dmi.product.sku: LENOVO_MT_20HN_BU_Think_FM_ThinkPad X270
dmi.product.version: ThinkPad X270
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug disco

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

Title:
  When trying to print a test page CUPS crashes

Status in cups package in Ubuntu:
  New

Bug description:
  I'm trying to get my printer working correctly and when I try and
  print test pages it seems like cups crashes and restarts in the
  background.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: cups 2.2.10-4ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  8 10:33:49 2019
  InstallationDate: Installed on 2019-07-03 (35 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lpstat: device for Samsung_C43x_Series_printer_: 
ipp://printer.local:631/ipp/print
  MachineType: LENOVO 20HN0016UK
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Samsung_C43x_Series_printer_.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Samsung_C43x_Series_printer_.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=91a2a717-12eb-448f-8b5b-48dd8d3dc145 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0IET57W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HN0016UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET57W(1.35):bd03/25/2019:svnLENOVO:pn20HN0016UK:pvrThinkPadX270:rvnLENOVO:rn20HN0016UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X270
  dmi.product.name: 20HN0016UK
  dmi.product.sku: LENOVO_MT_20HN_BU_Think_FM_ThinkPad X270
  dmi.product.version: ThinkPad X270
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1681970] Re: gnome-calendar with google account only can start from terminal, no launchers works

Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018
Bug did not expire due to bug watch
Upstream report suggests issue may have been fixed in version 3.24
Works ok with version 3.28.2 in Ubuntu 18.04
No further information provided by reporter so closing


** Changed in: gnome-calendar (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  gnome-calendar with google account only can start  from terminal, no
  launchers works

Status in GNOME Calendar:
  Expired
Status in gnome-calendar package in Ubuntu:
  Invalid

Bug description:
  ubuntu 17.04 after add google account is not capable to launch gnome-
  calendar except from a terminal; also gnome-todo cant bring google
  task .. only can push new tasks

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

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

[Desktop-packages] [Bug 1576581] Re: New Firefox release hogging CPU

Bug report did not expire due to bug watch.
Further to comment #8, now closing as fixed.


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

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

Title:
  New Firefox release hogging CPU

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Since the new Firefox release into 16.04 yesterday [1] Firefox is
  constantly using more than 100% CPU.

  [1]
  https://launchpad.net/ubuntu/+source/firefox/46.0+build5-0ubuntu0.16.04.2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 46.0+build5-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  michal 8674 F pulseaudio
   /dev/snd/controlC0:  michal 8674 F pulseaudio
  BrokenPermissions:
   greasefi...@b0nk3rz.net/indexes/exclude.dat (0o400)
   greasefi...@b0nk3rz.net/indexes/include.dat (0o400)
   greasefi...@b0nk3rz.net/indexes/info.ini (0o400)
   greasefi...@b0nk3rz.net/indexes/scripts.db (0o400)
  BuildID: 20160425114621
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Fri Apr 29 10:35:53 2016
  ForcedLayersAccel: False
  IncompatibleExtensions:
   Polski Language Pack - langpack...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  Plugins:
   Google Talk Plugin Video Renderer - /opt/google/talkplugin/libnpo1d.so 
(google-talkplugin)
   Google Talk Plugin - /opt/google/talkplugin/libnpgoogletalk.so 
(google-talkplugin)
   Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
   IcedTea-Web Plugin (using IcedTea-Web 1.6.2 (1.6.2-3ubuntu1)) - 
/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so 
(icedtea-8-plugin)
  PrefSources:
   prefs.js
   
[Profile]/extensions/https-everywhere-...@eff.org/defaults/preferences/preferences.js
  Profiles: Profile0 (Default) - LastVersion=46.0/20160425114621 (In use)
  RelatedPackageVersions:
   google-talkplugin 5.41.0.0-1
   icedtea-8-plugin  1.6.2-3ubuntu1
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: XPS 12-9Q33
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A06
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd04/15/2014:svnDellInc.:pnXPS12-9Q33:pvrA06:rvnDellInc.:rnXPS12-9Q33:rvrA06:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 12-9Q33
  dmi.product.version: A06
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1821427] Re: gnome-shell crashed with SIGTRAP in g_log_writer_default() from g_log_structured_array() from g_log_structured_array() from g_log_structured_standard("The program

Upstream bug reports:

https://gitlab.gnome.org/GNOME/gnome-shell/issues/760
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1230
https://gitlab.gnome.org/GNOME/gnome-shell/issues/661
https://gitlab.gnome.org/GNOME/gnome-shell/issues/627
https://gitlab.gnome.org/GNOME/gnome-shell/issues/496
https://gitlab.gnome.org/GNOME/gnome-shell/issues/375
https://gitlab.gnome.org/GNOME/gnome-shell/issues/213

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

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

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

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

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

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

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

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

Title:
  gnome-shell crashed with SIGTRAP in g_log_writer_default() from
  g_log_structured_array() from g_log_structured_array() from
  g_log_structured_standard("The program 'gnome-shell' received an X
  Window System error.\nThis probably reflects a bug in the
  program.\nThe error was 'BadWindow (invalid Window parameter)'.\n
  (Details: serial 333851 error_code 3 r");

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

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

  Had this happen a few times now, where closing the main evolution
  window (last visible window on desktop) results in a gnome-shell crash
  (see bug 1821262)

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 22 18:49:10 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-09-26 (177 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to disco on 2019-03-11 (11 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1821427] Re: gnome-shell crashed with SIGTRAP in g_log_writer_default() from g_log_structured_array() from g_log_structured_array() from g_log_structured_standard("The program

2019-08-08 Thread Jean-Louis Dupond

I have an 100% reliable way to reproduce this crash :)

Take a screenshot & copy to clipboard, try to paste the image (clipboard
content) inside a telegram-desktop chat -> BOOM, gnome-shell crashes

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

Title:
  gnome-shell crashed with SIGTRAP in g_log_writer_default() from
  g_log_structured_array() from g_log_structured_array() from
  g_log_structured_standard("The program 'gnome-shell' received an X
  Window System error.\nThis probably reflects a bug in the
  program.\nThe error was 'BadWindow (invalid Window parameter)'.\n
  (Details: serial 333851 error_code 3 r");

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

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

  Had this happen a few times now, where closing the main evolution
  window (last visible window on desktop) results in a gnome-shell crash
  (see bug 1821262)

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 22 18:49:10 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-09-26 (177 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to disco on 2019-03-11 (11 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1821427] Re: gnome-shell crashed with signal 5 in g_log_writer_default() from g_log_structured_array() from g_log_structured_array() from g_log_structured_standard("The program

** Summary changed:

- gnome-shell crashed with signal 5 when closing evolution, logging "The 
program 'gnome-shell' received an X Window System error.\nThis probably 
reflects a bug in the program.\nThe error was 'BadWindow (invalid Window 
parameter)'.\n  (Details: serial 333851 error_code 3 r"
+ gnome-shell crashed with signal 5 in g_log_writer_default() from 
g_log_structured_array() from g_log_structured_array() from 
g_log_structured_standard("The program 'gnome-shell' received an X Window 
System error.\nThis probably reflects a bug in the program.\nThe error was 
'BadWindow (invalid Window parameter)'.\n  (Details: serial 333851 error_code 3 
r");

** Summary changed:

- gnome-shell crashed with signal 5 in g_log_writer_default() from 
g_log_structured_array() from g_log_structured_array() from 
g_log_structured_standard("The program 'gnome-shell' received an X Window 
System error.\nThis probably reflects a bug in the program.\nThe error was 
'BadWindow (invalid Window parameter)'.\n  (Details: serial 333851 error_code 3 
r");
+ gnome-shell crashed with SIGTRAP in g_log_writer_default() from 
g_log_structured_array() from g_log_structured_array() from 
g_log_structured_standard("The program 'gnome-shell' received an X Window 
System error.\nThis probably reflects a bug in the program.\nThe error was 
'BadWindow (invalid Window parameter)'.\n  (Details: serial 333851 error_code 3 
r");

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

Title:
  gnome-shell crashed with SIGTRAP in g_log_writer_default() from
  g_log_structured_array() from g_log_structured_array() from
  g_log_structured_standard("The program 'gnome-shell' received an X
  Window System error.\nThis probably reflects a bug in the
  program.\nThe error was 'BadWindow (invalid Window parameter)'.\n
  (Details: serial 333851 error_code 3 r");

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

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

  Had this happen a few times now, where closing the main evolution
  window (last visible window on desktop) results in a gnome-shell crash
  (see bug 1821262)

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 22 18:49:10 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-09-26 (177 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to disco on 2019-03-11 (11 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace

** Merge proposal linked:
   
https://code.launchpad.net/~fourdollars/ubuntu/+source/systemd/+git/systemd/+merge/370808

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

Title:
  KEY_RFKILL is not passed to userspace

Status in OEM Priority Project:
  New
Status in OEM Priority Project bionic series:
  New
Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in xorgproto package in Ubuntu:
  Fix Released
Status in libxkbcommon source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in xkeyboard-config source package in Bionic:
  Fix Committed
Status in xorgproto source package in Bionic:
  Fix Released
Status in libxkbcommon source package in Cosmic:
  Fix Released
Status in xkeyboard-config source package in Cosmic:
  Fix Released
Status in xorgproto source package in Cosmic:
  Fix Released

Bug description:
  * Impact
  the airplane mode key doesn't work in GNOME

  * Test case
  Use a laptop with a key to activate airplane mode, it should toggle the 
corresponding mode on/off when used

  * Regression potential
  The change adds a new key definition but doesn't touch any existing one, 
nothing specific to test out of the new key working

  -

  There are a couple things going on, that could be fixed by a Debian or
  Ubuntu maintainer:

  - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This
  introduces the RFKill key: https://lists.freedesktop.org/archives
  /wayland-devel/2017-August/034721.html

  - x11-proto needs a new release. This commit added RFKill, but it is
  not in a release:
  
https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf

  - Likely other X11 packages need to be rebuilt.

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

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

[Desktop-packages] [Bug 1839442] [NEW] desktop icons vanish after drag'n'drop then requires a restart

2019-08-08 Thread IanFHood

Public bug reported:

All of the desktop icons (and conky, etc) suddenly vanish after I drag
and drop something into a desktop folder (typically dragging selected
text from chrome browser, which normally creates a text file in the
folder).

Does not trigger the bug every time, but quite frequently. Once the bug
triggers the icon area is useless and requires a system restart to
restore the icons and normal functioning.

This is a new XPS laptop with Ubuntu 18.04 freshly installed (and little
else modified).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.4-0~ubuntu18.04.4
ProcVersionSignature: Ubuntu 4.15.0-1045.50-oem 4.15.18
Uname: Linux 4.15.0-1045-oem x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug  8 01:24:33 2019
InstallationDate: Installed on 2019-03-15 (145 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus: dropbox 2019.02.14

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


** Tags: amd64 apport-bug bionic

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

Title:
  desktop icons vanish after drag'n'drop then requires a restart

Status in nautilus package in Ubuntu:
  New

Bug description:
  All of the desktop icons (and conky, etc) suddenly vanish after I drag
  and drop something into a desktop folder (typically dragging selected
  text from chrome browser, which normally creates a text file in the
  folder).

  Does not trigger the bug every time, but quite frequently. Once the
  bug triggers the icon area is useless and requires a system restart to
  restore the icons and normal functioning.

  This is a new XPS laptop with Ubuntu 18.04 freshly installed (and
  little else modified).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.4-0~ubuntu18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-1045.50-oem 4.15.18
  Uname: Linux 4.15.0-1045-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  8 01:24:33 2019
  InstallationDate: Installed on 2019-03-15 (145 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: dropbox 2019.02.14

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

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

[Desktop-packages] [Bug 1837098] Re: Can't print in monochrome, only in colour

** Attachment added: "Disco PPD"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+attachment/5281554/+files/Samsung_C43x_Series_printer_.ppd

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

Title:
  Can't print in monochrome, only in colour

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Printer is a Samsung C430W connected over wifi and using driverless
  printing.  Everything is discovered and I can print in colour just
  fine.

  In Bionic I was able to toggle in to monochrome, but in Disco I am
  not.  I now have to print everything in colour.

  $ lpoptions -l
  PageSize/Media Size: 4x6 8.5x13.5 *A4 A5 A6 B5 Executive FanFoldGermanLegal 
ISOB5 Legal Letter Custom.WIDTHxHEIGHT
  MediaType/Media Type: *Stationery StationeryHeavyweight StationeryLightweight 
StationeryBond StationeryColored Cardstock Labels Recycled Preprinted Cotton 
Archive
  ColorModel/Print Color Mode: *RGB
  cupsPrintQuality/Print Quality: *4
  print-scaling/Print Scaling: *auto auto-fit fill fit none

  I have also attached the output of ipptool.

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

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

[Desktop-packages] [Bug 1838358] Re: Ibus causes gnome-shell to freeze when password fields are selected in Firefox

2019-08-08 Thread Łukasz Zemczak

Hello Matthew, or anyone else affected,

Accepted ibus into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/ibus/1.5.17-3ubuntu5
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: ibus (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  Ibus causes gnome-shell to freeze when password fields are selected in
  Firefox

Status in ibus package in Ubuntu:
  Fix Released
Status in ibus source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  The following has been seen in a VMware Horizon VDI. I cannot reproduce this
  issue myself.

  When a user interacts with any password field in Firefox, gnome-shell
  and Firefox both freeze and the system becomes unusable. If you ssh
  into the system and terminate Firefox, gnome-shell unfreezes.

  This only happens when the environment variable GTK_IM_MODULE is set to 
"ibus". If you unset the variable, or change it to
  GTK_IM_MODULE=gtk-im-context-simple and then start Firefox, everything works 
as intended.

  This has been seen before with gnome-shell 3.28.4-0ubuntu18.04.1, ibus
  1.5.17-3ubuntu4 and Firefox versions starting with 
68.0+build3-0ubuntu0.18.04.1

  Note: Chrome[ium] and other applications do not trigger it, and it cannot be
  reproduced in other desktop environments.

  This seems to be an interaction issue between ibus and gnome-shell.

  
  [Test Case]

  Launch firefox from within a gnome-session, making sure the
  GTK_IM_MODULE is set to "ibus". Note, this is the default value.

  $ env GTK_IM_MODULE="ibus" firefox

  Navigate to any website which has a password field. Wikipedia or
  Reddit will do.

  Click a password field and attempt to enter text. Firefox and gnome-
  shell both lock up and stay frozen for an extended period of time.

  Now, try it with the fix by enabling:

  $ env IBUS_DISCARD_PASSWORD=1 firefox

  When you enter text into a password field, ibus should directly pass through
  the text and the problem will be solved.

  We can also ask it to always apply for a specific application with:

  $ export IBUS_DISCARD_PASSWORD_APPS="firefox"
  $ firefox

  Again, when you enter text into a password input field, the problem will be
  solved.

  Test package is available here:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf235370-test

  Please test with the revised version,
  1.5.17-3ubuntu4+sf235370v20190731b1.

  [Regression Potential]

  This change has a low risk of regression, because the default behaviour is
  unchanged. To be able to use the password input field discard functionality, 
a user has to explicitly set an environment variable for the specific process, 
or set a regex that matches a process name.

  This means the fix is not enabled by default on any machines, and will
  only be utilised by those suffering problems and go and manually set
  environment variables or have their system administrator enable the
  environment variables permanently.

  This commit is present in upstream ibus from version ibus-1.5.19
  onward, and is currently present in cosmic, disco and eoan.

  If a regression occurs, users can ensure that the environment
  variables are unset and continue working.

  [Other info]

  * This patch is functionally the same as ibus-xx-f19-password.patch,
  but just hides the features behind environment variables.

  * When ibus is built with the patch ibus-xx-f19-password.patch which
  was dropped in ibus-1.5.17-2, the problem is solved.

  Instead of using ibus-xx-f19-password.patch, we will instead fix it with
  upstream commit f328fd67f479faa46ca87bf3c85eed7080ec5ec0:

  https://github.com/ibus/ibus/commit/f328fd67f479faa46ca87bf3c85eed7080ec5ec0

  Subject: client/gtk2: Add IBUS_DISCARD_PASSWORD for firefox and

[Desktop-packages] [Bug 1839068] Re: Wrong password every time after changing login password

2019-08-08 Thread leopoldog

All the time I receive this error in the journal.

ago 08 09:53:23 lathy passwd[621]: pam_unix(passwd:chauthtok): password changed 
for lghi
ago 08 09:53:23 lathy gnome-keyring-daemon[17482]: couldn't change login master 
password, original password was wrong: La password o il PIN non è corretto
ago 08 09:53:23 lathy passwd[621]: gkr-pam: couldn't change password for the 
login keyring: the passwords didn't match.

I've receiving the same error when I try to change from the old password to the 
new and vice versa.
I was expecting to have no error if the change was from the old password to the 
new and an error in the other way.

Maybe is because the first time I've changed the password I was logged
in with root, but this should not be a problem if the wallet change is
made via PAM.

My problem is not that the wallet doesn't change password automatically
(even if it's practical) but that I can't change the wallet password
anymore because even the old password is considered wrong.

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

Title:
  Wrong password every time after changing login password

Status in seahorse package in Ubuntu:
  New

Bug description:
  After changing password with "passwd" command it's not possible to open the 
keyring anymore.
  Each time I have the dialog that open asking me for the password.
  I've tried to enter the old password and the new password but nothing changes.
  I've changed back the login password to the old one but even in that case the 
seahorse password dialog opens saying that the login password doesn't matches 
the keyring password and asking me to enter it again.

  I need a procedure to change the keyring password without login into
  the seahorse, so that it can match the login password of Ubuntu.

  Ubuntu 18.04.2 LTS

  Seahorse 3.20.0-5 from http://ch.archive.ubuntu.com/ubuntu bionic/main
  amd64 Packages

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

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

[Desktop-packages] [Bug 1838358] Re: Ibus causes gnome-shell to freeze when password fields are selected in Firefox

2019-08-08 Thread Łukasz Zemczak

Excellent. If the issue is reproducible and affects multiple users, this
seems like a +1 on the SRU.

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

Title:
  Ibus causes gnome-shell to freeze when password fields are selected in
  Firefox

Status in ibus package in Ubuntu:
  Fix Released
Status in ibus source package in Bionic:
  In Progress

Bug description:
  [Impact]

  The following has been seen in a VMware Horizon VDI. I cannot reproduce this
  issue myself.

  When a user interacts with any password field in Firefox, gnome-shell
  and Firefox both freeze and the system becomes unusable. If you ssh
  into the system and terminate Firefox, gnome-shell unfreezes.

  This only happens when the environment variable GTK_IM_MODULE is set to 
"ibus". If you unset the variable, or change it to
  GTK_IM_MODULE=gtk-im-context-simple and then start Firefox, everything works 
as intended.

  This has been seen before with gnome-shell 3.28.4-0ubuntu18.04.1, ibus
  1.5.17-3ubuntu4 and Firefox versions starting with 
68.0+build3-0ubuntu0.18.04.1

  Note: Chrome[ium] and other applications do not trigger it, and it cannot be
  reproduced in other desktop environments.

  This seems to be an interaction issue between ibus and gnome-shell.

  
  [Test Case]

  Launch firefox from within a gnome-session, making sure the
  GTK_IM_MODULE is set to "ibus". Note, this is the default value.

  $ env GTK_IM_MODULE="ibus" firefox

  Navigate to any website which has a password field. Wikipedia or
  Reddit will do.

  Click a password field and attempt to enter text. Firefox and gnome-
  shell both lock up and stay frozen for an extended period of time.

  Now, try it with the fix by enabling:

  $ env IBUS_DISCARD_PASSWORD=1 firefox

  When you enter text into a password field, ibus should directly pass through
  the text and the problem will be solved.

  We can also ask it to always apply for a specific application with:

  $ export IBUS_DISCARD_PASSWORD_APPS="firefox"
  $ firefox

  Again, when you enter text into a password input field, the problem will be
  solved.

  Test package is available here:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf235370-test

  Please test with the revised version,
  1.5.17-3ubuntu4+sf235370v20190731b1.

  [Regression Potential]

  This change has a low risk of regression, because the default behaviour is
  unchanged. To be able to use the password input field discard functionality, 
a user has to explicitly set an environment variable for the specific process, 
or set a regex that matches a process name.

  This means the fix is not enabled by default on any machines, and will
  only be utilised by those suffering problems and go and manually set
  environment variables or have their system administrator enable the
  environment variables permanently.

  This commit is present in upstream ibus from version ibus-1.5.19
  onward, and is currently present in cosmic, disco and eoan.

  If a regression occurs, users can ensure that the environment
  variables are unset and continue working.

  [Other info]

  * This patch is functionally the same as ibus-xx-f19-password.patch,
  but just hides the features behind environment variables.

  * When ibus is built with the patch ibus-xx-f19-password.patch which
  was dropped in ibus-1.5.17-2, the problem is solved.

  Instead of using ibus-xx-f19-password.patch, we will instead fix it with
  upstream commit f328fd67f479faa46ca87bf3c85eed7080ec5ec0:

  https://github.com/ibus/ibus/commit/f328fd67f479faa46ca87bf3c85eed7080ec5ec0

  Subject: client/gtk2: Add IBUS_DISCARD_PASSWORD for firefox and chrome
  Author: fujiwarat 

  This implements the password discard functionality found in
  ibus-xx-f19-password.patch and places it behind two environment variables,
  IBUS_DISCARD_PASSWORD and IBUS_DISCARD_PASSWORD_APPS.

  IBUS_DISCARD_PASSWORD is for a single process, and IBUS_DISCARD_PASSWORD_APPS
  lets you set a regex of process names to filter and enable the fix for.

  If IBUS_DISCARD_PASSWORD is set or IBUS_DISCARD_PASSWORD_APPS is set
  with the process name which input is being placed into password
  fields, ibus will pass through the input to the application without
  any processing.

  * This only affect Bionic

  - Upstream first introduction:
  $ git describe --contains  f328fd67f479faa46ca87bf3c85eed7080ec5ec0
  1.5.19~7

  - Ubuntu ibus current version found in the archive:
  $ rmadison ibus
   ==> ibus | 1.5.17-3ubuntu4   | bionic 
   ibus | 1.5.19-1ubuntu1   | cosmic 
   ibus | 1.5.19-1ubuntu2   | disco  
   ibus | 1.5.19-4ubuntu2   | eoan

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

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

[Desktop-packages] [Bug 1839380] Re: Nautilus freezes when restoring files and a copy already exists

2019-08-08 Thread Sebastien Bacher

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

** Changed in: nautilus (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Nautilus freezes when restoring files and a copy already exists

Status in Nautilus:
  Unknown
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  I have trashed the hidden file using nautilus to the trash bin, be it
  the hidden configuration file for XScreenSaver that is compiled from
  source, and it regenerated the hidden file in the same location that I
  have deleted the old copy in.

  I attempted to restore the file, but because the file with the same
  name is originated on the same location, Nautilus freezes. It should
  give me the "Replace file with newer version" dialog so I can decide
  if I want to replace the old file with the new one, or if I want to
  rename the trashed hidden file to another name. It shouldn't freeze.

  Here's the clearer example. Suppose that...

  1. I created a file named "test.txt" on "/home/eofla",
  2. I put it to the trash bin,
  3. I repeated Step 1, and
  4. I attempted to restore the same file that was on the trash.
  5. Nautilus freezes.

  Version of Ubuntu:

  Description:  Ubuntu Eoan Ermine (development branch)
  Release:  19.10

  Version of Nautilus:

  nautilus:
    Installed: 1:3.32.1-1ubuntu1
    Candidate: 1:3.32.1-1ubuntu1
    Version table:
   *** 1:3.32.1-1ubuntu1 500
  500 http://sy.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  Debug output with "G_DEBUG="all" NAUTILUS_DEBUG="All" nautilus":

  Nautilus-Share-Message: 23:01:44.608: Called "net usershare info" but
  it failed: Failed to execute child process “net” (No such file or
  directory)

  Debug output using "gdb nautilus" with exported environment variables
  of G_DEBUG="all" NAUTILUS_DEBUG="All" (More useful, with stack trace):
  https://paste.ubuntu.com/p/ChpBrDsTtd/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.32.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  7 13:43:40 2019
  GsettingsChanges:

  InstallationDate: Installed on 2019-07-21 (16 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1839010] Re: Touchpad does not work after installing Ubuntu

2019-08-08 Thread Sebastien Bacher

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

The journal log has those

Aug 08 13:18:28 primovictoria /usr/lib/gdm3/gdm-x-session[1540]: (II) event8  - 
HID 1018:1006 Touchpad: is tagged by udev as: Touchpad
Aug 08 13:18:28 primovictoria /usr/lib/gdm3/gdm-x-session[1540]: (II) event8  - 
HID 1018:1006 Touchpad: device is a touchpad
Aug 08 13:18:28 primovictoria /usr/lib/gdm3/gdm-x-session[1540]: (II) event8  - 
HID 1018:1006 Touchpad: device removed

Aug 08 13:18:28 primovictoria /usr/lib/gdm3/gdm-x-session[1540]: (II) event8  - 
HID 1018:1006 Touchpad: is tagged by udev as: Touchpad
Aug 08 13:18:28 primovictoria /usr/lib/gdm3/gdm-x-session[1540]: (II) event8  - 
HID 1018:1006 Touchpad: device is a touchpad
Aug 08 13:18:28 primovictoria /usr/lib/gdm3/gdm-x-session[1540]: (II) event8  - 
HID 1018:1006 Touchpad: device removed

Reassigning to libinput for now but could be a kernel issue

** Package changed: gnome-control-center (Ubuntu) => libinput (Ubuntu)

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

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

Title:
  Touchpad does not work after installing Ubuntu

Status in libinput package in Ubuntu:
  New

Bug description:
  I previously had Windows 10 on my protab laptop. After wiping the hard
  drive and installing Ubuntu 19.04 on the device, the touchpad ceases
  to respond at all. I am using an external mouse currently.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.32.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug  6 02:39:36 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-02-22 (164 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago)

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

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

[Desktop-packages] [Bug 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path

2019-08-08 Thread Sebastien Bacher

** Changed in: nautilus (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  nautilus crashed with SIGSEGV in widget_needs_widget_path

Status in Nautilus:
  Unknown
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/nautilus/issues/1190

  ---

  https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Budgie:GNOME
  Date: Sun Oct 22 15:30:05 2017
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-10-19 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  ProcCmdline: nautilus --new-window
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax
   PC (0x7fe0115bd2a4) ok
   source "0x380(%rax)" (0x0380) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: nautilus crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1830022] Re: DirtyCleanInterval should be 0 by default

This bug was fixed in the package cups - 2.2.11-0ubuntu1

---
cups (2.2.11-0ubuntu1) eoan; urgency=medium

  * New upstream release
  * Removed 10 patches taken from upstream.
  * Refreshed 13 patches with quilt.
  * Removed patch to set "LogDebugHistory 9" as it causes high
system load when there are very many jobs (LP: #1831021).
  * Set "DirtyCleanInterval 0" in CUPS configuration to avoid losses of
jobs when cupsd gets killed (LP: #1830022).

 -- Till Kamppeter   Mon, 05 Aug 2019 11:40:10
+0200

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

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

Title:
  DirtyCleanInterval should be 0 by default

Status in cups package in Ubuntu:
  Fix Released

Bug description:
  Please consider changing DirtyCleanInterval value to 0 as default.

  Otherwise if cupsd crashes due to (e.g. OOM killer) under a heavy
  workload even hundreds of jobs may be lost. This concern is backed up
  by a real-life scenario and leaves the client sending thousands of
  jobs unaware that many of them are lost during a crash.

  After cupsd gets restarted it rewinds it's job counter to the last
  cached and continues unaware about the jobs accepted and lost.

  Having DirtyCleanInterval set to 0 will cause some performance impact,
  but not significant under lighter workloads and a completely justified
  price for reliability under heavy workloads.

  Test scenario:
  1. sudo apt install printer-driver-cups-pdf
  2. while [ 1 ]; do lp -d PDF somepdf.pdf; done;
  3. # on other terminal
 kill -9 $(pidof cupsd)
  4. Note last job number and wait for cupsd to be restarted by systemd.
  5. Once accepting jobs is resumend the job counter is rewound.

  Expected behavior:
  Accepted jobs are queued for processing.

  Actual behavior:
  Some accepted jobs are lost.

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

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

[Desktop-packages] [Bug 1831021] Re: Extremely high memory consumption under heavy workload