[Desktop-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

[Paul Smith]

Is this going to be fixed in disco?

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  New
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed
Status in network-manager source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

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

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

[Desktop-packages] [Bug 1284466] Re: [Inspiron 1420, SigmaTel STAC9228, Speaker, Internal] No sound at all

[Launchpad Bug Tracker]

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

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

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

Title:
  [Inspiron 1420, SigmaTel STAC9228, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  For a few years sound did not work on this laptop. Sometime during the
  13.10 release cycle the problem was fixed in the kernel. Now in the
  14.04 after a kernel update sound no longer works. I'm not 100% sure
  which kernel update broke sound. I will try to install some of the
  older kernels and track it down.

  Alsa and PulseAudio both show that the sound is turned all the way up,
  but no sound plays and the sound tests fail to make any noise too.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic i686
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  3312 F pulseaudio
  CurrentDesktop: LXDE
  Date: Tue Feb 25 01:01:28 2014
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1907 F pulseaudio
david  3312 F pulseaudio
   /dev/snd/seq:timidity   1585 F timidity
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Inspiron 1420, SigmaTel STAC9228, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to trusty on 2013-12-29 (58 days ago)
  dmi.bios.date: 12/19/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0DT492
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd12/19/2008:svnDellInc.:pnInspiron1420:pvr:rvnDellInc.:rn0DT492:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1420
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1354739] Re: [System Product Name, Realtek ALC662 rev1, Green Line Out, Rear] No sound at all

[Launchpad Bug Tracker]

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

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

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

Title:
  [System Product Name, Realtek ALC662 rev1, Green Line Out, Rear] No
  sound at all

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  Sound stops after fast forwarding/progressing in the VLC media player.
  It stops for all applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anirban2143 F pulseaudio
  Date: Sun Aug 10 01:37:22 2014
  InstallationDate: Installed on 2014-07-09 (31 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anirban2143 F pulseaudio
   /dev/snd/seq:timidity   1576 F timidity
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [System Product Name, Realtek ALC662 rev1, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0412
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5KPL-AM/PS
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0412:bd06/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-AM/PS:rvrx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1377404] Re: [Latitude 3540, Realtek ALC283, Black Headphone Out, Left] No sound at all

[Launchpad Bug Tracker]

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

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

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

Title:
  [Latitude 3540, Realtek ALC283, Black Headphone Out, Left] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  This bug manifested itself only recently (kernel update?).  I have
  sound through the internal speakers but nothing (except occasional
  clicks) through the headphones.  'What device did you plug in?' dialog
  appearing fine, headphones show up in sound preferences, test sounds
  not audible.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ajp109 2262 F pulseaudio
ajp109 3563 F audacity
   /dev/snd/pcmC0D0c:   ajp109 2262 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Sat Oct  4 10:19:17 2014
  InstallationDate: Installed on 2014-02-01 (244 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140201)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ajp109 2262 F pulseaudio
ajp109 3563 F audacity
   /dev/snd/pcmC0D0c:   ajp109 2262 F...m pulseaudio
   /dev/snd/seq:timidity   1224 F timidity
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [Latitude 3540, Realtek ALC283, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 02RKKX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A04
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd11/12/2013:svnDellInc.:pnLatitude3540:pvrA04:rvnDellInc.:rn02RKKX:rvrA00:cvnDellInc.:ct8:cvrA04:
  dmi.product.name: Latitude 3540
  dmi.product.version: A04
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-09-19T21:53:03.868459

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

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

[Desktop-packages] [Bug 1598008] Re: [Veriton M200-H110, Realtek ALC662 rev3, Speaker, Internal] No sound at all

[Launchpad Bug Tracker]

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

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

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

Title:
  [Veriton M200-H110, Realtek ALC662 rev3, Speaker, Internal] No sound
  at all

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  my sound is not coming

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2014 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jul  1 11:44:29 2016
  InstallationDate: Installed on 2016-06-30 (0 days ago)
  InstallationMedia: Ubuntu-Linux-14.04-eCommittee 14.04 - Release amd64
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_AlsaPlaybackTestStderr:
   W r i t e   e r r o r :   - 5 , I n p u t / o u t p u t   e r r o r 
x r u n _ r e c o v e r y   f a i l e d :   - 5 , I n p u t / o u t p u t   
e r r o r 
T r a n s f e r   f a i l e d :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2014 F pulseaudio
   /dev/snd/seq:timidity   1325 F timidity
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Veriton M200-H110, Realtek ALC662 rev3, Speaker, Internal] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A02
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: H110-M1
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: PEGATRON CORPORATION
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A02:bd03/22/2016:svnAcer:pnVeritonM200-H110:pvr:rvnPEGATRONCORPORATION:rnH110-M1:rvr:cvnPEGATRONCORPORATION:ct3:cvr:
  dmi.product.name: Veriton M200-H110
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1822446] Re: [B450M DS3H, Realtek ALC887-VD] Sound is occasionally distorted

[Launchpad Bug Tracker]

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

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

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

Title:
  [B450M DS3H, Realtek ALC887-VD] Sound is occasionally distorted

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Sound from youtube in playing firefox is distorted. After waiting a
  half hour the problem went away. i then tried to file a bug report.
  while playing the first set of test tones the test tone played fine
  after it finished the youtube audio was distorted again. then the
  second set of test tones from the troubleshooter played and were
  distorted as well.

  Also in the summary it ended up saying "FRONT" but it is the rear
  green jack on my motherboard that i am plugged into.

  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04

  5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:58:11 UTC 2019 x86_64
  x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mike   1833 F pulseaudio
   /dev/snd/pcmC1D0p:   mike   1833 F...m pulseaudio
   /dev/snd/controlC0:  mike   1833 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 30 21:02:38 2019
  InstallationDate: Installed on 2019-03-30 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190329)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful
  Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [B450M DS3H, Realtek ALC887-VD, Green Headphone Out, Front] Sound is 
distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1822527] Re: System appears to use wayland despite my having Wayland Enable set to false.

[Launchpad Bug Tracker]

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

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

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

Title:
  System appears to use wayland despite my having Wayland Enable set to
  false.

Status in gdm3 package in Ubuntu:
  Expired

Bug description:
  1. Ubuntu 18.10
  2. xorg:
Installed: 1:7.7+19ubuntu8
  Version table:
   *** 1:7.7+19ubuntu8 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  Basically, when I rebooted the computer, the graphics were scrambled
  and the system behaved as it did when wayland was enabled despite the
  .conf file saying "WaylandEnabled=False", and that line being
  uncommented.

  Steps to Reproduce:
  1. Edit the .conf file to uncomment "WaylandEnabled"
  2. Reboot the machine
  3. Wait 2 days before booting it back up
  4. Notice the machine is using Wayland despite the conf file specifying 
otherwise.

  Expected Results:
  Machine runs with the behavior of Xorg.

  Actual Results:
  Machine appears to run Wayland.

  Workaround: Edit the conf file again, and then reboot.

  In respect to the diagnostics taken, this issue occurred before I took
  the diagnostics and was able to use Firefox to write this report. This
  at around 9:56 PM, EDT on March 31, 2019.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 31 22:18:52 2019
  DistUpgraded: 2018-11-20 23:52:16,217 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 
OEM] [1682:3207]
  InstallationDate: Installed on 2018-10-07 (175 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gateway DX4860
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=4c74a6f6-2050-43cf-96aa-f3d050456a3d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2018-11-21 (130 days ago)
  dmi.bios.date: 08/01/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02-A1
  dmi.board.name: IPISB-VR
  dmi.board.vendor: Gateway
  dmi.board.version: 1.01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr:
  dmi.product.family: Gateway Desktop
  dmi.product.name: DX4860
  dmi.sys.vendor: Gateway
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1821904] Re: Sound is muted by default after upgrading 18.04->18.10->19.04

[Launchpad Bug Tracker]

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

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

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

Title:
  Sound is muted by default after upgrading 18.04->18.10->19.04

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  On Disco, Gnome Shell always starts muted.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joe4766 F pulseaudio
   /dev/snd/pcmC0D0p:   joe4766 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-09-15 (193 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: pulseaudio 1:12.2-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Tags:  disco wayland-session
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-03-20 (7 days ago)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd02/14/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

Re: [Desktop-packages] [Bug 1768166] Re: Random crashes

[Ping-Wu]

"My biggest concern--ibus-libpinyin, also is working OK!"

"ibus-libpinyin" should be --ibus-pinyin--.

On Fri, May 31, 2019 at 2:10 PM Gunnar Hjalmarsson <
1768...@bugs.launchpad.net> wrote:

> Call for testing
> 
>
> I hope for help by both Ping-Wu (the bug reporter) and other Chinese
> users to test the proposed upgrade of the ibus-libpinyin package in
> Ubuntu 18.04. I have subscribed the Ubuntu CJK Testers team to this bug
> report to reach out to more possible testers.
>
> "Intelligent Pinyin", which is provided by ibus-libpinyin, is the
> default input method in Ubuntu for inputting Simplified Chinese. While
> we want to address the crash problem reported in this bug, we want to
> minimize the regression risk.
>
> The new versions of the affected packages are available in bionic-
> proposed. These are the steps to install them:
>
>
> 1. Enable bionic-proposed
> -
>
> * Open Software & Updates and select the "Developer Options" tab.
>
> * Check the "Pre-released updates" option.
>
> 2. Update the package information on your system
> 
>
> sudo apt update
>
> 3. Install/upgrade the packages
> ---
>
> sudo apt install ibus-libpinyin libpinyin-data libpinyin13
>
> (Please note that it's not sufficient for this test to only upgrade
> ibus-libpinyin.)
>
> 4. Disable bionic-proposed
> --
>
> * Open Software & Updates and select the "Developer Options" tab.
>
> * Uncheck the "Pre-released updates" option.
>
> 5. Update the package information on your system
> 
>
> sudo apt update
>
>
> With that your system is back to normal, except for those three packages
> from -proposed. You can confirm that you got the right versions by using
> this command:
>
> dpkg-query -W ibus-libpinyin libpinyin-data libpinyin13
>
> It should show this info:
>
> ibus-libpinyin  1.11.0-1ubuntu0.18.04.1
> libpinyin-data:amd642.2.2-1~ubuntu18.04.1
> libpinyin13:amd64   2.2.2-1~ubuntu18.04.1
>
>
> Then I simply ask you to use "Intelligent Pinyin" for your daily needs,
> and submit a comment here after a few days about your experience. Any kinds
> of comments are helpful, both "works well" and info about issues you
> stumble upon. Most important, of course, is that no new issues are
> introduced via this upgrade.
>
> Thanks in advance for your help with this!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1768166
>
> Title:
>   Random crashes
>
> Status in ibus-libpinyin package in Ubuntu:
>   Fix Released
> Status in libpinyin package in Ubuntu:
>   Fix Released
> Status in ibus-libpinyin source package in Bionic:
>   Fix Committed
> Status in libpinyin source package in Bionic:
>   Fix Committed
> Status in ibus-libpinyin source package in Cosmic:
>   Fix Committed
> Status in libpinyin source package in Cosmic:
>   Fix Committed
>
> Bug description:
>   [Impact]
>
>   ibus-libpinyin has proved to crash far too often. One or more files in
>   ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
>   directory allows the user to keep using ibus-libpinyin.
>
>   In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are
>   present, and the number of crashes has been reduced significantly:
>
>   https://errors.ubuntu.com/?package=ibus-libpinyin=month
>
>   Upstream ChangeLog ibus-libpinyin:
>   --
>   version 1.11.0
>   * fixes keypad decimal
>   * fixes emoji candidates
>   * support configurable opencc config
>
>   version 1.10.92
>   * fixes Enter handling
>
>   version 1.10.91
>   * support ime.register_trigger in lua extension
>   * support predicted candidates
>   * support emoji input
>
>   version 1.10.0
>   * bug fixes
>
>   version 1.9.91
>   * migrate to use GSettings
>   * fixes lyx short cut issue
>
>   version 1.9.3
>   * translate input method name in ibus menu
>
>   Upstream ChangeLog libpinyin:
>   -
>   version 2.2.2
>   * minor fixes
>
>   version 2.2.1
>   * fixes predicted candidates
>
>   version 2.2.0
>   * bug fixes
>
>   The proposal is to backport the disco versions of those packages to
>   bionic and cosmic in an attempt to prevent crashes. Proposed uploads
>   are available in this PPA:
>
>   https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin
>
>   [Test Case]
>
>   * Install from {bionic,cosmic}-proposed:
> - libpinyin13
> - libpinyin-data
> - ibus-libpinyin
>
>   * Use "Intelligent Pinyin" for typing and confirm that no new issues
> show up when doing so.
>
>   (This is apparently not a confirmation that the upload really fixes
>   the bug. To compensate for that, we will await testing of the
>   -proposed packages by a few Chinese users before considering the
>   uploads verified.)
>
>   Reverse dependencies
>   

[Desktop-packages] [Bug 1715602] Re: ubiquity-dm / Install Ubuntu - Power button/menu does nothing

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1715602

** Tags added: iso-testing

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

Title:
  ubiquity-dm / Install Ubuntu - Power button/menu does nothing

Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  Artful Desktop 20170907

  In ubiquity-dm and 'Install Ubuntu' the power button does nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubiquity 17.10.6
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 09:55:57 2017
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170907)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Desktop-packages] [Bug 1768166] Re: Random crashes

[Ping-Wu]

At the first run, things are looking good.  My biggest
concern--ibus-libpinyin, also is working OK!

On Fri, May 31, 2019 at 2:10 PM Gunnar Hjalmarsson <
1768...@bugs.launchpad.net> wrote:

