date:20190611

** Changed in: pulseaudio
   Status: Unknown => Fix Released

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

Title:
  Pulseaudio module-jack-source unable to connect to jackd2

Status in PulseAudio:
  Fix Released
Status in jackd2 package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/604

  ---

  When installing jackd2 in ubuntu 18.04, i am unable to load the
  module-jack-source.

  Syslog gives me:

  Dec  5 11:49:45 nvidion pulseaudio[7905]: JACK error >attempt to connect to 
server failed<
  Dec  5 11:49:45 nvidion pulseaudio[7905]: jack_client_open() failed.
  Dec  5 11:49:45 nvidion pulseaudio[7905]: Failed to load module 
"module-jack-source" (argument: ""): initialization failed.
  Dec  5 11:49:45 nvidion pulseaudio[7905]: JACK error >connect(2) call to 
/dev/shm/jack-1000/default/jack_0 failed (err=Datei oder Verzeichnis nicht 
gefunden)<
  Dec  5 11:49:50 nvidion pulseaudio[7905]: message repeated 5 times: [ JACK 
error >connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=Datei 
oder Verzeichnis nicht gefunden)<]
  Dec  5 11:49:51 nvidio

  So the path to the shared memory location is not as expected.

  When jackd2 is running i have:

  hcw@nvidion:$ cd /dev/shm/
  hcw@nvidion:/dev/shm$ ls
  jack-1000-0  jack_sem.1000_default_1000_0_system  
jack_sem.1000_default_jack_rack  jack_sem.1000_jack_default_1000_0_system
  jack-1000-1  jack_sem.1000_default_freewheel  
jack_sem.1000_default_qjackctl   jack-shm-registry
  jack_default_1000_0  jack_sem.1000_default_jack_mixer 
jack_sem.1000_default_system

  So it seems module-jack-source / sink are guessing the wrong shared
  memory paths to the jackd2 server..

  Versions:
  jackd2 1.9.12~dfsg-2
  pulseaudio-module-jack 1:11.1-1ubuntu7.1
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-lowlatency 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-39-lowlatency x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-16 (111 days ago)
  UserGroups: adm audio dialout disk docker kvm libvirt mythtv tracing video 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 12/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 042NDD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd12/05/2017:svnDellInc.:pnInspiron7566:pvr:rvnDellInc.:rn042NDD:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7566
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2018-12-04T10:32:39.961952
  mtime.conffile..etc.pulse.default.pa: 2018-12-03T11:18:37.948772

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

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

[Desktop-packages] [Bug 1710060] Re: Sound Chipmunks on playback with Jabra Evolve 65 UC Headset

Launchpad has imported 13 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1282285.

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

On 2015-11-16T02:50:21+00:00 gizmo wrote:

Description of problem:
When playing audio through the Jabra Evolve 65 UC headset using either the USB 
cable or the Jabra Link 360 USB dongle, sound is played back too fast, with a 
'chipmunk' effect.  I don't know if the recording side is affected or not, but 
people have not commented on it if it is.

Version-Release number of selected component (if applicable):
Name: pulseaudio
Arch: x86_64
Epoch   : 0
Version : 6.0
Release : 8.fc22
Size: 3.3 M
Repo: @System

Name: alsa-plugins-pulseaudio
Arch: i686
Epoch   : 0
Version : 1.0.29
Release : 1.fc22
Size: 101 k
Repo: @System

How reproducible:
Always

Steps to Reproduce:
1. Plug in headset using USB cable.
2. Play audio

Actual results:
Audio plays fast.  Buffered audio streams (like youtube) play without gaps, but 
realtime streams (like Skype, or Jabber) play with gaps.

Expected results:
Audio should play back at the normal rate with no gaps.

Additional info:
My Logitech USB headset plays just fine.

When using the Jabra headset in BlueTooth mode, audio playback is normal
using either the A2DP audio profile or the HSP/HFP.

When connected with the USB cable lsusb reports the Jabra device as:
Bus 001 Device 008: ID 0b0e:030b GN Netcom

The Jabra device plays just fine on Windows, using the same computer.

System is running KDE with Phonon GStreamer and alsa.

I honestly don't know if this is a Pulse problem or an ALSA problem.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1710060/comments/0

On 2016-01-26T20:16:12+00:00 gizmo wrote:

This bug has been open now for 2 months with zero movement.  Is there
anything I can do to help out here?  I'm willing to troubleshoot, I just
have no idea what to do next.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1710060/comments/1

On 2016-01-29T18:50:29+00:00 wtaymans wrote:

I'm pretty sure that this is an alsa problem. The driver probably
configures the wrong samplerate or maybe it needs a tweak for this
particular hardware.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1710060/comments/2

On 2016-02-15T17:11:38+00:00 joerg.pareigis wrote:

Exactly the same here.
Trying with newest version of Debian 8 and SuSE 42.1.

The headset plays too fast with a short gap every second. Regardless
which connection is used. Directly via USB-Cable, or via BT-Dongle. Both
with the same result.

It plays the correct speed when connected via Bluetooth to Android devices.
Connected at Windows PC it pays also without any spot.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1710060/comments/3

On 2016-02-15T19:13:10+00:00 gizmo wrote:

(In reply to Wim Taymans from comment #2)
> I'm pretty sure that this is an alsa problem. The driver probably configures
> the wrong samplerate or maybe it needs a tweak for this particular hardware.

Ok, so I've got the same question; what can I do to help troubleshoot
this?  Guys, I'm willing to be your eyes and hands here, but these eyes
and hands need a brain to direct them. :)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1710060/comments/4

On 2016-03-05T22:15:20+00:00 bs.alex.mail wrote:

Hi. I've had the same problem.
Here is workaround that helped me:

In file

/etc/pulse/daemon.conf

replace
---
;default-sample-rate = 44100

|
v

with
---
default-sample-rate = 48000

And then reload pulseaudio

pulseaudio -k

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1710060/comments/5

On 2016-03-08T03:56:03+00:00 gizmo wrote:

Just tried this, and it appears to work here as well.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1710060/comments/6

On 2016-07-19T20:15:30+00:00 bcotton wrote:

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce

[Desktop-packages] [Bug 1831514] Re: Ubuntu 19.04 system update causes boot failure

2019-06-11 Thread Eli Linares

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

I apologize if I caused any confusion, to me I'm experiencing the same
problem as the other people commenting here after getting this update.
System won't boot, so I'm not sure how it's different, I Have hidden my
comments now though.

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

Title:
  Ubuntu 19.04 system update causes boot failure

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  ***
  *** Please reassign bug to proper package
  ***

  On Jun 3 2019, the system update corrupts the system.  It will not
  boot.  It hangs on the 3rd red dot of the Ubuntu splash screen.  The
  remaining 2 dots are white.  You never get the terminal screen with
  green [ ok] status lines.

  A complete new install works fine.  When you do a system update, you
  get the corruption and boot failure.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gedit 3.32.0-3
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  3 21:12:08 2019
  InstallationDate: Installed on 2019-04-14 (50 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  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/1831514/+subscriptions

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

Now tracking in bug 1832426 :(

-- 
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 Released
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 1832426] Re: "Program" is not responding when debugging in gdb

** Description changed:

- I believe this is a regression for  
- #1740869  is not responding window is constantly showing when 
debugging a program 
+ I believe this is a regression for bug 1740869:
+  is not responding window is constantly showing when debugging a 
program
  
  I'm debugging my c++ sdl2 program in gdb and when I hit a breakpoint
  this window shows up and I can't get it to stop asking me to close the
  program.
  
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:  Ubuntu 19.04
  Release:  19.04
  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  gnome-shell:
-   Installed: 3.32.1-1ubuntu1~19.04.1
-   Candidate: 3.32.1-1ubuntu1~19.04.1
-   Version table:
-  *** 3.32.1-1ubuntu1~19.04.1 500
- 500 http://us.archive.ubuntu.com/ubuntu disco-updates/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  3.32.0+git20190410-1ubuntu1 500
- 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
+   Installed: 3.32.1-1ubuntu1~19.04.1
+   Candidate: 3.32.1-1ubuntu1~19.04.1
+   Version table:
+  *** 3.32.1-1ubuntu1~19.04.1 500
+ 500 http://us.archive.ubuntu.com/ubuntu disco-updates/main amd64 
Packages
+ 100 /var/lib/dpkg/status
+  3.32.0+git20190410-1ubuntu1 500
+ 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  
  3) What you expected to happen
  When I hit a breakpoint in gdb, the program should stop.
  
  4) What happened instead
  The program stops and ubuntu asks me if i want to kill the program.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 11 22:03:44 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-08 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Status in gnome-shell package in Ubuntu:
  New

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 11 22:03:44 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-08 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

Does the freeze only happen when connected to wifi?

I can see a couple of errors from the kernel graphics driver suggesting
the display might freeze:

[  598.213901] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure 
on pipe A ...
[ 3696.507718] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure 
on pipe A ...

Please try logging into "Ubuntu on Wayland" and tell us if that helps.

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

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

** Summary changed:

- Xorg freeze
+ Display freezes

** Summary changed:

- Display freezes
+ Acer Chromebook [banon] display freezes

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

Title:
  Acer Chromebook [banon] display freezes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Freezes  when connected to wifi.  Running lsof -i and closing some of
  the processes results in black display, need to restart computer.  i
  can use the computer for very short periods when connected to the
  internet, frequently the display freezes requiring restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Jun 11 18:39:05 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-29-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-51-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270]
  InstallationDate: Installed on 2019-06-11 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: GOOGLE Banon
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-51-generic 
root=UUID=526150f3-bfd9-4afe-9eb7-32e6f327bfec ro quiet splash vt.handoff=1 
initrd=boot\initrd.img-4.15.0-51-generic
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2019
  dmi.bios.vendor: coreboot
  dmi.bios.version: MrChromebox-4.9
  dmi.board.name: Banon
  dmi.board.vendor: GOOGLE
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvrMrChromebox-4.9:bd01/04/2019:svnGOOGLE:pnBanon:pvr1.0:rvnGOOGLE:rnBanon:rvr1.0:cvnGOOGLE:ct9:cvr:
  dmi.product.family: Intel_Strago
  dmi.product.name: Banon
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE
  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 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

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

2019-06-11 Thread Eric Shaw

Public bug reported:

I believe this is a regression for    
#1740869  is not responding window is constantly showing when 
debugging a program 

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

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

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

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

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

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
Uname: Linux 5.0.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 11 22:03:44 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-06-08 (4 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco

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

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

Status in gnome-shell package in Ubuntu:
  New

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 11 22:03:44 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-08 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1832369] Re: [Thomson THN14B] Internal speaker does not work

Can you please try booting Ubuntu 19.04 from USB and tell us if that
fixes the problem?

  http://releases.ubuntu.com/19.04/

Please also note that Ubuntu 18.10 will reach end-of-life next month
(https://wiki.ubuntu.com/Releases).

** Summary changed:

- AUDIO WORK ONLY WITH AUDIO EXTERNAL. AUDIO DIDNT WORK ON INTERNAL SPEAKER
+ [Thomson THN14B] Internal speaker does not work

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

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

Title:
  [Thomson THN14B] Internal speaker does not work

Status in linux package in Ubuntu:
  New

Bug description:
  HI,

  I have a thomson THN14B with audio card rt5651 and bluetooth

  If i list a aplay -l to list all my sound card i get :

   Liste des Périphériques Matériels PLAYBACK 
  carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 0: HdmiLpeAudio [Intel 
HDMI/DP LPE Audio]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 1: HdmiLpeAudio [Intel 
HDMI/DP LPE Audio]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 2: HdmiLpeAudio [Intel 
HDMI/DP LPE Audio]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 0: 3 []
Sous-périphériques: 0/1
Sous-périphérique #0: subdevice #0
  carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 1: Deep-Buffer Audio (*) []
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0

  
  I thinks it's a bug with interaction to HDMI and RT5651 who broke my internal 
speaker sound.

  Have a nice day

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sandra 1154 F pulseaudio
   /dev/snd/pcmC1D0c:   sandra 1154 F...m pulseaudio
   /dev/snd/pcmC1D0p:   sandra 1154 F...m pulseaudio
   /dev/snd/controlC0:  sandra 1154 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Jun 11 17:21:59 2019
  InstallationDate: Installed on 2019-06-11 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to cosmic on 2019-06-11 (0 days ago)
  dmi.bios.date: 01/02/2018
  dmi.bios.version: HXFZ-14-BI-Y116CR600-CC34O-001-D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Cherry Trail CR
  dmi.board.vendor: AMI Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvn:bvrHXFZ-14-BI-Y116CR600-CC34O-001-D:bd01/02/2018:svnThomson:pnTHN14B:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnCherryTrailCR:rvrTobefilledbyO.E.M.:cvn:ct10:cvrTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: THN14B
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Thomson
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2019-06-11T15:27:04.110034

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

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

[Desktop-packages] [Bug 1832004] Re: [amdgpu] display hanging after laptop opens lid

Also, do you have any nonstandard gnome-shell extensions installed?

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

Title:
  [amdgpu] display hanging after laptop opens lid

Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 19.04

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  7 14:56:09 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   anbox, 1, 5.0.0-15-generic, x86_64: installed
   anbox, 1, 5.0.0-16-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-15-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev da) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1043:1680]
  InstallationDate: Installed on 2018-08-03 (308 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. E402BA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=c593d94b-7cc0-45ca-a012-f79a49d00093 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E402BA.311
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E402BA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE402BA.311:bd09/06/2018:svnASUSTeKCOMPUTERINC.:pnE402BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE402BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: E402BA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1832004/+subscriptions

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

[Desktop-packages] [Bug 1832004] Re: [amdgpu] display hanging after laptop opens lid

Thanks. I can't yet see any explanation for the problem.

In case something has crashed, please try following these instructions:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

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

Title:
  [amdgpu] display hanging after laptop opens lid

Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 19.04

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  7 14:56:09 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   anbox, 1, 5.0.0-15-generic, x86_64: installed
   anbox, 1, 5.0.0-16-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-15-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev da) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1043:1680]
  InstallationDate: Installed on 2018-08-03 (308 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. E402BA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=c593d94b-7cc0-45ca-a012-f79a49d00093 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E402BA.311
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E402BA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE402BA.311:bd09/06/2018:svnASUSTeKCOMPUTERINC.:pnE402BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE402BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: E402BA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1832004/+subscriptions

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

[Desktop-packages] [Bug 1806860] Re: Pulseaudio module-jack-source unable to connect to jackd2

** Bug watch added: PulseAudio #604
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/604

** Also affects: pulseaudio via
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/604
   Importance: Unknown
   Status: Unknown

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

Title:
  Pulseaudio module-jack-source unable to connect to jackd2

Status in PulseAudio:
  Unknown
Status in jackd2 package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/604

  ---

  When installing jackd2 in ubuntu 18.04, i am unable to load the
  module-jack-source.

  Syslog gives me:

  Dec  5 11:49:45 nvidion pulseaudio[7905]: JACK error >attempt to connect to 
server failed<
  Dec  5 11:49:45 nvidion pulseaudio[7905]: jack_client_open() failed.
  Dec  5 11:49:45 nvidion pulseaudio[7905]: Failed to load module 
"module-jack-source" (argument: ""): initialization failed.
  Dec  5 11:49:45 nvidion pulseaudio[7905]: JACK error >connect(2) call to 
/dev/shm/jack-1000/default/jack_0 failed (err=Datei oder Verzeichnis nicht 
gefunden)<
  Dec  5 11:49:50 nvidion pulseaudio[7905]: message repeated 5 times: [ JACK 
error >connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=Datei 
oder Verzeichnis nicht gefunden)<]
  Dec  5 11:49:51 nvidio

  So the path to the shared memory location is not as expected.

  When jackd2 is running i have:

  hcw@nvidion:$ cd /dev/shm/
  hcw@nvidion:/dev/shm$ ls
  jack-1000-0  jack_sem.1000_default_1000_0_system  
jack_sem.1000_default_jack_rack  jack_sem.1000_jack_default_1000_0_system
  jack-1000-1  jack_sem.1000_default_freewheel  
jack_sem.1000_default_qjackctl   jack-shm-registry
  jack_default_1000_0  jack_sem.1000_default_jack_mixer 
jack_sem.1000_default_system

  So it seems module-jack-source / sink are guessing the wrong shared
  memory paths to the jackd2 server..

  Versions:
  jackd2 1.9.12~dfsg-2
  pulseaudio-module-jack 1:11.1-1ubuntu7.1
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-lowlatency 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-39-lowlatency x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-16 (111 days ago)
  UserGroups: adm audio dialout disk docker kvm libvirt mythtv tracing video 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 12/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 042NDD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd12/05/2017:svnDellInc.:pnInspiron7566:pvr:rvnDellInc.:rn042NDD:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7566
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2018-12-04T10:32:39.961952
  mtime.conffile..etc.pulse.default.pa: 2018-12-03T11:18:37.948772

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

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