> Call for testing
> 
>
> I hope for help by both Ping-Wu (the bug reporter) and other Chinese
> users to test the proposed upgrade of the ibus-libpinyin package in
> Ubuntu 18.04. I have subscribed the Ubuntu CJK Testers team to this bug
> report to reach out to more possible testers.
>
> "Intelligent Pinyin", which is provided by ibus-libpinyin, is the
> default input method in Ubuntu for inputting Simplified Chinese. While
> we want to address the crash problem reported in this bug, we want to
> minimize the regression risk.
>
> The new versions of the affected packages are available in bionic-
> proposed. These are the steps to install them:
>
>
> 1. Enable bionic-proposed
> -
>
> * Open Software & Updates and select the "Developer Options" tab.
>
> * Check the "Pre-released updates" option.
>
> 2. Update the package information on your system
> 
>
> sudo apt update
>
> 3. Install/upgrade the packages
> ---
>
> sudo apt install ibus-libpinyin libpinyin-data libpinyin13
>
> (Please note that it's not sufficient for this test to only upgrade
> ibus-libpinyin.)
>
> 4. Disable bionic-proposed
> --
>
> * Open Software & Updates and select the "Developer Options" tab.
>
> * Uncheck the "Pre-released updates" option.
>
> 5. Update the package information on your system
> 
>
> sudo apt update
>
>
> With that your system is back to normal, except for those three packages
> from -proposed. You can confirm that you got the right versions by using
> this command:
>
> dpkg-query -W ibus-libpinyin libpinyin-data libpinyin13
>
> It should show this info:
>
> ibus-libpinyin  1.11.0-1ubuntu0.18.04.1
> libpinyin-data:amd642.2.2-1~ubuntu18.04.1
> libpinyin13:amd64   2.2.2-1~ubuntu18.04.1
>
>
> Then I simply ask you to use "Intelligent Pinyin" for your daily needs,
> and submit a comment here after a few days about your experience. Any kinds
> of comments are helpful, both "works well" and info about issues you
> stumble upon. Most important, of course, is that no new issues are
> introduced via this upgrade.
>
> Thanks in advance for your help with this!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1768166
>
> Title:
>   Random crashes
>
> Status in ibus-libpinyin package in Ubuntu:
>   Fix Released
> Status in libpinyin package in Ubuntu:
>   Fix Released
> Status in ibus-libpinyin source package in Bionic:
>   Fix Committed
> Status in libpinyin source package in Bionic:
>   Fix Committed
> Status in ibus-libpinyin source package in Cosmic:
>   Fix Committed
> Status in libpinyin source package in Cosmic:
>   Fix Committed
>
> Bug description:
>   [Impact]
>
>   ibus-libpinyin has proved to crash far too often. One or more files in
>   ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
>   directory allows the user to keep using ibus-libpinyin.
>
>   In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are
>   present, and the number of crashes has been reduced significantly:
>
>   https://errors.ubuntu.com/?package=ibus-libpinyin=month
>
>   Upstream ChangeLog ibus-libpinyin:
>   --
>   version 1.11.0
>   * fixes keypad decimal
>   * fixes emoji candidates
>   * support configurable opencc config
>
>   version 1.10.92
>   * fixes Enter handling
>
>   version 1.10.91
>   * support ime.register_trigger in lua extension
>   * support predicted candidates
>   * support emoji input
>
>   version 1.10.0
>   * bug fixes
>
>   version 1.9.91
>   * migrate to use GSettings
>   * fixes lyx short cut issue
>
>   version 1.9.3
>   * translate input method name in ibus menu
>
>   Upstream ChangeLog libpinyin:
>   -
>   version 2.2.2
>   * minor fixes
>
>   version 2.2.1
>   * fixes predicted candidates
>
>   version 2.2.0
>   * bug fixes
>
>   The proposal is to backport the disco versions of those packages to
>   bionic and cosmic in an attempt to prevent crashes. Proposed uploads
>   are available in this PPA:
>
>   https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin
>
>   [Test Case]
>
>   * Install from {bionic,cosmic}-proposed:
> - libpinyin13
> - libpinyin-data
> - ibus-libpinyin
>
>   * Use "Intelligent Pinyin" for typing and confirm that no new issues
> show up when doing so.
>
>   (This is apparently not a confirmation that the upload really fixes
>   the bug. To compensate for that, we will await testing of the
>   -proposed packages by a few Chinese users before considering the
>   uploads verified.)
>
>   Reverse dependencies
>   
> 

[Desktop-packages] [Bug 1809788] Re: Shell dialog messages are truncated and ellipsized...

[Treviño]

apt-cache policy gnome-shell
gnome-shell:
  Installato: 3.28.4-0ubuntu18.04.1
  Candidato:  3.28.4-0ubuntu18.04.1
  Tabella versione:
 *** 3.28.4-0ubuntu18.04.1 100

Message is fully visible here

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

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

Title:
  Shell dialog messages are truncated and ellipsized...

Status in GNOME Shell:
  Fix Released
Status in OEM Priority Project:
  In Progress
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Disco:
  In Progress

Bug description:
  [ Impact ]

  When plugging in a Thunderbolt device, under certain conditions, there
  could be a pop-up window asking for authentication from the user.

  In the dialog box, the prompt text is truncated. Please refer to
  attached screen shot for more details.

  The issue can be found in the gnome-control-center package for bionic:
  1:3.28.2-0ubuntu0.18.04.2
  1:3.28.1-0ubuntu1

  However, the issue is confirmed to be gone in latest such package for Cosmic:
  1:3.30.2-1ubuntu0.18.10.1

  [ Test case ]

  In a terminal run:
   $ boltctl enroll foo

  Text in the auth message should not be cut, using both Ubuntu theme,
  Yaru or default gnome-shell

  [ Regression Potential ]

  The dialogs text is wrapped when not needed, or dialog text isn't
  ellipsized when requested.

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

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

[Desktop-packages] [Bug 1827029] Re: Extended characters in OSK don't get entered

[Treviño]

$ apt-cache policy mutter
mutter:
  Installato: 3.28.4-0ubuntu18.04.1
  Candidato:  3.28.4-0ubuntu18.04.1
  Tabella versione:
 *** 3.28.4-0ubuntu18.04.1 100

Umlaut is properly inserted with this version.

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

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

Title:
  Extended characters in OSK don't get entered

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Fix Committed
Status in mutter source package in Cosmic:
  In Progress
Status in mutter source package in Disco:
  Fix Released

Bug description:
  [Impact]
  This bug affects any of the "extended characters" clicked on from the 
long-press popup in the Screen Keyboard.

  [Test Case]
  1. Open GNOME Settings > Universal Access
  2. Enable the Screen Keyboard. (Optionally, turn on Always Show Universal 
Access Menu to make turning the Screen Keyboard on and off easier.)
  3. Open Text Editor
  4. Click the u button on the Screen Keyboard
  5. Long-press the u button on the Screen Keyboard for a few seconds.
  6. On the popup, click the ü character.

  What Happens
  In Step 4, u is entered in the Text Editor document.
  Nothing is entered in Step 5.

  [Regression Potential]
  The code to be backported only affects OSK. Check that normal OSK keys (e.g. 
a,b,c,...) normally works.

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

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

[Desktop-packages] [Bug 1740869] Re: is not responding window is constantly showing when debugging a program

[Treviño]

$ apt-cache policy gnome-shell
gnome-shell:
  Installato: 3.28.4-0ubuntu18.04.1
  Candidato:  3.28.4-0ubuntu18.04.1
  Tabella versione:
 *** 3.28.4-0ubuntu18.04.1 100

I confirm the fix works.

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

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

Title:
   is not responding window is constantly showing when
  debugging a program

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Disco:
  Fix Released

Bug description:
  Mentioned window about no responding program is showing and stealing
  focus when I try to debug a Java program in Eclipse. When I click on
  Wait, it disappears for a moment and opens again.

  This renders Ubuntu 17.10 with Gnome 3 nearly useless for program
  debugging.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: mutter 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  2 14:22:56 2018
  InstallationDate: Installed on 2017-12-04 (28 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1796606] Re: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node() from BoxPointer::_reposition()

[Treviño]

No errors.ubuntu.com report for 3.28.4 and 3.32.0 (where the same patch
is applied), plus this fix is part of the upstream release, and so
marking as verified as per the GNOME SRU release exception.

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

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

Title:
  gnome-shell crashed with SIGSEGV in st_widget_get_theme_node() from
  BoxPointer::_reposition()

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Disco:
  Fix Released

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/804

  ---

  [ Impact ]

   - GNOME Shell crashes in st_widget_get_theme_node

  [ Test Case ]

   - No clear test case for this, monitoring errors.ubuntu.com is the
  only feasible solution

  [ Regression Potential ]

  Shell actors might have wrong theming.
  The crash will be converted in error trackable through journalctl

  ---

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

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

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

[Desktop-packages] [Bug 1831301] Re: sound doesn't works in both kernel. no one cards is recognize by system-

[Seth Arnold]

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

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

Title:
  sound doesn't works in both kernel. no one cards is recognize by
  system-

Status in linux package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base (not installed)
  ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Sat Jun  1 04:26:10 2019
  InstallationDate: Installed on 2019-04-03 (58 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-05-31T22:19:11.232515

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

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

[Desktop-packages] [Bug 1831301] [NEW] sound doesn't works in both kernel. no one cards is recognize by system-

[gabriele]

Public bug reported:

.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base (not installed)
ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
Date: Sat Jun  1 04:26:10 2019
InstallationDate: Installed on 2019-04-03 (58 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-05-31T22:19:11.232515

** Affects: linux (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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1831301

Title:
  sound doesn't works in both kernel. no one cards is recognize by
  system-

Status in linux package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base (not installed)
  ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Sat Jun  1 04:26:10 2019
  InstallationDate: Installed on 2019-04-03 (58 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-05-31T22:19:11.232515

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

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

[Desktop-packages] [Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]

[Treviño]

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

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

Title:
  [bionic][regression] gnome-shell crashes with SIGSEGV in
  meta_window_actor_is_destroyed(self=NULL) called from
  _switchWorkspaceDone() [windowManager.js:1787]

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  Invalid
Status in gnome-shell source package in Eoan:
  Invalid

Bug description:
  https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/927

  [ Impact ]

  Switching workspace with the Android Emulator running will blink the
  screen as if gnome restarted, if I switch workspace one more time, it
  will completely crash and I will need to log in again.

  [ Test case ]

  Open Android Emulator and switch workspace
  or
  Open Skype, start a test call and switch workspace

  GNOME-Shell should not crash

  [ Regression potential ]

  Very low, we remove windows from Javascript array when they're destroyed.
  A possible regression could be not switching to workspace when selecting a 
window that is in another one.

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  Uname: Linux 4.20.3-acso x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 19 20:05:34 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-01-15 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1768166] Re: Random crashes

[Gunnar Hjalmarsson]

Call for testing


I hope for help by both Ping-Wu (the bug reporter) and other Chinese
users to test the proposed upgrade of the ibus-libpinyin package in
Ubuntu 18.04. I have subscribed the Ubuntu CJK Testers team to this bug
report to reach out to more possible testers.

"Intelligent Pinyin", which is provided by ibus-libpinyin, is the
default input method in Ubuntu for inputting Simplified Chinese. While
we want to address the crash problem reported in this bug, we want to
minimize the regression risk.

The new versions of the affected packages are available in bionic-
proposed. These are the steps to install them:


1. Enable bionic-proposed
-

* Open Software & Updates and select the "Developer Options" tab.

* Check the "Pre-released updates" option.

2. Update the package information on your system


sudo apt update

3. Install/upgrade the packages
---

sudo apt install ibus-libpinyin libpinyin-data libpinyin13

(Please note that it's not sufficient for this test to only upgrade
ibus-libpinyin.)

4. Disable bionic-proposed
--

* Open Software & Updates and select the "Developer Options" tab.

* Uncheck the "Pre-released updates" option.

5. Update the package information on your system


sudo apt update


With that your system is back to normal, except for those three packages from 
-proposed. You can confirm that you got the right versions by using this 
command:

dpkg-query -W ibus-libpinyin libpinyin-data libpinyin13

It should show this info:

ibus-libpinyin  1.11.0-1ubuntu0.18.04.1
libpinyin-data:amd642.2.2-1~ubuntu18.04.1
libpinyin13:amd64   2.2.2-1~ubuntu18.04.1


Then I simply ask you to use "Intelligent Pinyin" for your daily needs, and 
submit a comment here after a few days about your experience. Any kinds of 
comments are helpful, both "works well" and info about issues you stumble upon. 
Most important, of course, is that no new issues are introduced via this 
upgrade.

Thanks in advance for your help with this!

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

Title:
  Random crashes

Status in ibus-libpinyin package in Ubuntu:
  Fix Released
Status in libpinyin package in Ubuntu:
  Fix Released
Status in ibus-libpinyin source package in Bionic:
  Fix Committed
Status in libpinyin source package in Bionic:
  Fix Committed
Status in ibus-libpinyin source package in Cosmic:
  Fix Committed
Status in libpinyin source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  ibus-libpinyin has proved to crash far too often. One or more files in
  ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
  directory allows the user to keep using ibus-libpinyin.

  In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are
  present, and the number of crashes has been reduced significantly:

  https://errors.ubuntu.com/?package=ibus-libpinyin=month

  Upstream ChangeLog ibus-libpinyin:
  --
  version 1.11.0
  * fixes keypad decimal
  * fixes emoji candidates
  * support configurable opencc config

  version 1.10.92
  * fixes Enter handling

  version 1.10.91
  * support ime.register_trigger in lua extension
  * support predicted candidates
  * support emoji input

  version 1.10.0
  * bug fixes

  version 1.9.91
  * migrate to use GSettings
  * fixes lyx short cut issue

  version 1.9.3
  * translate input method name in ibus menu

  Upstream ChangeLog libpinyin:
  -
  version 2.2.2
  * minor fixes

  version 2.2.1
  * fixes predicted candidates

  version 2.2.0
  * bug fixes

  The proposal is to backport the disco versions of those packages to
  bionic and cosmic in an attempt to prevent crashes. Proposed uploads
  are available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin

  [Test Case]

  * Install from {bionic,cosmic}-proposed:
    - libpinyin13
    - libpinyin-data
    - ibus-libpinyin

  * Use "Intelligent Pinyin" for typing and confirm that no new issues
    show up when doing so.

  (This is apparently not a confirmation that the upload really fixes
  the bug. To compensate for that, we will await testing of the
  -proposed packages by a few Chinese users before considering the
  uploads verified.)

  Reverse dependencies
  
  Besides ibus-libpinyin, also fcitx-libpinyin and ibus-libzhuyin depend on 
packages belonging to the libpinyin source package. So additional test measures 
are:

  * Install fcitx-libpinyin and ibus-libzhuyin.

  * Use both those tools for typing Chinese, and confirm that you don't
    observe any adverse effects of the libpinyin upgrade.

  [Regression Potential]

  The changes are mostly bug fixes, so the 

[Desktop-packages] [Bug 1768166] Re: Random crashes

[Gunnar Hjalmarsson]

I have done these tests:

bionic
--
Installed from bionic-proposed these packages:

* ibus-libpinyin 1.11.0-1ubuntu0.18.04.1
* libpinyin-data 2.2.2-1~ubuntu18.04.1
* libpinyin13 2.2.2-1~ubuntu18.04.1

Used the Intelligent Pinyin method for inputting some Chinese
characters. Didn't observe any oddities. Bug #1829947 is not present (as
expected).

cosmic
--
Installed from cosmic-proposed these packages:

* ibus-libpinyin 1.11.0-1ubuntu0.18.10.1
* libpinyin-data 2.2.2-1~ubuntu18.10.1
* libpinyin13 2.2.2-1~ubuntu18.10.1

Used the Intelligent Pinyin method for inputting some Chinese
characters. Didn't observe any oddities.

fcitx-libpinyin and ibus-libzhuyin
--
Installed fcitx-libpinyin 0.5.3-1 and ibus-libzhuyin 1.8.2-1 from 
bionic-release, and libzhuyin13 2.2.2-1~ubuntu18.04.1 from bionic-proposed.
Used
- the Pinyin (LibPinyin) (Fcitx) method (on Unity)
- the New Zhuyin method
for inputting some Chinese characters. Didn't observe any issues due to the 
upgraded packages built from libpinyin.

Successfully rebuilt the bionic-release versions of fcitx-libpinyin and
ibus-libzhuyin with libpinyin 2.2.2.

Conclusion: We can stay with the current bionic versions of fcitx-
libpinyin and ibus-libzhuyin. Upgrading those would be beyond the scope
of this bug.

** Description changed:

  [Impact]
  
  ibus-libpinyin has proved to crash far too often. One or more files in
  ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
  directory allows the user to keep using ibus-libpinyin.
  
  In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are
  present, and the number of crashes has been reduced significantly:
  
  https://errors.ubuntu.com/?package=ibus-libpinyin=month
  
  Upstream ChangeLog ibus-libpinyin:
  --
  version 1.11.0
  * fixes keypad decimal
  * fixes emoji candidates
  * support configurable opencc config
  
  version 1.10.92
  * fixes Enter handling
  
  version 1.10.91
  * support ime.register_trigger in lua extension
  * support predicted candidates
  * support emoji input
  
  version 1.10.0
  * bug fixes
  
  version 1.9.91
  * migrate to use GSettings
  * fixes lyx short cut issue
  
  version 1.9.3
  * translate input method name in ibus menu
  
  Upstream ChangeLog libpinyin:
  -
  version 2.2.2
  * minor fixes
  
  version 2.2.1
  * fixes predicted candidates
  
  version 2.2.0
  * bug fixes
  
  The proposal is to backport the disco versions of those packages to
  bionic and cosmic in an attempt to prevent crashes. Proposed uploads are
  available in this PPA:
  
  https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin
  
  [Test Case]
  
  * Install from {bionic,cosmic}-proposed:
    - libpinyin13
    - libpinyin-data
    - ibus-libpinyin
  
  * Use "Intelligent Pinyin" for typing and confirm that no new issues
    show up when doing so.
  
  (This is apparently not a confirmation that the upload really fixes the
  bug. To compensate for that, we will await testing of the -proposed
  packages by a few Chinese users before considering the uploads
  verified.)
  
  Reverse dependencies
  
- Besides ibus-libpinyin, also fcitx-libpinyin and ibus-zhuyin depend on 
packages belonging to the libpinyin source package. So additional test measures 
are:
+ Besides ibus-libpinyin, also fcitx-libpinyin and ibus-libzhuyin depend on 
packages belonging to the libpinyin source package. So additional test measures 
are:
  
- * Install fcitx-libpinyin and ibus-zhuyin.
+ * Install fcitx-libpinyin and ibus-libzhuyin.
  
  * Use both those tools for typing Chinese, and confirm that you don't
    observe any adverse effects of the libpinyin upgrade.
  
  [Regression Potential]
  
  The changes are mostly bug fixes, so the regression risk should be
  limited. Also consider that the starting point is a rather unstable
  functionality.
  
  NOTE TO SRU TEAM: Please let the SRU age for longer than 7 days to get
  as much testing as possible. There do not seem to be too many risky
  changes carried, but such jumps in upstream versions always carry some
  regression-risk.
  
  [Original description]
  
  I have experienced random ibus-libpinyin crashes in bionic.  I cannot
  reproduce it, but it occurred at least a few times, even after the
  official bionic release.  Same crashes were also reported in the Ubuntu
  Chinese forum.
  
  Currently, the workaround is to delete the ~/.cache/ibus/libpinyin
  folder.
  
  I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he
  suggested that we update the version of ibus-libpinyin to 1.10.
  
  Can we give this update a trial?

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

Title:
  Random crashes

Status in ibus-libpinyin package in Ubuntu:
  Fix Released
Status in libpinyin package in 

[Desktop-packages] [Bug 1830096] Re: Firefox 67 in Ubuntu 18.10 thinks it's an older version

[Mason Loring Bliss]

For what it's worth, my kids encountered this on two desktops today,
moving from 16.04 to 18.04. As this would be a major issue for non-
technical folk I'd urge getting the fix out the door sooner rather than
later - especially on 18.04, to preserve LTS as being a safe choice.

The workaround I used here, prior to being shown this bug, was to let
Firefox make a new profile and to follow these instructions to copy over
all the critical files:

https://support.mozilla.org/en-US/kb/recovering-important-data-from-
an-old-profile

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

Title:
  Firefox 67 in Ubuntu 18.10 thinks it's an older version

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

Bug description:
  Today I installed the Firefox 67 update on Ubuntu 18.04, then updated
  to Ubuntu 18.10. After this, launching Firefox gave me a "Using an
  older version of Firefox" message with only two options: create a new
  profile or quit.

  Apparently the Firefox 67 build for 18.10 thinks it's an older version
  than the Firefox 67 build for 18.04.

  For now I worked around the issue by manually installing the Firefox
  67 build for Ubuntu 18.04, which did load the existing user profile
  correctly.

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

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

[Desktop-packages] [Bug 1830096] Re: Firefox 67 in Ubuntu 18.10 thinks it's an older version

[Seth Arnold]

I saw a comment somewhere that suggested this was "rare".

I think this is actually pretty common -- it feels like this has been
discussed more than any other single issue on irc lately.

The consequence for most users is losing their entire Firefox history,
settings, addons, saved passwords, sessions, etc.

Can we please push the time-delayed-rebuilds, if not the actual fixes,
sooner rather than later?

Thanks

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

Title:
  Firefox 67 in Ubuntu 18.10 thinks it's an older version

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

Bug description:
  Today I installed the Firefox 67 update on Ubuntu 18.04, then updated
  to Ubuntu 18.10. After this, launching Firefox gave me a "Using an
  older version of Firefox" message with only two options: create a new
  profile or quit.

  Apparently the Firefox 67 build for 18.10 thinks it's an older version
  than the Firefox 67 build for 18.04.

  For now I worked around the issue by manually installing the Firefox
  67 build for Ubuntu 18.04, which did load the existing user profile
  correctly.

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

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

[Desktop-packages] [Bug 1831299] [NEW] i cant install driver

[Iqbale Maulana]

Public bug reported:

idk more about this bug , but can you fix it

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun  1 06:10:43 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0724]
InstallationDate: Installed on 2019-05-30 (1 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: Acer Aspire V5-431
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic 
root=UUID=c6efd4c5-770f-43f5-babc-e1f4d6123bf6 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/18/2012
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: V1.05.
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Aspire V5-431
dmi.board.vendor: Acer
dmi.board.version: V1.05.
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.05.
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV1.05.:bd04/18/2012:svnAcer:pnAspireV5-431:pvrV1.05.:rvnAcer:rnAspireV5-431:rvrV1.05.:cvnAcer:ct9:cvrV1.05.:
dmi.product.family: ChiefRiver System
dmi.product.name: Aspire V5-431
dmi.product.sku: System SKUNumber
dmi.product.version: V1.05.
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  i cant install driver

Status in xorg package in Ubuntu:
  New

Bug description:
  idk more about this bug , but can you fix it

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  1 06:10:43 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0724]
  InstallationDate: Installed on 2019-05-30 (1 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Acer Aspire V5-431
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic 
root=UUID=c6efd4c5-770f-43f5-babc-e1f4d6123bf6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V1.05.
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire V5-431
  dmi.board.vendor: Acer
  dmi.board.version: V1.05.
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05.
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV1.05.:bd04/18/2012:svnAcer:pnAspireV5-431:pvrV1.05.:rvnAcer:rnAspireV5-431:rvrV1.05.:cvnAcer:ct9:cvrV1.05.:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire V5-431
  dmi.product.sku: System SKUNumber
  dmi.product.version: V1.05.
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  

[Desktop-packages] [Bug 1831039] Re: wayland onscreen keyboard not open

[Petr Olexa]

apport-collect sent - but no update in this issue

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

Title:
  wayland onscreen keyboard not open

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When using wayland - onscreen keyboard not open in text inputs in many
  applications such as firefox or chrome.

  Ubuntu 18.04

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

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

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

[Warren]

Sorry I thought this was a thread about Brave Browser and freezing, not
just Ubuntu in general.  Well touch wood I only get freezes with Braze
meaning I'll have to ditch Brave Browser.

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

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

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

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

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

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

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

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

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

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

[Warren]

Hi All.

I am getting system freezes on a dual boot base unit with Ryzen 1700 and
a R9 380 graphics card.  I'm running Kubuntu 19.04.  The whole system
locks up and I have to hard power down with the power button.  This is
happening at least once a day.  I don't think its worth trying fixes #43
and #58 because this is not a laptop and my graphics card is not Intel.

This is annoying as I have just migrated over to Brave but now I have
gone back to FF (if this doesn't get fixed) for good.

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1831140] Re: GNOME Magnifier Flickering when using none-full screen modes

[Lee Clark]

Both of my machines are now on 19.04, I'm still seeing the issue. I've
got all extensions turned off.

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

Title:
  GNOME Magnifier Flickering when using none-full screen  modes

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When using the GNOME magnifier (Zoom) feature the magnified display
  flickers when used in any of the following modes: Left, Right, Top or
  Bottom screen part. This occures when the mouse moves towards the edge
  directly opossite to the magnified view.

  To reproduce:
  * Open GNOME Control Centre.
  * Go to Universal Access.
  * Click on Zoom.
  * Enable Zoom
  * Selct either Top, Bottom, Left or Right from the screen part drop down list.
  * Move the mouse cursor to the opossite edge of the screen to that where the 
magnified view is located.

  I have tested on multiple systems running Ubuntu 18.04. I am yet to
  test with 19.04.

  I use this feature to allow me to use two monitors with one showing a
  magnified view the other showing a normal view.

  Happy to provide additional details.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 30 19:14:43 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-03-12 (78 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

[Bug Watch Updater]

** Changed in: systemd (Debian)
   Status: Unknown => New

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

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in udisks2 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Committed
Status in udisks2 source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Fix Committed
Status in udisks2 source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  New
Status in systemd source package in Disco:
  Fix Committed
Status in udisks2 source package in Disco:
  Invalid
Status in linux source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Fix Committed
Status in udisks2 source package in Eoan:
  Invalid
Status in systemd package in Debian:
  New

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

  --
  sru template for systemd upload:

  [impact]
  buffer overflow can cause memory corruption; this is seen in failed 
autopkgtests

  [test case]
  see comment 6

  [regression potential]
  the patch is minimal and clearly correct; however the regression potential is 
around invalid/corrupted keys read from the keyring.

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

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

[Desktop-packages] [Bug 1831295] [NEW] Firefox freeze when I drag an URL address to a Nautilus window

[J-Paul BERARD]

Public bug reported:

When a web page is displayed in Firefox, if you select the URL in the address 
bar and try to drag it to the desktop or a Nautilus window, it is not done.
But, afterwards, the mouse cursor become a hand and nothing is more possible 
with Firefox : you cannot select something, see the menu...
You can only kill the app.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: firefox 67.0+build2-0ubuntu0.19.04.1
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  jpaul  2420 F pulseaudio
 /dev/snd/controlC0:  jpaul  2420 F pulseaudio
 /dev/snd/controlC2:  jpaul  2420 F pulseaudio
BuildID: 20190517140251
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Fri May 31 23:21:34 2019
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2019-04-26 (35 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
IpRoute:
 default via 192.168.0.254 dev wlp4s6 proto dhcp metric 600 
 169.254.0.0/16 dev wlp4s6 scope link metric 1000 
 192.168.0.0/24 dev wlp4s6 proto kernel scope link src 192.168.0.10 metric 600
Locales: extensions.sqlite corrupt or missing
Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:1151
PrefSources: prefs.js
ProcEnviron:
 LANGUAGE=fr_FR:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=67.0/20190517140251 (In use)
RelatedPackageVersions: adobe-flashplugin 1:20190514.1-0ubuntu0.19.04.1
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/05/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.80
dmi.board.name: 970 Extreme4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd08/05/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug disco wayland-session

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

Title:
  Firefox freeze when I drag an URL address to a Nautilus window

Status in firefox package in Ubuntu:
  New

Bug description:
  When a web page is displayed in Firefox, if you select the URL in the address 
bar and try to drag it to the desktop or a Nautilus window, it is not done.
  But, afterwards, the mouse cursor become a hand and nothing is more possible 
with Firefox : you cannot select something, see the menu...
  You can only kill the app.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: firefox 67.0+build2-0ubuntu0.19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jpaul  2420 F pulseaudio
   /dev/snd/controlC0:  jpaul  2420 F pulseaudio
   /dev/snd/controlC2:  jpaul  2420 F pulseaudio
  BuildID: 20190517140251
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 31 23:21:34 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2019-04-26 (35 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.0.254 dev wlp4s6 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s6 scope link metric 1000 
   192.168.0.0/24 dev wlp4s6 proto kernel scope link src 192.168.0.10 metric 600
  Locales: extensions.sqlite corrupt or missing

[Desktop-packages] [Bug 1770929] Re: Duplicity fails with UnicodeDecodeError in uexc function

[Aaron Whitehouse]

All,

This should be fixed in 0.8.00, which has now been released. This is the
first 0.8-series release, so expect issues and test it out on data you
can afford to lose (if it comes to that).

I have now packaged up this version as a snap. You can install it by typing:
snap install duplicity --classic --beta
Please uninstall your current version of duplicity to ensure you are using the 
snap instead of one from apt etc.
(This will work out of the box on nearly all versions of Ubuntu. If you use a 
different distro and have never installed snaps before, visit this page:
https://docs.snapcraft.io/installing-snapd )

This includes the latest duplicity and all dependencies wrapped up in a
self-contained bundle. You should not need to install anything else for
this to work (including for all backends).

If you do test this, it would be very helpful if you could please
comment here, even if the only feedback is that all worked as expected.

If you are giving any feedback, please also give the output of:
which duplicity
and
snap list | grep duplicity
and let me know which backends you used.

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

Title:
  Duplicity fails with UnicodeDecodeError in uexc function

Status in Duplicity:
  Fix Released
Status in duplicity package in Ubuntu:
  Fix Released

Bug description:
  backup worked under Ubuntu 17.10
  It also worked on Ubuntu 18.4 before last week's update (run on Friday 11.5)
  my drive is encrypted
  this is the error message in the error frame
  Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1393, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
  incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
  globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
  (tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
146, in schedule_task
  return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
172, in __run_synchronously
  ret = fn(*params)
File "/usr/bin/duplicity", line 453, in 
  vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
  backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in 
inner_retry
  % (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
  return ufn(unicode(e).encode('utf-8'))
   UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: 
ordinal not in range(128)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: duplicity 0.7.17-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 13 09:55:00 2018
  InstallationDate: Installed on 2018-05-01 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1753120] Re: package libgtkmm-2.4-doc (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README', which is also in package

[thomas]

strange

Correcting dependencies... Done
The following additional packages will be installed:
  libgtkmm-2.4-dev
The following packages will be upgraded:
  libgtkmm-2.4-dev
1 upgraded, 0 newly installed, 0 to remove and 92 not upgraded.


same package will b upgraded and installed, but does not worl

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

Title:
  package libgtkmm-2.4-doc (not installed) failed to install/upgrade:
  trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README',
  which is also in package libgtkmm-2.4-dev:amd64 1:2.24.5-2

Status in gtkmm2.4 package in Ubuntu:
  Confirmed
Status in gtkmm2.4 package in Debian:
  Fix Released

Bug description:
  E: /var/cache/apt/archives/libgtkmm-2.4-doc_1%3a2.24.5-2_all.deb:
  trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README',
  which is also in package libgtkmm-2.4-dev:amd64 1:2.24.5-2

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgtkmm-2.4-doc (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-10.11-lowlatency 4.15.3
  Uname: Linux 4.15.0-10-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sat Mar  3 10:59:55 2018
  DuplicateSignature:
   package:libgtkmm-2.4-doc:(not installed)
   Unpacking libgtkmm-2.4-doc (1:2.24.5-2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-ebi0hY/58-libgtkmm-2.4-doc_1%3a2.24.5-2_all.deb 
(--unpack):
trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README', 
which is also in package libgtkmm-2.4-dev:amd64 1:2.24.5-2
  ErrorMessage: trying to overwrite 
'/usr/share/doc/libgtkmm-2.4-dev/examples/README', which is also in package 
libgtkmm-2.4-dev:amd64 1:2.24.5-2
  InstallationDate: Installed on 2018-03-02 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180302)
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu2
  SourcePackage: gtkmm2.4
  Title: package libgtkmm-2.4-doc (not installed) failed to install/upgrade: 
trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README', which is 
also in package libgtkmm-2.4-dev:amd64 1:2.24.5-2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtkmm2.4/+bug/1753120/+subscriptions

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

[Desktop-packages] [Bug 1753120] Re: package libgtkmm-2.4-doc (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README', which is also in package

[thomas]

The following packages have unmet dependencies:
 libgtkmm-2.4-dev : Depends: libgtkmm-2.4-1v5 (= 1:2.24.4-2) but 1:2.24.5-2 is 
installed

how to remove?

apt --fix-broken install does not help

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

Title:
  package libgtkmm-2.4-doc (not installed) failed to install/upgrade:
  trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README',
  which is also in package libgtkmm-2.4-dev:amd64 1:2.24.5-2

Status in gtkmm2.4 package in Ubuntu:
  Confirmed
Status in gtkmm2.4 package in Debian:
  Fix Released

Bug description:
  E: /var/cache/apt/archives/libgtkmm-2.4-doc_1%3a2.24.5-2_all.deb:
  trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README',
  which is also in package libgtkmm-2.4-dev:amd64 1:2.24.5-2

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgtkmm-2.4-doc (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-10.11-lowlatency 4.15.3
  Uname: Linux 4.15.0-10-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sat Mar  3 10:59:55 2018
  DuplicateSignature:
   package:libgtkmm-2.4-doc:(not installed)
   Unpacking libgtkmm-2.4-doc (1:2.24.5-2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-ebi0hY/58-libgtkmm-2.4-doc_1%3a2.24.5-2_all.deb 
(--unpack):
trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README', 
which is also in package libgtkmm-2.4-dev:amd64 1:2.24.5-2
  ErrorMessage: trying to overwrite 
'/usr/share/doc/libgtkmm-2.4-dev/examples/README', which is also in package 
libgtkmm-2.4-dev:amd64 1:2.24.5-2
  InstallationDate: Installed on 2018-03-02 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180302)
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu2
  SourcePackage: gtkmm2.4
  Title: package libgtkmm-2.4-doc (not installed) failed to install/upgrade: 
trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README', which is 
also in package libgtkmm-2.4-dev:amd64 1:2.24.5-2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtkmm2.4/+bug/1753120/+subscriptions

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

[Desktop-packages] [Bug 1753120] Re: package libgtkmm-2.4-doc (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README', which is also in package

[thomas]

I am having the same problem, how to solve this?

Unpacking libgtkmm-2.4-dev:amd64 (1:2.24.5-2) over (1:2.24.4-2) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-Aze5mQ/23-libgtkmm-2.4-dev_1%3a2.24.5-2_amd64.deb 
(--unpack):
 trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README', which 
is also in package libgtkmm-2.4-doc 1:2.24.5-2
Errors were encountered while processing:
 /tmp/apt-dpkg-install-Aze5mQ/23-libgtkmm-2.4-dev_1%3a2.24.5-2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

Title:
  package libgtkmm-2.4-doc (not installed) failed to install/upgrade:
  trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README',
  which is also in package libgtkmm-2.4-dev:amd64 1:2.24.5-2

Status in gtkmm2.4 package in Ubuntu:
  Confirmed
Status in gtkmm2.4 package in Debian:
  Fix Released

Bug description:
  E: /var/cache/apt/archives/libgtkmm-2.4-doc_1%3a2.24.5-2_all.deb:
  trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README',
  which is also in package libgtkmm-2.4-dev:amd64 1:2.24.5-2

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgtkmm-2.4-doc (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-10.11-lowlatency 4.15.3
  Uname: Linux 4.15.0-10-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sat Mar  3 10:59:55 2018
  DuplicateSignature:
   package:libgtkmm-2.4-doc:(not installed)
   Unpacking libgtkmm-2.4-doc (1:2.24.5-2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-ebi0hY/58-libgtkmm-2.4-doc_1%3a2.24.5-2_all.deb 
(--unpack):
trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README', 
which is also in package libgtkmm-2.4-dev:amd64 1:2.24.5-2
  ErrorMessage: trying to overwrite 
'/usr/share/doc/libgtkmm-2.4-dev/examples/README', which is also in package 
libgtkmm-2.4-dev:amd64 1:2.24.5-2
  InstallationDate: Installed on 2018-03-02 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180302)
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu2
  SourcePackage: gtkmm2.4
  Title: package libgtkmm-2.4-doc (not installed) failed to install/upgrade: 
trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README', which is 
also in package libgtkmm-2.4-dev:amd64 1:2.24.5-2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtkmm2.4/+bug/1753120/+subscriptions

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

[Desktop-packages] [Bug 1831144] Re: GNOME control center UI does not update dconf setting for magnifier mouse tracking m ode

[Gunnar Hjalmarsson]

Thanks! But you filed it as a gnome-shell issue, while my belief is that
it is a gnome-control-center one. Hence there is a risk that it doesn't
get attention from the right people.

I'm really not sure that the commit I linked to is the culprit. But the
panels/universal-access/zoom-options.{c,ui} files are probably involved
somehow, and that commit contains the most extensive changes of those
files after 3.28 (when it worked).

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

Title:
  GNOME control center UI does not update dconf setting for magnifier
  mouse tracking m ode

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

Bug description:
  If you attempt to change the mouse cursor tracking mode in the gnome
  control centre UI for the gnome magnifier the radio buttons have no
  effect. If yous use dconf-editor to manual change the option at:
  org.gnome.desktop.a11y.magnifier.mouse-tracking the setting will have
  an effect.

  To reproduce
  * Open gnome control centre and select universal access.
  * Click on Zoom.
  * Toggle between "Keep the mouse cursor centred" and the other two options 
(proportional and push).
  * If you enable Zoom and change these settings they have no effect.
  * Open dconf-editor.
  * Navigate to:

  org/gnome/desktop/a11y/magnifier/

  * Select the mouse tracking entry and change the setting to different
  values while the Zoom is enabled. The setting will change the way the
  mouse tracking behaves.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.32.1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 30 20:12:41 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-05-30 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no username)
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs

[Dan Streetman]

** Tags added: sts

** Changed in: cups (Ubuntu Disco)
 Assignee: (unassigned) => Dariusz Gadomski (dgadomski)

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

Title:
  PreserveJobHistory and PreserveJobLog do not respect numeric input as
  outlined in the docs

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  In Progress
Status in cups source package in Bionic:
  In Progress
Status in cups source package in Cosmic:
  In Progress
Status in cups source package in Disco:
  In Progress

Bug description:
  [Impact]

   The documentation allows the following types of arguments for the 
PreserveJobHistory parameter:
  PreserveJobHistory Yes
  PreserveJobHistory No
  PreserveJobHistory seconds
  
  The value in seconds is treated in the same as 'No' resulting in immediate 
removing of jobs from history, while it is supposed to save it for .

  [Test Case]

   * Set PreserveJobHistory to 300.
   * Schedule a job for printing.
   * Check the error_log.

  Expected result:
  Job is save for at least 300 seconds.

  Actual results:
  Job is immediately removed from history.

  [Regression Potential]

   * With the fix the jobs will be saved longer than before, so in tight
  conditions (low disk space) and heavy workload it may affect
  memory/disk space consumption and lead to running out of free space in
  worst case.

  [Other Info]
   
   * Original bug description:

  1) Ubuntu Release
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  2) Version of the package
  cups:
    Installed: 2.1.3-4ubuntu0.3
    Candidate: 2.1.3-4ubuntu0.3
    Version table:
   *** 2.1.3-4ubuntu0.3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages

  3) What I expected to happen:
  from man cupsd.conf

    PreserveJobFiles Yes

     PreserveJobFiles No

     PreserveJobFiles seconds
  Specifies  whether  job files (documents) are preserved after a 
job is printed.  If a numeric value is specified, job files are preserved
  for the indicated number of seconds after printing.  The default 
is "86400" (preserve 1 day).

     PreserveJobHistory Yes

     PreserveJobHistory No

     PreserveJobHistory seconds
  Specifies whether the job history is preserved after a job is 
printed.  If a numeric value is specified, the job history is preserved for
  the  indicated number of seconds after printing.  If "Yes", the 
job history is preserved until the MaxJobs limit is reached.  The default
  is "Yes".

  4) What happens instead

  If I put the following directives in cupsd.conf the job files and
  history are deleted immediately.

  PreserveJobFiles 604800
  PreserveJobHistory 604800

  Debug log showing history being purged:
  d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, 
ac-power=-1, reload=0, curtime=1517951519
  d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, 
JobHistory=604800, JobFiles=604800
  D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history.
  D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading...

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

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

[Desktop-packages] [Bug 1831140] Re: GNOME Magnifier Flickering when using none-full screen modes

[Lee Clark]

OK, turns out my laptop is on 18.10 not 19.04. I assumed the upgrade
would go all the way but I was wrong. :(

I'm upgrading now and will test again.

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

Title:
  GNOME Magnifier Flickering when using none-full screen  modes

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When using the GNOME magnifier (Zoom) feature the magnified display
  flickers when used in any of the following modes: Left, Right, Top or
  Bottom screen part. This occures when the mouse moves towards the edge
  directly opossite to the magnified view.

  To reproduce:
  * Open GNOME Control Centre.
  * Go to Universal Access.
  * Click on Zoom.
  * Enable Zoom
  * Selct either Top, Bottom, Left or Right from the screen part drop down list.
  * Move the mouse cursor to the opossite edge of the screen to that where the 
magnified view is located.

  I have tested on multiple systems running Ubuntu 18.04. I am yet to
  test with 19.04.

  I use this feature to allow me to use two monitors with one showing a
  magnified view the other showing a normal view.

  Happy to provide additional details.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 30 19:14:43 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-03-12 (78 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1831144] Re: GNOME control center UI does not update dconf setting for magnifier mouse tracking m ode

[Lee Clark]

Turns out I already reported this on the GNOME gitlab a while back but
have had no reply. I've updated it with the new information I've
learned. Here is the link: https://gitlab.gnome.org/GNOME/gnome-
shell/issues/865

I've looked at the commit but it's not immediately obvious to me why it
isn't working or if it is even related to this commit. But I'll look it
it more over the weekend.

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

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

Title:
  GNOME control center UI does not update dconf setting for magnifier
  mouse tracking m ode

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

Bug description:
  If you attempt to change the mouse cursor tracking mode in the gnome
  control centre UI for the gnome magnifier the radio buttons have no
  effect. If yous use dconf-editor to manual change the option at:
  org.gnome.desktop.a11y.magnifier.mouse-tracking the setting will have
  an effect.

  To reproduce
  * Open gnome control centre and select universal access.
  * Click on Zoom.
  * Toggle between "Keep the mouse cursor centred" and the other two options 
(proportional and push).
  * If you enable Zoom and change these settings they have no effect.
  * Open dconf-editor.
  * Navigate to:

  org/gnome/desktop/a11y/magnifier/

  * Select the mouse tracking entry and change the setting to different
  values while the Zoom is enabled. The setting will change the way the
  mouse tracking behaves.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.32.1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 30 20:12:41 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-05-30 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no username)
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1831140] Re: GNOME Magnifier Flickering when using none-full screen modes

[Lee Clark]

Here is the lspci output from my laptop.

** Attachment added: "lspci -k output (Dell XPS 3630)"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1831140/+attachment/5268096/+files/dell-xps-lspci.txt

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

Title:
  GNOME Magnifier Flickering when using none-full screen  modes

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When using the GNOME magnifier (Zoom) feature the magnified display
  flickers when used in any of the following modes: Left, Right, Top or
  Bottom screen part. This occures when the mouse moves towards the edge
  directly opossite to the magnified view.

  To reproduce:
  * Open GNOME Control Centre.
  * Go to Universal Access.
  * Click on Zoom.
  * Enable Zoom
  * Selct either Top, Bottom, Left or Right from the screen part drop down list.
  * Move the mouse cursor to the opossite edge of the screen to that where the 
magnified view is located.

  I have tested on multiple systems running Ubuntu 18.04. I am yet to
  test with 19.04.

  I use this feature to allow me to use two monitors with one showing a
  magnified view the other showing a normal view.

  Happy to provide additional details.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 30 19:14:43 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-03-12 (78 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1831140] Re: GNOME Magnifier Flickering when using none-full screen modes

[Lee Clark]

I've attached the requested output.

I have done additional testing today on my Dell XPS laptop running
Ubuntu 19.04, my personal desktop running 18.04 and my work PC running
18.04.

* I removed all extensions, uninstalled packages for those that had them or 
deleted via the gnome extension website.
* Rebooted
* Re-enabled magnifier and switched between 'Full Screen' and 'Left' Screen 
parts.

I see the issue on all three machines though on 19.04 the effect is
slightly different.

Opening the activities overlay causes the issue to fanish until it is
closed again.

** Attachment added: "lspci -k output"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1831140/+attachment/5268095/+files/pc-lspci.txt

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

Title:
  GNOME Magnifier Flickering when using none-full screen  modes

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When using the GNOME magnifier (Zoom) feature the magnified display
  flickers when used in any of the following modes: Left, Right, Top or
  Bottom screen part. This occures when the mouse moves towards the edge
  directly opossite to the magnified view.

  To reproduce:
  * Open GNOME Control Centre.
  * Go to Universal Access.
  * Click on Zoom.
  * Enable Zoom
  * Selct either Top, Bottom, Left or Right from the screen part drop down list.
  * Move the mouse cursor to the opossite edge of the screen to that where the 
magnified view is located.

  I have tested on multiple systems running Ubuntu 18.04. I am yet to
  test with 19.04.

  I use this feature to allow me to use two monitors with one showing a
  magnified view the other showing a normal view.

  Happy to provide additional details.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 30 19:14:43 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-03-12 (78 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1831264] [NEW] Sun keyboard Front key not accepted by gnome-control-center

[Charles Lindsey]

Public bug reported:

A Sun keyboards is recognized by the hardware detector with no problem.
xmodmap -pk gives the following for the relevant keys:

136 0xff69 (Cancel) 0x (NoSymbol)   0xff69 (Cancel) 
137 0xff66 (Redo)   0x (NoSymbol)   0xff66 (Redo)   
138 0x1005ff70 (SunProps)   0x (NoSymbol)   0x1005ff70 
(SunProps)   
139 0xff65 (Undo)   0x (NoSymbol)   0xff65 (Undo)   
140 0x1005ff71 (SunFront)   0x (NoSymbol)   0x1005ff71 
(SunFront)   
141 0x1008ff57 (XF86Copy)   0x (NoSymbol)   0x1008ff57 
(XF86Copy)   
142 0x1008ff6b (XF86Open)   0x (NoSymbol)   0x1008ff6b 
(XF86Open)   
143 0x1008ff6d (XF86Paste)  0x (NoSymbol)   0x1008ff6d 
(XF86Paste)  
144 0xff68 (Find)   0x (NoSymbol)   0xff68 (Find)   
145 0x1008ff58 (XF86Cut)0x (NoSymbol)   0x1008ff58 
(XF86Cut)
146 0xff6a (Help)   0x (NoSymbol)   0xff6a (Help)   

Observe that the names of the two keysyms 0x1005ff70 and 0x1005ff71 are
SUN specials, not in the XF86 set. Pressing either of these using xev
behaves as expected:

KeyPress event, serial 37, synthetic NO, window 0x361,
root 0x4fe, subw 0x0, time 3071686, (118,83), root:(1365,168),
state 0x0, keycode 140 (keysym 0x1005ff71, SunFront), same_screen YES,
XLookupString gives 0 bytes: 
XmbLookupString gives 0 bytes: 
XFilterEvent returns: False

KeyRelease event, serial 37, synthetic NO, window 0x361,
root 0x4fe, subw 0x0, time 3071688, (118,83), root:(1365,168),
state 0x0, keycode 140 (keysym 0x1005ff71, SunFront), same_screen YES,
XLookupString gives 0 bytes: 
XFilterEvent returns: False

I tried binding "Lower window below other windows" to the SunFront using
the Settings app, but it did not work.(Note that back in the days of
14.04 where you uses CCSM to make this setting, it worked fine.)

After this I did
$ dconf dump /org/gnome/desktop/wm/keybindings/
[/]
lower=['0x1005ff71']
switch-to-workspace-1=['1']
move-to-workspace-1=@as []
switch-to-workspace-2=['2']
switch-to-workspace-3=['3']
switch-to-workspace-4=['4']
move-to-monitor-down=@as []
move-to-monitor-up=@as []

So it had recognized the correct keysym, but does not know that the name
of that keysym is SunFront.

So far so bad. It works fine with keysyms with known names (e.g. the
CANCEL key), and it should not be hard to construct a workaround my
modifying the keyboard tables to map that key to some better-named
keysym, so it might be argued that this bug is of Low Priority.

BUT

there is a serious side effect. With that dconf setting in place: the
Left Arrow key on the keyboard no longer works (for example, I made that
change whilst composing this report, and I cannot now move the cursor
backwards with the Left Arrow key, though fortunately the Left Arrow on
the numeric keypad still behaves). All applications seem to be affected
(e.g. Firefox, Terminal, Gedit). Left and Left still work,
except that if you engage Num Lock, Left now stops working.

Using xev to see what happens when Left Arrow is pressed yields:

FocusOut event, serial 37, synthetic NO, window 0x361,
mode NotifyGrab, detail NotifyAncestor

FocusOut event, serial 37, synthetic NO, window 0x361,
mode NotifyUngrab, detail NotifyPointer

FocusIn event, serial 37, synthetic NO, window 0x361,
mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 37, synthetic NO, window 0x0,
keys:  2   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

which is crazy! You should not be surprised that I spent a whole day
gradually removing all the changes I had made until finally I narrowed
it down to dconf, and then to that particular setting. Changing the
binding back to CANCEL removes the problem (except that you have to
restart each application affected, so I have just restarted Terminal,
but I cannot restart Firefox while I am still typing this report).

My main worry is that there may be some other keybinding errors that cause the 
same side effect, and therefor the Priority of fixing this bug needs to be much 
higher. Moreover, this problem seems to have been around for a long time. see:

https://unix.stackexchange.com/questions/231307/key-for-the-letter-o-stopped-working-works-only-with-shift-linux
which produces exactly the same xev output with a completely different binding 
problem.

To reproduce the Bug, ideally just find a Sun Keyboard and plug it into
a spare USB port, and then follow what I have described.

If you cannot lay your hands on a Sun Keyboard, then it is likely that

$ dconf load /org/gnome/desktop/wm/keybindings/
lower=['0x1005ff71']

will produce the same effect.

In case the bug reporting system has not supplied my full details, here
is

$ uname -a
Linux clerew 

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

[Bug Watch Updater]

** Bug watch added: Mozilla Bugzilla #1552613
   https://bugzilla.mozilla.org/show_bug.cgi?id=1552613

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

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

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

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

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

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

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

  Systems tried on:

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

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

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

[Desktop-packages] [Bug 1831261] [NEW] OpenVPN Other DNS Servers ignored if no Search Domains specified

[Mark Rose]

Public bug reported:

On Kubuntu 18.04.2 LTS, with network-manager 1.10.14-0ubuntu2, DNS
servers in "Other DNS Servers" are ignored unless a Search Domain is
also specified. This difference can be seen in the output of `systemd-
resolve --status`.

For my use case, I need to specify an additional DNS server but I have
no need to specify a search domain. Specifying a bogus domain fixes the
problem, and the DNS server appears in `systemd-resolve --status`.

I suspect this may be related to the fix for #1754671, which was
released in 1.10.14-0ubuntu1.

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

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

Title:
  OpenVPN Other DNS Servers ignored if no Search Domains specified

Status in network-manager package in Ubuntu:
  New

Bug description:
  On Kubuntu 18.04.2 LTS, with network-manager 1.10.14-0ubuntu2, DNS
  servers in "Other DNS Servers" are ignored unless a Search Domain is
  also specified. This difference can be seen in the output of `systemd-
  resolve --status`.

  For my use case, I need to specify an additional DNS server but I have
  no need to specify a search domain. Specifying a bogus domain fixes
  the problem, and the DNS server appears in `systemd-resolve --status`.

  I suspect this may be related to the fix for #1754671, which was
  released in 1.10.14-0ubuntu1.

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

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

[Desktop-packages] [Bug 1802039]

[Bug-husbandry-bot]

https://bugzilla.mozilla.org/show_bug.cgi?id=1552613

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

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

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

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

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

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

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

  Systems tried on:

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

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

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

[Desktop-packages] [Bug 1798074] Re: LIbreoffice crashes on startup

[Marcus Tomlinson]

** Description changed:

  [Impact]
  
-  * This effects all bionic and cosmic users who have 'libcpd*' 'cpdb*'
+  * This effects all bionic and cosmic users who have 'libcpd*' 'cpdb*'
  packages installed.
  
-  * The fix is currently in LibreOffice 6.2.0+ on disco and eoan.
+  * The fix is currently in LibreOffice 6.2.0+ on disco and eoan.
  
  [Test Case]
  
-  1. apt install cpdb-backend-gcp
-  2. run LibreOffice
+  1. apt install cpdb-backend-gcp
+  2. run LibreOffice
  
  [Regression Potential]
  
-  * We're backporting a patch that has already been applied to 6.2.0+
+  * We're backporting a patch that has already been applied to 6.2.0+
  with no regression, so potential for regression here is low.
  
-  * A combination of autopkgtests and manual testing as described above
- should provide reasonable confidence that no regressions sneaked in.
+  * A combination of autopkgtests and manual testing should provide
+ reasonable confidence that no regressions sneaked in.
  
  [Original Description]
  
  On starting up LibreOffice, it crashes. Starting from a terminal with
  just "libreoffice", I see the "general open a document" libreoffice
  window and a popup dialog titled "LibreOffice 6.0 Document Recovery",
  with text "Due to an unexpected error, LibreOffice crashed. All the
  files you were working on will now be saved. The next time LibreOffice
  is launched, your files will be recovered automatically. The following
  files will be recovered:" (and no files to be recovered are listed).
  Clicking "OK" on this dialog hides it and the general window, and then
  shows them both again; clicking OK on that dialog exits. LibreOffice
  does not start.
  
  Running "libreoffice --norestore" gives a stack trace:
  
  $ libreoffice --norestore
  Application Error
  
  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7fa00e2c8568]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c3c6)[0x7fa00e2f13c6]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fa00df02e97]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7fa00df04801]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2d5b562)[0x7fa01126a562]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0xa2)[0x7fa0111f61c2]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x1d0d580)[0x7fa01021c580]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cecb6d)[0x7fa0111fbb6d]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x163b2)[0x7fa00e2cb3b2]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c28f)[0x7fa00e2f128f]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20]
  /lib/x86_64-linux-gnu/libc.so.6(+0x18e5a1)[0x7fa00e0525a1]
  
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7fa00c0e7aa4]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2d6972b)[0x7fa01127872b]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9156)[0x7fa00c0dd156]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9398)[0x7fa00c0dd398]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8db66)[0x7fa00c0a1b66]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc0fc2)[0x7fa00c0d4fc2]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d179)[0x7fa00c0a1179]
  
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x155)[0x7fa00baf60f5]
  /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c4c0)[0x7fa00baf64c0]
  
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7fa00baf654c]
  /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x414d4)[0x7f9ff8b524d4]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x2e)[0x7fa0111f68ce]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7fa0111f8075]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x1d12fa3)[0x7fa010221fa3]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cee756)[0x7fa0111fd756]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7fa0111fd860]
  
/usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7fa0102430c5]
  /usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x55dd01f4578b]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7fa00dee5b97]
  /usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x55dd01f457ca]
  
  I have tried entirely removing my profile, ~/.config/libreoffice , but
  the same problem still exhibits.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-common 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Oct 16 12:58:04 2018
  InstallationDate: Installed on 2014-04-07 (1653 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy 

[Desktop-packages] [Bug 1798074] Re: LIbreoffice crashes on startup

[Marcus Tomlinson]

** Description changed:

+ [Impact]
+ 
+  * This effects all bionic and cosmic users who have 'libcpd*' 'cpdb*'
+ packages installed.
+ 
+  * The fix is currently in LibreOffice 6.2.0+ on disco and eoan.
+ 
+ [Test Case]
+ 
+  1. apt install cpdb-backend-gcp
+  2. run LibreOffice
+ 
+ [Regression Potential]
+ 
+  * We're backporting a patch that has already been applied to 6.2.0+
+ with no regression, so potential for regression here is low.
+ 
+  * A combination of autopkgtests and manual testing as described above
+ should provide reasonable confidence that no regressions sneaked in.
+ 
+ [Original Description]
+ 
  On starting up LibreOffice, it crashes. Starting from a terminal with
  just "libreoffice", I see the "general open a document" libreoffice
  window and a popup dialog titled "LibreOffice 6.0 Document Recovery",
  with text "Due to an unexpected error, LibreOffice crashed. All the
  files you were working on will now be saved. The next time LibreOffice
  is launched, your files will be recovered automatically. The following
  files will be recovered:" (and no files to be recovered are listed).
  Clicking "OK" on this dialog hides it and the general window, and then
  shows them both again; clicking OK on that dialog exits. LibreOffice
  does not start.
  
  Running "libreoffice --norestore" gives a stack trace:
  
- 
  $ libreoffice --norestore
  Application Error
- 
  
  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7fa00e2c8568]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c3c6)[0x7fa00e2f13c6]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fa00df02e97]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7fa00df04801]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2d5b562)[0x7fa01126a562]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0xa2)[0x7fa0111f61c2]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x1d0d580)[0x7fa01021c580]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cecb6d)[0x7fa0111fbb6d]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x163b2)[0x7fa00e2cb3b2]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c28f)[0x7fa00e2f128f]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20]
  /lib/x86_64-linux-gnu/libc.so.6(+0x18e5a1)[0x7fa00e0525a1]
  
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7fa00c0e7aa4]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2d6972b)[0x7fa01127872b]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9156)[0x7fa00c0dd156]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9398)[0x7fa00c0dd398]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8db66)[0x7fa00c0a1b66]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc0fc2)[0x7fa00c0d4fc2]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d179)[0x7fa00c0a1179]
  
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x155)[0x7fa00baf60f5]
  /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c4c0)[0x7fa00baf64c0]
  
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7fa00baf654c]
  /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x414d4)[0x7f9ff8b524d4]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x2e)[0x7fa0111f68ce]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7fa0111f8075]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x1d12fa3)[0x7fa010221fa3]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cee756)[0x7fa0111fd756]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7fa0111fd860]
  
/usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7fa0102430c5]
  /usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x55dd01f4578b]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7fa00dee5b97]
  /usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x55dd01f457ca]
  
  I have tried entirely removing my profile, ~/.config/libreoffice , but
  the same problem still exhibits.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-common 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Oct 16 12:58:04 2018
  InstallationDate: Installed on 2014-04-07 (1653 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-04-28 (171 days ago)

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

Title:
  LIbreoffice crashes on startup

Status in 

[Desktop-packages] [Bug 1831021] Re: Extremely high memory consumption under heavy workload

[Dariusz Gadomski]

Thank you for the explanation Till.

I believe the lack of previous complaints is because this happens in a
pretty unique conditions (very high MaxJobs and large batches of jobs).
The test case however was based on a real-life scenario reported to me.

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

Title:
  Extremely high memory consumption under heavy workload

Status in cups package in Ubuntu:
  Triaged

Bug description:
  Under heavy workload conditions cups can reach irrationally high
  memory consumption very quickly (tens of GBs).

  Test case:
  1. Set MaxJobs to 4 in cupsd.conf.
  2. sudo apt install cups-pdf
  3. Fill the queue with jobs:
  while [ 1 ]; lp -d PDF /usr/share/cups/data/default.pdf; done
  4. Cancel all jobs
  cancel -a PDF
  5. Restart cups.
  6. Start filling the queue again (as in step 3).

  Expected result:
  Jobs are processed and memory consumption is proportional to the number of 
jobs.

  Actual result:
  After step 5 or at latest step 6 memory consumption starts to increase 
exponentially - from ~150-200 MB to 8+GB. Without foreseeing this it's very 
easy to get cupsd killed by OOM killer.

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

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

[Desktop-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

[Timo Aaltonen]

Hello Dimitri, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.22 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: systemd (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in udisks2 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Committed
Status in udisks2 source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Fix Committed
Status in udisks2 source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  New
Status in systemd source package in Disco:
  Fix Committed
Status in udisks2 source package in Disco:
  Invalid
Status in linux source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Fix Committed
Status in udisks2 source package in Eoan:
  Invalid
Status in systemd package in Debian:
  Unknown

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

  --
  sru template for systemd upload:

  [impact]
  buffer overflow can cause memory corruption; this is seen in failed 
autopkgtests

  [test case]
  see comment 6

  [regression potential]
  the patch is minimal and clearly correct; however the regression potential is 
around invalid/corrupted keys read from the keyring.

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

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

[Desktop-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

[Timo Aaltonen]

systemd accepted to bionic/cosmic-proposed, please test

** Tags removed: verification-failed verification-failed-bionic
** Tags added: verification-needed verification-needed-bionic 
verification-needed-cosmic

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

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

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  New
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed
Status in network-manager source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

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

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

[Desktop-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

[Timo Aaltonen]

Hello Dimitri, or anyone else affected,

Accepted systemd into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/240-6ubuntu5.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-disco to verification-done-disco. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-disco. 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: systemd (Ubuntu Disco)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-disco

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

** Tags added: verification-needed-cosmic

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

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in udisks2 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  In Progress
Status in udisks2 source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Fix Committed
Status in udisks2 source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  New
Status in systemd source package in Disco:
  Fix Committed
Status in udisks2 source package in Disco:
  Invalid
Status in linux source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Fix Committed
Status in udisks2 source package in Eoan:
  Invalid
Status in systemd package in Debian:
  Unknown

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

  --
  sru template for systemd upload:

  [impact]
  buffer overflow can cause memory corruption; this is seen in failed 
autopkgtests

  [test case]
  see comment 6

  [regression potential]
  the patch is minimal and clearly correct; however the regression potential is 
around invalid/corrupted keys read from the keyring.

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

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

[Desktop-packages] [Bug 1814373] Please test proposed package

[Timo Aaltonen]

Hello Dimitri, or anyone else affected,

Accepted systemd into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu10.14 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-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. 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.

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

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in udisks2 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  In Progress
Status in udisks2 source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Fix Committed
Status in udisks2 source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  New
Status in systemd source package in Disco:
  Fix Committed
Status in udisks2 source package in Disco:
  Invalid
Status in linux source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Fix Committed
Status in udisks2 source package in Eoan:
  Invalid
Status in systemd package in Debian:
  Unknown

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

  --
  sru template for systemd upload:

  [impact]
  buffer overflow can cause memory corruption; this is seen in failed 
autopkgtests

  [test case]
  see comment 6

  [regression potential]
  the patch is minimal and clearly correct; however the regression potential is 
around invalid/corrupted keys read from the keyring.

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

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

[Desktop-packages] [Bug 1768756] Re: Libreoffice 6 does not start on Kubuntu 18.04 (clean install)

[Marcus Tomlinson]

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

** This bug has been marked a duplicate of bug 1798074
   LIbreoffice crashes on startup

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

Title:
  Libreoffice 6 does not start on Kubuntu 18.04 (clean install)

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I just did a clean install of Kubuntu 18.04 (the minimal one) and
  manually installed Libreoffice [1]. Now, when I try to start it, I get
  this:

  $ libreoffice 
  terminate called after throwing an instance of 
'com::sun::star::uno::RuntimeException'

  
  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7f8545b22568]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c316)[0x7f8545b4b316]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7f854575cf20]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f854575ce97]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f854575e801]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x8c8fb)[0x7f853d5228fb]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x92d3a)[0x7f853d528d3a]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x92d95)[0x7f853d528d95]
  /usr/lib/x86_64-linux-gnu/libstdc++.so.6(__cxa_rethrow+0x4d)[0x7f853d52903d]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x10ab728)[0x7f8546e14728]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN10comphelper6detail20ConfigurationWrapper3getERKN3com3sun4star3uno9ReferenceINS5_17XComponentContextEEE+0x47)[0x7f8546e147f7]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN12OpenGLHelper18isVCLOpenGLEnabledEv+0x2e5)[0x7f8548b408c5]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN10SalDisplay10BestVisualEP9_XDisplayiR11XVisualInfo+0xfd)[0x7f852dbdbc2d]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZNK10SalDisplay10initScreenE12SalX11Screen+0x8b)[0x7f852dbe113b]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN7vcl_sal9WMAdaptorC1EP10SalDisplay+0x21d)[0x7f852dbe6e4d]
  /usr/lib/libreoffice/program/libvclplug_genlo.so(+0x4024b)[0x7f852dbe724b]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN7vcl_sal9WMAdaptor15createWMAdaptorEP10SalDisplay+0x21)[0x7f852dbe8171]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN10SalDisplay4InitEv+0x467)[0x7f852dbe2997]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN13SalX11DisplayC1EP9_XDisplay+0x24)[0x7f852dbe2b44]
  /usr/lib/libreoffice/program/libvclplug_kde4lo.so(+0x1963e)[0x7f85302d263e]
  /usr/lib/libreoffice/program/libvclplug_kde4lo.so(+0x1e636)[0x7f85302d7636]
  