[Desktop-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while

Filip,

Since you are the original reporter and no longer experience a problem
then I would prefer to keep this bug closed.

---

Gabriele,

If you are experiencing audio problems then please open a new bug by
running:

  ubuntu-bug pulseaudio

so that we can review the details of your affected machine.

** Changed in: linux (Ubuntu)
   Status: Expired => Fix Released

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

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

Title:
  [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails
  after a while

Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Audio dies after few seconds, returns after few minutes and dies again

  filip@ux433:~$ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.20.14-042014-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filip  8566 F pulseaudio
   /dev/snd/pcmC0D0p:   filip  8566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  6 10:11:01 2019
  InstallationDate: Installed on 2019-01-05 (59 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 
comm="/usr/bin/pulseaudio --daemonize=no ")
  Symptom_Type: Sound works for a while, then breaks
  Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails 
after a while
  UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago)
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX433FN.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX433FN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX433FN_UX433FN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Sp

David, see bug 1832138.

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

Title:
  CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error
  calling StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  That error is logged:

  org.gnome.ScreenSaver[1081]: Unable to init server: Could not connect:
  Connection refused

  then:

  gnome-session[895]: gnome-session-binary[895]: CRITICAL: Unable to
  create a DBus proxy for GnomeScreensaver: Error calling
  StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

  oem@ubuntu:~$ localectl
     System Locale: LANG=en_US.UTF-8
     VC Keymap: n/a
    X11 Layout: fr
     X11 Model: pc105
   X11 Variant: oss

  So, with googling help (https://bbs.archlinux.org/viewtopic.php?id=180103), 
i've edited /etc/locale-gen (as user) and uncommented the line: fr_FR.UTF-8
   and then ran 'sudo locale-gen' and finally rebooted.

  But the error is still logged after reboot: either i need to set also
  'VC Keymap', but how ?, or it is related to the vte version actually
  used (and need an upgrade)
  (https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1721412)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.26.1-0ubuntu7
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec  3 17:17:45 2017
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

** Also affects: gdm3 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: mutter (Ubuntu Eoan)
   Importance: Undecided
 Assignee: Daniel van Vugt (vanvugt)
   Status: Confirmed

** Also affects: gdm3 (Ubuntu Eoan)
   Importance: Undecided
   Status: Confirmed

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

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

** No longer affects: gdm3 (Ubuntu)

** No longer affects: gdm3 (Ubuntu Bionic)

** No longer affects: gdm3 (Ubuntu Eoan)

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

** Changed in: mutter (Ubuntu Bionic)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

** Changed in: mutter (Ubuntu Eoan)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

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

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

Status in mutter package in Ubuntu:
  Invalid
Status in mutter source package in Bionic:
  Confirmed
Status in mutter source package in Eoan:
  Invalid

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.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 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1

[Desktop-packages] [Bug 1018204] Re:

Launchpad has imported 9 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=835863.

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


On 2012-06-27T10:29:19+00:00 jlieskov wrote:

Common Vulnerabilities and Exposures assigned an identifier
CVE-2012-2807 to the following vulnerability:

Multiple integer overflows in libxml2, as used in Google Chrome before
20.0.1132.43, on 64-bit Linux platforms allow remote attackers to cause
a denial of service or possibly have unspecified other impact via
unknown vectors.

References:
[1] http://code.google.com/p/chromium/issues/detail?id=129930
[2] 
http://googlechromereleases.blogspot.com/2012/06/stable-channel-update_26.html

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1018204/comments/1


On 2012-06-28T12:08:51+00:00 jlieskov wrote:

Relevant Google Chrome patch:
[3] 
http://git.chromium.org/gitweb/?p=chromium/src.git;a=commitdiff;h=f183580d61c054f7f6bb35cfe29e1b342390fbeb

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1018204/comments/4


On 2012-07-18T10:26:45+00:00 veillard wrote:

Okay, i finally pushed a patch upstream that I think should backport
rather easily

http://git.gnome.org/browse/libxml2/commit/?id=459eeb9dc752d5185f57ff6b135027f11981a626

that one

http://git.gnome.org/browse/libxml2/commit/?id=4f9fdc709c4861c390cd84e2ed1fd878b3442e28

should also be applied in the errata to avoid similar problem elsewhere.
Somehow that's not a complete fix but that's the most immediate and
simple way to stop the given problem. I'm still working on a (rather
large and intrusive) set of patches for upstream but I would not suggest
to push that in RHEL. For fedora I may be tempted to rebase once a new
libxml2 version is out

Daniel

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1018204/comments/7


On 2012-07-27T07:08:17+00:00 huzaifas wrote:

The above patches, described in comment #4 seems to solve the problem
here. libxml2 no longer crashes with them.

For Red Hat Enterprise Linux use case, we may however require few more
patches from upstream.

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1018204/comments/8


On 2012-07-27T08:42:59+00:00 huzaifas wrote:

Created libxml2 tracking bugs for this issue

Affects: fedora-all [bug 843743]

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1018204/comments/9


On 2012-09-04T21:37:12+00:00 teger wrote:

This has been reported over 2 months ago with a possible fix coming in a
little over a month.  Is there any plan of action to fix libxml2
vulnerabilities?

Primarily this is a bump to put in back on someones to do list.
Thank you

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1018204/comments/10


On 2012-09-18T17:21:34+00:00 errata-xmlrpc wrote:

This issue has been addressed in following products:

  Red Hat Enterprise Linux 5
  Red Hat Enterprise Linux 6

Via RHSA-2012:1288 https://rhn.redhat.com/errata/RHSA-2012-1288.html

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1018204/comments/12


On 2012-09-20T02:42:09+00:00 huzaifas wrote:

Created mingw32-libxml2 tracking bugs for this issue

Affects: epel-5 [bug 858914]
Affects: fedora-all [bug 858915]

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1018204/comments/13


On 2013-01-04T10:35:49+00:00 huzaifas wrote:

This flaw affects x86_64 version of libxml2 only, however
mingw32-libxml2 is only shipped as x86 (32-bit) and therefore it is not
affected.


Statement:

This issue affected the version of libxml2 as shipped with Red Hat
Enterprise Linux 5 and 6 has been addressed via RHSA-2012:1288. This
issue does not affect the version of mingw32-libxml2 as shipped with Red
Hat Enterprise Linux 6.

Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1018204/comments/17


** Bug watch added: code.google.com/p/chromium/issues #129930
   http://code.google.com/p/chromium/issues/detail?id=129930

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed

[Desktop-packages] [Bug 1831356] Re: Settings crashes when I click "Devices"(Enheter in norwegian) tap

Thanks. I see now that you filed this bug from a Unity session, and I
can reproduce the problem on Unity. The problem is that AFAIK gnome-
control-center is not designed to work with Unity; unity-control-center
is there for reasons.

Why are you using gnome-control-center on Unity?

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

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

Title:
  Settings crashes when I click "Devices"(Enheter in norwegian) tap

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

Bug description:
  Not much to say. It crashes every time, I cleick devices - and then
  continues to crash on every start up. Trying the command:

gsettings reset org.gnome.ControlCenter last-panel

  as a known workaround for a similar problem, will let me access gnome-
  control-center and use it, until I click Devices again.

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Jun  2 03:21:58 2019
  InstallationDate: Installed on 2018-12-11 (172 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to disco on 2019-06-02 (0 days ago)

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

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

[Desktop-packages] [Bug 1800003] Re: evince crashes in FcConfigParseAndLoad

2019-06-11 Thread J B

This bug https://gitlab.freedesktop.org/fontconfig/fontconfig/issues/71
suggests that substantial improvements have been made to the fontconfig
package against null pointer dereferences after version 2.13.0-5.

https://cgit.freedesktop.org/fontconfig/commit/?id=efac784b0108d3140d7ec51cf22cb8a4453bd566
https://cgit.freedesktop.org/fontconfig/commit/?id=b1762935c3db2bc611750c61ce9cb38b9008db6b
https://cgit.freedesktop.org/fontconfig/commit/?id=b047e299546ac3abb79cf0bac3c67f5c2dfc7fb6
https://cgit.freedesktop.org/fontconfig/commit/?id=f3981a8bcd97a0388bf150ea7c1b4a1015e5e358

Can fontconfig be updated?

** Bug watch added: gitlab.freedesktop.org/fontconfig/fontconfig/issues #71
   https://gitlab.freedesktop.org/fontconfig/fontconfig/issues/71

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

Title:
  evince crashes in FcConfigParseAndLoad

Status in fontconfig package in Ubuntu:
  Confirmed

Bug description:
  I have the following situation persistently on my system (Ubuntu
  18.04.1 on Dell Latitude E6500):

  Evince called with any pdf file crashes immediately with a
  segmentation fault. From the crash dump, I see that the crash happens
  in fontconfig's FcConfigParseAndLoad function, i.e. when the system
  fonts.conf is read. I can reproduce the crash with the following
  minimal example:

  
  #include 

  const FcChar8* filename = "/home/mirkoh/fontconfig-test/fonts.conf";
  FcConfig* config;

  int main(){
 FcConfigParseAndLoad(config, filename, FcTrue);
  }
  

  The fonts.conf file used here is also absolutely minimal:

  
  
  
  
  
  

  (Get me right. It first happened with my system fonts.conf, which is
  not empty. In order to find out whether a specific entry lead to the
  crash, I deleted entry after entry, ultimately reaching the file
  above, and always FcConfigParseAndLoad crashes.

  I have no idea how to go on from here.

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

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

[Desktop-packages] [Bug 1832419] [NEW] Xorg freeze

2019-06-11 Thread catherine

Public bug reported:

Freezes  when connected to wifi.  Running lsof -i and closing some of
the processes results in black display, need to restart computer.  i can
use the computer for very short periods when connected to the internet,
frequently the display freezes requiring restart.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Uname: Linux 4.15.0-51-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompositorRunning: None
Date: Tue Jun 11 18:39:05 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.18, 4.15.0-29-generic, x86_64: installed
 virtualbox, 5.2.18, 4.15.0-51-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA 
controller])
   Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270]
InstallationDate: Installed on 2019-06-11 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: GOOGLE Banon
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-51-generic 
root=UUID=526150f3-bfd9-4afe-9eb7-32e6f327bfec ro quiet splash vt.handoff=1 
initrd=boot\initrd.img-4.15.0-51-generic
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/04/2019
dmi.bios.vendor: coreboot
dmi.bios.version: MrChromebox-4.9
dmi.board.name: Banon
dmi.board.vendor: GOOGLE
dmi.board.version: 1.0
dmi.chassis.type: 9
dmi.chassis.vendor: GOOGLE
dmi.modalias: 
dmi:bvncoreboot:bvrMrChromebox-4.9:bd01/04/2019:svnGOOGLE:pnBanon:pvr1.0:rvnGOOGLE:rnBanon:rvr1.0:cvnGOOGLE:ct9:cvr:
dmi.product.family: Intel_Strago
dmi.product.name: Banon
dmi.product.version: 1.0
dmi.sys.vendor: GOOGLE
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 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Freezes  when connected to wifi.  Running lsof -i and closing some of
  the processes results in black display, need to restart computer.  i
  can use the computer for very short periods when connected to the
  internet, frequently the display freezes requiring restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Jun 11 18:39:05 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-29-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-51-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270]
  InstallationDate: Installed on 2019-06-11 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: GOOGLE Banon
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-51-generic 
root=UUID=526150f3-bfd9-4afe-9eb7-32e6f327bfec ro quiet splash vt.handoff=1 
initrd=boot\initrd.img-4.15.0-51-generic
  SourcePackage: xorg
  Symptom:

[Desktop-packages] [Bug 1800003] Re: evince crashes in FcConfigParseAndLoad

2019-06-11 Thread J B

I can also reproduce the crash with the minimal test program provided in
the bug report (nice catch!). I am on Ubuntu 18.04.2.

** Changed in: fontconfig (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  evince crashes in FcConfigParseAndLoad

Status in fontconfig package in Ubuntu:
  Confirmed

Bug description:
  I have the following situation persistently on my system (Ubuntu
  18.04.1 on Dell Latitude E6500):

  Evince called with any pdf file crashes immediately with a
  segmentation fault. From the crash dump, I see that the crash happens
  in fontconfig's FcConfigParseAndLoad function, i.e. when the system
  fonts.conf is read. I can reproduce the crash with the following
  minimal example:

  
  #include 

  const FcChar8* filename = "/home/mirkoh/fontconfig-test/fonts.conf";
  FcConfig* config;

  int main(){
 FcConfigParseAndLoad(config, filename, FcTrue);
  }
  

  The fonts.conf file used here is also absolutely minimal:

  
  
  
  
  
  

  (Get me right. It first happened with my system fonts.conf, which is
  not empty. In order to find out whether a specific entry lead to the
  crash, I deleted entry after entry, ultimately reaching the file
  above, and always FcConfigParseAndLoad crashes.

  I have no idea how to go on from here.

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

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

[Desktop-packages] [Bug 1800003] Re: evince crashes in FcConfigParseAndLoad

2019-06-11 Thread J B

Please re-open. I have the same bug.

$ /usr/bin/evince

(evince:2751): Gtk-WARNING **: 00:31:32.744: Attempting to read the recently 
used resources file at '/home/user/.local/share/recently-used.xbel', but the 
parser failed: Failed to open file 
“/home/user/.local/share/recently-used.xbel”: Permission denied.
Segmentation fault (core dumped)

 $ { echo run; echo thread apply all bt full; quit; } | gdb /usr/bin/evince
GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/evince...
Command 'quit' not found, did you mean:

  command 'luit' from deb x11-utils
  command 'quiz' from deb bsdgames
  command 'qgit' from deb qgit
  command 'quilt' from deb quilt
  command 'quot' from deb quota

Try: sudo apt install 

(no debugging symbols found)...done.
(gdb) Starting program: /usr/bin/evince 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7f82dcba5700 (LWP 1767)]
[New Thread 0x7f82d7fff700 (LWP 1768)]
[New Thread 0x7f82d698b700 (LWP 1770)]

(evince:1763): Gtk-WARNING **: 00:25:28.185: Attempting to read the
recently used resources file at '/home/user/.local/share/recently-
used.xbel', but the parser failed: Failed to open file
“/home/user/.local/share/recently-used.xbel”: Permission denied.

Thread 1 "evince" received signal SIGSEGV, Segmentation fault.
tcache_get (tc_idx=2) at malloc.c:2943
2943malloc.c: No such file or directory.
(gdb) 
Thread 4 (Thread 0x7f82d698b700 (LWP 1770)):
#0  0x7f82e51f2839 in syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f82e5b175ca in g_cond_wait_until () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f82e5aa4571 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f82e5af98b4 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f82e5af8f15 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f82e54cf6db in start_thread (arg=0x7f82d698b700) at 
pthread_create.c:463
pd = 0x7f82d698b700
now = 
unwind_buf = 
  {cancel_jmp_buf = {{jmp_buf = {140199922808576, 
1224657468070533167, 140199922805888, 0, 93940877964608, 140722239005440, 
-1154198811298523089, -115430923678801}, mask_was_saved = 0}}, priv = {pad 
= {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = 
#6  0x7f82e51f888f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f82d7fff700 (LWP 1768)):
#0  0x7f82e51ebbf9 in __GI___poll (fds=0x557050881f10, nfds=2, timeout=-1) 
at ../sysdeps/unix/sysv/linux/poll.c:29
resultvar = 18446744073709551100
sc_cancel_oldtype = 0
#1  0x7f82e5ad14c9 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f82e5ad1862 in g_main_loop_run () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f82e62e2026 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x7f82e5af8f15 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f82e54cf6db in start_thread (arg=0x7f82d7fff700) at 
pthread_create.c:463
pd = 0x7f82d7fff700
now = 
unwind_buf = 
  {cancel_jmp_buf = {{jmp_buf = {140199946352384, 
1224657468070533167, 140199946349696, 0, 93940875327344, 140722239002480, 
-1154200763361159121, -115430923678801}, mask_was_saved = 0}}, priv = {pad 
= {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = 
#6  0x7f82e51f888f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f82dcba5700 (LWP 1767)):
#0  0x7f82e51ebbf9 in __GI___poll (fds=0x55705086fe50, nfds=2, timeout=-1) 
at ../sysdeps/unix/sysv/linux/poll.c:29
resultvar = 18446744073709551100
sc_cancel_oldtype = 0
#1  0x7f82e5ad14c9 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f82e5ad15dc in g_main_context_iteration () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f82e5ad1621 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f82e5af8f15 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f82e54cf6db in start_thread (arg=0x7f82dcba5700) at 
pthread_create.c:463
pd = 0x7f82dcba5700
now = 
unwind_buf =

[Desktop-packages] [Bug 1831356] Re: Settings crashes when I click "Devices"(Enheter in norwegian) tap

2019-06-11 Thread Lars Bahner

bahner@venus:~$ gnome-control-center

(gnome-control-center:14031): display-cc-panel-WARNING **: 00:05:00.218:
no sunset data, using 16,00

(gnome-control-center:14031): display-cc-panel-WARNING **: 00:05:00.218:
no sunrise data, using 8,00

(gnome-control-center:14031): GLib-GObject-CRITICAL **: 00:05:00.230: 
g_object_ref: assertion 'G_IS_OBJECT (object)' failed
Minnesegmentsfeil (kjerne lagret i fil)
bahner@venus:~$ 

That's a segfault. This happens, when I click Devices, and everytime I
start gnome-control-center after that (without getting the time to do
anything).

Cheers.

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

Title:
  Settings crashes when I click "Devices"(Enheter in norwegian) tap

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

Bug description:
  Not much to say. It crashes every time, I cleick devices - and then
  continues to crash on every start up. Trying the command:

gsettings reset org.gnome.ControlCenter last-panel

  as a known workaround for a similar problem, will let me access gnome-
  control-center and use it, until I click Devices again.

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Jun  2 03:21:58 2019
  InstallationDate: Installed on 2018-12-11 (172 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to disco on 2019-06-02 (0 days ago)

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

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

[Desktop-packages] [Bug 1832414] [NEW] Removing document files spam from cups

2019-06-11 Thread Dave Jones

Public bug reported:

Since my server (running xenial) updated to cups 2.1.3-4ubuntu0.9 last
night the CUPS logs have had a considerable number of messages from
cupsd stating "Removing document files" - about 3 or 4 a second
constantly. Stopping the cups service stops the log-spam, and starting
it again immediately resumes it (after a few hundred "Loading from
cache..." messages). I've tried removing document files from the cache
(there were a couple of ancient ones lying around - it's not a heavily
used printer), but this made little difference to the symptoms.

I'm pretty confident this is due to the upgrade as:

1. the spam in the logs starts immediately after CUPS reloads (after the
upgrade)

2. looking at the diff for 2.1.3-4ubuntu0.9 it does seem to be fiddling
with things related to job clean-up (e.g. cupsdUpdateJobs and
cupsdCleanJobs in scheduler/job.c)

If I can provide any further information, do let me know!

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

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

Title:
  Removing document files spam from cups

Status in cups package in Ubuntu:
  New

Bug description:
  Since my server (running xenial) updated to cups 2.1.3-4ubuntu0.9 last
  night the CUPS logs have had a considerable number of messages from
  cupsd stating "Removing document files" - about 3 or 4 a second
  constantly. Stopping the cups service stops the log-spam, and starting
  it again immediately resumes it (after a few hundred "Loading from
  cache..." messages). I've tried removing document files from the cache
  (there were a couple of ancient ones lying around - it's not a heavily
  used printer), but this made little difference to the symptoms.

  I'm pretty confident this is due to the upgrade as:

  1. the spam in the logs starts immediately after CUPS reloads (after
  the upgrade)

  2. looking at the diff for 2.1.3-4ubuntu0.9 it does seem to be
  fiddling with things related to job clean-up (e.g. cupsdUpdateJobs and
  cupsdCleanJobs in scheduler/job.c)

  If I can provide any further information, do let me know!

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

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

[Desktop-packages] [Bug 1731318] Re: NVIDIA systems will not suspend with lid close and no external monitors

2019-06-11 Thread Jeremy Soller

Please see https://gitlab.gnome.org/GNOME/gnome-
desktop/merge_requests/39

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

Title:
  NVIDIA systems will not suspend with lid close and no external
  monitors

Status in gnome-desktop:
  Confirmed
Status in gnome-desktop3 package in Ubuntu:
  Confirmed

Bug description:
  With the NVIDIA driver, nvidia-384, the system will not sleep when the
  lid is closed due to gnome_rr_output_is_builtin_display incorrectly
  returning false. I have linked to an upstream bug, which also has
  patches fixing the issue.

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

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

[Desktop-packages] [Bug 1731318] Re: NVIDIA systems will not suspend with lid close and no external monitors

2019-06-11 Thread Jeremy Soller

For what it's worth, what was said about the patch was that the code it
was editing would be going away soon. That never happened. I have
commented again to see if there is still interest in the patch upstream.

I highly recommend considering the patch for Ubuntu even if upstream has
not taken it.

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

Title:
  NVIDIA systems will not suspend with lid close and no external
  monitors

Status in gnome-desktop:
  Confirmed
Status in gnome-desktop3 package in Ubuntu:
  Confirmed

Bug description:
  With the NVIDIA driver, nvidia-384, the system will not sleep when the
  lid is closed due to gnome_rr_output_is_builtin_display incorrectly
  returning false. I have linked to an upstream bug, which also has
  patches fixing the issue.

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

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

[Desktop-packages] [Bug 1731318] Re: NVIDIA systems will not suspend with lid close and no external monitors

> I have commented again to see if there is still interest in the patch
upstream.

The right way to contribute a patch to GNOME nowadays is to make a pull
request on gitlab, a comment on a bug is likely to not get in any
reviewer queue and would require extra maintainer to be merged, please
be a good upstream citizen and do a proper PR for the change

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

Title:
  NVIDIA systems will not suspend with lid close and no external
  monitors

Status in gnome-desktop:
  Confirmed
Status in gnome-desktop3 package in Ubuntu:
  Confirmed

Bug description:
  With the NVIDIA driver, nvidia-384, the system will not sleep when the
  lid is closed due to gnome_rr_output_is_builtin_display incorrectly
  returning false. I have linked to an upstream bug, which also has
  patches fixing the issue.

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

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

[Desktop-packages] [Bug 1141034] Re: RTL Spreadsheet Insert Cells

2019-06-11 Thread EliCoten

Still present in LibreOffice 6.1.5.2
Build ID: 1:6.1.5-0ubuntu0.18.10.1

https://bugs.documentfoundation.org/show_bug.cgi?id=125868

** Bug watch added: Document Foundation Bugzilla #125868
   https://bugs.documentfoundation.org/show_bug.cgi?id=125868

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

Title:
  RTL Spreadsheet Insert Cells

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  When using a right-to-left spreadsheet, right clicking and selected
  "insert cells" shows the normal LTR option to shift cells right,
  although when used it actually shifts cells left.

  I believe that shifting cells left is the correct behaviour in this
  case, but the text of the option should be changed to read "shift
  cells left". This was first noticed when using the Hebrew language
  user interface, but the problem is present when using English UI too.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice-calc 1:3.5.7-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37
  Uname: Linux 3.2.0-38-generic i686
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: i386
  CheckboxSubmission: ad9a15703e19217cb3448f881e125f6a
  CheckboxSystem: abc83e3988b72e7c3a9b3aa684cb92fd
  Date: Sun Mar  3 00:47:21 2013
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to precise on 2012-05-01 (305 days ago)

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

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

[Desktop-packages] [Bug 1828124] Re: org.gnome.evolution.dataserver.Source completely unveils account credentials in plain text while using dbus-monitor

** Changed in: evolution-data-server (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  org.gnome.evolution.dataserver.Source completely unveils account
  credentials in plain text while using dbus-monitor

Status in evolution-data-server:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Won't Fix

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 16.04 LTS
  2. Install Evolution
  3. Set-up Google account with default settings (this will end with e-mail and 
calendar)
  4. Reboot
  5. Open evolution Calendar and/or indicator-datetime
  6. Launch `dbus-monitor`

  Expected results:
  * Evolution does not show account credentials in plain text in `dbus-monitor` 
output

  Actual results:
  * Evolution shows account credentials in plain text in `dbus-monitor` output:

  
  method call time=1557268474.383095 sender=:1.74 -> destination=:1.40 
serial=939 path=/org/gnome/evolution/dataserver/SourceManager/Source_17; 
interface=org.gnome.evolution.dataserver.Source; member=InvokeAuthenticate
 array [
string "password:myrealpassword"
string "ssl-trust:"
 ]
  method return time=1557268474.383686 sender=:1.40 -> destination=:1.74 
serial=366 reply_serial=939
  signal time=1557268474.389206 sender=:1.40 -> destination=(null destination) 
serial=367 path=/org/gnome/evolution/dataserver/SourceManager/Source_17; 
interface=org.gnome.evolution.dataserver.Source; member=Authenticate
 array [
string "password:myrealpassword"
string "ssl-trust:"
 ]

  signal time=1557268520.956861 sender=:1.40 -> destination=(null destination) 
serial=408 path=/org/gnome/evolution/dataserver/SourceManager/Source_19; 
interface=org.gnome.evolution.dataserver.Source; member=Authenticate
 array [
string "password:myrealpassword"
string "ssl-trust:"
string "username:real@email"
 ]
  signal time=1557268520.960443 sender=:1.40 -> destination=(null destination) 
serial=409 path=/org/gnome/evolution/dataserver/SourceManager/Source_18; 
interface=org.gnome.evolution.dataserver.Source; member=Authenticate
 array [
string "password:myrealpassword"
string "ssl-trust:"
string "username:real@email"
 ]
  signal time=1557268520.964374 sender=:1.40 -> destination=(null destination) 
serial=410 path=/org/gnome/evolution/dataserver/SourceManager/Source_20; 
interface=org.gnome.evolution.dataserver.Source; member=Authenticate
 array [
string "password:myrealpassword"
string "ssl-trust:"
string "username:real@email"
 ]

  -
  This is huge security flaw. The malicious script can parse `dbus-monitor` 
output...
  Not sure about more recent Ubuntu and Evolution versions.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: evolution-data-server-common 3.18.5-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May  8 01:40:27 2019
  InstallationDate: Installed on 2018-01-04 (488 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: evolution-data-server
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1828124/+subscriptions

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

[Desktop-packages] [Bug 1786344] Re: Default IBus input method ignored in live session

** Description changed:

+ [Impact]
+
+ If you
+
+ * start your computer with a bootable USB stick or DVD with the
+ 18.04.2 desktop ISO
+
+ * wait until Ubiquity's welcome screen shows up (only possible on
+ systems with legacy BIOS; bug #1766047)
+
+ * select a language which requires an input method for typing
+
+ * click the "Try Ubuntu" button
+
+ no IBus method is made easily available via the input source indicator
+ in the session you enter. If you for instance select zh_CN as language
+ and "Try Ubuntu", you would expect to enter a session with the
+ "Intelligent Pinyin" method included among the available input sources.
+
+ The proposed fix should ensure that an IBus method is always available
+ in "live sessions" in languages which are prepared for it.
+
+ [Test Case]
+
+ 1. Install ibus-libpinyin and make sure that "Intelligent Pinyin" is
+not included among your available input sources.
+
+ 2. Generate the Chinese locale:
+
+sudo locale-gen zh_CN.UTF-8
+
+ 3. Add to ~/.profile this line:
+
+export LC_CTYPE=zh_CN.UTF-8
+
+ 4. Remove the gnome-settings-daemon stamp file:
+
+rm ~/.local/share/gnome-settings-daemon/input-sources-converted
+
+ 5. Log out and log in again.
+
+ => Find that the "Intelligent Pinyin" method was not added (since the
+ sources already in the list prevented it from being added).
+
+ 6. Install gnome-settings-daemon from bionic-proposed.
+
+ 7. Repeat step 4 and 5.
+
+ => Find that the "Intelligent Pinyin" method was added.
+
+ [Regression Potential]
+
+ The proposed upload includes a small change which specifically addresses
+ the issue as described above. I find that the risk for adverse side
+ effects is low.
+
+ [Original description]
+
Ubuntu 18.10 iso (2018.8.7), select Simplified Chinese for booting, can't
input Chinese character. From Settings -> Regions and Languages, selected
Intelligent Pinyin, also could not input Chinese.

---

18.10 镜像（2018.8.7）选择简体中文开机，无法输入中文。由 Settings -> Regions and Languages，选择
智能拼音，也无法输入中文。

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

Title:
Default IBus input method ignored in live session

Status in gnome-settings-daemon package in Ubuntu:
In Progress
Status in gnome-settings-daemon source package in Bionic:
Confirmed

Bug description:
[Impact]

If you

* start your computer with a bootable USB stick or DVD with the
18.04.2 desktop ISO

* wait until Ubiquity's welcome screen shows up (only possible on
systems with legacy BIOS; bug #1766047)

* select a language which requires an input method for typing

* click the "Try Ubuntu" button

no IBus method is made easily available via the input source indicator
in the session you enter. If you for instance select zh_CN as language
and "Try Ubuntu", you would expect to enter a session with the
"Intelligent Pinyin" method included among the available input
sources.

The proposed fix should ensure that an IBus method is always available
in "live sessions" in languages which are prepared for it.

[Test Case]

1. Install ibus-libpinyin and make sure that "Intelligent Pinyin" is
not included among your available input sources.

2. Generate the Chinese locale:

sudo locale-gen zh_CN.UTF-8

3. Add to ~/.profile this line:

export LC_CTYPE=zh_CN.UTF-8

4. Remove the gnome-settings-daemon stamp file:

rm ~/.local/share/gnome-settings-daemon/input-sources-converted

5. Log out and log in again.

=> Find that the "Intelligent Pinyin" method was not added (since the
sources already in the list prevented it from being added).

6. Install gnome-settings-daemon from bionic-proposed.

7. Repeat step 4 and 5.

=> Find that the "Intelligent Pinyin" method was added.

[Regression Potential]

The proposed upload includes a small change which specifically
addresses the issue as described above. I find that the risk for
adverse side effects is low.

[Original description]

Ubuntu 18.10 iso (2018.8.7), select Simplified Chinese for booting, can't
input Chinese character. From Settings -> Regions and Languages, selected
Intelligent Pinyin, also could not input Chinese.

---

18.10 镜像（2018.8.7）选择简体中文开机，无法输入中文。由 Settings -> Regions and
Languages，选择 智能拼音，也无法输入中文。

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

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

[Desktop-packages] [Bug 1731318] Re: NVIDIA systems will not suspend with lid close and no external monitors

@Michael, please keep advertisement for your OS out of launchpad

The right place to fix that bug would be to work with upstream on a
proper solution. The suggested change has been review by GNOME upstream
on https://bugzilla.gnome.org/show_bug.cgi?id=777538 and they found
issues with it.

Pop_OS team, any chance you would try to do the right thing there and
submit a pull request with your patch on gitlab?

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

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

Title:
  NVIDIA systems will not suspend with lid close and no external
  monitors

Status in gnome-desktop:
  Confirmed
Status in gnome-desktop3 package in Ubuntu:
  Confirmed

Bug description:
  With the NVIDIA driver, nvidia-384, the system will not sleep when the
  lid is closed due to gnome_rr_output_is_builtin_display incorrectly
  returning false. I have linked to an upstream bug, which also has
  patches fixing the issue.

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

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

[Desktop-packages] [Bug 1832374] Re: Media keys stop working due to missing service file

Thank you for your bug report, could you also send it upstream on
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues ?

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

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

Title:
  Media keys stop working due to missing service file

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

Bug description:
  Over the last two releases I've noticed that if you have an audio
  player such as Clementine running, pause the audio playback and watch
  a video via VLC or SMPlayer and then close the video player and try to
  use the media keys again, the following is logged to journald:

  gsd-media-keys[2607]: Error calling method
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.mpris.MediaPlayer2.smplayer was not provided by any .service
  files.

  From what I can see is that a service file is created for the media
  keys for SMPlayer, when SMPlayer is closed that service file is
  removed and then media keys are still bound to that service.

  I get the above output for previous track, stop, play, pause and next
  track media keys.

  I do get the following output if neither is SMPlayer or Clementine is
  running or if Clementine is running and playing audio and SMPlayer is
  open, but no video is loaded:

  org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing 
binding of keysym ffb5 with keysym ffb5 (keycode 54).
  org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing 
binding of keysym 31 with keysym 31 (keycode a-e,12,f,10,11) <-- I collapsed 
the range into a comma separated list

  If you re-open SMPlayer and load a video, the media keys work and the
  GDBus error doesn't occur but the above "Overwriting ..." messages
  still get logged. Closing SMPlayer again does not restore media keys
  so that Clementine can handle them. I had SMPlayer running ~17 hours
  ago.

  Doing a shell reload doesn't seem to fix this either.

  I can't really tell if this is an SMPlay/VLC/Video Player issue or
  actually an issue in GSD, so filing here until someone can reassign to
  the relevant project.

  I hit this a while ago, while trying to get some debugging information
  for a Clementine bug: https://github.com/clementine-
  player/Clementine/issues/6320

  If you need any other information let me know.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-settings-daemon 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jun 11 17:36:07 2019
  InstallationDate: Installed on 2019-02-01 (129 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20181202)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to disco on 2019-04-09 (63 days ago)

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

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

[Desktop-packages] [Bug 1786344] Re: Default IBus input method ignored in live session

** Merge proposal unlinked:
   
https://code.launchpad.net/~gunnarhj/ubuntu/+source/gnome-settings-daemon/+git/gnome-settings-daemon/+merge/368657

** Merge proposal unlinked:
   
https://code.launchpad.net/~gunnarhj/ubuntu/+source/gnome-settings-daemon/+git/gnome-settings-daemon/+merge/368409

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

Title:
  Default IBus input method ignored in live session

Status in gnome-settings-daemon package in Ubuntu:
  In Progress
Status in gnome-settings-daemon source package in Bionic:
  Confirmed

Bug description:
  Ubuntu 18.10 iso (2018.8.7), select Simplified Chinese for booting, can't
  input Chinese character. From Settings -> Regions and Languages, selected
  Intelligent Pinyin, also could not input Chinese.

  ---

  18.10 镜像（2018.8.7）选择简体中文开机，无法输入中文。由 Settings -> Regions and
  Languages，选择 智能拼音，也无法输入中文。

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

-- 
Mailing list: https://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 1731318] Re: NVIDIA systems will not suspend with lid close and no external monitors

2019-06-11 Thread Michael Aaron Murphy

Canonical still does not carry this or many other patches we've made for
Pop!_OS to improve NVIDIA support. If you want a better experience for
your hardware, I'd recommend to install Pop!_OS. We've been carrying the
patch you mentioned since 17.10, so it is enabled in both our 18.04 LTS
and 19.04 ISOs.

https://system76.com/pop

On Tue, Jun 11, 2019, at 1:39 PM, Stephan Fabel wrote:
> Can you confirm this patch made it into 19.04? I am running Disco and
> still seem to be suffering from it.
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1731318
> 
> Title:
>  NVIDIA systems will not suspend with lid close and no external
>  monitors
> 
> Status in gnome-desktop:
>  Confirmed
> Status in gnome-desktop3 package in Ubuntu:
>  Confirmed
> 
> Bug description:
>  With the NVIDIA driver, nvidia-384, the system will not sleep when the
>  lid is closed due to gnome_rr_output_is_builtin_display incorrectly
>  returning false. I have linked to an upstream bug, which also has
>  patches fixing the issue.
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-desktop/+bug/1731318/+subscriptions
>

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

Title:
  NVIDIA systems will not suspend with lid close and no external
  monitors

Status in gnome-desktop:
  Confirmed
Status in gnome-desktop3 package in Ubuntu:
  Confirmed

Bug description:
  With the NVIDIA driver, nvidia-384, the system will not sleep when the
  lid is closed due to gnome_rr_output_is_builtin_display incorrectly
  returning false. I have linked to an upstream bug, which also has
  patches fixing the issue.

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

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

[Desktop-packages] [Bug 1786344] Re: Default IBus input method ignored in live session

** Merge proposal linked:
   
https://code.launchpad.net/~gunnarhj/ubuntu/+source/gnome-settings-daemon/+git/gnome-settings-daemon/+merge/368678

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

Title:
  Default IBus input method ignored in live session

Status in gnome-settings-daemon package in Ubuntu:
  In Progress
Status in gnome-settings-daemon source package in Bionic:
  Confirmed

Bug description:
  Ubuntu 18.10 iso (2018.8.7), select Simplified Chinese for booting, can't
  input Chinese character. From Settings -> Regions and Languages, selected
  Intelligent Pinyin, also could not input Chinese.

  ---

  18.10 镜像（2018.8.7）选择简体中文开机，无法输入中文。由 Settings -> Regions and
  Languages，选择 智能拼音，也无法输入中文。

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

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

[Desktop-packages] [Bug 1141034] Re: RTL Spreadsheet Insert Cells

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

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

Title:
  RTL Spreadsheet Insert Cells

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  When using a right-to-left spreadsheet, right clicking and selected
  "insert cells" shows the normal LTR option to shift cells right,
  although when used it actually shifts cells left.

  I believe that shifting cells left is the correct behaviour in this
  case, but the text of the option should be changed to read "shift
  cells left". This was first noticed when using the Hebrew language
  user interface, but the problem is present when using English UI too.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice-calc 1:3.5.7-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37
  Uname: Linux 3.2.0-38-generic i686
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: i386
  CheckboxSubmission: ad9a15703e19217cb3448f881e125f6a
  CheckboxSystem: abc83e3988b72e7c3a9b3aa684cb92fd
  Date: Sun Mar  3 00:47:21 2013
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to precise on 2012-05-01 (305 days ago)

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

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

[Desktop-packages] [Bug 1257110] Re: RTL UI: Special numbers shown RTL even in cells that are formatted as LTR

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

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

Title:
  RTL UI: Special numbers shown RTL even in cells that are formatted as
  LTR

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  When using a RTL UI (e.g. Hebrew) even on English spreadsheets the
  numbers are shown in RTL direction even if the cells are set to be
  LTR.

  It's difficult to explain precisely what the problem is, but it causes
  weird quirks like for negative numbers, the - appears on the wrong
  side of the number (in LTR, it's normally before the number e.g. -127
  but with RTL UI, even in an LTR cell the number appears as 127-.

  The same problem appears in cells formatted to show date time, e.g.
  D/MM/ hh:nn.

  See the attached spreadsheet in LibreOffice when a RTL UI Language in
  use. I would expect cells A3 and B3 to appear as shown in the
  screenshot embedded into the sheet. (The screenshot was created by
  changing the UI language back to English)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libreoffice-calc 1:4.1.2~rc3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  CheckboxSubmission: ad9a15703e19217cb3448f881e125f6a
  CheckboxSystem: abc83e3988b72e7c3a9b3aa684cb92fd
  Date: Mon Dec  2 22:56:53 2013
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to saucy on 2013-11-19 (13 days ago)

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

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

[Desktop-packages] [Bug 1739897] Re: Background color of calc8 in Impress has unwanted offset

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

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

Title:
  Background color of calc8 in Impress has unwanted offset

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  1) XFCE desktop enviroment 4.12

  2)
  Version: 5.4.3.2
  Build ID: 1:5.4.3~rc2-0ubuntu0.17.04.1~lo1
  CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk3; 
  Locale: nl-BE (en_US.UTF-8); Calc: group

  3) The background color respects the border

  4)The background color of pasted calc8 has an offset from the boarder.
  I made it visible with an object behind. (Screenshot)

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

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

[Desktop-packages] [Bug 1772520] Re: Font metrics mixed up when selecting Arabic characters in Writer

** Also affects: df-libreoffice via
   https://bugs.documentfoundation.org/show_bug.cgi?id=119347
   Importance: Unknown
   Status: Unknown

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

Title:
  Font metrics mixed up when selecting Arabic characters in Writer

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  In most fonts, many characters in the Arabic script change their width
  and height as typing progresses. For example the letter ب (U+0628) is
  reduced to about a half or even a third of its width if it's followed
  by another character such as ا (U+0627): با. Usually LibreOffice
  understands the changes in font metrics pretty well but not always.

  See the attached screenshot where I've written the sentence "مرحبا يا
  صديقي العزيز" in Writer and started selecting letters from the
  beginning of the line. The selection shown in the screenshot looks
  like the whole first word plus the following space but actually it
  only covers the first 4 letters of the first word out of 5 total:
  مرحب. From a user's point of view, this is very confusing, as I can't
  tell how far I've already selected without counting the characters in
  my mind. Even more surprisingly, LibreOffice Calc shows the selection
  as expected, i.e. different from Writer, so this does not feel like a
  font problem per se, although only some fonts display this behavior.

  The font I'm using in this example is Scheherazade, available through
  a third-party repository at packages.sil.org. The font is designed to
  cover a very wide variety of characters used for Arabic-script
  minority languages in both Asia and Africa, and in many cases it's the
  only professionally made font available for people working on many of
  these languages.

  Description:  Ubuntu 17.10
  Release:  17.10

  libreoffice-writer:
Installed: 1:5.4.6-0ubuntu0.17.10.1
Candidate: 1:5.4.6-0ubuntu0.17.10.1
Version table:
   *** 1:5.4.6-0ubuntu0.17.10.1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.4.5-0ubuntu0.17.10.5 500
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
   1:5.4.1-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-writer 1:5.4.6-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 21 21:03:43 2018
  InstallationDate: Installed on 2017-02-13 (462 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-11-05 (197 days ago)

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

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

[Desktop-packages] [Bug 1820561] Re: color picker window is not movable

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

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

Title:
  color picker window is not movable

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  From the highlight color button on the toolbar, you Left click on
  custom color. That opens a window called "Pick a color". If you click
  on the top bar of the window, it won't let you drag the window to the
  side so you can see what colors you highlighted in your document.

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

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

[Desktop-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while

2019-06-11 Thread Filip Golab

Hey, Im not quite sure how I can reopen it, if you could tell me I would
do it for you. For me this issue had fixed randomly before I upgraded to
19.04 and was not pressent since then.

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

Title:
  [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails
  after a while

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Audio dies after few seconds, returns after few minutes and dies again

  filip@ux433:~$ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.20.14-042014-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filip  8566 F pulseaudio
   /dev/snd/pcmC0D0p:   filip  8566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  6 10:11:01 2019
  InstallationDate: Installed on 2019-01-05 (59 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 
comm="/usr/bin/pulseaudio --daemonize=no ")
  Symptom_Type: Sound works for a while, then breaks
  Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails 
after a while
  UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago)
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX433FN.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX433FN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX433FN_UX433FN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1731318] Re: NVIDIA systems will not suspend with lid close and no external monitors

2019-06-11 Thread Stephan Fabel

Can you confirm this patch made it into 19.04? I am running Disco and
still seem to be suffering from it.

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

Title:
  NVIDIA systems will not suspend with lid close and no external
  monitors

Status in gnome-desktop:
  Confirmed
Status in gnome-desktop3 package in Ubuntu:
  Confirmed

Bug description:
  With the NVIDIA driver, nvidia-384, the system will not sleep when the
  lid is closed due to gnome_rr_output_is_builtin_display incorrectly
  returning false. I have linked to an upstream bug, which also has
  patches fixing the issue.

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

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

[Desktop-packages] [Bug 1778361] Re: The Processes tab only displays the current user's processes

2019-06-11 Thread Ken VanDine

This was definitely fixed in revision 70.  The specific fix was actually
building it based on core18/bionic with a newer version of GTK.  This is
a new bug that I'll look into.

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

Title:
  The Processes tab only displays the current user's processes

Status in gnome-system-monitor package in Ubuntu:
  Fix Released

Bug description:
  ***
  *** Please attribute this bug to the correct package.
  ***

  ubuntu-bug -w failed.

  The "All Processes" option only displays the current user's processes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gedit 3.28.1-1ubuntu1
  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: Sat Jun 23 17:02:00 2018
  InstallationDate: Installed on 2018-05-03 (50 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1832004] Re: [amdgpu] display hanging after laptop opens lid

2019-06-11 Thread Jan Boomsma

Dear Daniel,

Here is the file you've request.
With regards,
Jan Boomsma.

On jun. 10 2019, at 3:57 am, Daniel van Vugt  
wrote:
> Please:
>
> 1. Reproduce the hang again.
> 2. Reboot and then immediately run:
> journalctl -b-1 > prevboot.txt
> and send us the file 'prevboot.txt'.
>
> ** Summary changed:
> - display hanging after laptop opens lid
> + [amdgpu] display hanging after laptop opens lid
>
> ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu)
> ** Tags added: amdgpu
> ** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1832004
>
> Title:
> [amdgpu] display hanging after laptop opens lid
>
> Status in xserver-xorg-video-amdgpu package in Ubuntu:
> Incomplete
>
> Bug description:
> ubuntu 19.04
>
> ProblemType: Bug
> DistroRelease: Ubuntu 19.04
> Package: xorg 1:7.7+19ubuntu12
> ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
> Uname: Linux 5.0.0-16-generic x86_64
> .tmp.unity_support_test.0:
>
> ApportVersion: 2.20.10-0ubuntu27
> Architecture: amd64
> BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
> CompositorRunning: None
> CurrentDesktop: ubuntu:GNOME
> Date: Fri Jun 7 14:56:09 2019
> DistUpgraded: Fresh install
> DistroCodename: disco
> DistroVariant: ubuntu
> DkmsStatus:
> anbox, 1, 5.0.0-15-generic, x86_64: installed
> anbox, 1, 5.0.0-16-generic, x86_64: installed
> virtualbox, 6.0.6, 5.0.0-15-generic, x86_64: installed
> virtualbox, 6.0.6, 5.0.0-16-generic, x86_64: installed
> ExtraDebuggingInterest: No
> GraphicsCard:
> Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
> [1002:98e4] (rev da) (prog-if 00 [VGA controller])
> Subsystem: ASUSTeK Computer Inc. Stoney [Radeon R2/R3/R4/R5 Graphics] 
> [1043:1680]
> InstallationDate: Installed on 2018-08-03 (308 days ago)
> InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
> MachineType: ASUSTeK COMPUTER INC. E402BA
> ProcEnviron:
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=
> LANG=nl_NL.UTF-8
> SHELL=/bin/bash
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
> root=UUID=c593d94b-7cc0-45ca-a012-f79a49d00093 ro quiet splash vt.handoff=1
> SourcePackage: xorg
> Symptom: display
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 09/06/2018
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: E402BA.311
> dmi.board.asset.tag: ATN12345678901234567
> dmi.board.name: E402BA
> dmi.board.vendor: ASUSTeK COMPUTER INC.
> dmi.board.version: 1.0
> dmi.chassis.asset.tag: No Asset Tag
> dmi.chassis.type: 10
> dmi.chassis.vendor: ASUSTeK COMPUTER INC.
> dmi.chassis.version: 1.0
> dmi.modalias: 
> dmi:bvnAmericanMegatrendsInc.:bvrE402BA.311:bd09/06/2018:svnASUSTeKCOMPUTERINC.:pnE402BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE402BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
> dmi.product.family: VivoBook
> dmi.product.name: E402BA
> dmi.product.version: 1.0
> dmi.sys.vendor: ASUSTeK COMPUTER INC.
> version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
> version.libdrm2: libdrm2 2.4.97-1ubuntu1
> version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
> version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
> version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
> version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
> version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
> version.xserver-xorg-video-intel: xserver-xorg-video-intel 
> 2:2.99.917+git20180925-2
> version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1832004/+subscriptions
>


** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/bugs/1832004/+attachment/5270193/+files/prevboot.txt

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

Title:
  [amdgpu] display hanging after laptop opens lid

Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 19.04

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  7 14:56:09 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   anbox, 1, 5.0.0-15-generic, x86_64: installed
   anbox, 1, 5.0.0-16-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-15-generic, x86_64: installed
   virtualbox, 6.0.6,

[Desktop-packages] [Bug 1825983] Re: chromium-browser ignores system proxy settings

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

** Changed in: chromium-browser (Ubuntu)
   Status: New => Confirmed

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

Title:
  chromium-browser ignores system proxy settings

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04.2
  chromium-browser 73.0.3683.86

  Network proxy is configured via Settings GUI dialog. chromium-browser
  is started with verbose output:

  [9810:9810:0423/134338.510775:VERBOSE1:proxy_config_service_linux.cc(484)] 
All gsettings tests OK. Will get proxy config from gsettings.
  [9810:9810:0423/134338.510926:VERBOSE1:proxy_config_service_linux.cc(1243)] 
Obtained proxy settings from annotation hash code 11258689
  
[9810:9810:0423/134338.510949:VERBOSE1:pref_proxy_config_tracker_impl.cc(184)] 
0x55e7b2944b00: set chrome proxy config service to 0x55e7b27e3f10

  Listing all gsettings with proxy:
  ~$ gsettings list-recursively | grep proxy
  will return:

  org.gnome.system.proxy.http host 'gse.auk.cvclab.lan'
  org.gnome.system.proxy.http port 9191
  org.gnome.system.proxy.http use-authentication false
  org.gnome.system.proxy.http authentication-password ''
  org.gnome.system.proxy.http authentication-user ''
  org.gnome.system.proxy.http enabled false
  org.gnome.evolution.shell.network-config proxy-type 0
  org.gnome.evolution.shell.network-config use-http-proxy false
  org.gnome.system.proxy.https host ''
  org.gnome.system.proxy.https port 0
  org.gnome.system.proxy.socks host ''
  org.gnome.system.proxy.socks port 0
  org.gnome.system.proxy.ftp host ''
  org.gnome.system.proxy.ftp port 0
  org.gnome.system.proxy use-same-proxy true
  org.gnome.system.proxy mode 'manual'
  org.gnome.system.proxy autoconfig-url ''
  org.gnome.system.proxy ignore-hosts ['localhost', '127.0.0.0/8', '::1']
  org.gnome.settings-daemon.plugins.screensaver-proxy active true
  org.gnome.settings-daemon.plugins.screensaver-proxy priority 0

  chromium-browsers fails to connect to the internet with the error
  message: ERR_CONNECTION_TIMED_OUT

  
  Starting chromium-browser with the proxy command line parameter:
  ~$ chromium-browser --proxy-server="gse.auk.cvclab.lan:9191"
  This starts the browser and the internet connection works fine.

  With Firefox there are no issues, it works with the configured system
  proxy settings.

  Regards

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

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

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

2019-06-11 Thread Bill Coleman

CONFIRMED: Same situation running 18.04.2 on VMWare 12.5.9. After
uncommenting the WaylandEnable=false line and rebooting, then I see the
login prompt as expected and I can then log in and use the system
normally again.

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

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.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 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1831988] Re: msgfmt produces invalid UTF-8 sequences for desktop files

I can reproduce the error in a xenial VM, not in a bionic one.

** Changed in: gettext (Ubuntu)
   Status: New => Fix Released

** Also affects: gettext (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

Title:
   msgfmt produces  invalid UTF-8 sequences for desktop files

Status in gettext package in Ubuntu:
  Fix Released
Status in gettext source package in Xenial:
  Confirmed

Bug description:
  VIM has recently added support for validating gnome desktop files and
  this is reporting  errors due to invalid UTF-8 sequences produced by
  msgfmt.

  Steps to reproduce:
  1. Checkout rev 1253704 from the VIM git repo on GitHub - 
https://github.com/vim/vim
  2. Run ./configure in the repo to set up the build environment.
  2. Change to the po directory in the repo - cd src/po
  3. Process and validate the gvim desktop file using the Makefile -

  $ make gvim.desktop
  msgfmt --desktop -d . --template gvim.desktop.in -o tmp_gvim.desktop
  rm -f LINGUAS
  if command -v desktop-file-validate; then desktop-file-validate 
tmp_gvim.desktop; fi
  /usr/bin/desktop-file-validate
  tmp_gvim.desktop: warning: file contains lines that are not UTF-8 encoded. 
There is no guarantee the validator will correctly work.
  [Invalid UTF-8] tmp_gvim.desktop: error: value 
"\xe0\xac\xaa\xe0\xac\xbe\xe0\xac\xa0\xe0\xad\x8d\xe0\xac\xaf 
\xe0\xac\xab\xe0\xac\xbe\xe0\xac\x87\xe0\xac\xb2\xe0\xac\x97\xe0\xad\x81\xe0\xac\xa1\xe0\xac\xbc\xe0\xac\xbf\xe0\xac\x95\xe0\xad\x81
 
\xe0\xac\xb8\xe0\xac\xae\xe0\xad\x8d\xe0\xac\xaa\xe0\xac\xbe\xe0\xac\xa6\xe0\xac\xa8
 \xe0\xac\x95\xe0\xac\xb0\xe0\xac\xa8\xe0\xad\x8d\xe0\xac\xa4\xe0\xad" for 
locale string key "Comment[or]" in group "Desktop Entry" contains invalid UTF-8 
characters, locale string values should be encoded in UTF-8
  Makefile:176: recipe for target 'gvim.desktop' failed
  make: *** [gvim.desktop] Error 1

  The template file has valid UTF-8 sequences so no errors are expected.
  The error is correct as the generated desktop file has a truncated 3
  byte UTF-8 sequence at the end of the line as reported.  The problem
  is msgfmt is emitting an invalid UTF-8 sequence for this one line.

  This is happening  on an up to date 16.04 LTS -

  $ apt list gettext desktop-file-utils
  Listing... Done
  desktop-file-utils/xenial-updates,now 0.22-1ubuntu5.2 i386 [installed]
  gettext/xenial-updates,xenial-security,now 0.19.7-2ubuntu3.1 i386 [installed]

  There has been some discussion of this issue on the VIM developers
  mailing list -
  https://groups.google.com/d/msg/vim_dev/yYGCsJJPlA0/i1PNO_46AgAJ

  A candidate patch for the issue from upstream for the gettext package has 
been identified -
  https://groups.google.com/d/msg/vim_dev/yYGCsJJPlA0/6yAEzO9LAgAJ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gettext 0.19.7-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-51-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  CurrentDesktop: Unity
  Date: Fri Jun  7 10:30:31 2019
  InstallationDate: Installed on 2019-02-05 (121 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release i386 (20180731)
  SourcePackage: gettext
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1832015] Re: firefox 67.0.1 lost my profile

Thanks for the confirmation. I'm updating the bug title accordingly. The
67.0.2 update that's currently being built should fix the issue.

** Summary changed:

- firefox 67.0.1 lost my profile
+ [upstream regression] Switching to Safe Mode with firefox 67.0.1 locks the 
profile

** Changed in: firefox (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  [upstream regression] Switching to Safe Mode with firefox 67.0.1 locks
  the profile

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  In Progress

Bug description:
  On bionic, Firefox was upgraded to 67.0.1 this morning (7 June).

  When I launch firefox I've a message like this

  "Using an older version of Firefox can corrupt bookmarks and browsing
  history already saved to an existing profile. To protect your
  information, create a new profile for this installation of Firefox."

  And I've just one option: Create a new profile.

  Of course, this new profile ignore all my bookmarks, identification,
  password, etc.

  I've tried:

  -1 Erase the new profile folder and the installs.ini file, rewrite the
  profiles.ini with the name of my old profile. Same problem.

  -2 run firefox -p into a terminal to choose my old profile. Same
  problem, rejected.

  It's strange the message box is saying "Using an older version of
  Firefox", why old ?

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

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

[Desktop-packages] [Bug 1832374] [NEW] Media keys stop working due to missing service file

2019-06-11 Thread Bruce Pieterse

Public bug reported:

Over the last two releases I've noticed that if you have an audio player
such as Clementine running, pause the audio playback and watch a video
via VLC or SMPlayer and then close the video player and try to use the
media keys again, the following is logged to journald:

gsd-media-keys[2607]: Error calling method
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.mpris.MediaPlayer2.smplayer was not provided by any .service files.

>From what I can see is that a service file is created for the media keys
for SMPlayer, when SMPlayer is closed that service file is removed and
then media keys are still bound to that service.

I get the above output for previous track, stop, play, pause and next
track media keys.

I do get the following output if neither is SMPlayer or Clementine is
running or if Clementine is running and playing audio and SMPlayer is
open, but no video is loaded:

org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing 
binding of keysym ffb5 with keysym ffb5 (keycode 54).
org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing 
binding of keysym 31 with keysym 31 (keycode a-e,12,f,10,11) <-- I collapsed 
the range into a comma separated list

If you re-open SMPlayer and load a video, the media keys work and the
GDBus error doesn't occur but the above "Overwriting ..." messages still
get logged. Closing SMPlayer again does not restore media keys so that
Clementine can handle them. I had SMPlayer running ~17 hours ago.

Doing a shell reload doesn't seem to fix this either.

I can't really tell if this is an SMPlay/VLC/Video Player issue or
actually an issue in GSD, so filing here until someone can reassign to
the relevant project.

I hit this a while ago, while trying to get some debugging information
for a Clementine bug: https://github.com/clementine-
player/Clementine/issues/6320

If you need any other information let me know.

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-settings-daemon 3.32.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
Uname: Linux 5.0.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Jun 11 17:36:07 2019
InstallationDate: Installed on 2019-02-01 (129 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20181202)
SourcePackage: gnome-settings-daemon
UpgradeStatus: Upgraded to disco on 2019-04-09 (63 days ago)

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


** Tags: amd64 apport-bug disco

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

Title:
  Media keys stop working due to missing service file

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

Bug description:
  Over the last two releases I've noticed that if you have an audio
  player such as Clementine running, pause the audio playback and watch
  a video via VLC or SMPlayer and then close the video player and try to
  use the media keys again, the following is logged to journald:

  gsd-media-keys[2607]: Error calling method
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.mpris.MediaPlayer2.smplayer was not provided by any .service
  files.

  From what I can see is that a service file is created for the media
  keys for SMPlayer, when SMPlayer is closed that service file is
  removed and then media keys are still bound to that service.

  I get the above output for previous track, stop, play, pause and next
  track media keys.

  I do get the following output if neither is SMPlayer or Clementine is
  running or if Clementine is running and playing audio and SMPlayer is
  open, but no video is loaded:

  org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing 
binding of keysym ffb5 with keysym ffb5 (keycode 54).
  org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing 
binding of keysym 31 with keysym 31 (keycode a-e,12,f,10,11) <-- I collapsed 
the range into a comma separated list

  If you re-open SMPlayer and load a video, the media keys work and the
  GDBus error doesn't occur but the above "Overwriting ..." messages
  still get logged. Closing SMPlayer again does not restore media keys
  so that Clementine can handle them. I had SMPlayer running ~17 hours
  ago.

  Doing a shell reload doesn't seem to fix this either.

  I can't really tell if this is an SMPlay/VLC/Video Player issue or
  actually an issue in GSD, so filing here until someone can reassign to
  the relevant project.

  I hit this a while ago, while trying to get some debugging information
  for a Clementine bug: https://github.com/clementine-
  player/Clementine/issues/6320

  If you need any other information let me know.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package:

[Desktop-packages] [Bug 1832015] Re: firefox 67.0.1 lost my profile

2019-06-11 Thread VinsS

Olivier, yes, possible at 90 %.

I switch regularly between safe-mode and mode with addons activated.

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

Title:
  firefox 67.0.1 lost my profile

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  On bionic, Firefox was upgraded to 67.0.1 this morning (7 June).

  When I launch firefox I've a message like this

  "Using an older version of Firefox can corrupt bookmarks and browsing
  history already saved to an existing profile. To protect your
  information, create a new profile for this installation of Firefox."

  And I've just one option: Create a new profile.

  Of course, this new profile ignore all my bookmarks, identification,
  password, etc.

  I've tried:

  -1 Erase the new profile folder and the installs.ini file, rewrite the
  profiles.ini with the name of my old profile. Same problem.

  -2 run firefox -p into a terminal to choose my old profile. Same
  problem, rejected.

  It's strange the message box is saying "Using an older version of
  Firefox", why old ?

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

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

[Desktop-packages] [Bug 1832369] [NEW] AUDIO WORK ONLY WITH AUDIO EXTERNAL. AUDIO DIDNT WORK ON INTERNAL SPEAKER

2019-06-11 Thread Alexandre

Public bug reported:

HI,

I have a thomson THN14B with audio card rt5651 and bluetooth

If i list a aplay -l to list all my sound card i get :

 Liste des Périphériques Matériels PLAYBACK 
carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 0: HdmiLpeAudio [Intel 
HDMI/DP LPE Audio]
  Sous-périphériques: 1/1
  Sous-périphérique #0: subdevice #0
carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 1: HdmiLpeAudio [Intel 
HDMI/DP LPE Audio]
  Sous-périphériques: 1/1
  Sous-périphérique #0: subdevice #0
carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 2: HdmiLpeAudio [Intel 
HDMI/DP LPE Audio]
  Sous-périphériques: 1/1
  Sous-périphérique #0: subdevice #0
carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 0: 3 []
  Sous-périphériques: 0/1
  Sous-périphérique #0: subdevice #0
carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 1: Deep-Buffer Audio (*) []
  Sous-périphériques: 1/1
  Sous-périphérique #0: subdevice #0


I thinks it's a bug with interaction to HDMI and RT5651 who broke my internal 
speaker sound.

Have a nice day

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: pulseaudio 1:12.2-0ubuntu5
ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20
Uname: Linux 4.18.0-21-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  sandra 1154 F pulseaudio
 /dev/snd/pcmC1D0c:   sandra 1154 F...m pulseaudio
 /dev/snd/pcmC1D0p:   sandra 1154 F...m pulseaudio
 /dev/snd/controlC0:  sandra 1154 F pulseaudio
CurrentDesktop: XFCE
Date: Tue Jun 11 17:21:59 2019
InstallationDate: Installed on 2019-06-11 (0 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to cosmic on 2019-06-11 (0 days ago)
dmi.bios.date: 01/02/2018
dmi.bios.version: HXFZ-14-BI-Y116CR600-CC34O-001-D
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Cherry Trail CR
dmi.board.vendor: AMI Corporation
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 10
dmi.chassis.version: To be filled by O.E.M.
dmi.modalias: 
dmi:bvn:bvrHXFZ-14-BI-Y116CR600-CC34O-001-D:bd01/02/2018:svnThomson:pnTHN14B:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnCherryTrailCR:rvrTobefilledbyO.E.M.:cvn:ct10:cvrTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: THN14B
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Thomson
modified.conffile..etc.pulse.daemon.conf: [modified]
mtime.conffile..etc.pulse.daemon.conf: 2019-06-11T15:27:04.110034

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


** Tags: amd64 apport-bug cosmic third-party-packages

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

Title:
  AUDIO WORK ONLY WITH AUDIO EXTERNAL. AUDIO DIDNT WORK ON INTERNAL
  SPEAKER

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  HI,

  I have a thomson THN14B with audio card rt5651 and bluetooth

  If i list a aplay -l to list all my sound card i get :

   Liste des Périphériques Matériels PLAYBACK 
  carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 0: HdmiLpeAudio [Intel 
HDMI/DP LPE Audio]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 1: HdmiLpeAudio [Intel 
HDMI/DP LPE Audio]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 0: Audio [Intel HDMI/DP LPE Audio], périphérique 2: HdmiLpeAudio [Intel 
HDMI/DP LPE Audio]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 0: 3 []
Sous-périphériques: 0/1
Sous-périphérique #0: subdevice #0
  carte 1: bytcrrt5651 [bytcr-rt5651], périphérique 1: Deep-Buffer Audio (*) []
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0

  
  I thinks it's a bug with interaction to HDMI and RT5651 who broke my internal 
speaker sound.

  Have a nice day

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sandra 1154 F pulseaudio
   /dev/snd/pcmC1D0c:   sandra 1154 F...m pulseaudio
   /dev/snd/pcmC1D0p:   sandra 1154 F...m pulseaudio
   /dev/snd/controlC0:  sandra 1154 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Jun 11 17:21:59 2019
  InstallationDate: Installed on 2019-06-11 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS

[Desktop-packages] [Bug 1786344] Re: Default IBus input method ignored in live session

Ok, noted Sebastien. I do plan to SRU it myself, so I re-added a bionic
task and assigned it to me.

** Also affects: gnome-settings-daemon (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: gnome-settings-daemon (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: gnome-settings-daemon (Ubuntu Bionic)
   Status: New => Confirmed

** Changed in: gnome-settings-daemon (Ubuntu Bionic)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  Default IBus input method ignored in live session

Status in gnome-settings-daemon package in Ubuntu:
  In Progress
Status in gnome-settings-daemon source package in Bionic:
  Confirmed

Bug description:
  Ubuntu 18.10 iso (2018.8.7), select Simplified Chinese for booting, can't
  input Chinese character. From Settings -> Regions and Languages, selected
  Intelligent Pinyin, also could not input Chinese.

  ---

  18.10 镜像（2018.8.7）选择简体中文开机，无法输入中文。由 Settings -> Regions and
  Languages，选择 智能拼音，也无法输入中文。

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

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

[Desktop-packages] [Bug 1832015] Re: firefox 67.0.1 lost my profile

Launchpad has imported 20 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1556612.

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

On 2019-06-04T03:56:49+00:00 Asif Youssuff wrote:

Created attachment 9069563
Screenshot from 2019-06-03 21-33-23.png

Steps to reproduce

1. Delete ~/.mozilla/firefox
2. Download build 20190603160429 (not sure it matters if it is after 67, but 
this is what I used). Add policies.json file to disable updates.
3. Start Firefox
4. Notice profile is "default-release"
5. Create new profile using about:profiles UI, call it "whatever"
6. Quit Firefox
7. Start Firefox
8. Notice profile in use is "whatever", not "default-release" This is Bug 
1556603
9. Quit Firefox
10. start Firefox with --safe-mode, start in safe mode
11. Quit Firefox
12. Launch Firefox

What happens:

Error message saying "You've launched an older version of Firefox"

Expected result:

No error message, Firefox launches into a profile.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1832015/comments/0

On 2019-06-04T16:02:06+00:00 Dtownsend wrote:

[Tracking Requested - why for this release]:

Users will be blocked from using their profile if they ever use safe-
mode.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1832015/comments/1

On 2019-06-04T20:40:59+00:00 Dtownsend wrote:

Ok, there are a few bugs that combine to cause this behaviour. I have
fixes for all of them and while I'm sure of being able to get them into
betas I'm less sure of getting them into the next release. So I'm going
to attach the simplest fix here that should be perfectly safe to uplift.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1832015/comments/2

On 2019-06-04T20:41:28+00:00 Dtownsend wrote:

Created attachment 9069765
Bug 1556612: Hardcode considering this an upgrade if the last build to run was 
run in safe mode. r=froydnj

When safe mode runs it writes out "Safe Mode" as the compatibility version (bug
1556831). Due to bug 1556832 and bug 1556829 this makes us think that the next
run is a downgrade.

This is the simplest possible fix that should be totally safe to upload to
release.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1832015/comments/3

On 2019-06-04T21:35:55+00:00 Lhenry wrote:

Pascal, I figure this should be in the next dot release; marking it as a
blocker.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1832015/comments/4

On 2019-06-05T15:14:23+00:00 Pascalc wrote:

Dave, does this bug only manifests with a policies.json file to block
updates? In that case that sounds like it would affect a tiny % of our
users and could be included in a future dot release but would not
trigger a 67.0.2 ASAP. If you think this is a widespread problem, should
we stop  updating users to 67.0.1? Thanks

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1832015/comments/5

On 2019-06-05T15:31:51+00:00 Dtownsend wrote:

(In reply to Pascal Chevrel:pascalc from comment #5)
> Dave, does this bug only manifests with a policies.json file to block 
> updates? In that case that sounds like it would affect a tiny % of our users 
> and could be included in a future dot release but would not trigger a 67.0.2 
> ASAP. If you think this is a widespread problem, should we stop  updating 
> users to 67.0.1? Thanks

This bug affects anyone who uses safe mode.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1832015/comments/6

On 2019-06-05T15:50:47+00:00 Pascalc wrote:

(In reply to Dave Townsend [:mossop] (he/him) from comment #6)
> (In reply to Pascal Chevrel:pascalc from comment #5)
> > Dave, does this bug only manifests with a policies.json file to block 
> > updates? In that case that sounds like it would affect a tiny % of our 
> > users and could be included in a future dot release but would not trigger a 
> > 67.0.2 ASAP. If you think this is a widespread problem, should we stop  
> > updating users to 67.0.1? Thanks
> 
> This bug affects anyone who uses safe mode.

well, I just launched 67.0.1 in safe mode and it works for me…

[EDIT] I can reproduce the bug on linux on the second start in safe mode

Reply at:

[Desktop-packages] [Bug 1786344] Re: Default IBus input method ignored in live session

** Merge proposal linked:
   
https://code.launchpad.net/~gunnarhj/ubuntu/+source/gnome-settings-daemon/+git/gnome-settings-daemon/+merge/368657

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

Title:
  Default IBus input method ignored in live session

Status in gnome-settings-daemon package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 18.10 iso (2018.8.7), select Simplified Chinese for booting, can't
  input Chinese character. From Settings -> Regions and Languages, selected
  Intelligent Pinyin, also could not input Chinese.

  ---

  18.10 镜像（2018.8.7）选择简体中文开机，无法输入中文。由 Settings -> Regions and
  Languages，选择 智能拼音，也无法输入中文。

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

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

[Desktop-packages] [Bug 1832360] [NEW] autopkgtests flaky on s390x

Public bug reported:

The "uno" autopkgtest has been failing quite a few times recently, and
this seems to have gotten worse on eoan (it happened on disco already).
See http://autopkgtest.ubuntu.com/packages/libr/libreoffice/eoan/s390x.

### float does not match! failed
struct comparison test failed
### float does not match! failed
recursive test results failed
standard test failed
exception occurred: error: test failed!

I'm attaching the relevant excerpt of the most recent failed test run.

** Affects: libreoffice (Ubuntu)
 Importance: Undecided
 Assignee: Marcus Tomlinson (marcustomlinson)
 Status: New

** Attachment added: "autopkgtest-s390x.log"
   
https://bugs.launchpad.net/bugs/1832360/+attachment/5270146/+files/autopkgtest-s390x.log

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

Title:
  autopkgtests flaky on s390x

Status in libreoffice package in Ubuntu:
  New

Bug description:
  The "uno" autopkgtest has been failing quite a few times recently, and
  this seems to have gotten worse on eoan (it happened on disco
  already). See
  http://autopkgtest.ubuntu.com/packages/libr/libreoffice/eoan/s390x.

  ### float does not match! failed
  struct comparison test failed
  ### float does not match! failed
  recursive test results failed
  standard test failed
  exception occurred: error: test failed!

  I'm attaching the relevant excerpt of the most recent failed test run.

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

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

[Desktop-packages] [Bug 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Sp

2019-06-11 Thread David Wolff

I posted too soon.  It turns out that in my case the error was a red-herring.  
I loaded a backed up VM without the latest Ubuntu updates and I am able to log 
in fine even though the syslog still contains the error:
CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling 
StartServiceByName for org.gnome.ScreenSaver: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.gnome.ScreenSaver exited with status 1

This clearly isn't the root cause of my missing login screen.

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

Title:
  CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error
  calling StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  That error is logged:

  org.gnome.ScreenSaver[1081]: Unable to init server: Could not connect:
  Connection refused

  then:

  gnome-session[895]: gnome-session-binary[895]: CRITICAL: Unable to
  create a DBus proxy for GnomeScreensaver: Error calling
  StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

  oem@ubuntu:~$ localectl
     System Locale: LANG=en_US.UTF-8
     VC Keymap: n/a
    X11 Layout: fr
     X11 Model: pc105
   X11 Variant: oss

  So, with googling help (https://bbs.archlinux.org/viewtopic.php?id=180103), 
i've edited /etc/locale-gen (as user) and uncommented the line: fr_FR.UTF-8
   and then ran 'sudo locale-gen' and finally rebooted.

  But the error is still logged after reboot: either i need to set also
  'VC Keymap', but how ?, or it is related to the vte version actually
  used (and need an upgrade)
  (https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1721412)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.26.1-0ubuntu7
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec  3 17:17:45 2017
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1786344] Re: Default IBus input method ignored in live session

@Gunnar, we discussed it in the meeting and decided it was not important
to rls track, that doesn't mean it can't be fixed/SRUed though (also in
the futur, please don't do direct nomination without assignement, either
you plan to fix it yourself and then you can assign the bug to you or
use rls-nn-incoming tagging)

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

Title:
  Default IBus input method ignored in live session

Status in gnome-settings-daemon package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 18.10 iso (2018.8.7), select Simplified Chinese for booting, can't
  input Chinese character. From Settings -> Regions and Languages, selected
  Intelligent Pinyin, also could not input Chinese.

  ---

  18.10 镜像（2018.8.7）选择简体中文开机，无法输入中文。由 Settings -> Regions and
  Languages，选择 智能拼音，也无法输入中文。

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

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

** Changed in: libreoffice (Ubuntu)
   Importance: Undecided => High

** Changed in: libreoffice (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: libreoffice (Ubuntu Cosmic)
   Importance: Undecided => High

** Changed in: libreoffice-l10n (Ubuntu)
   Importance: Undecided => High

** Changed in: libreoffice-l10n (Ubuntu Cosmic)
   Importance: Undecided => High

** Changed in: libreoffice-l10n (Ubuntu Bionic)
   Importance: Undecided => High

-- 
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-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Bionic:
  In Progress
Status in libreoffice-l10n source package in Bionic:
  In Progress
Status in libreoffice source package in Cosmic:
  Fix Committed
Status in libreoffice-l10n source package in Cosmic:
  Fix Committed

Bug description:
  [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 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]

[Desktop-packages] [Bug 1786344] Re: Default IBus input method ignored in live session

** No longer affects: gnome-settings-daemon (Ubuntu Bionic)

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

Title:
  Default IBus input method ignored in live session

Status in gnome-settings-daemon package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 18.10 iso (2018.8.7), select Simplified Chinese for booting, can't
  input Chinese character. From Settings -> Regions and Languages, selected
  Intelligent Pinyin, also could not input Chinese.

  ---

  18.10 镜像（2018.8.7）选择简体中文开机，无法输入中文。由 Settings -> Regions and
  Languages，选择 智能拼音，也无法输入中文。

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

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

** Tags removed: rls-ee-incoming
** Tags added: rls-ee-notfixing

-- 
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 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Sp

2019-06-11 Thread David Wolff

Same issue after an update this morning on Ubuntu 18.04.  Running Ubuntu
in a VMWare Workstation.  My login screen never appears after startup.

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

Title:
  CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error
  calling StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  That error is logged:

  org.gnome.ScreenSaver[1081]: Unable to init server: Could not connect:
  Connection refused

  then:

  gnome-session[895]: gnome-session-binary[895]: CRITICAL: Unable to
  create a DBus proxy for GnomeScreensaver: Error calling
  StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

  oem@ubuntu:~$ localectl
     System Locale: LANG=en_US.UTF-8
     VC Keymap: n/a
    X11 Layout: fr
     X11 Model: pc105
   X11 Variant: oss

  So, with googling help (https://bbs.archlinux.org/viewtopic.php?id=180103), 
i've edited /etc/locale-gen (as user) and uncommented the line: fr_FR.UTF-8
   and then ran 'sudo locale-gen' and finally rebooted.

  But the error is still logged after reboot: either i need to set also
  'VC Keymap', but how ?, or it is related to the vte version actually
  used (and need an upgrade)
  (https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1721412)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.26.1-0ubuntu7
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec  3 17:17:45 2017
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1824855] Re: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..."

2019-06-11 Thread Brian Murray

On Tue, Jun 11, 2019 at 02:07:14AM -, Daniel van Vugt wrote:
> What model machine are you seeing this bug on?

A Lenovo T450s, while it has a fingerprint reader I've no interest in
using it.

--
Brian Murray

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

Title:
  Unlocking the screen takes a long time after "Starting Fingerprint
  Authentication Daemon..."

Status in fprintd package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  When waking my laptop screen up at the lock screen, it takes a very
  long time to display the password prompt (definitely longer than 30s,
  possibly longer than 1m - I didn't time it).  I notice that while
  waiting for the password prompt, the screen is showing a full list of
  (obfuscated) desktop notifications.  After logging in, I used the
  gnome-shell interface to clear the notifications; then I locked my
  screen again, at which point hitting the space bar caused the password
  prompt to show up immediately.

  So it looks like the time to display the password prompt might scale
  linearly with the number of notifications; which is not useful,
  because there is a finite number of (obfuscated!) notifications that
  will be displayed on the lock screen, and AFAIK you can't interact
  with them through the lock screen at all.  So we shouldn't be wasting
  time processing (and presumably rendering) notifications that will
  never be visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 09:58:23 2019
  InstallationDate: Installed on 2010-09-24 (3125 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago)

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

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

[Desktop-packages] [Bug 1832015] Re: firefox 67.0.1 lost my profile

Thanks for the confirmation Paul, I can reliably reproduce the issue,
and this is upstream bug
https://bugzilla.mozilla.org/show_bug.cgi?id=1556612, which is fixed in
the upcoming 67.0.2.

@VinsS: could it be that what originally triggered the bug for you was
entering Safe Mode?

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

** Also affects: firefox via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1556612
   Importance: Unknown
   Status: Unknown

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

Title:
  firefox 67.0.1 lost my profile

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

Bug description:
  On bionic, Firefox was upgraded to 67.0.1 this morning (7 June).

  When I launch firefox I've a message like this

  "Using an older version of Firefox can corrupt bookmarks and browsing
  history already saved to an existing profile. To protect your
  information, create a new profile for this installation of Firefox."

  And I've just one option: Create a new profile.

  Of course, this new profile ignore all my bookmarks, identification,
  password, etc.

  I've tried:

  -1 Erase the new profile folder and the installs.ini file, rewrite the
  profiles.ini with the name of my old profile. Same problem.

  -2 run firefox -p into a terminal to choose my old profile. Same
  problem, rejected.

  It's strange the message box is saying "Using an older version of
  Firefox", why old ?

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

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

[Desktop-packages] [Bug 1828124] Re: org.gnome.evolution.dataserver.Source completely unveils account credentials in plain text while using dbus-monitor

** Changed in: evolution-data-server
   Status: New => Fix Released

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

Title:
  org.gnome.evolution.dataserver.Source completely unveils account
  credentials in plain text while using dbus-monitor

Status in evolution-data-server:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 16.04 LTS
  2. Install Evolution
  3. Set-up Google account with default settings (this will end with e-mail and 
calendar)
  4. Reboot
  5. Open evolution Calendar and/or indicator-datetime
  6. Launch `dbus-monitor`

  Expected results:
  * Evolution does not show account credentials in plain text in `dbus-monitor` 
output

  Actual results:
  * Evolution shows account credentials in plain text in `dbus-monitor` output:

  
  method call time=1557268474.383095 sender=:1.74 -> destination=:1.40 
serial=939 path=/org/gnome/evolution/dataserver/SourceManager/Source_17; 
interface=org.gnome.evolution.dataserver.Source; member=InvokeAuthenticate
 array [
string "password:myrealpassword"
string "ssl-trust:"
 ]
  method return time=1557268474.383686 sender=:1.40 -> destination=:1.74 
serial=366 reply_serial=939
  signal time=1557268474.389206 sender=:1.40 -> destination=(null destination) 
serial=367 path=/org/gnome/evolution/dataserver/SourceManager/Source_17; 
interface=org.gnome.evolution.dataserver.Source; member=Authenticate
 array [
string "password:myrealpassword"
string "ssl-trust:"
 ]

  signal time=1557268520.956861 sender=:1.40 -> destination=(null destination) 
serial=408 path=/org/gnome/evolution/dataserver/SourceManager/Source_19; 
interface=org.gnome.evolution.dataserver.Source; member=Authenticate
 array [
string "password:myrealpassword"
string "ssl-trust:"
string "username:real@email"
 ]
  signal time=1557268520.960443 sender=:1.40 -> destination=(null destination) 
serial=409 path=/org/gnome/evolution/dataserver/SourceManager/Source_18; 
interface=org.gnome.evolution.dataserver.Source; member=Authenticate
 array [
string "password:myrealpassword"
string "ssl-trust:"
string "username:real@email"
 ]
  signal time=1557268520.964374 sender=:1.40 -> destination=(null destination) 
serial=410 path=/org/gnome/evolution/dataserver/SourceManager/Source_20; 
interface=org.gnome.evolution.dataserver.Source; member=Authenticate
 array [
string "password:myrealpassword"
string "ssl-trust:"
string "username:real@email"
 ]

  -
  This is huge security flaw. The malicious script can parse `dbus-monitor` 
output...
  Not sure about more recent Ubuntu and Evolution versions.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: evolution-data-server-common 3.18.5-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May  8 01:40:27 2019
  InstallationDate: Installed on 2018-01-04 (488 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: evolution-data-server
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1828124/+subscriptions

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

[Desktop-packages] [Bug 421660] Re: gksu's and gksudo's modal password prompt prevents OnBoard's virtual keyboard input, causing accessibility issues

2019-06-11 Thread TJ

Had a user in IRC #ubuntu today re-rporting this for 18.04 when trying
to use Onboard. The user was asked to create a new bug report for their
issue but may not do so.

Adding this link which may be useful for other users caught by this:

https://stackoverflow.com/questions/33065735/replacing-gnomes-virtual-
keyboard-with-onboard-hide-show-via-dbus-doesnt-wor

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

Title:
  gksu's and gksudo's modal password prompt prevents OnBoard's virtual
  keyboard input, causing accessibility issues

Status in ubuntu-nexus7:
  Fix Released
Status in gksu package in Ubuntu:
  Confirmed
Status in ubuntu-defaults-nexus7 package in Ubuntu:
  Invalid
Status in xdiagnose package in Ubuntu:
  Fix Released
Status in gksu source package in Raring:
  Won't Fix
Status in ubuntu-defaults-nexus7 source package in Raring:
  Invalid
Status in xdiagnose source package in Raring:
  Fix Released

Bug description:
  I'm loath to report this as a bug, since it is functioning as
  designed, but I can't really find a better place to submit my
  complaint. I'm running 9.04 Netbook Remix, and if I run a GUI
  application and do something requiring sudo privileges, I receive a
  password prompt that blocks access to any other windows on the screen.
  Fine and good, but because of a disability, my only means of keyboard
  input is the OnBoard on-screen keyboard. My only recourse for such
  basic tasks as installing updates and adding packages is to pull out
  the terminal, hope I can find the pertinent command, and sudo it so I
  can give my password via terminal. This rather negates the convenience
  of doing these things from the GUI.

  Naturally, the expected behavior is that I be able to use OnBoard to
  enter my password into the prompt.

  Any other user who uses an on-screen keyboard or other GUI-based
  application for keyboard input will be susceptible to this issue. I
  imagine there are a fair number.

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

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

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

2019-06-11 Thread Michael Terry

To add on to Aaron's comment, if you are coming here because you hit
this bug while using deja-dup, you can install a version of deja-dup
that bundles in duplicity 0.8.0, which has the fix:

snap install deja-dup --classic --candidate

-- 
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 1832337] [NEW] Require password when starting usb-creator

2019-06-11 Thread Mike Salvatore

Public bug reported:

Because usb-creator performs privileged actions, it should require
authentication prior to starting. policykit-desktop-privileges should be
modified so that usb-creator requires password authentication prior to
starting.

While it was a deliberate design decision to allow usb-creator to
perform mounting and writing without authentication (see
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-
privileges/+bug/1568149), this decision should be revisited. Allowing
the use of usb-creator without authentication presents an unnecessary
security risk.

** Affects: policykit-desktop-privileges (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu Security Team (ubuntu-security)
 Status: New

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

Title:
  Require password when starting usb-creator

Status in policykit-desktop-privileges package in Ubuntu:
  New

Bug description:
  Because usb-creator performs privileged actions, it should require
  authentication prior to starting. policykit-desktop-privileges should
  be modified so that usb-creator requires password authentication prior
  to starting.

  While it was a deliberate design decision to allow usb-creator to
  perform mounting and writing without authentication (see
  https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-
  privileges/+bug/1568149), this decision should be revisited. Allowing
  the use of usb-creator without authentication presents an unnecessary
  security risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1832337/+subscriptions

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

[Desktop-packages] [Bug 1806860] Re: Pulseaudio module-jack-source unable to connect to jackd2

The reported commented upstream 'Does not seem to occur with ubuntu
19.04 any longer.', closing the bug

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

** Changed in: jackd2 (Ubuntu)
   Status: New => Fix Released

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

Title:
  Pulseaudio module-jack-source unable to connect to jackd2

Status in jackd2 package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/604

  ---

  When installing jackd2 in ubuntu 18.04, i am unable to load the
  module-jack-source.

  Syslog gives me:

  Dec  5 11:49:45 nvidion pulseaudio[7905]: JACK error >attempt to connect to 
server failed<
  Dec  5 11:49:45 nvidion pulseaudio[7905]: jack_client_open() failed.
  Dec  5 11:49:45 nvidion pulseaudio[7905]: Failed to load module 
"module-jack-source" (argument: ""): initialization failed.
  Dec  5 11:49:45 nvidion pulseaudio[7905]: JACK error >connect(2) call to 
/dev/shm/jack-1000/default/jack_0 failed (err=Datei oder Verzeichnis nicht 
gefunden)<
  Dec  5 11:49:50 nvidion pulseaudio[7905]: message repeated 5 times: [ JACK 
error >connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=Datei 
oder Verzeichnis nicht gefunden)<]
  Dec  5 11:49:51 nvidio

  So the path to the shared memory location is not as expected.

  When jackd2 is running i have:

  hcw@nvidion:$ cd /dev/shm/
  hcw@nvidion:/dev/shm$ ls
  jack-1000-0  jack_sem.1000_default_1000_0_system  
jack_sem.1000_default_jack_rack  jack_sem.1000_jack_default_1000_0_system
  jack-1000-1  jack_sem.1000_default_freewheel  
jack_sem.1000_default_qjackctl   jack-shm-registry
  jack_default_1000_0  jack_sem.1000_default_jack_mixer 
jack_sem.1000_default_system

  So it seems module-jack-source / sink are guessing the wrong shared
  memory paths to the jackd2 server..

  Versions:
  jackd2 1.9.12~dfsg-2
  pulseaudio-module-jack 1:11.1-1ubuntu7.1
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-lowlatency 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-39-lowlatency x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-16 (111 days ago)
  UserGroups: adm audio dialout disk docker kvm libvirt mythtv tracing video 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 12/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 042NDD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd12/05/2017:svnDellInc.:pnInspiron7566:pvr:rvnDellInc.:rn042NDD:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7566
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2018-12-04T10:32:39.961952
  mtime.conffile..etc.pulse.default.pa: 2018-12-03T11:18:37.948772

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

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

[Desktop-packages] [Bug 1832015] Re: firefox 67.0.1 lost my profile

2019-06-11 Thread Paul White

Olivier, it seems that the LastVersion line of compatibility.ini is the
problem.

I changed 'SafeMode' to '67.0.1_20190530055249/20190530055249' as per
VinsS's comment and Firefox started normally.

I then restarted Firefox in safe mode and the problem returned.
Reverting LastVersion to '67.0.1_20190530055249/20190530055249' enabled
Firefox to start again normally.

I can't remember doing so but over last weekend I must have started
Firefox in safe mode which is why I didn't see the problem when I
restarted Firefox immediately after upgrading on Friday(?).

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

Title:
  firefox 67.0.1 lost my profile

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  On bionic, Firefox was upgraded to 67.0.1 this morning (7 June).

  When I launch firefox I've a message like this

  "Using an older version of Firefox can corrupt bookmarks and browsing
  history already saved to an existing profile. To protect your
  information, create a new profile for this installation of Firefox."

  And I've just one option: Create a new profile.

  Of course, this new profile ignore all my bookmarks, identification,
  password, etc.

  I've tried:

  -1 Erase the new profile folder and the installs.ini file, rewrite the
  profiles.ini with the name of my old profile. Same problem.

  -2 run firefox -p into a terminal to choose my old profile. Same
  problem, rejected.

  It's strange the message box is saying "Using an older version of
  Firefox", why old ?

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

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

[Desktop-packages] [Bug 1832038] Re: nautilus do not anymore start

Thank you for your bug report report. Could you add your "journalctl -b
0 "log to the bug after getting the issue?

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

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

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

Title:
  nautilus do not anymore start

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Since restart Nautilus do not anymore start.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.32.1-0ubuntu0.19.04.0
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  7 20:32:41 2019
  InstallationDate: Installed on 2018-05-25 (378 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-05-21 (17 days ago)
  usr_lib_nautilus:

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

-- 
Mailing list: https://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 1832317] Re: A quick type in the Gnome 3 search sticks

2019-06-11 Thread Artyom Pozharov

Anyone doesn't notice this bug, that I had opened. Please check it. It's
critical error: https://bugs.launchpad.net/bugs/1831374

вт, 11 июн. 2019 г., 13:10 Bug Watch Updater
<1832...@bugs.launchpad.net>:

> ** Changed in: gnome-shell
>Status: Unknown => New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1832317
>
> Title:
>   A quick type in the Gnome 3 search sticks
>
> Status in GNOME Shell:
>   New
> Status in gnome-shell package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Details in my video: https://photos.app.goo.gl/h1eDdgkdJLDTDKH67
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.04
>   Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
>   ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
>   Uname: Linux 5.0.0-16-generic x86_64
>   ApportVersion: 2.20.10-0ubuntu27
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Jun 11 11:10:33 2019
>   DisplayManager: gdm3
>   GsettingsChanges:
>b'org.gnome.shell' b'app-picker-view' b'uint32 1'
>b'org.gnome.shell' b'command-history' redacted by apport
>b'org.gnome.desktop.interface' b'gtk-im-module'
> b"'gtk-im-context-simple'"
>   InstallationDate: Installed on 2019-06-06 (4 days ago)
>   InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
>   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/1832317/+subscriptions
>

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

Title:
  A quick type in the Gnome 3 search sticks

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

Bug description:
  Details in my video: https://photos.app.goo.gl/h1eDdgkdJLDTDKH67

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 11 11:10:33 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-06-06 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  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/1832317/+subscriptions

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

[Desktop-packages] [Bug 1832330] Re: gnome archive manager: "show the files" -> "Close and show the files"

Thank you for your bug report, that has been reported upstream before
but they didn't comment on it

** Changed in: file-roller (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: file-roller (Ubuntu)
   Status: New => Triaged

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

Title:
  gnome archive manager: "show the files" -> "Close and show the files"

Status in file-roller package in Ubuntu:
  Triaged

Bug description:
  this is about the application Archive manager (I do not like generic
  names btw. makes searching a pita) in gnome 3 as used by Ubuntu 18.04

  If I open an archive and extract the contents, I get a window with two
  options: close and show the files. I always want to press both buttons
  at the same time as I am finished with the archive and want to
  continue with the extracted files. there is no need to keep the
  archive manager window open.

  Hence my request for a change of the button "show the files" to a
  "close and show the files"

  uname -a: Linux compaq 4.15.0-51-generic #55-Ubuntu SMP Wed May 15
  14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  ubuntu 18.04.2 LTS, Gnome 3.28.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1832330/+subscriptions

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

[Desktop-packages] [Bug 1832015] Re: firefox 67.0.1 lost my profile

2019-06-11 Thread VinsS

Seems OK, I've upgrade and, at first launch, a dialog box let me choose the 
profile I want to use.
(I've just one profile) 

This is the content of the new compatibility.ini:
--
[Compatibility]
LastVersion=67.0.1_20190530055249/20190530055249
LastOSABI=Linux_x86_64-gcc3
LastPlatformDir=/usr/lib/firefox
LastAppDir=/usr/lib/firefox/browser
-

apt policy firefox
firefox:
  Installé : 67.0.1+build1-0ubuntu0.18.04.1
  Candidat : 67.0.1+build1-0ubuntu0.18.04.1
 Table de version :
 *** 67.0.1+build1-0ubuntu0.18.04.1 500
500 http://be.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
100 /var/lib/dpkg/status
 59.0.2+build1-0ubuntu1 500
500 http://be.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

Title:
  firefox 67.0.1 lost my profile

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  On bionic, Firefox was upgraded to 67.0.1 this morning (7 June).

  When I launch firefox I've a message like this

  "Using an older version of Firefox can corrupt bookmarks and browsing
  history already saved to an existing profile. To protect your
  information, create a new profile for this installation of Firefox."

  And I've just one option: Create a new profile.

  Of course, this new profile ignore all my bookmarks, identification,
  password, etc.

  I've tried:

  -1 Erase the new profile folder and the installs.ini file, rewrite the
  profiles.ini with the name of my old profile. Same problem.

  -2 run firefox -p into a terminal to choose my old profile. Same
  problem, rejected.

  It's strange the message box is saying "Using an older version of
  Firefox", why old ?

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

-- 
Mailing list: https://launchpad.net/~desktop-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] Re: [nvidia] gnome-shell eats 100% cpu when seconds display is on and screen is locked

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

-- 
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:
  Fix Released
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 1832015] Re: firefox 67.0.1 lost my profile

2019-06-11 Thread VinsS

Olivier, no I maintain the previous version, waiting the confirmation of
the bug is fixed.

I do the upgrade now.

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

Title:
  firefox 67.0.1 lost my profile

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  On bionic, Firefox was upgraded to 67.0.1 this morning (7 June).

  When I launch firefox I've a message like this

  "Using an older version of Firefox can corrupt bookmarks and browsing
  history already saved to an existing profile. To protect your
  information, create a new profile for this installation of Firefox."

  And I've just one option: Create a new profile.

  Of course, this new profile ignore all my bookmarks, identification,
  password, etc.

  I've tried:

  -1 Erase the new profile folder and the installs.ini file, rewrite the
  profiles.ini with the name of my old profile. Same problem.

  -2 run firefox -p into a terminal to choose my old profile. Same
  problem, rejected.

  It's strange the message box is saying "Using an older version of
  Firefox", why old ?

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

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

[Desktop-packages] [Bug 1832015] Re: firefox 67.0.1 lost my profile

2019-06-11 Thread Paul White

Olivier, yes this still an issue on my Ubuntu 18.04 laptop. My Xubuntu
18.04 laptop worked as expected after the upgrade.

As requested:

apt policy firefox
firefox:
  Installed: 67.0.1+build1-0ubuntu0.18.04.1
  Candidate: 67.0.1+build1-0ubuntu0.18.04.1
  Version table:
 *** 67.0.1+build1-0ubuntu0.18.04.1 500
500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
500 http://gb.archive.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
100 /var/lib/dpkg/status
 59.0.2+build1-0ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

paul@N1642:~$ grep firefox /var/log/apt/history.log
Upgrade: gir1.2-geocodeglib-1.0:amd64 (3.25.4.1-4, 3.25.4.1-4ubuntu0.18.04.1), 
gir1.2-mutter-2:amd64 (3.28.3+git20190124-0ubuntu18.04.2, 
3.28.4-0ubuntu18.04.1), libapt-inst2.0:amd64 (1.6.10, 1.6.11), libegl1:amd64 
(1.0.0-2ubuntu2.2, 1.0.0-2ubuntu2.3), update-notifier-common:amd64 (3.192.1.5, 
3.192.1.7), apt:amd64 (1.6.10, 1.6.11), libgl1:amd64 (1.0.0-2ubuntu2.2, 
1.0.0-2ubuntu2.3), libmutter-2-0:amd64 (3.28.3+git20190124-0ubuntu18.04.2, 
3.28.4-0ubuntu18.04.1), libgles2:amd64 (1.0.0-2ubuntu2.2, 1.0.0-2ubuntu2.3), 
libapt-pkg5.0:amd64 (1.6.10, 1.6.11), mutter-common:amd64 
(3.28.3+git20190124-0ubuntu18.04.2, 3.28.4-0ubuntu18.04.1), 
libgeocode-glib0:amd64 (3.25.4.1-4, 3.25.4.1-4ubuntu0.18.04.1), 
firefox-locale-en:amd64 (67.0+build2-0ubuntu0.18.04.1, 
67.0.1+build1-0ubuntu0.18.04.1), gnome-shell-common:amd64 
(3.28.3+git20190124-0ubuntu18.04.2, 3.28.4-0ubuntu18.04.1), libglx0:amd64 
(1.0.0-2ubuntu2.2, 1.0.0-2ubuntu2.3), apt-utils:amd64 (1.6.10, 1.6.11), 
epiphany-browser:amd64 (3.28.1-1ubuntu1, 3.28.5-0ubuntu1), firefox:amd64 
(67.0+build2-0ubuntu0.18.04.1, 67.0.1+build1-0ubuntu0.18.04.1), 
gnome-shell:amd64 (3.28.3+git20190124-0ubuntu18.04.2, 3.28.4-0ubuntu18.04.1), 
apt-transport-https:amd64 (1.6.10, 1.6.11), epiphany-browser-data:amd64 
(3.28.1-1ubuntu1, 3.28.5-0ubuntu1), update-notifier:amd64 (3.192.1.5, 
3.192.1.7), mutter:amd64 (3.28.3+git20190124-0ubuntu18.04.2, 
3.28.4-0ubuntu18.04.1), libglvnd0:amd64 (1.0.0-2ubuntu2.2, 1.0.0-2ubuntu2.3)

paul@N1642:~$ grep -H LastVersion ~/.mozilla/firefox/*/compatibility.ini
/home/paul/.mozilla/firefox/xwgyic9w.default/compatibility.ini:LastVersion=Safe 
Mode

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

Title:
  firefox 67.0.1 lost my profile

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  On bionic, Firefox was upgraded to 67.0.1 this morning (7 June).

  When I launch firefox I've a message like this

  "Using an older version of Firefox can corrupt bookmarks and browsing
  history already saved to an existing profile. To protect your
  information, create a new profile for this installation of Firefox."

  And I've just one option: Create a new profile.

  Of course, this new profile ignore all my bookmarks, identification,
  password, etc.

  I've tried:

  -1 Erase the new profile folder and the installs.ini file, rewrite the
  profiles.ini with the name of my old profile. Same problem.

  -2 run firefox -p into a terminal to choose my old profile. Same
  problem, rejected.

  It's strange the message box is saying "Using an older version of
  Firefox", why old ?

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

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

[Desktop-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while

2019-06-11 Thread Gabriele Ara

I can confirm that the same problem affects 19.04 too.

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

Title:
  [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails
  after a while

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Audio dies after few seconds, returns after few minutes and dies again

  filip@ux433:~$ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.20.14-042014-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filip  8566 F pulseaudio
   /dev/snd/pcmC0D0p:   filip  8566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  6 10:11:01 2019
  InstallationDate: Installed on 2019-01-05 (59 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 
comm="/usr/bin/pulseaudio --daemonize=no ")
  Symptom_Type: Sound works for a while, then breaks
  Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails 
after a while
  UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago)
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX433FN.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX433FN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX433FN_UX433FN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while

2019-06-11 Thread Gabriele Ara

Hey there, same problem here, audio has strange glitches, maybe we could
reopen this issue? Both a collegue and I bought this same laptop and we
are both affected by this issue, even on recent kernel builds.

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

Title:
  [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails
  after a while

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Audio dies after few seconds, returns after few minutes and dies again

  filip@ux433:~$ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.20.14-042014-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filip  8566 F pulseaudio
   /dev/snd/pcmC0D0p:   filip  8566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  6 10:11:01 2019
  InstallationDate: Installed on 2019-01-05 (59 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 
comm="/usr/bin/pulseaudio --daemonize=no ")
  Symptom_Type: Sound works for a while, then breaks
  Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails 
after a while
  UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago)
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX433FN.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX433FN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX433FN_UX433FN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1832330] [NEW] gnome archive manager: "show the files" -> "Close and show the files"

2019-06-11 Thread simon

Public bug reported:

this is about the application Archive manager (I do not like generic
names btw. makes searching a pita) in gnome 3 as used by Ubuntu 18.04

If I open an archive and extract the contents, I get a window with two
options: close and show the files. I always want to press both buttons
at the same time as I am finished with the archive and want to continue
with the extracted files. there is no need to keep the archive manager
window open.

Hence my request for a change of the button "show the files" to a "close
and show the files"

uname -a: Linux compaq 4.15.0-51-generic #55-Ubuntu SMP Wed May 15
14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

ubuntu 18.04.2 LTS, Gnome 3.28.2

** Affects: file-roller (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  gnome archive manager: "show the files" -> "Close and show the files"

Status in file-roller package in Ubuntu:
  New

Bug description:
  this is about the application Archive manager (I do not like generic
  names btw. makes searching a pita) in gnome 3 as used by Ubuntu 18.04

  If I open an archive and extract the contents, I get a window with two
  options: close and show the files. I always want to press both buttons
  at the same time as I am finished with the archive and want to
  continue with the extracted files. there is no need to keep the
  archive manager window open.

  Hence my request for a change of the button "show the files" to a
  "close and show the files"

  uname -a: Linux compaq 4.15.0-51-generic #55-Ubuntu SMP Wed May 15
  14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  ubuntu 18.04.2 LTS, Gnome 3.28.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1832330/+subscriptions

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

[Desktop-packages] [Bug 1797734] Re: slow calculator startup

2019-06-11 Thread Valentin Crone

Hello,
Try to remove the snap package:

snap remove gnome-calculator

And install the deb package:

apt-get install gnome-calculator


I have experimented this on Ubuntu 18.04 and 19.04 and it seem to be really 
faster.
I have experienced many speed problems with snap apps. And some was really 
laggy.

For example, with discord on snap, on one of my laptop: crashes, and mic 
problems.
For the other laptop: Really laggy, 5 to 10s between the time I type something, 
and the time it appear on the screen, on a laptop with 2 SSD.
I have the time to start firefox 3 times on the same period, and discord in 
firefox doesn't present any of theses problems.

After this, I remove the snap version, and install the official deb
version (from the discord website), and no problems. Fluid and not full
of bugs.

Same problem for Atom (atom.io), buggy and laggy with snap.
I don't understand why snap is slow like this for certain apps, and I don't 
understand exactly how snap works, but I suspect him to be the cause of many 
slow apps on recent versions of Ubuntu.

On my laptop, for gnome-calculator, the time to open:
- Snap: 2 to 10s
- Deb: 0.1 to 1s

I can't say it's definitely snap, but I suppose you can look at this.

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

Title:
  slow calculator startup

Status in gnome-calculator package in Ubuntu:
  Confirmed

Bug description:
  The calculator starts very slowly. It's a tiny program, but it runs
  like a very big one. In previous versions of Ubuntu, the launch was
  normal, very fast.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-calculator (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 08:40:06 2018
  InstallationDate: Installed on 2018-05-06 (160 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calculator
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1832094] Re: Error on login due to wrong permissions on /usr/lib/chromium-browser/extensions

"/usr/lib/chromium-browser/extensions" isn't created by any package, as
far as I can tell.

Does this directory contain anything on your system?

Does the following command reveal anything interesting?

dpkg -S /usr/lib/chromium-browser/extensions

** Changed in: chromium-browser (Ubuntu)
   Status: New => Incomplete

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

Title:
  Error on login due to wrong permissions on /usr/lib/chromium-
  browser/extensions

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  During X login, a grey box pops up with:
  find: ‘/usr/lib/chromium-browser/extensions’: Permission denied
  find: ‘/usr/lib/chromium-browser/extensions’: Permission denied
  (Repeated multiple time)
  Pressing the ok/continue button allows the login to continue without problems.

  The same messages are repeated on .xsession-errors:
  ~$ !grep
  grep chrome .xsession-errors
  find: ‘/usr/lib/chromium-browser/extensions’: Permission denied
  find: ‘/usr/lib/chromium-browser/extensions’: Permission denied
  find: ‘/usr/lib/chromium-browser/extensions’: Permission denied
  find: ‘/usr/lib/chromium-browser/extensions’: Permission denied
  find: ‘/usr/lib/chromium-browser/extensions’: Permission denied
  find: ‘/usr/lib/chromium-browser/extensions’: Permission denied
  find: ‘/usr/lib/chromium-browser/extensions’: Permission denied
  find: ‘/usr/lib/chromium-browser/extensions’: Permission denied
  find: ‘/usr/lib/chromium-browser/extensions’: Permission denied
  find: ‘/usr/lib/chromium-browser/extensions’: Permission denied

  /usr/lib/chromium-browser# ls -al
  drwx-- 1 root root 0 Dec  7  2017 extensions

  ~$ dpkg -l chromium-browser
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name VersionArchitecture Description
  
+++--==--===
  ii  chromium-browser 74.0.3729.169-0ubuntu0.19.04.1 amd64Chromium web 
br

  Not quite certain when this started, but:
  From /var/log/apt/history.log.1.gz 
  Start-Date: 2019-05-11  15:42:30
  Commandline: apt upgrade -y
  Upgrade: ... chromium-browser 73.0.3683.86-0ubuntu0.18.10.1,v73 ...

  Start-Date: 2019-05-30  06:54:44
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: chromium-chromedriver:amd64 (73.0.3683.103-0ubuntu1, 
74.0.3729.169-0ubuntu0.19.04.1)
  End-Date: 2019-05-30  06:54:48

  Probably just a packaging bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: chromium-browser 74.0.3729.169-0ubuntu0.19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: MATE
  DRM.card0-DVI-I-1:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBMLWoANzFPTSYMAQMPIhuM6m+LolpNlCQaUVa/74CBgGFARUAxQIGPYU9FTzFPMCoAmFEAKkAwcBMAUg4RAAAe/QA4Sx5RDgAKICAgICAg/ABTeW5jTWFzdGVyCiAg/wBINExUOTAxNDgzCiAgAC4=
   modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400
  Date: Sat Jun  8 15:58:14 2019
  Desktop-Session:
   'mate'
   '/etc/xdg/xdg-mate:/etc/xdg'
   
'/usr/share/mate:/usr/share/mate:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-02-28 (1196 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Load-Avg-1min: 2.36
  Load-Processes-Running-Percent:   0.3%
  MachineType: MEDIONPC MS-7502
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic 
root=UUID=f98d8628-faf4-4755-887c-9c5e197910ea ro rootflags=subvol=@ 
cgroup_enable=memory swapaccount=1 nopat
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to disco on 2019-05-11 (28 days ago)
  dmi.bios.date: 03/02/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-7502
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Fab D
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd03/02/2009:svnMEDIONPC:pnMS-7502:pvrOEM:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7502:rvrFabD:cvnOEM:ct3:cvrOEM:
  dmi.product.name: MS-7502
  dmi.product.version: OEM
  dmi.sys.vendor: MEDIONPC
  modified.conffile..etc.default.chromium-browser: [deleted]

To

[Desktop-packages] [Bug 1832015] Re: firefox 67.0.1 lost my profile

@VinsS: it looks like you manually worked around the issue, I assume
you're not seeing the problem any longer?

@Paul: if you can still observe the issue on 18.04, can you please share
the output of the following commands:

apt policy firefox

grep firefox /var/log/apt/history.log

grep -H LastVersion ~/.mozilla/firefox/*/compatibility.ini

** Changed in: firefox (Ubuntu)
   Importance: Undecided => High

** Changed in: firefox (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  firefox 67.0.1 lost my profile

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  On bionic, Firefox was upgraded to 67.0.1 this morning (7 June).

  When I launch firefox I've a message like this

  "Using an older version of Firefox can corrupt bookmarks and browsing
  history already saved to an existing profile. To protect your
  information, create a new profile for this installation of Firefox."

  And I've just one option: Create a new profile.

  Of course, this new profile ignore all my bookmarks, identification,
  password, etc.

  I've tried:

  -1 Erase the new profile folder and the installs.ini file, rewrite the
  profiles.ini with the name of my old profile. Same problem.

  -2 run firefox -p into a terminal to choose my old profile. Same
  problem, rejected.

  It's strange the message box is saying "Using an older version of
  Firefox", why old ?

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

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

[Desktop-packages] [Bug 1832317] Re: A quick type in the Gnome 3 search sticks

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  A quick type in the Gnome 3 search sticks

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

Bug description:
  Details in my video: https://photos.app.goo.gl/h1eDdgkdJLDTDKH67

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 11 11:10:33 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-06-06 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  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/1832317/+subscriptions

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

[Desktop-packages] [Bug 1615389] Re: Searching for files and folders in AO takes much longer than previously

This bug is nearly 3 years old. Can you say if you think GNOME 3.32 in
Ubuntu 19.04 performs adequately now?

** Changed in: ubuntu-gnome
   Status: New => Incomplete

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

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

** Tags added: performance

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

Title:
  Searching for files and folders in AO takes much longer than
  previously

Status in Ubuntu GNOME:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in tracker package in Ubuntu:
  Incomplete

Bug description:
  I have noticed that after upgrading from Ubuntu GNOME 15.10 to 16.04
  with GNOME 3.20 that searching for files and folders in the Activities
  Overview takes much much longer when previously (before upgrading) it
  would find them almost instantly as it currently does with
  applications.

  In the preferences for Tracker I have it set up so that it is meant to
  index content. What is interesting though is that for instance it
  might take 5 minutes to find my Artwork folder in my Documents
  directory through the AO. But if I run 'locate Artwork' in Terminal it
  finds it almost instantly.

  So that makes me think that perhaps it is an issue with it not
  properly indexing the content or not being able to retrieve the
  information or something and being forced to do a real-time search.

  But it is becoming rather annoying so I thought I would report it so
  that we can try to figure out what the issue is and hopefully find a
  solution.

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

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

[Desktop-packages] [Bug 1819207] Re: [FFe] Add Modaliases to open-vm-tools-desktop to allow automatic installation by ubuntu-drivers

2019-06-11 Thread Christian Ehrhardt 

While the main verification is on VMWare as usual this bug - since it is 
referenced in the changelog - is tracked as well.
And while right now there are no intentions to pick up the modalias with the 
other tools (e.g. installer) lets make sure this worked for the open-vm-tools 
portion on the backport.

I poked at ubunut-drivers a bit to check if things would work and got 
open-vm-tools-desktop: installed: 2:10.3.10-1~ubuntu0.18.04.1   available: 
2:10.3.10-1~ubuntu0.18.04.1 (auto-install)  [distro]  free
Not perfect, but ok - and given that we don't SRU the installer part that is ok.

For the context here the important part is if the modalias is there, and
that is true for both releases.

$ apt show open-vm-tools-desktop 2>/dev/null | grep Modalias
Modaliases: vmwgfx(pci:v15ADd0405sv*sd*bc*sc*i*)


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

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

Title:
  [FFe] Add Modaliases to open-vm-tools-desktop to allow automatic
  installation by ubuntu-drivers

Status in open-vm-tools package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in open-vm-tools source package in Bionic:
  Fix Committed
Status in ubiquity source package in Bionic:
  Won't Fix
Status in ubuntu-drivers-common source package in Bionic:
  Won't Fix
Status in open-vm-tools source package in Cosmic:
  Fix Committed
Status in ubiquity source package in Cosmic:
  Won't Fix
Status in ubuntu-drivers-common source package in Cosmic:
  Won't Fix
Status in open-vm-tools source package in Disco:
  Fix Released
Status in ubiquity source package in Disco:
  Fix Released
Status in ubuntu-drivers-common source package in Disco:
  Fix Released

Bug description:
  [Rationale]
  On Ubuntu Desktop, we want to install automatically at installation time 
open-vm-tools-desktop and its dependencies to provide an improved user 
experience on first boot after installation of the guest. This method also 
provides an easy way to install the drivers after installation if they have not 
been installed at installation time.

  It is achieved adding an XB-Modaliases field to the control file for
  the record 'open-vm-tools-desktop' so ubuntu-drivers can detect the
  packages to install when running in a VMware guest and adding open-vm-
  tools to the list of whitelisted packages in ubuntu-drivers

  [Impact]
  The change adds an additional field to the control file used by 
ubuntu-drivers to detect the drivers to install automatically. In the worst 
case scenario either the field is not added or the detection by ubuntu-drivers 
fails. In both cases the package o-v-t-desktop is not installed and can still 
be installed manually.

  Note: open-vm-tools-desktop is in universe and for the final feature
  (>=Disco) it must be in main (already promoted). But for the SRU
  context (as this was accepted by Debian in 10.3.5-8) in our regular
  MRE we only cover the open-vm-tools change to "provide" the modalias.
  We do not change the ubuntu-drivers or ubiquity to depend on it - so
  no need to promote it on the SRU.

  [Test Case]
  With the patched versions of ubuntu-drivers and open-vm-tools
  1. Boot a daily ISO of Ubuntu Desktop to the live session in a VMware Guest 
(with VMWare Workstation for example)
  2. Open a terminal, make sure the package cache is up to date with the 
version of o-v-t containing the Modaliases field
  3. Run the command:
     $ ubuntu-drivers list
     and verify that o-v-t-desktop is in the output
  4. Run the command:
     $ ubuntu-drivers devices
     And verify that the output shows the details of the sys entry for this 
device
  5. Run the command:
     $ sudo ubuntu-drivers install
     and verify that the package o-v-t-desktop is installed

  [Regression Potential]
  Very Low. Package may fail to build if for some reason dh-gencontrol fails. 
Otherwise, given that the package is not already installed automatically, if 
automated installation doesn't work then we're still in the same situation than 
today.
  On ubuntu-drivers side, the change just adds o-v-t-desktop to the whitelist 
using an existing mechanism so other than a typo there is no risk of regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: open-vm-tools-desktop (not installed)
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  8 20:02:49 2019
  InstallationDate: Installed on 2014-07-15 (1697 days ago)

[Desktop-packages] [Bug 1832317] Re: A quick type in the Gnome 3 search sticks

Yes, it is a bug. Thanks for reporting it.

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

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

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

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

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

Title:
  A quick type in the Gnome 3 search sticks

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

Bug description:
  Details in my video: https://photos.app.goo.gl/h1eDdgkdJLDTDKH67

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 11 11:10:33 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-06-06 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  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/1832317/+subscriptions

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

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

Seems like a bionic updates regression. Duplicate bug 1832320 confirms
the same date.

** Tags added: regression-update

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

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.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 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

If I had to guess then I would guess the most likely cause is the
changes I made in the latest update:

https://launchpad.net/ubuntu/+source/mutter/3.28.4-0ubuntu18.04.1

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

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.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 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://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 1832317] Re: A quick type in the Gnome 3 search sticks

2019-06-11 Thread Artyom Pozharov

I don't understand you in "and unsurprising if it's during an operation
that requires
gnome-shell to perform disk IO like searching". What does it mean? Do such
freezes look like norm? I believe it's a problem and we should solve it. I
want to add, that I will not see such problems if I print a random text in
the search line. Problem will appear only if I enter a part of name of
Ubuntu package, file or folder.

вт, 11 июн. 2019 г. в 12:00, Daniel van Vugt :

> In your video it looks like you are typing "ubuntu" and gnome-shell is
> too slow to display much of the typing. So this is a performance
> problem, and unsurprising if it's during an operation that requires
> gnome-shell to perform disk IO like searching.
>
>
> ** Tags added: performance
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1832317
>
> Title:
>   A quick type in the Gnome 3 search sticks
>
> Status in gnome-shell package in Ubuntu:
>   New
>
> Bug description:
>   Details in my video: https://photos.app.goo.gl/h1eDdgkdJLDTDKH67
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.04
>   Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
>   ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
>   Uname: Linux 5.0.0-16-generic x86_64
>   ApportVersion: 2.20.10-0ubuntu27
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Jun 11 11:10:33 2019
>   DisplayManager: gdm3
>   GsettingsChanges:
>b'org.gnome.shell' b'app-picker-view' b'uint32 1'
>b'org.gnome.shell' b'command-history' redacted by apport
>b'org.gnome.desktop.interface' b'gtk-im-module'
> b"'gtk-im-context-simple'"
>   InstallationDate: Installed on 2019-06-06 (4 days ago)
>   InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
>   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/1832317/+subscriptions
>

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

Title:
  A quick type in the Gnome 3 search sticks

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Details in my video: https://photos.app.goo.gl/h1eDdgkdJLDTDKH67

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 11 11:10:33 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-06-06 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  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/1832317/+subscriptions

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

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

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

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

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

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.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 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1832320] Re: Login screen hang after June 10 package upgrades

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

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


** This bug has been marked a duplicate of bug 1832138
   Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

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

Title:
  Login screen hang after June 10 package upgrades

Status in xorg-server package in Ubuntu:
  New

Bug description:
  After package updates on 10/6/19 the login screen froze. Turning
  Wayland off in the GDM configuration worked around the issue,

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu4.2
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 11 09:56:56 2019
  DistUpgraded: 2018-08-19 11:49:41,331 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2016-04-28 (1138 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=UUID=5701a684-d599-4319-b6ee-89d8ef7a11db ro quiet splash
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to bionic on 2018-08-19 (295 days ago)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  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 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

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

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

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

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.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 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1832320] [NEW] Login screen hang after June 10 package upgrades

2019-06-11 Thread Neil Wilson

Public bug reported:

After package updates on 10/6/19 the login screen froze. Turning Wayland
off in the GDM configuration worked around the issue,

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xwayland 2:1.19.6-1ubuntu4.2
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Uname: Linux 4.15.0-51-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 11 09:56:56 2019
DistUpgraded: 2018-08-19 11:49:41,331 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2016-04-28 (1138 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=UUID=5701a684-d599-4319-b6ee-89d8ef7a11db ro quiet splash
SourcePackage: xorg-server
UpgradeStatus: Upgraded to bionic on 2018-08-19 (295 days ago)
dmi.bios.date: 04/13/2018
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
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 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

Title:
  Login screen hang after June 10 package upgrades

Status in xorg-server package in Ubuntu:
  New

Bug description:
  After package updates on 10/6/19 the login screen froze. Turning
  Wayland off in the GDM configuration worked around the issue,

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu4.2
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 11 09:56:56 2019
  DistUpgraded: 2018-08-19 11:49:41,331 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2016-04-28 (1138 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=UUID=5701a684-d599-4319-b6ee-89d8ef7a11db ro quiet splash
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to bionic on 2018-08-19 (295 days ago)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure

[Desktop-packages] [Bug 1814465] Re: Firefox 65 cannot load Flash on trusty because of libxul.so broken dependency

Ubuntu 14.04 reached end-of-life in April 2019, and the Extended
Security Maintenance plan (which is a paid option) doesn't include
firefox (see https://wiki.ubuntu.com/SecurityTeam/ESM/14.04).

** Changed in: firefox (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Firefox 65 cannot load Flash on trusty because of libxul.so broken
  dependency

Status in firefox package in Ubuntu:
  Won't Fix

Bug description:
  Package:
  firefox  65.0+build2-0ubuntu0.14.04.1

  Error message in shell:
  /usr/lib/firefox/plugin-container: symbol lookup error: 
/usr/lib/firefox/libxul.so: undefined symbol: wl_surface_interface
  [Parent 3419, Gecko_IOThread] WARNING: pipe error (151): Connection reset by 
peer: file 
/build/firefox-mzqi2a/firefox-65.0+build2/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 349

  Steps:
  1) Run firefox 65 on Ubuntu 14.04.5 LTS in a terminal
  2) Visit a flash site and no flash content is displayed
  3) Look in the terminal for the libxul.so error message

  Note: This bug is similar to Bug #1720908 fixed in 2017

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

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

[Desktop-packages] [Bug 1832317] Re: A quick type in the Gnome 3 search sticks

In your video it looks like you are typing "ubuntu" and gnome-shell is
too slow to display much of the typing. So this is a performance
problem, and unsurprising if it's during an operation that requires
gnome-shell to perform disk IO like searching.


** Tags added: performance

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

Title:
  A quick type in the Gnome 3 search sticks

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Details in my video: https://photos.app.goo.gl/h1eDdgkdJLDTDKH67

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 11 11:10:33 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-06-06 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  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/1832317/+subscriptions

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

[Desktop-packages] [Bug 508522] Re: Mic is not available with A2DP Bluetooth profile