/usr/lib/libreoffice/program/libvclplug_genlo.so(_ZN14X11SalInstance12AfterAppInitEv+0x12)[0x7f852dbe3282]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z7InitVCLv+0x382)[0x7f8548a53742]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cebd3d)[0x7f8548a54d3d]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7f8548a54da0]
  
/usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7f8547a9a215]
  /usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x560c5d84978b]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f854573fb97]
  /usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x560c5d8497ca]

  No matter what I try (e.g. [2]), the result is always the same.

  I also tried to remove my config dir [3] but no luck.

  Any idea what could be wrong? Thanks.

  Description:Ubuntu 18.04 LTS
  Release:18.04

  libreoffice version: 6.0.3-0ubuntu1

  [1] apt install libreoffice
  [2] libreoffice --help
  [3] ~/.config/libreoffice/

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

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

[Desktop-packages] [Bug 1830049] Re: nvidia-graphics-drivers-340 340.107-0ubuntu3 ADT test failure with linux 5.2.0-0.1

[Seth Forshee]

** Attachment added: "make.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1830049/+attachment/5268060/+files/make.log

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

Title:
  nvidia-graphics-drivers-340 340.107-0ubuntu3 ADT test failure with
  linux 5.2.0-0.1

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/amd64/n/nvidia-graphics-drivers-340/20190522_043007_06930@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/i386/n/nvidia-graphics-drivers-340/20190522_121357_06930@/log.gz

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

-- 
Mailing list: https://launchpad.net/~desktop-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

[Till Kamppeter]

I have raised the default LogDebugHistory some years ago as most
printing problems happen during the execution of a job and this way one
gets a logging with debug verbosity only for jobs and standard verbosity
for all the rest. This way one often did not need to ask the bug-
reporting users to reproduce their problems after having set logging to
debug mode but instead, one could simply start to work with the
error_log auto-captured by Apport.

Up to now no one complained that it somehow overloaded system resources.

Please add a line "LogDebugHistory 200" to your /etc/cups/cupsd.conf and
restart CUPS.

I will remove this change from the next release of the CUPS package.

OdyX, could you remove the LogDebugHistory=9 default change from the
CUPS package for Debian (remove log-debug-history-nearly-
unlimited.patch)? Thanks.

** Changed in: cups (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Extremely high memory consumption under heavy workload

Status in cups package in Ubuntu:
  Triaged

Bug description:
  Under heavy workload conditions cups can reach irrationally high
  memory consumption very quickly (tens of GBs).

  Test case:
  1. Set MaxJobs to 4 in cupsd.conf.
  2. sudo apt install cups-pdf
  3. Fill the queue with jobs:
  while [ 1 ]; lp -d PDF /usr/share/cups/data/default.pdf; done
  4. Cancel all jobs
  cancel -a PDF
  5. Restart cups.
  6. Start filling the queue again (as in step 3).

  Expected result:
  Jobs are processed and memory consumption is proportional to the number of 
jobs.

  Actual result:
  After step 5 or at latest step 6 memory consumption starts to increase 
exponentially - from ~150-200 MB to 8+GB. Without foreseeing this it's very 
easy to get cupsd killed by OOM killer.

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

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

[Desktop-packages] [Bug 1814125]

[Daniel van Vugt]

And an extra, final nail in the coffin for this bug:

https://gitlab.gnome.org/GNOME/mutter/merge_requests/602

Although you only need !363 to solve this bug. !602 clarifies things
further by showing after !363 it is now safe to revert commit
383ba566bd7c2a76d0856015a66e47caedef06b6 and more.

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

Title:
  [nvidia] gnome-shell eats 100% cpu when seconds display is on and
  screen is locked

Status in Mutter:
  Confirmed
Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  on my laptop (xiaomi notebook pro), ubuntu 18.10 amd64, standart ubuntu 
desktop (gnome-shell), no application running
  just activate second display in gnome tweak, let it lock itself
  the fan is going fast, simply moving the mouse and the fan slow down.
  wrote a simple script to append a top every minut in a log file, show that 
gnome-shell consumes 100% when locked.
  workaround : disabling second displaying and no more CPU usage / fan noise 
when locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  415.27  Thu Dec 20 17:25:03 
CST 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 31 16:19:16 2019
  DistUpgraded: 2018-12-30 21:42:17,971 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 415.27, 4.18.0-13-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Xiaomi UHD Graphics 620 [1d72:1701]
 Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701]
  InstallationDate: Installed on 2018-06-08 (236 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Timi TM1701
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=174e8747-a737-411b-bfaf-4e6795426fea ro quiet splash nouveau.runpm=0 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-12-30 (31 days ago)
  dmi.bios.date: 10/13/2017
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: XMAKB5R0P0502
  dmi.board.asset.tag: Any
  dmi.board.name: TM1701
  dmi.board.vendor: Timi
  dmi.board.version: MP
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrXMAKB5R0P0502:bd10/13/2017:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:
  dmi.product.family: Timibook
  dmi.product.name: TM1701
  dmi.sys.vendor: Timi
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1798074] Re: LIbreoffice crashes on startup

[Marcus Tomlinson]

** Also affects: libreoffice (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Changed in: libreoffice (Ubuntu Cosmic)
 Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson)

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

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

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

Title:
  LIbreoffice crashes on startup

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Bionic:
  Triaged
Status in libreoffice source package in Cosmic:
  Triaged

Bug description:
  On starting up LibreOffice, it crashes. Starting from a terminal with
  just "libreoffice", I see the "general open a document" libreoffice
  window and a popup dialog titled "LibreOffice 6.0 Document Recovery",
  with text "Due to an unexpected error, LibreOffice crashed. All the
  files you were working on will now be saved. The next time LibreOffice
  is launched, your files will be recovered automatically. The following
  files will be recovered:" (and no files to be recovered are listed).
  Clicking "OK" on this dialog hides it and the general window, and then
  shows them both again; clicking OK on that dialog exits. LibreOffice
  does not start.

  Running "libreoffice --norestore" gives a stack trace:


  $ libreoffice --norestore
  Application Error

  
  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7fa00e2c8568]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c3c6)[0x7fa00e2f13c6]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fa00df02e97]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7fa00df04801]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2d5b562)[0x7fa01126a562]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0xa2)[0x7fa0111f61c2]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x1d0d580)[0x7fa01021c580]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cecb6d)[0x7fa0111fbb6d]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x163b2)[0x7fa00e2cb3b2]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c28f)[0x7fa00e2f128f]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20]
  /lib/x86_64-linux-gnu/libc.so.6(+0x18e5a1)[0x7fa00e0525a1]
  
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7fa00c0e7aa4]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2d6972b)[0x7fa01127872b]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9156)[0x7fa00c0dd156]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9398)[0x7fa00c0dd398]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8db66)[0x7fa00c0a1b66]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc0fc2)[0x7fa00c0d4fc2]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d179)[0x7fa00c0a1179]
  
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x155)[0x7fa00baf60f5]
  /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c4c0)[0x7fa00baf64c0]
  
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7fa00baf654c]
  /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x414d4)[0x7f9ff8b524d4]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x2e)[0x7fa0111f68ce]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7fa0111f8075]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x1d12fa3)[0x7fa010221fa3]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cee756)[0x7fa0111fd756]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7fa0111fd860]
  
/usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7fa0102430c5]
  /usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x55dd01f4578b]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7fa00dee5b97]
  /usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x55dd01f457ca]

  I have tried entirely removing my profile, ~/.config/libreoffice , but
  the same problem still exhibits.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-common 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Oct 16 12:58:04 2018
  InstallationDate: Installed on 2014-04-07 (1653 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-04-28 (171 days ago)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]

[ekimai]

Thanks for your efforts :)

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

Title:
  [bionic][regression] gnome-shell crashes with SIGSEGV in
  meta_window_actor_is_destroyed(self=NULL) called from
  _switchWorkspaceDone() [windowManager.js:1787]

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  Invalid
Status in gnome-shell source package in Eoan:
  Invalid

Bug description:
  https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/927

  [ Impact ]

  Switching workspace with the Android Emulator running will blink the
  screen as if gnome restarted, if I switch workspace one more time, it
  will completely crash and I will need to log in again.

  [ Test case ]

  Open Android Emulator and switch workspace
  or
  Open Skype, start a test call and switch workspace

  GNOME-Shell should not crash

  [ Regression potential ]

  Very low, we remove windows from Javascript array when they're destroyed.
  A possible regression could be not switching to workspace when selecting a 
window that is in another one.

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  Uname: Linux 4.20.3-acso x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 19 20:05:34 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-01-15 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1830936] Re: Wayland freeze 18.04 using VLC

[Dilip]

Thanks for the reply. Earlier, taking suggestions from the community I
used the default video player and mpv video player which I downloaded
from the store app in 18.04. Both work fine with the same files without
any freeze. I think it crashes only with the VLC.

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

Title:
  Wayland freeze 18.04 using VLC

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I tried Wayland while logging in and it works fine until I try to play
  some local video file using VLC. Ubuntu freezes completely and I have
  to power off by pressing the power button. It works fine in the
  default Xorg Ubuntu session. I have the latest version of VLC that
  comes with the update which 3.0.6 and Ubuntu 18.04 fully updated.

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

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

[Desktop-packages] [Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]

[ekimai]

It would appear that something has changed in the Android emulator, and
it's less likely to be the cause of the crash.

I'd expected to simply run gnome with animations turned on, run the
emulator, get a crash when switching desktops.  While this now seems
more stable, it does occasionally crash.

I can confirm that using the above update resolves the problem.  I've
been using it for a couple of days without any issues.

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

Title:
  [bionic][regression] gnome-shell crashes with SIGSEGV in
  meta_window_actor_is_destroyed(self=NULL) called from
  _switchWorkspaceDone() [windowManager.js:1787]

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  Invalid
Status in gnome-shell source package in Eoan:
  Invalid

Bug description:
  https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/927

  [ Impact ]

  Switching workspace with the Android Emulator running will blink the
  screen as if gnome restarted, if I switch workspace one more time, it
  will completely crash and I will need to log in again.

  [ Test case ]

  Open Android Emulator and switch workspace
  or
  Open Skype, start a test call and switch workspace

  GNOME-Shell should not crash

  [ Regression potential ]

  Very low, we remove windows from Javascript array when they're destroyed.
  A possible regression could be not switching to workspace when selecting a 
window that is in another one.

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  Uname: Linux 4.20.3-acso x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 19 20:05:34 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-01-15 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1830936] Re: Wayland freeze 18.04 using VLC

[Daniel van Vugt]

Thanks.

Unfortunately those crash files don't appear to be related to this bug.
That's not completely surprising if the "freeze" isn't caused by a
crash.

Next, please get a second computer and ssh into the freezing one (you
may need to install 'openssh-server' on the freezing one first). Then
reproduce the freeze and while it is frozen, from ssh run:

  killall -ABRT gnome-shell

Wait a minute or two and that should produce a new crash file. Then
follow the instructions in comment #2 again.

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

Title:
  Wayland freeze 18.04 using VLC

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I tried Wayland while logging in and it works fine until I try to play
  some local video file using VLC. Ubuntu freezes completely and I have
  to power off by pressing the power button. It works fine in the
  default Xorg Ubuntu session. I have the latest version of VLC that
  comes with the update which 3.0.6 and Ubuntu 18.04 fully updated.

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

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

[Desktop-packages] [Bug 1831218] [NEW] xorg

[Vladimir Skakalin]

Public bug reported:

ubuntu 16.04
GF106GL
$ sudo ubuntu-drivers autoinstall
nvidia-384
$ sudo ubuntu-bug xorg
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.130  Wed Mar 21 03:37:26 
PDT 2018
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri May 31 12:33:50 2019
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.15.0-50-generic, x86_64: installed
 nvidia-384, 384.130, 4.15.0-50-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation GF106GL [Quadro 2000] [10de:0dd8] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: NVIDIA Corporation GF106GL [Quadro 2000] [10de:084a]
InstallationDate: Installed on 2019-05-24 (6 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: System manufacturer System Product Name
ProcEnviron:
 LANGUAGE=ru
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=010c1118-5303-4b15-9fc0-a5cb2c806fb5 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/11/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1205
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z270-P
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1205:bd05/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ270-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Fri May 31 11:53:07 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu 16.04
  GF106GL
  $ sudo ubuntu-drivers autoinstall
  nvidia-384
  $ sudo ubuntu-bug xorg
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.130 

[Desktop-packages] [Bug 1827948] Re: Use libreoffice-style-breeze as the default icon theme

[Marcus Tomlinson]

I'm a +1 for Colibre too

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

Title:
  Use libreoffice-style-breeze as the default icon theme

Status in libreoffice package in Ubuntu:
  New

Bug description:
  The Yaru icon theme uses 1 pixel strokes for its symbolic icon set. 
  So do the breeze icons for libreoffice.

  All in all does the breeze icon set for libre office fit very good to
  the look of the Yaru icons.

  https://i.imgur.com/tgioycv.png

  https://i.imgur.com/WwKvjMh.png

  Thus I would suggest to use it as the default icon set in Ubuntu to
  guarantee a consistent look and feel across the desktop

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

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

[Desktop-packages] [Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]

[Pedro]

Thank you, Ahmed Mamdouh.
After your suggestion, I update gnome-shell.
Finally, it won't be crash.
I was waitting for a long time, and can not use "workspace".
Now I can use multi workspaces again.

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

Title:
  [bionic][regression] gnome-shell crashes with SIGSEGV in
  meta_window_actor_is_destroyed(self=NULL) called from
  _switchWorkspaceDone() [windowManager.js:1787]

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  Invalid
Status in gnome-shell source package in Eoan:
  Invalid

Bug description:
  https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/927

  [ Impact ]

  Switching workspace with the Android Emulator running will blink the
  screen as if gnome restarted, if I switch workspace one more time, it
  will completely crash and I will need to log in again.

  [ Test case ]

  Open Android Emulator and switch workspace
  or
  Open Skype, start a test call and switch workspace

  GNOME-Shell should not crash

  [ Regression potential ]

  Very low, we remove windows from Javascript array when they're destroyed.
  A possible regression could be not switching to workspace when selecting a 
window that is in another one.

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  Uname: Linux 4.20.3-acso x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 19 20:05:34 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-01-15 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1830532] Re: Writer does not export hyperlinks in second Table of Contents / Figures when exporting to PDF

[Marcus Tomlinson]

** Changed in: libreoffice (Ubuntu Disco)
   Status: Triaged => Fix Committed

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

Title:
  Writer does not export hyperlinks in second Table of Contents /
  Figures when exporting to PDF

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Disco:
  Fix Committed

Bug description:
  When exporting a document that contains both a Table of Contents and a
  Table of Figures to PDF Writer does not correctly hyperlink whichever
  table comes second.

  Version: 6.2.3.2 (not present in 6.0.7.3 shipped with 18.04)

  Severity: Normal.

  Reproducible: Always

  Steps to reproduce:
  1. Open Writer, create document with a number of headings and images (see 
attached)
  2. Insert both a Tale of Contents and Table of Figures
  3. Export document to PDF, either using File | Export As | Export as PDF or 
using Export as PDF toolbar button
  3. Open PDF in document viewer (Evince, Okular, Acrobat)
  4. Test hyperlinks in ToC and ToF

  Actual result:
  Hyperlinks work in ToC, but not ToF.

  Expected result:
  Hyperlink work in both ToC and ToF

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 26 20:47:43 2019
  InstallationDate: Installed on 2019-05-11 (15 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  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/1830532/+subscriptions

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

[Desktop-packages] [Bug 1830691] Re: [SRU] libreoffice 6.2.4 for disco

[Marcus Tomlinson]

Upgraded libreoffice from 1:6.2.3-0ubuntu0.19.04.1 to
1:6.2.4-0ubuntu0.19.04.1 from disco-proposed in a clean and up-to-date
disco amd64 VM, and successfully ran test plan at
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice.

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

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

Title:
  [SRU] libreoffice 6.2.4 for disco

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Disco:
  Fix Committed
Status in libreoffice-l10n source package in Disco:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 6.2.4 is in its fourth bugfix release of the 6.2 line. Version 
6.2.4 is currently in Eoan.
     For a list of fixed bugs compared to 6.2.3 see the list of bugs fixed in 
the two release candidates:
   https://wiki.documentfoundation.org/Releases/6.2.4/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.2.4/RC2#List_of_fixed_bugs
     (that's a total of 115 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 115 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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

[Desktop-packages] [Bug 1830936] Re: Wayland freeze 18.04 using VLC

[Dilip]

I somehow messed up the command you gave.

I was in Wayland and VLC crashed just now. I am attaching var/crash
files. There was only 2 of them. Thanks.

** Attachment added: "crash.zip"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830936/+attachment/5268008/+files/crash.zip

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

Title:
  Wayland freeze 18.04 using VLC

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I tried Wayland while logging in and it works fine until I try to play
  some local video file using VLC. Ubuntu freezes completely and I have
  to power off by pressing the power button. It works fine in the
  default Xorg Ubuntu session. I have the latest version of VLC that
  comes with the update which 3.0.6 and Ubuntu 18.04 fully updated.

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

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

Re: [Desktop-packages] [Bug 1827948] Use libreoffice-style-breeze as the default icon theme

[Marcus Tomlinson]

** Attachment added: "Base - Colibre.png"
   
https://bugs.launchpad.net/bugs/1827948/+attachment/5268001/+files/Base%20-%20Colibre.png

** Attachment added: "Calc - Colibre.png"
   
https://bugs.launchpad.net/bugs/1827948/+attachment/5268002/+files/Calc%20-%20Colibre.png

** Attachment added: "Draw - Colibre.png"
   
https://bugs.launchpad.net/bugs/1827948/+attachment/5268003/+files/Draw%20-%20Colibre.png

** Attachment added: "Writer - Colibre.png"
   
https://bugs.launchpad.net/bugs/1827948/+attachment/5268004/+files/Writer%20-%20Colibre.png

** Attachment added: "Math - Colibre.png"
   
https://bugs.launchpad.net/bugs/1827948/+attachment/5268005/+files/Math%20-%20Colibre.png

** Attachment added: "Impress - Colibre.png"
   
https://bugs.launchpad.net/bugs/1827948/+attachment/5268006/+files/Impress%20-%20Colibre.png

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

Title:
  Use libreoffice-style-breeze as the default icon theme

Status in libreoffice package in Ubuntu:
  New

Bug description:
  The Yaru icon theme uses 1 pixel strokes for its symbolic icon set. 
  So do the breeze icons for libreoffice.

  All in all does the breeze icon set for libre office fit very good to
  the look of the Yaru icons.

  https://i.imgur.com/tgioycv.png

  https://i.imgur.com/WwKvjMh.png

  Thus I would suggest to use it as the default icon set in Ubuntu to
  guarantee a consistent look and feel across the desktop

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

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

Re: [Desktop-packages] [Bug 1827948] Use libreoffice-style-breeze as the default icon theme

[Marcus Tomlinson]

** Attachment added: "Base - Colibre.png"
   
https://bugs.launchpad.net/bugs/1827948/+attachment/5267995/+files/Base%20-%20Colibre.png

** Attachment added: "Calc - Colibre.png"
   
https://bugs.launchpad.net/bugs/1827948/+attachment/5267996/+files/Calc%20-%20Colibre.png

** Attachment added: "Draw - Colibre.png"
   
https://bugs.launchpad.net/bugs/1827948/+attachment/5267997/+files/Draw%20-%20Colibre.png

** Attachment added: "Writer - Colibre.png"
   
https://bugs.launchpad.net/bugs/1827948/+attachment/5267998/+files/Writer%20-%20Colibre.png

** Attachment added: "Math - Colibre.png"
   
https://bugs.launchpad.net/bugs/1827948/+attachment/5267999/+files/Math%20-%20Colibre.png

** Attachment added: "Impress - Colibre.png"
   
https://bugs.launchpad.net/bugs/1827948/+attachment/5268000/+files/Impress%20-%20Colibre.png

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

Title:
  Use libreoffice-style-breeze as the default icon theme

Status in libreoffice package in Ubuntu:
  New

Bug description:
  The Yaru icon theme uses 1 pixel strokes for its symbolic icon set. 
  So do the breeze icons for libreoffice.

  All in all does the breeze icon set for libre office fit very good to
  the look of the Yaru icons.

  https://i.imgur.com/tgioycv.png

  https://i.imgur.com/WwKvjMh.png

  Thus I would suggest to use it as the default icon set in Ubuntu to
  guarantee a consistent look and feel across the desktop

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

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

[Desktop-packages] [Bug 1827948] Re: Use libreoffice-style-breeze as the default icon theme

[Olivier Tilloy]

Thanks for the detailed analysis mpt!

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

Title:
  Use libreoffice-style-breeze as the default icon theme

Status in libreoffice package in Ubuntu:
  New

Bug description:
  The Yaru icon theme uses 1 pixel strokes for its symbolic icon set. 
  So do the breeze icons for libreoffice.

  All in all does the breeze icon set for libre office fit very good to
  the look of the Yaru icons.

  https://i.imgur.com/tgioycv.png

  https://i.imgur.com/WwKvjMh.png

  Thus I would suggest to use it as the default icon set in Ubuntu to
  guarantee a consistent look and feel across the desktop

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

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

[Desktop-packages] [Bug 1827948] Re: Use libreoffice-style-breeze as the default icon theme

[Will Cooke]

Would someone be able to post some screenshots showing Colibre so that
we can all see what's being discussed?

I've used this page as a primer:
https://colibreoffice.wordpress.com/2018/05/21/libreoffice-6-1-fits-
windows-10/

and on first inspection, I like.

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

Title:
  Use libreoffice-style-breeze as the default icon theme

Status in libreoffice package in Ubuntu:
  New

Bug description:
  The Yaru icon theme uses 1 pixel strokes for its symbolic icon set. 
  So do the breeze icons for libreoffice.

  All in all does the breeze icon set for libre office fit very good to
  the look of the Yaru icons.

  https://i.imgur.com/tgioycv.png

  https://i.imgur.com/WwKvjMh.png

  Thus I would suggest to use it as the default icon set in Ubuntu to
  guarantee a consistent look and feel across the desktop

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

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

[Desktop-packages] [Bug 1831204] [NEW] Package geckodriver

[Olivier Tilloy]

Public bug reported:

Using selenium to drive firefox requires an executable called
geckodriver, which is nowhere to be found in Ubuntu packages. Instead,
all the information I could find on the internet suggests fetching that
executable from upstream and installing it to /usr/local/bin (see e.g.
https://askubuntu.com/questions/851401/where-to-find-geckodriver-needed-
by-selenium-python-package).

The sources for geckodriver are included in the firefox source tarball, and the 
executable is being built when building packages, but it's not installed 
anywhere.
I propose to create a new firefox-geckodriver binary package for this purpose, 
similar to the chromium-chromedriver package.

For context, I became interested in driving firefox with selenium when
attempting to replicate chromium-browser's autopkgtests
(https://bazaar.launchpad.net/~chromium-team/chromium-browser/eoan-
stable/files/head:/debian/tests/).

Upstream documentation for geckodriver: https://firefox-source-
docs.mozilla.org/testing/geckodriver/.

** Affects: firefox (Ubuntu)
 Importance: High
 Assignee: Olivier Tilloy (osomon)
 Status: Triaged

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

Title:
  Package geckodriver

Status in firefox package in Ubuntu:
  Triaged

Bug description:
  Using selenium to drive firefox requires an executable called
  geckodriver, which is nowhere to be found in Ubuntu packages. Instead,
  all the information I could find on the internet suggests fetching
  that executable from upstream and installing it to /usr/local/bin (see
  e.g. https://askubuntu.com/questions/851401/where-to-find-geckodriver-
  needed-by-selenium-python-package).

  The sources for geckodriver are included in the firefox source tarball, and 
the executable is being built when building packages, but it's not installed 
anywhere.
  I propose to create a new firefox-geckodriver binary package for this 
purpose, similar to the chromium-chromedriver package.

  For context, I became interested in driving firefox with selenium when
  attempting to replicate chromium-browser's autopkgtests
  (https://bazaar.launchpad.net/~chromium-team/chromium-browser/eoan-
  stable/files/head:/debian/tests/).

  Upstream documentation for geckodriver: https://firefox-source-
  docs.mozilla.org/testing/geckodriver/.

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

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

[Desktop-packages] [Bug 1817020] Re: Touching and dragging an icon on the dock blocks input to other apps

[Will Cooke]

I have installed GNOME Shell 3.28.4-0ubuntu18.04.1 from proposed.

I have tested this fix by dragging an icon up and down the launched with
my finger and dropping on it on icons.  In the past I could lock up the
shell very easily.  Now I can't get it to crash at all.

Marking as verification done.

Thanks all.


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

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

Title:
  Touching and dragging an icon on the dock blocks input to other apps

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Disco:
  Fix Released

Bug description:
  [ Impact ]

  
  Touching and dragging an icon on the dock blocks input to other apps Edit

  [ Test case ]

  - make sure the Ubuntu dock is visible
  - Using a finger drag, for example, a LibreOffice icon up and down the dock 
and then drop   
it on Nautilus.
  - When releasing the drag the icon would land back on the dock and I could 
continue to use   
the desktop as usual.

  [ Regression potential ]

  Touch events could not be handled properly at all by dock

  ---

  
  Steps to reproduce

  In GNOME Shell, make sure the Ubuntu dock is visible
  Using a finger drag, for example, a LibreOffice icon up and down the dock and 
then drop it on Nautilus.
  Notice that (sometimes?) the icon will continue to float above the dock and 
that the mouse will keep the clicky-finger icon.
  Notice that you can still open Activities and launch an application
  Notice however, that you can't actually interact with the application you 
have just launched

  = What I expected to happen =

  When releasing the drag the icon would land back on the dock and I
  could continue to use the desktop as usual.

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

-- 
Mailing list: https://launchpad.net/~desktop-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

[Dariusz Gadomski]

In a recent test with MaxJobs of 4 I was easily able to reach over
65 GB of memory consumption within 60 mins, while with LogDebugHistory
set to 0 the consumption was below 400 MB.

My recommendation is to lower the default LogDebugHistory value back to
what is upstream: 200.

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

Title:
  Extremely high memory consumption under heavy workload

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Under heavy workload conditions cups can reach irrationally high
  memory consumption very quickly (tens of GBs).

  Test case:
  1. Set MaxJobs to 4 in cupsd.conf.
  2. sudo apt install cups-pdf
  3. Fill the queue with jobs:
  while [ 1 ]; lp -d PDF /usr/share/cups/data/default.pdf; done
  4. Cancel all jobs
  cancel -a PDF
  5. Restart cups.
  6. Start filling the queue again (as in step 3).

  Expected result:
  Jobs are processed and memory consumption is proportional to the number of 
jobs.

  Actual result:
  After step 5 or at latest step 6 memory consumption starts to increase 
exponentially - from ~150-200 MB to 8+GB. Without foreseeing this it's very 
easy to get cupsd killed by OOM killer.

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

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

[Desktop-packages] [Bug 775502] Re: dconf-editor: set to default doesn't survive logout-in

[Sam_]

Solved on 18.04.2 with gnome-shell.

** Changed in: d-conf (Ubuntu)
   Status: New => Fix Released

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

Title:
  dconf-editor: set to default doesn't survive logout-in

Status in d-conf package in Ubuntu:
  Fix Released

Bug description:
  Reproducable.
  Install dconf-tools. Open dconf-editor. Go to /desktop/unity/launcher. Click 
on the string, then click on the button 'Set to default'.
  String changes to default values. Logout-in, go to the string again, custom 
values are displayed again. Custom apps in launcher still exist too.
  Expected: 'Set to default' should display default values immediately after 
change in launcher and survive the change througout logout.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: dconf-tools 0.7.3-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  Architecture: amd64
  Date: Mon May  2 13:21:39 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=de:en
   LANG=C
   SHELL=/bin/bash
  SourcePackage: d-conf
  UpgradeStatus: Upgraded to natty on 2011-04-28 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/775502/+subscriptions

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

[Desktop-packages] [Bug 799933] Re: Palimpsest window unrezisable, overlaps Unity workspace when a device is selected

[Sam_]

The issue is fixed on 18.04.2 with gnome-shell.

** Changed in: gnome-disk-utility (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Palimpsest window unrezisable, overlaps Unity workspace when a device
  is selected

Status in gnome-disk-utility package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: gnome-disk-utility

  In contrary to Bug #700749 it resizes now when clicked on a device in left 
menu. 
  But it resizes so big that it overlaps Unity workspaces and refuses to be 
resized manually, even the arrows are displayed, which make a user believe it 
can be resized (screenshot #1).
  A workaround would be to add a window rule via CCSM, on Natty it got 
respected, but not on Oneiric. 
  ## Side note. After enabling window rules plugin, Unity gets disrupted 
(screenshot #2 example shows the situation when the launcher is dogded).

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-disk-utility 3.0.0-1ubuntu1
  ProcVersionSignature: Ubuntu 3.0-1.2-generic 3.0.0-rc3
  Uname: Linux 3.0-1-generic x86_64
  NonfreeKernelModules: wl
  Architecture: amd64
  Date: Mon Jun 20 22:12:10 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110423)
  ProcEnviron:
   LANGUAGE=de:en
   PATH=(custom, no user)
   LANG=C
   LC_MESSAGES=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 340359] Re: Not a WebDAV enabled share

[Sam_]

No issue on 18.04.2 - closing as fixed.

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

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

Title:
  Not a WebDAV enabled share

Status in gvfs:
  Expired
Status in One Hundred Papercuts:
  Invalid
Status in gvfs package in Ubuntu:
  Fix Released

Bug description:
  (system: Ubuntu 8.10, i386, GNOME Desktop)

  Hallo,

  recently I started to play around with WebDAV shares. I'm running an
  apache webserver with DAV modules enabled on a remote mashine. Access
  seems to work an has been tested with different client.

  First Problem: Using Gnome's "connect to server" tool it is not
  possible to connect to a DAVS (webdav over SSL) server. At least, I
  was not able to do so.

  Second Problem: Unsing Nautilus I managed to connect my server using
  the URI "davs://server/path". The remote share is mounted and nautilus
  showes the content. Additionally a new icon appears on desktop
  representing the mountpoint. When I try to use that icon I always get
  the error "Not a WebDAV enabled share". I have to unmount this share
  (icon disappeares) and mount it again from scratch (or use a
  bookmark). An "ls ~.gvfs" on command-line gives another error message,
  namely "Input/output error ... WebDAV on Servername".

  What peace of software does all the magic (package)? So far I don't
  know.

  All that makes handling of davs shares very unpleasant. Please let me
  know if I can supply any further information, messages or application
  output.

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

-- 
Mailing list: https://launchpad.net/~desktop-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

[Dariusz Gadomski]

** Tags added: rls-ee-incoming

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

Title:
  Extremely high memory consumption under heavy workload

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Under heavy workload conditions cups can reach irrationally high
  memory consumption very quickly (tens of GBs).

  Test case:
  1. Set MaxJobs to 4 in cupsd.conf.
  2. sudo apt install cups-pdf
  3. Fill the queue with jobs:
  while [ 1 ]; lp -d PDF /usr/share/cups/data/default.pdf; done
  4. Cancel all jobs
  cancel -a PDF
  5. Restart cups.
  6. Start filling the queue again (as in step 3).

  Expected result:
  Jobs are processed and memory consumption is proportional to the number of 
jobs.

  Actual result:
  After step 5 or at latest step 6 memory consumption starts to increase 
exponentially - from ~150-200 MB to 8+GB. Without foreseeing this it's very 
easy to get cupsd killed by OOM killer.

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

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

[Desktop-packages] [Bug 1655348] Re: gpu-manager Error: can't open /lib/modules/

[Sam_]

This is on 18.04.2:
Issue solved from my side by not using chromium any longer, since then no 
system freeze.
The error message in title remains, but obviously causing not a complete system 
freeze.

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

Title:
  gpu-manager Error: can't open /lib/modules/

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

Bug description:
  At least once a day there is an unexpected desktop freeze incl. mouse
  and keyboard. Even magic-sys-rq isn't possible, only hard switch-off.
  From smartmontools I can exclude a hardware failure.

  I've found that gpu-manager and systemd fail to load kernel modules.
  This is among the output of journalctl | grep modules
  Jan 10 13:12:34  systemd[1]: systemd-modules-load.service: Unit entered 
failed state.
  Jan 10 13:12:34  systemd[1]: systemd-modules-load.service: Failed with result 
'exit-code'.
  Jan 10 13:12:49  gpu-manager[791]: Error: can't open 
/lib/modules/4.4.0-57-generic/updates/dkms
  Jan 10 13:12:49  gpu-manager[791]: Error: can't open 
/lib/modules/4.4.0-57-generic/updates/dkms
  (terminal-output attached)

  dito with latest kernel

  Jan 11 07:53:04 gpu-manager[786]: Error: can't open 
/lib/modules/4.4.0-59-generic/updates/dkms
  Jan 11 07:53:04 gpu-manager[786]: Error: can't open 
/lib/modules/4.4.0-59-generic/updates/dkms

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-drivers-common 1:0.4.17.2
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 10 14:37:00 2017
  InstallationDate: Installed on 2012-02-05 (1801 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120204)
  SourcePackage: ubuntu-drivers-common
  UpgradeStatus: Upgraded to xenial on 2016-08-01 (162 days ago)

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

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

[Desktop-packages] [Bug 1789656] Re: Complete system freeze happening sporadically when running chromium

[Sam_]

The issue was solved from my side by switching back to firefox. Before I had 
complete freezes but only the browser, this problem seems to be solved.
Since not using chromium there was no machine freeze at all.

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

Title:
  Complete system freeze happening sporadically when running chromium

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  This context is in syslog before complete system freeze, repeated a few times 
(attached file).
  Aug 29 15:43:41  chromium-browser.desktop[5003]: 
[5003:5017:0829/154341.786374:ERROR:service_manager_context.cc(250)] Attempting 
to run unsupported native service: 
/usr/lib/chromium-browser/chrome_renderer.service

  It happens sporadic but only after the start of chromium-browser loading 
about 20 tabs and moving from one to another.
  Complete system freeze, no console, no REISUB works.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 68.0.3440.106-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DVI-I-1:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBMLUoHABUUAQOANR54Cu6Ro1RMmSYPUFS/74BxT4EAgUCBgJUAlQ+zAAEBAjqAGHE4LUBYLEUAEyshAAAeAjqA0HI4LUAQLEWAEyshAAAe/QAYSxpRFwAKICAgICAg/ABTTUZYMjQ5MEhECiAgAYoCAxzxS5MEBRQDEhAfICEiIwkHB2cDDAAQALgtAR2A0HIcFiAQLCWAEyshAACeAR2AGHEcFiBYLCUAEyshAACeAR0AclHQHiBuKFUAEyshAAAejArQkCBAMSAMQFUAEyshAAAejArQiiDgLRAQPpYAEyshAAAezg==
   modes: 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 
1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 1680x1050 1280x1024 1280x1024 
1440x900 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 
1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 
720x576 720x480 720x480 720x480 640x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  Date: Wed Aug 29 16:01:30 2018
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg'
   
'/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2012-02-05 (2397 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120204)
  Load-Avg-1min: 2.18
  Load-Processes-Running-Percent:   0.1%
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=b3e26f93-613b-48e8-96d7-9c8854fe670c ro
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (15 days ago)
  dmi.bios.date: 07/30/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0305
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5QLD PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0305:bd07/30/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QLDPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2017-01-25T17:18:56.251795

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

-- 
Mailing list: https://launchpad.net/~desktop-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

[Launchpad Bug Tracker]

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

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

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

Title:
  Extremely high memory consumption under heavy workload

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Under heavy workload conditions cups can reach irrationally high
  memory consumption very quickly (tens of GBs).

  Test case:
  1. Set MaxJobs to 4 in cupsd.conf.
  2. sudo apt install cups-pdf
  3. Fill the queue with jobs:
  while [ 1 ]; lp -d PDF /usr/share/cups/data/default.pdf; done
  4. Cancel all jobs
  cancel -a PDF
  5. Restart cups.
  6. Start filling the queue again (as in step 3).

  Expected result:
  Jobs are processed and memory consumption is proportional to the number of 
jobs.

  Actual result:
  After step 5 or at latest step 6 memory consumption starts to increase 
exponentially - from ~150-200 MB to 8+GB. Without foreseeing this it's very 
easy to get cupsd killed by OOM killer.

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

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