[Desktop-packages] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

[Bug Watch Updater]

** Changed in: mesa
   Status: Confirmed => Won't Fix

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

Title:
  qemu-system-x86_64 crashed with signal 31 in
  __pthread_setaffinity_new()

Status in Mesa:
  Won't Fix
Status in QEMU:
  Fix Committed
Status in mesa package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Invalid
Status in mesa source package in Disco:
  Fix Released
Status in mesa source package in EE-Series:
  Triaged
Status in qemu source package in EE-Series:
  Triaged

Bug description:
  Unable to launch Default Fedora 29 images in gnome-boxes

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: qemu-system-x86 1:3.1+dfsg-2ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  Date: Thu Feb 14 11:00:45 2019
  ExecutablePath: /usr/bin/qemu-system-x86_64
  KvmCmdLine: COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
  MachineType: Dell Inc. Precision T3610
  ProcEnviron: PATH=(custom, user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic 
root=UUID=939b509b-d627-4642-a655-979b44972d17 ro splash quiet vt.handoff=1
  Signal: 31
  SourcePackage: qemu
  StacktraceTop:
   __pthread_setaffinity_new (th=, cpusetsize=128, 
cpuset=0x7f5771fbf680) at ../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34
   () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   start_thread (arg=) at pthread_create.c:486
   clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
  Title: qemu-system-x86_64 crashed with signal 31 in 
__pthread_setaffinity_new()
  UpgradeStatus: Upgraded to disco on 2018-11-14 (91 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  dmi.bios.date: 11/14/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 09M8Y8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd11/14/2018:svnDellInc.:pnPrecisionT3610:pvr00:rvnDellInc.:rn09M8Y8:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T3610
  dmi.product.sku: 05D2
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1815889]

[Ahzo]

This problem was solved by qemu [1], so this mesa bug can be closed.

[1]
https://git.qemu.org/git/qemu.git/?a=commitdiff;h=9a1565a03b79d80b236bc7cc2dbce52a2ef3a1b8

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

Title:
  qemu-system-x86_64 crashed with signal 31 in
  __pthread_setaffinity_new()

Status in Mesa:
  Won't Fix
Status in QEMU:
  Fix Committed
Status in mesa package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Invalid
Status in mesa source package in Disco:
  Fix Released
Status in mesa source package in EE-Series:
  Triaged
Status in qemu source package in EE-Series:
  Triaged

Bug description:
  Unable to launch Default Fedora 29 images in gnome-boxes

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: qemu-system-x86 1:3.1+dfsg-2ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  Date: Thu Feb 14 11:00:45 2019
  ExecutablePath: /usr/bin/qemu-system-x86_64
  KvmCmdLine: COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
  MachineType: Dell Inc. Precision T3610
  ProcEnviron: PATH=(custom, user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic 
root=UUID=939b509b-d627-4642-a655-979b44972d17 ro splash quiet vt.handoff=1
  Signal: 31
  SourcePackage: qemu
  StacktraceTop:
   __pthread_setaffinity_new (th=, cpusetsize=128, 
cpuset=0x7f5771fbf680) at ../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34
   () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   start_thread (arg=) at pthread_create.c:486
   clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
  Title: qemu-system-x86_64 crashed with signal 31 in 
__pthread_setaffinity_new()
  UpgradeStatus: Upgraded to disco on 2018-11-14 (91 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  dmi.bios.date: 11/14/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 09M8Y8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd11/14/2018:svnDellInc.:pnPrecisionT3610:pvr00:rvnDellInc.:rn09M8Y8:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T3610
  dmi.product.sku: 05D2
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1824677] [NEW] Display only has 640x480

[Kev Bowring]

Public bug reported:

Upgraded kernel available.

Restarted to 640x480 display.

No other resolutions apparently available.

Rebooted to previous kernel - display resolution now correct.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xserver-xorg-video-nouveau 1:1.0.16-1
ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
Uname: Linux 5.0.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Sun Apr 14 06:20:02 2019
DistUpgraded: 2018-10-14 15:47:40,052 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: ZOTAC International (MCO) Ltd. GT218 [GeForce 210] [19da:1160]
InstallationDate: Installed on 2018-08-27 (229 days ago)
InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180824)
MachineType: NOVATECH LTD MBB-44608
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-11-generic 
root=UUID=5ea4b063-e7d4-43c8-8d9a-5c5f89fa3a3f ro quiet splash vt.handoff=1
SourcePackage: xserver-xorg-video-nouveau
UpgradeStatus: Upgraded to disco on 2018-10-14 (181 days ago)
dmi.bios.date: 06/19/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81M-DS2V
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: 7383241-001
dmi.chassis.type: 3
dmi.chassis.vendor: NOVATECH LTD
dmi.chassis.version: V1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
dmi.product.family: AMI PLATFORM
dmi.product.name: MBB-44608
dmi.product.sku: MBB-44608
dmi.product.version: V1.0
dmi.sys.vendor: NOVATECH LTD
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-09-21T16:30:23.845026
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 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

** Affects: xserver-xorg-video-nouveau (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco ubuntu

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

Title:
  Display only has 640x480

Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  Upgraded kernel available.

  Restarted to 640x480 display.

  No other resolutions apparently available.

  Rebooted to previous kernel - display resolution now correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-nouveau 1:1.0.16-1
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Uname: Linux 5.0.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Apr 14 06:20:02 2019
  DistUpgraded: 2018-10-14 15:47:40,052 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: ZOTAC International (MCO) Ltd. GT218 [GeForce 210] [19da:1160]
  InstallationDate: Installed on 2018-08-27 (229 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180824)
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-11-generic 
root=UUID=5ea4b063-e7d4-43c8-8d9a-5c5f89fa3a3f ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to disco on 2018-10-14 (181 days ago)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co.

[Desktop-packages] [Bug 1759462] Re: Keyboard shortcuts not operational on 18.04

[Artemis]

I am currently using Ubuntu Budgie and I can confirm this issue still
occurs with the latest 18.04.2 version. Fresh install and I can only get
shortcuts to work using the Alt button. I am using an X240 Lenovo
Thinkpad Laptop. If anyone has any possible fixes let us know.

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

Title:
  Keyboard shortcuts not operational on 18.04

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

Bug description:
  After installing 18.04, I noticed that certain keyboard shortcuts no
  longer function.

  It appears to be related to the shortcuts that gnome-settings-daemon
  control as my shortcuts that are provided by my desktop (Budgie) still
  function.

  Some examples are:

  * Media keys for volume up/down/mute
  * ctrl-alt-t for the terminal. I tried changing the shortcut to test. Same 
behaviour.

  I double checked, and it looks like the needed daemon is still
  running,

  ```
  dustin3337  0.0  0.2 500736 22216 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-keyboard
  dustin3338  0.0  0.3 943372 25732 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-media-keys
  dustin3343  0.0  0.0 274908  5844 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-mouse
  dustin3345  0.0  0.3 519896 25144 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-power
  dustin3348  0.0  0.1 346004 10212 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-print-notifications
  dustin3351  0.0  0.0 374684  7952 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-smartcard
  dustin3355  0.0  0.1 329584  8064 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-sound
  dustin3361  0.0  0.1 449708  9856 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-sharing
  dustin3367  0.0  0.0 272416  4772 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
  dustin3375  0.0  0.0 420028  5804 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-rfkill
  dustin3383  0.0  0.2 507120 23244 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-wacom
  dustin3385  0.0  0.3 498040 25040 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-xsettings
  dustin3387  0.0  0.0 274900  5936 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-a11y-settings
  dustin3392  0.0  0.2 496016 22044 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-clipboard
  dustin3395  0.0  0.3 810156 25976 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-color
  dustin3396  0.0  0.2 471656 21080 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-datetime
  dustin3400  0.0  0.0 361196  7116 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-housekeeping
  dustin3433  0.0  0.1 505404 12576 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-printer
  dustin9776  0.0  0.0  18188  1032 pts/1S+   21:19   0:00 grep 
--color=auto gnome-settings-daemon
  ```

  Reboot does not seem to help. However, occasionally the shortcuts do
  seem to work - but only very occasionally.

  Any other info needed?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 27 21:12:18 2018
  InstallationDate: Installed on 2018-03-05 (22 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180304)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1592550] Re: nm-applet does not appear in notification area

[Launchpad Bug Tracker]

[Expired for network-manager-applet (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: network-manager-applet (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  nm-applet does not appear in notification area

Status in network-manager-applet package in Ubuntu:
  Expired

Bug description:
  I have to log in to a wifi service via PEAP at my university. After
  doing this, on each successive reboot my nm-applet does not appear in
  my notification area (all my other applets are still there). I can get
  the applet to appear by running "nm-applet" in a terminal. I do get
  two notifications in the terminal as nm-applet loads:

  (nm-applet:3100): Gtk-WARNING **: Theme parsing error: gtk-
  main.css:69:33: Failed to import: Error opening file: No such file or
  directory

  (nm-applet:3100): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates:
  assertion 'window->update_and_descendants_freeze_count > 0' failed

  I have installed Ubuntu Mate twice on my system, and the applet works fine 
after logging into various networks until I set up the PEAP login. Also, even 
if the applet doesn't appear I am still connected to any saved wifi network 
within range.
  I am running Ubuntu Mate 16.04, with Mate 1.12.1 on a Dell Latitude e6410.
  Thank you.

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

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

[Desktop-packages] [Bug 1814889] Re: Dock does not change position nor icon size

[Launchpad Bug Tracker]

[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there
has been no activity for 60 days.]

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Dock does not change position nor icon size

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Expired

Bug description:
  I cannot change the position of the dock.

  How to reproduce (on my system):

  Either:
  (a) open the settings -> Dock and select a different value for the dock, e.g. 
"Bottom", or
  (b) enter "gsettings set org.gnome.shell.extensions.dash-to-dock 
dock-position BOTTOM" in the command line

  Expected result: In both cases, the dock should move to the bottom of
  the screen.

  Actual result: The dock remains at the same position.

  
  Additional observations:
  1. I also cannot change the icon size (only tried via GUI, not command line).
  2. All the behavior is observed no matter what other settings (auto-hide, 
show on) I pick.
  3. This describes a similar (the same?) problem: 
https://askubuntu.com/questions/1061924/ubuntu-wont-register-dock-settings-changes-in-18-04#new-answer

  Screenshots are attached.

  Please let me know if I should provide additional information.
  I am a fairly technical user, and I am willing to put in some effort to get 
this resolved.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  6 12:51:39 2019
  InstallationDate: Installed on 2018-11-20 (77 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1824671] [NEW] message reporting app crash on system startup

[Robert Williamson]

Public bug reported:


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

Release: Ubuntu 18.04.2 LTS

2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center

robert@robert-HP-Pavilion-dm4-Notebook-PC:~$ apt-cache policy spice-vdagent
spice-vdagent:
  Installed: 0.17.0-1ubuntu2
  Candidate: 0.17.0-1ubuntu2
  Version table:
 *** 0.17.0-1ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

3) What you expected to happen
The computer was rebooting from the first update following the OS installation, 
I expected nothing to happen.
 
4) What happened instead
A message popped up on the desktop saying an app crashed asking permission to 
send a report.
I found a log file description of the problem:"Cannot access vdagent virtio 
channel /dev/virtio-ports/com.redhat.spice.0"

** Affects: spice-vdagent (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  message reporting app crash on system startup

Status in spice-vdagent package in Ubuntu:
  New

Bug description:

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

  Release: Ubuntu 18.04.2 LTS

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  robert@robert-HP-Pavilion-dm4-Notebook-PC:~$ apt-cache policy spice-vdagent
  spice-vdagent:
Installed: 0.17.0-1ubuntu2
Candidate: 0.17.0-1ubuntu2
Version table:
   *** 0.17.0-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  The computer was rebooting from the first update following the OS 
installation, I expected nothing to happen.
   
  4) What happened instead
  A message popped up on the desktop saying an app crashed asking permission to 
send a report.
  I found a log file description of the problem:"Cannot access vdagent virtio 
channel /dev/virtio-ports/com.redhat.spice.0"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1824671/+subscriptions

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

[Desktop-packages] [Bug 1824670] Re: Boot to black screen after Kubuntu 19.04 install

[Ubuntu QA Website]

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

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

** Tags added: iso-testing

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

Title:
  Boot to black screen after Kubuntu 19.04 install

Status in xorg package in Ubuntu:
  New

Bug description:
  Legacy laptop, Dell Vostro 1720, booted to black screen after fresh
  full disk install.  Using ctrl-alt-f2 to drop to a terminal and
  issuing "startx" completed the boot process.

  Installed NVidia 340 driver which crashed the current session and sent
  me to an endless GUI (sddm?) login loop where login immediately
  crashed back to the GUI login.

  Rebooting from the login screen worked as expected and system is
  running fine now.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Uname: Linux 5.0.0-11-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Apr 13 21:03:41 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus: nvidia-340, 340.107, 5.0.0-11-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation G96M [GeForce 9600M GS] [10de:0648] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G96M [GeForce 9600M GS] [1028:02c0]
  InstallationDate: Installed on 2019-04-14 (0 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.1)
  MachineType: Dell Inc. Vostro 1720
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-11-generic 
root=UUID=bd90d4b8-d528-46cd-8c3a-55001a8200b9 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0P369J
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/27/2009:svnDellInc.:pnVostro1720:pvrNull:rvnDellInc.:rn0P369J:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 1720
  dmi.product.sku: Null
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1821820] Re: Cannot boot or install - have to use nomodeset

[Robert Strube]

Sorry for the spam, last post for now I promise!

Reading this bug report more closely, it does appear different than the
bug I am encountering.  With *this* bug, one sees a black screen *with*
a cursor, my symptoms are different, as the laptop panel is failing
display link training, so nothing is displayed, it flickers a couple of
times and nothing every appears.  *This* bug appears to be Xorg related,
but the bug I'm encountering (which is known on bugs.freedesktop.org) is
a bug with the i915 kernel module.

For now I've removed the duplicate status of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824216 and will
add comments there moving forward.

Again apologies for posting so many times, I honestly thought this was
the same issue I'm encountering.

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

Title:
  Cannot boot or install - have to use nomodeset

Status in linux package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Committed

Bug description:
  On this 19.04 beta I have to use nomodeset to boot & install Ubuntu
  Budgie.

  This is different behaviour from 18.04 and 18.10 where it booted and
  installed just fine without nomodeset.

  Without nomodeset, grub/efi disappears, and after a while a solid
  rather than blinking cursor on a black screen is seen.  It does not
  boot into a live session, nor displays the ubiquity window

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 26 23:40:49 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf]
  InstallationDate: Installed on 2019-03-26 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1824670] [NEW] Boot to black screen after Kubuntu 19.04 install

[Darin Miller]

Public bug reported:

Legacy laptop, Dell Vostro 1720, booted to black screen after fresh full
disk install.  Using ctrl-alt-f2 to drop to a terminal and issuing
"startx" completed the boot process.

Installed NVidia 340 driver which crashed the current session and sent
me to an endless GUI (sddm?) login loop where login immediately crashed
back to the GUI login.

Rebooting from the login screen worked as expected and system is running
fine now.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
Uname: Linux 5.0.0-11-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
 GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
Date: Sat Apr 13 21:03:41 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus: nvidia-340, 340.107, 5.0.0-11-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation G96M [GeForce 9600M GS] [10de:0648] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Dell G96M [GeForce 9600M GS] [1028:02c0]
InstallationDate: Installed on 2019-04-14 (0 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.1)
MachineType: Dell Inc. Vostro 1720
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-11-generic 
root=UUID=bd90d4b8-d528-46cd-8c3a-55001a8200b9 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0P369J
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/27/2009:svnDellInc.:pnVostro1720:pvrNull:rvnDellInc.:rn0P369J:rvr:cvnDellInc.:ct8:cvrN/A:
dmi.product.family: Vostro
dmi.product.name: Vostro 1720
dmi.product.sku: Null
dmi.product.version: Null
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug disco 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/1824670

Title:
  Boot to black screen after Kubuntu 19.04 install

Status in xorg package in Ubuntu:
  New

Bug description:
  Legacy laptop, Dell Vostro 1720, booted to black screen after fresh
  full disk install.  Using ctrl-alt-f2 to drop to a terminal and
  issuing "startx" completed the boot process.

  Installed NVidia 340 driver which crashed the current session and sent
  me to an endless GUI (sddm?) login loop where login immediately
  crashed back to the GUI login.

  Rebooting from the login screen worked as expected and system is
  running fine now.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Uname: Linux 5.0.0-11-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and

[Desktop-packages] [Bug 1821820] Re: Cannot boot or install - have to use nomodeset

[Robert Strube]

Here are drm messages from logs booting up with drm.debug=14 with
5.0.0-11.12.  You can see the link training issues are still present.

21:00:11 kernel: [drm:intel_dp_get_link_train_fallback_values [i915]] Retrying 
Link training for eDP with same parameters
21:00:11 kernel: [drm:intel_dp_start_link_train [i915]] [CONNECTOR:85:eDP-1] 
Link Training failed at link rate = 324000, lane count = 1
21:00:11 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis 
level 0
21:00:11 kernel: [drm:intel_dp_program_link_training_pattern [i915]] Using DP 
training pattern TPS1
21:00:11 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis 
level 0
21:00:11 kernel: [drm:intel_dp_start_link_train [i915]] Using LINK_RATE_SET 
value 04

** Attachment added: "dmesg with drm.debug=14"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821820/+attachment/527/+files/log%20messages

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

Title:
  Cannot boot or install - have to use nomodeset

Status in linux package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Committed

Bug description:
  On this 19.04 beta I have to use nomodeset to boot & install Ubuntu
  Budgie.

  This is different behaviour from 18.04 and 18.10 where it booted and
  installed just fine without nomodeset.

  Without nomodeset, grub/efi disappears, and after a while a solid
  rather than blinking cursor on a black screen is seen.  It does not
  boot into a live session, nor displays the ubiquity window

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 26 23:40:49 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf]
  InstallationDate: Installed on 2019-03-26 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1821820] Re: Cannot boot or install - have to use nomodeset

[Robert Strube]

As a side note, this was the bug I had originally opened up in
launchpad, which I thought might have been a duplicate of this bug
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824216)

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

Title:
  Cannot boot or install - have to use nomodeset

Status in linux package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Committed

Bug description:
  On this 19.04 beta I have to use nomodeset to boot & install Ubuntu
  Budgie.

  This is different behaviour from 18.04 and 18.10 where it booted and
  installed just fine without nomodeset.

  Without nomodeset, grub/efi disappears, and after a while a solid
  rather than blinking cursor on a black screen is seen.  It does not
  boot into a live session, nor displays the ubiquity window

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 26 23:40:49 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf]
  InstallationDate: Installed on 2019-03-26 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1821820] Re: Cannot boot or install - have to use nomodeset

[Robert Strube]

I just tested with a fresh install of 19.04 (booted up with nomodeset
and installed).  After installation I confirmed I was running
5.0.0-11.12, but the laptop panel link training issue is still present
(Dell XPS 9575) causing a black screen on boot.  The only way to boot is
with nomodeset as a kernel boot parameter.

Note: as a side issue it was virtually impossible to bring up the grub
menu now in 19.04 (I think because the timeout is set to zero).  I had
to make sure to chroot into the newly installed system (after
installing) and then edit the /boot/grub/grub.cfg file and manually edit
the timeout value.

I thought that the this Ubuntu bug was referring to this bug
(REGRESSION: black screen with linux 5.0 when starting X)
https://bugs.freedesktop.org/show_bug.cgi?id=109959), but perhaps it's
referencing another issue entirely?  Not sure, but either way the failed
link training bug still appears to be present with 5.0.0-11.12 causing
black screens on bootups with certain laptop panels.

Reading through that thread on bugs.freedesktop.org, Intel realized the
problem was caused by certain laptop panels not reporting their
specifications correctly (Dell XPS systems appear affected, but other
laptops will most likely also be affected), so the code they added to
optimize the link (fast and narrow vs. slow and wide) would cause
certain laptop panels to never display anything with modesetting.

Towards the end of the thread to posted a 5.0 backport patch which
completely removes the link  optimizations,
https://patchwork.freedesktop.org/patch/296411/.  Based on the Ubuntu
kernel changelog I'm not sure exactly what patch was reverted.  My guess
is it's for another issue entirely.

I'll probably try to compile the Ubuntu kernel with their the
freedesktop.org backport patch applied and report back.  I can also post
my dmeg here for reference.

** Bug watch added: freedesktop.org Bugzilla #109959
   https://bugs.freedesktop.org/show_bug.cgi?id=109959

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

Title:
  Cannot boot or install - have to use nomodeset

Status in linux package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Committed

Bug description:
  On this 19.04 beta I have to use nomodeset to boot & install Ubuntu
  Budgie.

  This is different behaviour from 18.04 and 18.10 where it booted and
  installed just fine without nomodeset.

  Without nomodeset, grub/efi disappears, and after a while a solid
  rather than blinking cursor on a black screen is seen.  It does not
  boot into a live session, nor displays the ubiquity window

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 26 23:40:49 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf]
  InstallationDate: Installed on 2019-03-26 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2

[Desktop-packages] [Bug 1823077] Re: Cannot upgrade libxkbcommon0 without removing half the operating system

[Jeffrey Santoso]

I get the same problem when I tried to update the package.
I'm using Ubuntu 18.04


$ dpkg -l | grep  libxkbcommon0
ii  libxkbcommon0:amd640.8.0-1ubuntu0.1 
   amd64library interface to the XKB compiler - shared library


$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.2 LTS"


$ sudo apt-get install libxkbcommon0:i386
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  argyll argyll-ref bubblewrap cdrdao docutils-common docutils-doc dvdauthor 
fonts-font-awesome fonts-lato gir1.2-gconf-2.0
  gir1.2-javascriptcoregtk-4.0 gir1.2-polkit-1.0 gir1.2-snapd-1 
gir1.2-totemplparser-1.0 gksu gnome-control-center-faces gnome-software-common
  gnome-todo-common grilo-plugins-0.3-base liba11y-profile-manager-0.1-0 
libandroid-properties1 libapache2-mod-dnssd libappconfig-perl
  libboost-filesystem1.65.1 libboost-system1.65.1 libboost-thread1.65.1 
libbrotli1 libcairo-gobject-perl libcairo-perl libcapnp-0.6.1
  libclass-inspector-perl libclass-load-perl libclass-std-fast-perl 
libclass-std-perl libcommon-sense-perl libconvert-binhex-perl
  libdate-manip-perl libdbd-mysql-perl libdbi-perl libdevice-serialport-perl 
libdrm-dev libebackend-1.2-10 libebook-1.2-19
  libebook-contacts-1.2-2 libedata-book-1.2-25 libedata-cal-1.2-28 
libemail-date-format-perl libfcitx-gclient1 libfontenc-dev libfreetype6-dev
  libgdm1 libgeonames-common libgeonames0 libgksu2-0 
libglib-object-introspection-perl libglib-perl libgnome-autoar-0-0
  libgnome-games-support-common libgnome-todo libgom-1.0-0 libgrilo-0.3-0 
libgspell-1-common libgtk2-perl libgtop-2.0-11 libhardware2 libhybris
  libhybris-common1 libimage-base-bundle-perl libimage-info-perl 
libio-interface-perl libio-sessiondata-perl libio-socket-multicast-perl
  libjavascriptcoregtk-4.0-18 libjs-modernizr libjs-mootools libjs-sphinxdoc 
libjson-any-perl libjson-maybexs-perl libjson-xs-perl libmedia1
  libmediaart-2.0-0 libmime-lite-perl libmime-tools-perl libmime-types-perl 
libmircommon7 libmircookie-dev libmircookie2 libmircore-dev
  libmircore1 libmirprotobuf3 libmp4v2-2 libnet-sftp-foreign-perl 
libnss-myhostname libnumber-bytes-human-perl libossp-uuid-perl libossp-uuid16
  libpango-perl libpciaccess-dev libperl4-corelibs-perl libphonenumber7 
libphp-serialization-perl libpixman-1-dev libpng12-dev libprotobuf-dev
  libprotobuf-lite10 libproxy-tools libpthread-stubs0-dev libqqwing2v5 
libqt5script5 libqt5sensors5 libqt5webchannel5 libsnapd-glib1
  libsoap-lite-perl libsoap-wsdl-perl libsys-cpu-perl libsys-meminfo-perl 
libsys-mmap-perl libsysmetrics1 libtask-weaken-perl libtemplate-perl
  libterm-readkey-perl libtracker-sparql-2.0-0 libtypes-serialiser-perl 
liburi-encode-perl libvlc-bin libvlc5 libvlccore9 libvte-2.90-common
  libwoff1 libx11-dev libx11-doc libxau-dev libxcb-res0 libxcb-xinerama0 
libxcb1-dev libxdmcp-dev libxfont-dev libxkbfile-dev
  libxmlrpc-lite-perl mesa-common-dev mutter-common onboard-common 
oxideqt-codecs-extra php-apcu php-apcu-bc python-alabaster python-babel
  python-babel-localedata python-certifi python-compizconfig python-docutils 
python-imagesize python-jinja2 python-markupsafe python-pygments
  python-requests python-roman python-sphinx python-sphinx-rtd-theme 
python-typing python-tz python3-macaroonbakery python3-nacl
  python3-protobuf python3-pymacaroons python3-rfc3339 python3-tz sphinx-common 
sphinx-rtd-theme-common x11proto-core-dev x11proto-dev
  x11proto-dri2-dev x11proto-dri3-dev x11proto-fonts-dev x11proto-gl-dev 
x11proto-input-dev x11proto-kb-dev x11proto-present-dev
  x11proto-randr-dev x11proto-render-dev x11proto-resource-dev 
x11proto-scrnsaver-dev x11proto-video-dev x11proto-xext-dev
  x11proto-xf86bigfont-dev x11proto-xf86dri-dev x11proto-xinerama-dev 
xorg-sgml-doctools xtrans-dev zoneminder-doc
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  a11y-profile-manager-indicator activity-log-manager aisleriot apport-gtk 
apturl bamfdaemon baobab brasero brasero-cdrkit cheese compiz
  compiz-gnome deja-dup empathy eog evince evolution-data-server 
evolution-data-server-online-accounts ffmpeg file-roller gcr gedit
  gir1.2-appindicator3-0.1 gir1.2-gnomebluetooth-1.0 gir1.2-gtk-3.0 
gir1.2-gtksource-3.0 gir1.2-peas-1.0 gir1.2-rb-3.0 gir1.2-totem-1.0
  gir1.2-vte-2.90 gir1.2-vte-2.91 gir1.2-webkit-3.0 gir1.2-webkit2-4.0 
gir1.2-wnck-3.0 gkbd-capplet gnome-bluetooth gnome-calculator
  gnome-calendar gnome-color-manager gnome-contacts gnome-control-center 
gnome-disk-utility gnome-font-viewer gnome-getting-started-docs
  gnome-initial-setup gnome-keyring gnome-mahjongg gnome-mines 
gnome-online-accounts gnome-power-manager gnome-screensaver gnome-screenshot
  gnome-session-bin gnome-session-canberra gnome-settings-daemon gnome-software 
gnome-softw

[Desktop-packages] [Bug 1822587] Re: wifi service stops occasionally.

[El jinete sin cabeza]

Something similar happens to me. LP: #1824665

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

Title:
  wifi service stops occasionally.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  wifi service stops occasionally: ('?' in the top right icon). an old
  bug that disappeared a few updates back, back now after yesterday's
  update.  'service network-manager restart' gets it working again.
  annoying as i thought it gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.4-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 14:50:50 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-07-30 (975 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 
   192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.100 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to cosmic on 2018-12-06 (116 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTIONCON-UUID  CON-PATH   

   wlp3s0f0   wifi  connected 
/org/freedesktop/NetworkManager/Devices/3  HUAWEI-B315-D7CD  
01a82e09-44b7-4509-af07-4bf05f76759a  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   1C:AF:05:F7:CE:56  btdisconnected  
/org/freedesktop/NetworkManager/Devices/4  ---- 
   -- 
   enp2s0f1   ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/2  ---- 
   -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/1  ---- 
   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  disabled

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

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

[Desktop-packages] [Bug 1822587] Re: wifi service stops occasionally.

[Launchpad Bug Tracker]

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  wifi service stops occasionally.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  wifi service stops occasionally: ('?' in the top right icon). an old
  bug that disappeared a few updates back, back now after yesterday's
  update.  'service network-manager restart' gets it working again.
  annoying as i thought it gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.4-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 14:50:50 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-07-30 (975 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 
   192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.100 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to cosmic on 2018-12-06 (116 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTIONCON-UUID  CON-PATH   

   wlp3s0f0   wifi  connected 
/org/freedesktop/NetworkManager/Devices/3  HUAWEI-B315-D7CD  
01a82e09-44b7-4509-af07-4bf05f76759a  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   1C:AF:05:F7:CE:56  btdisconnected  
/org/freedesktop/NetworkManager/Devices/4  ---- 
   -- 
   enp2s0f1   ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/2  ---- 
   -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/1  ---- 
   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  disabled

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

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

[Desktop-packages] [Bug 1824665] [NEW] Disconnects from WiFi (SSID)

[El jinete sin cabeza]

Private bug reported:

[Impact]
I am working with several programs at the same time. Like the web browser, 
Transmission, and others. And it has happened to me twice today. The led of my 
USB Wifi adapter is always on and there is no packet transfer. Then the 
NetworkManager asks me for the password. Suggesting me in the small window with 
hidden characters. Press 'OK' and ask me again. 'I forget' the password and add 
it again. And I do not accept it either. I had to change the USB Wifi adapter 
several times in USB ports. And suddenly it works again.
 
[Test Case]
- Turn on the Notebook
- Open programs that use WiFi intensely (Transmission)
- Wait a few hours
- Internet traffic is blocked
- NetworkManager requests the password of the SSID that I use
- Login password
- Does not accept the password
- I forgot SSID data
- Context the SSID that I use
- Ask for a password again
- Does not accept Password
- Change USB ports with my WiFi USB adapter
- And after a few minutes, it is correctly connected again.

Others:
Attach: $_journalctl_-f.txt When this happens

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: network-manager 1.16.0-0ubuntu2
Uname: Linux 5.0.7-050007-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 13 19:36:13 2019
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-12-02 (132 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
IpRoute:
 
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to disco on 2018-12-02 (132 days ago)
nmcli-dev:
 DEVICE   TYPE  STATE IP4-CONNECTIVITY  
IP6-CONNECTIVITY  DBUS-PATH  CONNECTION  
CON-UUID  CON-PATH 
 wlx98ded0105daf  wifi  disconnected  limited   limited 
  /org/freedesktop/NetworkManager/Devices/2  --  ----   
 p2p-dev-wlx98ded0105daf  wifi-p2p  disconnected  none  none
  /org/freedesktop/NetworkManager/Devices/3  --  ----   
 lo   loopback  unmanaged unknown   unknown 
  /org/freedesktop/NetworkManager/Devices/1  --  ----
nmcli-nm:
 RUNNING  VERSION  STATE STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
 running  1.16.0   disconnected  started  limited   enabled enabled  
enabled  enabled  enabled

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


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

** Attachment added: "$ journalctl -f"
   
https://bugs.launchpad.net/bugs/1824665/+attachment/5255532/+files/%24_journalctl_-f.txt

** Summary changed:

- Disconnects from WiFi
+ Disconnects from WiFi (SSID)

** Information type changed from Public to Private

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

Title:
  Disconnects from WiFi (SSID)

Status in network-manager package in Ubuntu:
  New

Bug description:
  [Impact]
  I am working with several programs at the same time. Like the web browser, 
Transmission, and others. And it has happened to me twice today. The led of my 
USB Wifi adapter is always on and there is no packet transfer. Then the 
NetworkManager asks me for the password. Suggesting me in the small window with 
hidden characters. Press 'OK' and ask me again. 'I forget' the password and add 
it again. And I do not accept it either. I had to change the USB Wifi adapter 
several times in USB ports. And suddenly it works again.
   
  [Test Case]
  - Turn on the Notebook
  - Open programs that use WiFi intensely (Transmission)
  - Wait a few hours
  - Internet traffic is blocked
  - NetworkManager requests the password of the SSID that I use
  - Login password
  - Does not accept the password
  - I forgot SSID data
  - Context the SSID that I use
  - Ask for a password again
  - Does not accept Password
  - Change USB ports with my WiFi USB adapter
  - And after a few minutes, it is correctly connected again.

  Others:
  Attach: $_journalctl_-f.txt When this happens

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: network-manager 1.16.0-0ubuntu2
  Uname: Linux 5.0.7-050007-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 19:36:13 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-12-02 (132 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

[Matt Lee]

Interesting. Since I'm only getting VpxVideoDecoder decode, I guess I
have an installation issue of some kind.

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc`

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

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

[Desktop-packages] [Bug 1813209] Re: bubble help flashes in libreoffice

[Walter Lapchynski]

Given the above, I'm calling this fixed.

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

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

Title:
  bubble help flashes in libreoffice

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Hovering over any of the icons on the toolbar in libreoffice causes
  the bubble help to appear and disappear quickly.

  I'm attaching a video (mp4) of what I mean.

  Version: 6.1.4.2
  Build ID: 1:6.1.4-0ubuntu0.18.10.1
  CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; 
  Locale: en-CA (en_CA.UTF-8); Calc: group threaded

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

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

[Desktop-packages] [Bug 1811614] Re: nautilus crashed with SIGSEGV in g_str_hash()

[Bryan Quigley]

Reproducer no longer possible, closing.

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

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

Title:
  nautilus crashed with SIGSEGV in g_str_hash()

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  This looks to be an issue with the new desktop and getting properties
  on items on your desktop.

  On the desktop:
  Right click -> Properties
  Close it quickly.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.30.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.10-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 13 11:38:12 2019
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'276'
   b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'"
   b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 
'size', 'date_modified']"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency']"
  InstallationDate: Installed on 2018-04-14 (273 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180414)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fdd00975cc0 :   movsbl (%rdi),%edx
   PC (0x7fdd00975cc0) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   g_str_hash () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ()
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: Upgraded to disco on 2019-01-05 (7 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1813209] Re: bubble help flashes in libreoffice

[Dan Simmons]

I am not having this issue in Lubuntu 18.10 and libreoffice-calc Version: 
6.1.5.2
Build ID: 1:6.1.5-0ubuntu0.18.10.1
CPU threads: 4; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; 
Locale: en-US (en_US.UTF-8); Calc: group threaded

I have attached a short video.

** Attachment added: "simplescreenrecorder-2019-04-13_18.46.04.mkv"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1813209/+attachment/5255511/+files/simplescreenrecorder-2019-04-13_18.46.04.mkv

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

Title:
  bubble help flashes in libreoffice

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Hovering over any of the icons on the toolbar in libreoffice causes
  the bubble help to appear and disappear quickly.

  I'm attaching a video (mp4) of what I mean.

  Version: 6.1.4.2
  Build ID: 1:6.1.4-0ubuntu0.18.10.1
  CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; 
  Locale: en-CA (en_CA.UTF-8); Calc: group threaded

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

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

[Desktop-packages] [Bug 1824661] [NEW] Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile

[Eric]

Public bug reported:

Hello. I am having issues consistently with this laptop and the Nvidia
drivers in 19.04. I have tested this on Ubuntu, Kubuntu, Ubuntu Budgie,
and Ubuntu MATE. This is with both the recommended 418 driver as well as
390. Today I tried installing the latest daily of Ubuntu MATE with the
proprietary driver option on my Dell XPS 15 9570 with Nvidia GP107M
(GeForce GRX 1050 Time Mobile). Boots to blank screen that flashes a
couple times. Can't get to tty. Reboot, editing grub to include
nomodeset. Boots to underscore character in the top left. I can get tty
at least. 418 driver is installed. Looking at logs but nothing seems
obvious. If there's anything I can do to help with this please let me
know. Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
Uname: Linux 5.0.0-11-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  418.56  Fri Mar 15 12:59:26 
CDT 2019
 GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
Date: Sat Apr 13 18:27:12 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus: nvidia, 418.56, 5.0.0-11-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c]
   Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c]
InstallationDate: Installed on 2019-04-13 (0 days ago)
InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
MachineType: Dell Inc. XPS 15 9570
ProcEnviron:
 TERM=cygwin
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-11-generic 
root=UUID=add8471d-1273-4547-aef3-4be006f9eb9c ro quiet splash nomodeset 
vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/01/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.1
dmi.board.name: 0D0T05
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9570
dmi.product.sku: 087C
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 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 N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug disco 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/1824661

Title:
  Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello. I am having issues consistently with this laptop and the Nvidia
  drivers in 19.04. I have tested this on Ubuntu, Kubuntu, Ubuntu
  Budgie, and Ubuntu MATE. This is with both the recommended 418 driver
  as well as 390. Today I tried installing the latest daily of Ubuntu
  MATE with the proprietary driver option on my Dell XPS 15 9570 with
  Nvidia GP107M (GeForce GRX 1050 Time Mobile). Boots to blank screen
  that flashes a couple times. Can't get to tty. Reboot, editing grub to
  include nomodeset. Boots to underscore character in the top left. I
  can get tty at least. 418 driver is installed. Looking at logs but
  nothing seems obvious. If there's anything I can do to help with this
  please let me know. Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Uname: Linux 5.0.0-11-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 M

[Desktop-packages] [Bug 1813209] Re: bubble help flashes in libreoffice

[Walter Lapchynski]

At least with the current settings of Lubuntu 19.04 and libreoffice-calc
1:6.2.2-0ubuntu2, I can confirm this is not an issue.

** Attachment added: "libreoffice tooltips working correctly"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1813209/+attachment/5255497/+files/libreoffice.webm

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

Title:
  bubble help flashes in libreoffice

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Hovering over any of the icons on the toolbar in libreoffice causes
  the bubble help to appear and disappear quickly.

  I'm attaching a video (mp4) of what I mean.

  Version: 6.1.4.2
  Build ID: 1:6.1.4-0ubuntu0.18.10.1
  CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; 
  Locale: en-CA (en_CA.UTF-8); Calc: group threaded

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

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

[Desktop-packages] [Bug 1767122] Re: duplicity Errors 199 at end backup

[Michael Terry]

** No longer affects: deja-dup

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

Title:
  duplicity Errors 199 at end backup

Status in Duplicity:
  Invalid
Status in Python:
  New
Status in duplicity package in Ubuntu:
  New

Bug description:
  Hello,

  I use duplicity to backup my file. However. I get always this message
  at end backup with Error 199

  --[ Backup Statistics ]--
  StartTime 1524741993.34 (Thu Apr 26 13:26:33 2018)
  EndTime 1524746175.96 (Thu Apr 26 14:36:15 2018)
  ElapsedTime 4182.62 (1 hour 9 minutes 42.62 seconds)
  SourceFiles 3821570
  SourceFileSize 191576839080 (178 GB)
  NewFiles 2088902
  NewFileSize 19156070 (178 GB)
  DeletedFiles 3
  ChangedFiles 54
  ChangedFileSize 1834439 (1.75 MB)
  ChangedDeltaSize 0 (0 bytes)
  DeltaEntries 2088959
  RawDeltaSize 0 (0 bytes)
  TotalDestinationSizeChange 0 (0 bytes)
  Errors 199lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  Codename: bionic

  
  Step to reproduce :
  1. Configure duplicity
  2. Run a bakup.
  Result
  3. At end backup, you should get Error 199
  -
  uname -r
  4.15.0-20-generic

  My configuration :

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

  
  apt-cache policy duplicity 
  duplicity:
Installed: 0.7.17-0ubuntu1
Candidate: 0.7.17-0ubuntu1
Version table:
   *** 0.7.17-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  apt-cache policy python
  python:
Installed: 2.7.15~rc1-1
Candidate: 2.7.15~rc1-1
Version table:
   *** 2.7.15~rc1-1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Could you help me please to fix this issues ?

  
  Thanks by advance for your support

  
  Best regards

  Battant

  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: Thu Apr 26 15:58:41 2018
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1824657] Re: GNOME shell crash

[Emanuele]

I put the logs also on pastebin, maybe they are more readable.

https://paste.ubuntu.com/p/TPMDVJZgqJ/

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

Title:
  GNOME shell crash

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I was watching a video on youtube with the Chromium snap browser, suddenly 
the GNOME shell crashed, no possibility to click for Chromium or other closure, 
but I managed to access a tty4 session, by pressing the keys: ctrl + alt + f4.
  Using Ubuntu 19.04 from the beginning of development, first with KDE, after I 
install GNOME with the metapackage: sudo apt install ubuntu-desktop, 
eliminating any KDE package, until now I have had no problem.
  full update, proposed repository disabled.
  I attach the logs from the time I had the problem, about 10:50 pm, I started 
with the logs at 10:40 pm with this command: journalctl --since "2019-04-13 
22:40:00" ( if it is wrong, let him know)

  From the logs I see many gnome-shell errors, but obviously I can't
  decipher them if it was the cause of the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Uname: Linux 5.0.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 23:07:59 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.shell' b'enabled-extensions' 
b"['move_cl...@jonathan.bluemosh.com', 'openweather-extens...@jenslody.de', 
'sound-output-device-choo...@kgshank.net', 
'apps-m...@gnome-shell-extensions.gcampax.github.com', 
'applications_m...@rmy.pobox.com', 'gsconn...@andyholmes.github.io', 
'move_cl...@rmy.pobox.com', 'desktop-icons@csoriano']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'enable-animations' b'false'
  InstallationDate: Installed on 2019-02-18 (53 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.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/1824657/+subscriptions

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

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

[Steve Langasek]

Based on comment #12 I am not sure that this is considered
"verification-done" by the relevant developers and there was no comment
given when the tags were changed.  Resetting.

I also think there should be an affirmative test as part of this SRU
that the use case I described in comment #13 has not been regressed.

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

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

Title:
  Full-tunnel VPN DNS leakage regression

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

Bug description:
  * Impact

  When using a VPN the DNS requests might still be sent to a DNS server
  outside the VPN when they should not

  * Test case

  Configure the system to send all the traffic to a VPN, do a name
  resolution, the request should not go to the public DNS server (to be
  checked by capturing the traffic by example with wireshark)

  
  * Regression potential

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

  -

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

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

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

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

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

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

[Desktop-packages] [Bug 1760569] Re: Nautilus crashes in g_free -> g_bookmark_file_move_item -> gtk_recent_manager_move_item -> nautilus_recent_update_file_moved

[Mathew Hodson]

Does bionic need an update of nautilus as well?

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

Title:
  Nautilus crashes in g_free -> g_bookmark_file_move_item ->
  gtk_recent_manager_move_item -> nautilus_recent_update_file_moved

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  Fix Committed
Status in nautilus source package in Bionic:
  Invalid

Bug description:
  [ Description ]

  A crasher when using nautilus. No clear reproducer.

  [ QA ]

  Under the GNOME MRE, believe all bugs that upstream says are fixed are
  really fixed without explicitly verifying them.

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

  Make sure nautilus works, and that the error tracker buckets listed
  below at least don't increase more rapidly (but hopefully tail off
  with the new version)

  
  [ Regression potential ]

  It's GLib. A regression could break the whole desktop, or any part of
  it... Our QA should help us have confidence that the update is at
  least not that bad.

  [ Original description ]

  Happens when there's a "rename" to a file to its same value, no known
  reproducer though.

  Upstream fix: https://gitlab.gnome.org/GNOME/glib/merge_requests/456

  https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45
  https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9

  ProblemType: CrashDistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AssertionMessage: munmap_chunk(): invalid pointer
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  2 09:04:45 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'223'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+117+77'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2018-03-31 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8Signal: 6SourcePackage: nautilus
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f1a46fcfb9a 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7f1a46fd17a8 "munmap_chunk(): invalid 
pointer") at malloc.c:5350
   munmap_chunk (p=0x55f2e55b71f0) at malloc.c:2846
   __GI___libc_free (mem=0x55f2e55b7200) at malloc.c:3117
   g_bookmark_file_move_item () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus assert failure: munmap_chunk(): invalid pointer
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1760569/+subscriptions

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

[Desktop-packages] [Bug 1824657] [NEW] GNOME shell crash

[Emanuele]

Public bug reported:

I was watching a video on youtube with the Chromium snap browser, suddenly the 
GNOME shell crashed, no possibility to click for Chromium or other closure, but 
I managed to access a tty4 session, by pressing the keys: ctrl + alt + f4.
Using Ubuntu 19.04 from the beginning of development, first with KDE, after I 
install GNOME with the metapackage: sudo apt install ubuntu-desktop, 
eliminating any KDE package, until now I have had no problem.
full update, proposed repository disabled.
I attach the logs from the time I had the problem, about 10:50 pm, I started 
with the logs at 10:40 pm with this command: journalctl --since "2019-04-13 
22:40:00" ( if it is wrong, let him know)

>From the logs I see many gnome-shell errors, but obviously I can't
decipher them if it was the cause of the problem.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.32.0+git20190410-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
Uname: Linux 5.0.0-11-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 13 23:07:59 2019
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'app-picker-view' b'uint32 1'
 b'org.gnome.shell' b'favorite-apps' redacted by apport
 b'org.gnome.shell' b'enabled-extensions' 
b"['move_cl...@jonathan.bluemosh.com', 'openweather-extens...@jenslody.de', 
'sound-output-device-choo...@kgshank.net', 
'apps-m...@gnome-shell-extensions.gcampax.github.com', 
'applications_m...@rmy.pobox.com', 'gsconn...@andyholmes.github.io', 
'move_cl...@rmy.pobox.com', 'desktop-icons@csoriano']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.interface' b'enable-animations' b'false'
InstallationDate: Installed on 2019-02-18 (53 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.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 third-party-packages

** Attachment added: "log_freeze_desktop"
   
https://bugs.launchpad.net/bugs/1824657/+attachment/5255491/+files/log_freeze_desktop

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

Title:
  GNOME shell crash

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I was watching a video on youtube with the Chromium snap browser, suddenly 
the GNOME shell crashed, no possibility to click for Chromium or other closure, 
but I managed to access a tty4 session, by pressing the keys: ctrl + alt + f4.
  Using Ubuntu 19.04 from the beginning of development, first with KDE, after I 
install GNOME with the metapackage: sudo apt install ubuntu-desktop, 
eliminating any KDE package, until now I have had no problem.
  full update, proposed repository disabled.
  I attach the logs from the time I had the problem, about 10:50 pm, I started 
with the logs at 10:40 pm with this command: journalctl --since "2019-04-13 
22:40:00" ( if it is wrong, let him know)

  From the logs I see many gnome-shell errors, but obviously I can't
  decipher them if it was the cause of the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Uname: Linux 5.0.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 23:07:59 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.shell' b'enabled-extensions' 
b"['move_cl...@jonathan.bluemosh.com', 'openweather-extens...@jenslody.de', 
'sound-output-device-choo...@kgshank.net', 
'apps-m...@gnome-shell-extensions.gcampax.github.com', 
'applications_m...@rmy.pobox.com', 'gsconn...@andyholmes.github.io', 
'move_cl...@rmy.pobox.com', 'desktop-icons@csoriano']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'enable-animations' b'false'
  InstallationDate: Installed on 2019-02-18 (53 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.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/1824657/+subscriptions

-- 
Mailing list: https://laun

[Desktop-packages] [Bug 1811900] Re: SRU 3.28 latest git to bionic

[Mathew Hodson]

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

** Changed in: mutter (Ubuntu)
   Status: In Progress => Fix Released

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

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

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

Title:
  SRU 3.28 latest git to bionic

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

Bug description:
  [ Description ]

  3.28 gnome git branch has various upstream approved fixes for many
  months now, but no release has been done yet, thus we're releasing a
  git snapshot of the latest approved fixes.

  [ QA ]

  Run Ubuntu session, expect the shell to work normally with various
  setups

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

  [ Regresison potential ]

  Many patches we were including already have been included in upstream
  git now, various optimizations to clutter actors could cause drawing
  issues.

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

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

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

[Mathew Hodson]

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

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

Title:
  Full-tunnel VPN DNS leakage regression

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

Bug description:
  * Impact

  When using a VPN the DNS requests might still be sent to a DNS server
  outside the VPN when they should not

  * Test case

  Configure the system to send all the traffic to a VPN, do a name
  resolution, the request should not go to the public DNS server (to be
  checked by capturing the traffic by example with wireshark)

  
  * Regression potential

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

  -

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

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

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

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

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

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

[Desktop-packages] [Bug 1792017]

[Libreoffice-commits]

Takeshi Abe committed a patch related to this issue.
It has been pushed to "libreoffice-6-2":

https://git.libreoffice.org/core/+/64381dad01132f74e513c347db87f304d0e704ff%5E%21

tdf#119890 followup: Forbid HOME to be the default dir

It will be available in 6.2.4.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

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

Title:
  Default directory for my documents is not xdg-user-dir DOCUMENTS

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  The default working dir is hard coded to ~/Documents
  I had to redo my saved work, because I have assumed it was lost in ~/Dokumente

  I have now fixed this by changing the working directory manually.

  The default working dir should be changed to "xdg-user-dir DOCUMENTS"
  that other users so not suffer the same.

  I have updated from Xenial and never experienced these issues. Is it a
  kind of regression?

  libreoffice 1:6.0.3-0ubuntu1

  Ubuntu 18.04. LTS

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

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

[Desktop-packages] [Bug 1792017]

[Libreoffice-commits]

Takeshi Abe committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/+/88d46ba32e4a03d848d82210071c42208e0d6eca%5E%21

tdf#119890 followup: Forbid HOME to be the default dir

It will be available in 6.3.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

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

Title:
  Default directory for my documents is not xdg-user-dir DOCUMENTS

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  The default working dir is hard coded to ~/Documents
  I had to redo my saved work, because I have assumed it was lost in ~/Dokumente

  I have now fixed this by changing the working directory manually.

  The default working dir should be changed to "xdg-user-dir DOCUMENTS"
  that other users so not suffer the same.

  I have updated from Xenial and never experienced these issues. Is it a
  kind of regression?

  libreoffice 1:6.0.3-0ubuntu1

  Ubuntu 18.04. LTS

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

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

[Desktop-packages] [Bug 1735529] Re: Firefox incorrectly blacklists system for WebGL

[Stefano]

Same here, WebGL not activated. I'm trying to run scratch.mit.edu
programs.

No graphic card on this MSI U100 netbook, but there are the MESA
packages installed (libglx-mesa0, libgl1-mesa-dri,...)

error example in about config:
gfx.blacklist.webgl2.failureid;FEATURE_FAILURE_OPENGL_1

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

Title:
  Firefox incorrectly blacklists system for WebGL

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  This is with Ubuntu 16.04.

  Using the Ubuntu-provided Firefox 57.0, if I go to
  https://get.webgl.org/ I get the message:

  "Hmm. While your browser seems to support WebGL, it is disabled or
  unavailable. If possible, please ensure that you are running the
  latest drivers for your video card."

  In the JavaScript developer console there are some messages,
  including:

  "Error: WebGL warning: Failed to create WebGL context: WebGL creation failed: 
  * Refused to create native OpenGL context because of blacklist entry: 
FEATURE_FAILURE_OPENGL_1
  * Exhausted GL driver options."

  There are similar messages for WebGL in about:support.

  However if I download Firefox 57.0 from
  https://ftp.mozilla.org/pub/firefox/releases/57.0/linux-x86_64/en-
  US/firefox-57.0.tar.bz2 and use that to go to https://get.webgl.org/ ,
  I get the message "Your browser supports WebGL".

  So it looks like Ubuntu-provided Firefox has a problem while Mozilla-
  provided Firefox doesn't. (FYI, I reported a similar problem in
  https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1724705 , where
  DRM-protected content doesn't work with Ubuntu-provided Firefox but
  does work with Mozilla-provided Firefox.)

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

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

[Desktop-packages] [Bug 1824647] [NEW] Recurrent, annoying clicking sound but not showing any notifications

[Oregon TLC]

Public bug reported:

About two weeks ago, my computer began to make a recurrent, irregular,
clicking noise every few seconds.  It occurs regardless if the computer
is running on battery or electrical outlet.  There are no notifications
associated with this clicking noise.  Changing the notifications section
in systems does not stop this annoying clicking noise.  This noise
continues even when all browsers are shut off.  Only turning the volume
off stops the clicking noise.  I cannot watch movies or youtube without
hearing this annoying clicking noise.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
Uname: Linux 4.15.0-47-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  bob2260 F pulseaudio
 /dev/snd/controlC0:  bob2260 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 13 12:17:32 2019
InstallationDate: Installed on 2019-03-30 (14 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/18/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.26
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: EA50_HB
dmi.board.vendor: Acer
dmi.board.version: V1.26
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.26:bd12/18/2014:svnAcer:pnAspireE5-571:pvrV1.26:rvnAcer:rnEA50_HB:rvrV1.26:cvnAcer:ct10:cvrChassisVersion:
dmi.product.family: SharkBay System
dmi.product.name: Aspire E5-571
dmi.product.version: V1.26
dmi.sys.vendor: Acer

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  Recurrent, annoying clicking sound but not showing any notifications

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  About two weeks ago, my computer began to make a recurrent, irregular,
  clicking noise every few seconds.  It occurs regardless if the
  computer is running on battery or electrical outlet.  There are no
  notifications associated with this clicking noise.  Changing the
  notifications section in systems does not stop this annoying clicking
  noise.  This noise continues even when all browsers are shut off.
  Only turning the volume off stops the clicking noise.  I cannot watch
  movies or youtube without hearing this annoying clicking noise.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bob2260 F pulseaudio
   /dev/snd/controlC0:  bob2260 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 12:17:32 2019
  InstallationDate: Installed on 2019-03-30 (14 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.26
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA50_HB
  dmi.board.vendor: Acer
  dmi.board.version: V1.26
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.26:bd12/18/2014:svnAcer:pnAspireE5-571:pvrV1.26:rvnAcer:rnEA50_HB:rvrV1.26:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: SharkBay System
  dmi.product.name: Aspire E5-571
  dmi.product.version: V1.26
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1824641] Re: Blank screen after booting 4.4.0-145

[Tony Pursell]

Sorry I cannot collect log files for the kernel giving the bug.  If I
can collect any useful information using the kernel that does work,
please let me know

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

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1824641

Title:
  Blank screen after booting 4.4.0-145

Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual
  core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot
  this kernel everything is blank.  Just a black screen.  If I change to
  a terminal using Ctrl Alt F4 it is still a black screen but I can
  carefully type in my user name and password and then the shutdown
  command and it shuts down

  Using Advanced options in grub neither the upstart or the recovery
  option work.  The screen is still black.  The recovery option does,
  however, display the boot sequence before going black.

  I can boot the previous kernel 4.4.0-143 and all is OK.

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

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

[Desktop-packages] [Bug 1824641] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1824641

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Blank screen after booting 4.4.0-145

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

Bug description:
  Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual
  core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot
  this kernel everything is blank.  Just a black screen.  If I change to
  a terminal using Ctrl Alt F4 it is still a black screen but I can
  carefully type in my user name and password and then the shutdown
  command and it shuts down

  Using Advanced options in grub neither the upstart or the recovery
  option work.  The screen is still black.  The recovery option does,
  however, display the boot sequence before going black.

  I can boot the previous kernel 4.4.0-143 and all is OK.

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

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

[Desktop-packages] [Bug 1824641] Re: Blank screen after booting 4.4.0-145

[Tony Pursell]

Please not that Launchpad has automatically assigned this bug to mutter,
but mutter is not installed on the notebook in question, so I have added
linux

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

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

Title:
  Blank screen after booting 4.4.0-145

Status in linux package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual
  core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot
  this kernel everything is blank.  Just a black screen.  If I change to
  a terminal using Ctrl Alt F4 it is still a black screen but I can
  carefully type in my user name and password and then the shutdown
  command and it shuts down

  Using Advanced options in grub neither the upstart or the recovery
  option work.  The screen is still black.  The recovery option does,
  however, display the boot sequence before going black.

  I can boot the previous kernel 4.4.0-143 and all is OK.

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

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

[Desktop-packages] [Bug 1824641] [NEW] Blank screen after booting 4.4.0-145

[Tony Pursell]

Public bug reported:

Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual core
CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot this
kernel everything is blank.  Just a black screen.  If I change to a
terminal using Ctrl Alt F4 it is still a black screen but I can
carefully type in my user name and password and then the shutdown
command and it shuts down

Using Advanced options in grub neither the upstart or the recovery
option work.  The screen is still black.  The recovery option does,
however, display the boot sequence before going black.

I can boot the previous kernel 4.4.0-143 and all is OK.

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

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

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

Title:
  Blank screen after booting 4.4.0-145

Status in linux package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual
  core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot
  this kernel everything is blank.  Just a black screen.  If I change to
  a terminal using Ctrl Alt F4 it is still a black screen but I can
  carefully type in my user name and password and then the shutdown
  command and it shuts down

  Using Advanced options in grub neither the upstart or the recovery
  option work.  The screen is still black.  The recovery option does,
  however, display the boot sequence before going black.

  I can boot the previous kernel 4.4.0-143 and all is OK.

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

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

[Desktop-packages] [Bug 1824637] [NEW] Full load

[El jinete sin cabeza]

Public bug reported:

It always happens when I start the notebook. I must close it with 'kill
-u ProcessNumber'

Please indicate that more information is needed to repair this error.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: tracker 2.1.8-2
Uname: Linux 5.0.7-050007-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 13 12:42:44 2019
InstallationDate: Installed on 2018-12-02 (131 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: tracker
UpgradeStatus: Upgraded to disco on 2018-12-02 (131 days ago)

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


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

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

Title:
  Full load

Status in tracker package in Ubuntu:
  New

Bug description:
  It always happens when I start the notebook. I must close it with
  'kill -u ProcessNumber'

  Please indicate that more information is needed to repair this error.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: tracker 2.1.8-2
  Uname: Linux 5.0.7-050007-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 13 12:42:44 2019
  InstallationDate: Installed on 2018-12-02 (131 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to disco on 2018-12-02 (131 days ago)

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

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

[Desktop-packages] [Bug 1750264] Re: program 'cd-paranoia' is missing from package in 1.0.0-2

[Bug Watch Updater]

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

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

Title:
  program 'cd-paranoia' is missing from package in 1.0.0-2

Status in libcdio package in Ubuntu:
  Invalid
Status in libcdio-paranoia package in Ubuntu:
  Confirmed
Status in libcdio package in Debian:
  New

Bug description:
  apt show libcdio-utils:

  Description: sample applications based on the CDIO libraries
   This package contains a collection of small libcdio-based tools:
* cd-drive  show CD-ROM drive characteristics
* cd-info   show information about a CD or CD-image
* cd-paranoia   an audio CD ripper
* cd-read   read information from a CD or CD-image
* cdda-player   a simple curses-based audio CD player
* iso-info  show information about an ISO 9660 image
* iso-read  read portions of an ISO 9660 image
* mmc-tool  issue low-level commands to a CD drive

  cd-paranoia is missing from package. This breaks abcde 'optional'
  functionality which is in fact the most common used, since the
  original cdparanoia (separate program) is abandoned since 10 years.

  Description:Ubuntu Bionic Beaver (development branch)
  Release:18.04

  libcdio-utils:
Installiert:   1.0.0-2
Installationskandidat: 1.0.0-2
Versionstabelle:
   *** 1.0.0-2 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libcdio-utils 1.0.0-2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXQt
  Date: Sun Feb 18 18:18:55 2018
  ProcEnviron:
   TERM=qterminal
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: libcdio
  UpgradeStatus: Upgraded to bionic on 2017-06-03 (260 days ago)

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

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

[Desktop-packages] [Bug 1823550] Re: GtkSourceView wrongly has monospaced font in dropdown (context) menu

[Norbert]

Thanks, Khurshid!

I automated your method by

```
mkdir -p ~/.config/gtk-3.0

cat > ~/.config/gtk-3.0/gtk.css << EOF
.context-menu {
font-weight: medium;
font-family: regular;
}
EOF
```

and got almost normal context menu in Pluma.

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

Title:
  GtkSourceView wrongly has monospaced font in dropdown (context) menu

Status in GtkSourceView:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in gtksourceview3 package in Ubuntu:
  Invalid
Status in mate-themes package in Ubuntu:
  Confirmed
Status in pluma package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 17.04 or later installed
  2. Open any application with GtkSourceView component - such as Pluma, Gedit, 
Giggle, Gitg, gnome-builder and maybe others (see complete list with `apt-cache 
rdepends libgtksourceview-3.0-1`)
  3. Click right mouse button on text zone

  Expected result:
  * dropdown menu has normal font as all other interface elements

  Actual result:
  * dropdwon menu wrongly has monospaced font

  Notes:
  * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 
releases.
  * seems to be caused by GTK3 library

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pluma 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr  7 20:13:24 2019
  InstallationDate: Installed on 2018-08-07 (243 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pluma
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1823550] Re: GtkSourceView wrongly has monospaced font in dropdown (context) menu

[Khurshid Alam]

In lp: #1242984 light theme is already using (see
https://code.launchpad.net/~larsu/ubuntu-themes/gedit-
fixes/+merge/201212)

.context-menu { font: regular medium;}

not sure why it is not working. May be it needs to use font-family. So
changing it in ~/.config/gtk-3.0/gtk.css works for me.

.context-menu {
font-weight: medium;
font-family: regular;
}

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

Title:
  GtkSourceView wrongly has monospaced font in dropdown (context) menu

Status in GtkSourceView:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in gtksourceview3 package in Ubuntu:
  Invalid
Status in mate-themes package in Ubuntu:
  Confirmed
Status in pluma package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 17.04 or later installed
  2. Open any application with GtkSourceView component - such as Pluma, Gedit, 
Giggle, Gitg, gnome-builder and maybe others (see complete list with `apt-cache 
rdepends libgtksourceview-3.0-1`)
  3. Click right mouse button on text zone

  Expected result:
  * dropdown menu has normal font as all other interface elements

  Actual result:
  * dropdwon menu wrongly has monospaced font

  Notes:
  * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 
releases.
  * seems to be caused by GTK3 library

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pluma 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr  7 20:13:24 2019
  InstallationDate: Installed on 2018-08-07 (243 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pluma
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1811596] Re: Ubuntu Single Sign-On GUI not showing login button

[Khurshid Alam]

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

** Changed in: unity-control-center (Ubuntu)
   Status: Confirmed => Invalid

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

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

Title:
  Ubuntu  Single Sign-On GUI not showing  login button

Status in gnome-online-accounts package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Invalid

Bug description:
  System Settings->Online Accounts->Ubuntu Single Sign-On

  I can enter my email address and password abd select "I have an Ubuntu
  Single Sign-On account". But there is no "Save" or "Login" or any
  other button. I can only close the window.

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

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

[Desktop-packages] [Bug 1811596] Re: Ubuntu Single Sign-On GUI not showing login button

[Khurshid Alam]

Upstream bug: https://gitlab.gnome.org/GNOME/gnome-online-
accounts/issues/58

For workaround, run control center with csd enabled

GTK_CSD=1 unity-control-center

** Bug watch added: gitlab.gnome.org/GNOME/gnome-online-accounts/issues #58
   https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/58

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

Title:
  Ubuntu  Single Sign-On GUI not showing  login button

Status in gnome-online-accounts package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Invalid

Bug description:
  System Settings->Online Accounts->Ubuntu Single Sign-On

  I can enter my email address and password abd select "I have an Ubuntu
  Single Sign-On account". But there is no "Save" or "Login" or any
  other button. I can only close the window.

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

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

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

[Mario Vukelic]

Confirm that it also works with Cosmic on the Asus ZenBook Flip UX561UD from my 
comment #1
xkb-data 2.23.1-1ubuntu1.18.10.1

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

Title:
  KEY_RFKILL is not passed to userspace

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in xorgproto package in Ubuntu:
  Fix Released
Status in libxkbcommon source package in Bionic:
  Fix Released
Status in xkeyboard-config source package in Bionic:
  Fix Committed
Status in xorgproto source package in Bionic:
  Fix Released
Status in libxkbcommon source package in Cosmic:
  Fix Released
Status in xkeyboard-config source package in Cosmic:
  Fix Released
Status in xorgproto source package in Cosmic:
  Fix Released

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

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

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

  -

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

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

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

  - Likely other X11 packages need to be rebuilt.

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

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

[Desktop-packages] [Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.0.0-11.12

---
linux (5.0.0-11.12) disco; urgency=medium

  * linux: 5.0.0-11.12 -proposed tracker (LP: #1824383)

  * hns3: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1]
(LP: #1824194)
- net: hns3: fix for not calculating tx bd num correctly

  * disco: unable to use iptables/enable ufw under -virtual kernel
(LP: #1823862)
- [Packaging] add bpfilter to linux-modules

  * Make shiftfs a module rather than built-in (LP: #1824354)
- [Config] CONFIG_SHIFT_FS=m

  * shiftfs: chown sets untranslated ids in lower fs (LP: #1824350)
- SAUCE: shiftfs: use translated ids when chaning lower fs attrs

  * [Hyper-V] KVP daemon fails to start on first boot of disco VM (LP: #1820063)
- [Packaging] bind hv_kvp_daemon startup to hv_kvp device

linux (5.0.0-10.11) disco; urgency=medium

  * linux: 5.0.0-10.11 -proposed tracker (LP: #1823936)

  * Apparmor enforcement failure in lxc selftests (LP: #1823379)
- SAUCE: apparmor: Restore Y/N in /sys for apparmor's "enabled"

  * systemd cause kernel trace "BUG: unable to handle kernel paging request at
6db23a14" on Cosmic i386 (LP: #1813244)
- openvswitch: fix flow actions reallocation

linux (5.0.0-9.10) disco; urgency=medium

  * linux: 5.0.0-9.10 -proposed tracker (LP: #1823228)

  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
- [Packaging] update helper scripts
- [Packaging] resync retpoline extraction

  * Huawei Hi1822 NIC has poor performance (LP: #1820187)
- net-next/hinic: replace disable_irq_nosync/enable_irq

  * Add uid shifting overlay filesystem (shiftfs) (LP: #1823186)
- shiftfs: uid/gid shifting bind mount
- shiftfs: rework and extend
- shiftfs: support some btrfs ioctls
- [Config] enable shiftfs

  * Cannot boot or install - have to use nomodeset (LP: #1821820)
- Revert "drm/i915/fbdev: Actually configure untiled displays"

  * Disco update: v5.0.6 upstream stable release (LP: #1823060)
- netfilter: nf_tables: fix set double-free in abort path
- dccp: do not use ipv6 header for ipv4 flow
- genetlink: Fix a memory leak on error path
- gtp: change NET_UDP_TUNNEL dependency to select
- ipv6: make ip6_create_rt_rcu return ip6_null_entry instead of NULL
- mac8390: Fix mmio access size probe
- mISDN: hfcpci: Test both vendor & device ID for Digium HFC4S
- net: aquantia: fix rx checksum offload for UDP/TCP over IPv6
- net: datagram: fix unbounded loop in __skb_try_recv_datagram()
- net/packet: Set __GFP_NOWARN upon allocation in alloc_pg_vec
- net: phy: meson-gxl: fix interrupt support
- net: rose: fix a possible stack overflow
- net: stmmac: fix memory corruption with large MTUs
- net-sysfs: call dev_hold if kobject_init_and_add success
- net: usb: aqc111: Extend HWID table by QNAP device
- packets: Always register packet sk in the same order
- rhashtable: Still do rehash when we get EEXIST
- sctp: get sctphdr by offset in sctp_compute_cksum
- sctp: use memdup_user instead of vmemdup_user
- tcp: do not use ipv6 header for ipv4 flow
- tipc: allow service ranges to be connect()'ed on RDM/DGRAM
- tipc: change to check tipc_own_id to return in tipc_net_stop
- tipc: fix cancellation of topology subscriptions
- tun: properly test for IFF_UP
- vrf: prevent adding upper devices
- vxlan: Don't call gro_cells_destroy() before device is unregistered
- thunderx: enable page recycling for non-XDP case
- thunderx: eliminate extra calls to put_page() for pages held for recycling
- net: dsa: mv88e6xxx: fix few issues in mv88e6390x_port_set_cmode
- net: mii: Fix PAUSE cap advertisement from linkmode_adv_to_lcl_adv_t()
  helper
- net: phy: don't clear BMCR in genphy_soft_reset
- r8169: fix cable re-plugging issue
- ila: Fix rhashtable walker list corruption
- tun: add a missing rcu_read_unlock() in error path
- powerpc/fsl: Fix the flush of branch predictor.
- Btrfs: fix incorrect file size after shrinking truncate and fsync
- btrfs: remove WARN_ON in log_dir_items
- btrfs: don't report readahead errors and don't update statistics
- btrfs: Fix bound checking in qgroup_trace_new_subtree_blocks
- btrfs: Avoid possible qgroup_rsv_size overflow in
  btrfs_calculate_inode_block_rsv_size
- Btrfs: fix assertion failure on fsync with NO_HOLES enabled
- locks: wake any locks blocked on request before deadlock check
- tracing: initialize variable in create_dyn_event()
- ARM: imx6q: cpuidle: fix bug that CPU might not wake up at expected time
- powerpc: bpf: Fix generation of load/store DW instructions
- vfio: ccw: only free cp on final interrupt
- NFS: Fix nfs4_lock_state refcounting in nfs4_alloc_{lock,unlock}data()
- NFS: fix mount/umount race in nlmclnt.
- NFSv4.1 don't free interrupted slot on open
- net: dsa: qca8k: 

[Desktop-packages] [Bug 1821863] Re: Need to add Intel CML related pci-id's

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.0.0-11.12

---
linux (5.0.0-11.12) disco; urgency=medium

  * linux: 5.0.0-11.12 -proposed tracker (LP: #1824383)

  * hns3: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1]
(LP: #1824194)
- net: hns3: fix for not calculating tx bd num correctly

  * disco: unable to use iptables/enable ufw under -virtual kernel
(LP: #1823862)
- [Packaging] add bpfilter to linux-modules

  * Make shiftfs a module rather than built-in (LP: #1824354)
- [Config] CONFIG_SHIFT_FS=m

  * shiftfs: chown sets untranslated ids in lower fs (LP: #1824350)
- SAUCE: shiftfs: use translated ids when chaning lower fs attrs

  * [Hyper-V] KVP daemon fails to start on first boot of disco VM (LP: #1820063)
- [Packaging] bind hv_kvp_daemon startup to hv_kvp device

linux (5.0.0-10.11) disco; urgency=medium

  * linux: 5.0.0-10.11 -proposed tracker (LP: #1823936)

  * Apparmor enforcement failure in lxc selftests (LP: #1823379)
- SAUCE: apparmor: Restore Y/N in /sys for apparmor's "enabled"

  * systemd cause kernel trace "BUG: unable to handle kernel paging request at
6db23a14" on Cosmic i386 (LP: #1813244)
- openvswitch: fix flow actions reallocation

linux (5.0.0-9.10) disco; urgency=medium

  * linux: 5.0.0-9.10 -proposed tracker (LP: #1823228)

  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
- [Packaging] update helper scripts
- [Packaging] resync retpoline extraction

  * Huawei Hi1822 NIC has poor performance (LP: #1820187)
- net-next/hinic: replace disable_irq_nosync/enable_irq

  * Add uid shifting overlay filesystem (shiftfs) (LP: #1823186)
- shiftfs: uid/gid shifting bind mount
- shiftfs: rework and extend
- shiftfs: support some btrfs ioctls
- [Config] enable shiftfs

  * Cannot boot or install - have to use nomodeset (LP: #1821820)
- Revert "drm/i915/fbdev: Actually configure untiled displays"

  * Disco update: v5.0.6 upstream stable release (LP: #1823060)
- netfilter: nf_tables: fix set double-free in abort path
- dccp: do not use ipv6 header for ipv4 flow
- genetlink: Fix a memory leak on error path
- gtp: change NET_UDP_TUNNEL dependency to select
- ipv6: make ip6_create_rt_rcu return ip6_null_entry instead of NULL
- mac8390: Fix mmio access size probe
- mISDN: hfcpci: Test both vendor & device ID for Digium HFC4S
- net: aquantia: fix rx checksum offload for UDP/TCP over IPv6
- net: datagram: fix unbounded loop in __skb_try_recv_datagram()
- net/packet: Set __GFP_NOWARN upon allocation in alloc_pg_vec
- net: phy: meson-gxl: fix interrupt support
- net: rose: fix a possible stack overflow
- net: stmmac: fix memory corruption with large MTUs
- net-sysfs: call dev_hold if kobject_init_and_add success
- net: usb: aqc111: Extend HWID table by QNAP device
- packets: Always register packet sk in the same order
- rhashtable: Still do rehash when we get EEXIST
- sctp: get sctphdr by offset in sctp_compute_cksum
- sctp: use memdup_user instead of vmemdup_user
- tcp: do not use ipv6 header for ipv4 flow
- tipc: allow service ranges to be connect()'ed on RDM/DGRAM
- tipc: change to check tipc_own_id to return in tipc_net_stop
- tipc: fix cancellation of topology subscriptions
- tun: properly test for IFF_UP
- vrf: prevent adding upper devices
- vxlan: Don't call gro_cells_destroy() before device is unregistered
- thunderx: enable page recycling for non-XDP case
- thunderx: eliminate extra calls to put_page() for pages held for recycling
- net: dsa: mv88e6xxx: fix few issues in mv88e6390x_port_set_cmode
- net: mii: Fix PAUSE cap advertisement from linkmode_adv_to_lcl_adv_t()
  helper
- net: phy: don't clear BMCR in genphy_soft_reset
- r8169: fix cable re-plugging issue
- ila: Fix rhashtable walker list corruption
- tun: add a missing rcu_read_unlock() in error path
- powerpc/fsl: Fix the flush of branch predictor.
- Btrfs: fix incorrect file size after shrinking truncate and fsync
- btrfs: remove WARN_ON in log_dir_items
- btrfs: don't report readahead errors and don't update statistics
- btrfs: Fix bound checking in qgroup_trace_new_subtree_blocks
- btrfs: Avoid possible qgroup_rsv_size overflow in
  btrfs_calculate_inode_block_rsv_size
- Btrfs: fix assertion failure on fsync with NO_HOLES enabled
- locks: wake any locks blocked on request before deadlock check
- tracing: initialize variable in create_dyn_event()
- ARM: imx6q: cpuidle: fix bug that CPU might not wake up at expected time
- powerpc: bpf: Fix generation of load/store DW instructions
- vfio: ccw: only free cp on final interrupt
- NFS: Fix nfs4_lock_state refcounting in nfs4_alloc_{lock,unlock}data()
- NFS: fix mount/umount race in nlmclnt.
- NFSv4.1 don't free interrupted slot on open
- net: dsa: qca8k: 

[Desktop-packages] [Bug 1821820] Re: Cannot boot or install - have to use nomodeset

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.0.0-11.12

---
linux (5.0.0-11.12) disco; urgency=medium

  * linux: 5.0.0-11.12 -proposed tracker (LP: #1824383)

  * hns3: PPU_PF_ABNORMAL_INT_ST over_8bd_no_fe found [error status=0x1]
(LP: #1824194)
- net: hns3: fix for not calculating tx bd num correctly

  * disco: unable to use iptables/enable ufw under -virtual kernel
(LP: #1823862)
- [Packaging] add bpfilter to linux-modules

  * Make shiftfs a module rather than built-in (LP: #1824354)
- [Config] CONFIG_SHIFT_FS=m

  * shiftfs: chown sets untranslated ids in lower fs (LP: #1824350)
- SAUCE: shiftfs: use translated ids when chaning lower fs attrs

  * [Hyper-V] KVP daemon fails to start on first boot of disco VM (LP: #1820063)
- [Packaging] bind hv_kvp_daemon startup to hv_kvp device

linux (5.0.0-10.11) disco; urgency=medium

  * linux: 5.0.0-10.11 -proposed tracker (LP: #1823936)

  * Apparmor enforcement failure in lxc selftests (LP: #1823379)
- SAUCE: apparmor: Restore Y/N in /sys for apparmor's "enabled"

  * systemd cause kernel trace "BUG: unable to handle kernel paging request at
6db23a14" on Cosmic i386 (LP: #1813244)
- openvswitch: fix flow actions reallocation

linux (5.0.0-9.10) disco; urgency=medium

  * linux: 5.0.0-9.10 -proposed tracker (LP: #1823228)

  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
- [Packaging] update helper scripts
- [Packaging] resync retpoline extraction

  * Huawei Hi1822 NIC has poor performance (LP: #1820187)
- net-next/hinic: replace disable_irq_nosync/enable_irq

  * Add uid shifting overlay filesystem (shiftfs) (LP: #1823186)
- shiftfs: uid/gid shifting bind mount
- shiftfs: rework and extend
- shiftfs: support some btrfs ioctls
- [Config] enable shiftfs

  * Cannot boot or install - have to use nomodeset (LP: #1821820)
- Revert "drm/i915/fbdev: Actually configure untiled displays"

  * Disco update: v5.0.6 upstream stable release (LP: #1823060)
- netfilter: nf_tables: fix set double-free in abort path
- dccp: do not use ipv6 header for ipv4 flow
- genetlink: Fix a memory leak on error path
- gtp: change NET_UDP_TUNNEL dependency to select
- ipv6: make ip6_create_rt_rcu return ip6_null_entry instead of NULL
- mac8390: Fix mmio access size probe
- mISDN: hfcpci: Test both vendor & device ID for Digium HFC4S
- net: aquantia: fix rx checksum offload for UDP/TCP over IPv6
- net: datagram: fix unbounded loop in __skb_try_recv_datagram()
- net/packet: Set __GFP_NOWARN upon allocation in alloc_pg_vec
- net: phy: meson-gxl: fix interrupt support
- net: rose: fix a possible stack overflow
- net: stmmac: fix memory corruption with large MTUs
- net-sysfs: call dev_hold if kobject_init_and_add success
- net: usb: aqc111: Extend HWID table by QNAP device
- packets: Always register packet sk in the same order
- rhashtable: Still do rehash when we get EEXIST
- sctp: get sctphdr by offset in sctp_compute_cksum
- sctp: use memdup_user instead of vmemdup_user
- tcp: do not use ipv6 header for ipv4 flow
- tipc: allow service ranges to be connect()'ed on RDM/DGRAM
- tipc: change to check tipc_own_id to return in tipc_net_stop
- tipc: fix cancellation of topology subscriptions
- tun: properly test for IFF_UP
- vrf: prevent adding upper devices
- vxlan: Don't call gro_cells_destroy() before device is unregistered
- thunderx: enable page recycling for non-XDP case
- thunderx: eliminate extra calls to put_page() for pages held for recycling
- net: dsa: mv88e6xxx: fix few issues in mv88e6390x_port_set_cmode
- net: mii: Fix PAUSE cap advertisement from linkmode_adv_to_lcl_adv_t()
  helper
- net: phy: don't clear BMCR in genphy_soft_reset
- r8169: fix cable re-plugging issue
- ila: Fix rhashtable walker list corruption
- tun: add a missing rcu_read_unlock() in error path
- powerpc/fsl: Fix the flush of branch predictor.
- Btrfs: fix incorrect file size after shrinking truncate and fsync
- btrfs: remove WARN_ON in log_dir_items
- btrfs: don't report readahead errors and don't update statistics
- btrfs: Fix bound checking in qgroup_trace_new_subtree_blocks
- btrfs: Avoid possible qgroup_rsv_size overflow in
  btrfs_calculate_inode_block_rsv_size
- Btrfs: fix assertion failure on fsync with NO_HOLES enabled
- locks: wake any locks blocked on request before deadlock check
- tracing: initialize variable in create_dyn_event()
- ARM: imx6q: cpuidle: fix bug that CPU might not wake up at expected time
- powerpc: bpf: Fix generation of load/store DW instructions
- vfio: ccw: only free cp on final interrupt
- NFS: Fix nfs4_lock_state refcounting in nfs4_alloc_{lock,unlock}data()
- NFS: fix mount/umount race in nlmclnt.
- NFSv4.1 don't free interrupted slot on open
- net: dsa: qca8k: 

[Desktop-packages] [Bug 1824497] Re: unable to copy small files with nautilus on cifs mount

[Alain DELANGE]

Transferred to this location :

https://gitlab.gnome.org/GNOME/gvfs/issues/392
"gio copy and nautilus hang when copying small files on cifs shares on ubuntu 
18.04"

hope this will help

ad.

** Bug watch added: gitlab.gnome.org/GNOME/gvfs/issues #392
   https://gitlab.gnome.org/GNOME/gvfs/issues/392

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

Title:
  unable to copy small files with nautilus on cifs mount

Status in nautilus package in Ubuntu:
  New

Bug description:
  I have this bug on two different computers with ubuntu 18.04
  I never encounter this this 16.04 and any previous releases

  I am working on a web site with many (twenty) small php files (less
  than 100bytes)

  When I copy paste the full www folder nautilus hangs on a certain file, a 
small one...
  When I copy paste one small file from a subfolder of www to an other sufolder 
it hangs

  I got the message :
  Copie de index.php vers pictures
  0 octet / 65 octets - environ 596 523 heures restantes

  Sometimes I got a 0 byte in my folder which is hard to remove even on
  terminal

  But If I do a paste again, just after the stall, I got from nautilus
  the message the file exists and if I "replace" it works.

  Copying/pasting a file in the same folder don't work at all :
  Duplication de index.php
  0 octet / 65 octets - environ 596 523 heures restantes

  *
  context :
  I am working with different computers physicals and virtualbox on these files 
with absolutely no problems
  The configuration is always the same:
  My cifs mount are mounted with autofs on /home/ad/auto
  I have something like that in autofd configuration files:

  moi -fstype=cifs,credentials=/home/ad/.credentials/ad-
  credentials,iocharset=utf8 ://192.168.1.20/ad_moi

  I have the problem when I am on the same computer, the one with samba server, 
in this case I have
  127.0.0.1 instead of 192.168.1.20in config files.

  The problem is not with autofs. I can get it without it...

  I can reproduce it on an other computer with ubuntu 19.10
  the copy/paste of www hangs on the first file : a 388 bytes png file

  copying with terminal with cp works fine

  ***

  lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  apt-cache policy nautilus
  nautilus:
Installé : 1:3.26.4-0~ubuntu18.04.4
Candidat : 1:3.26.4-0~ubuntu18.04.4
   Table de version :
   *** 1:3.26.4-0~ubuntu18.04.4 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.26.3-0ubuntu4 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  I hope this bug will be solved soon !

  thank you

  ad.

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

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

[Desktop-packages] [Bug 1811596] Re: Ubuntu Single Sign-On GUI not showing login button

[Cigar Zh]

This bug seems like only in a unity session and the UI is normal in a ubuntu 
session.
Someone mentioned it there 
https://community.ubuntu.com/t/testing-unity-session-in-18-04/987/156

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

Title:
  Ubuntu  Single Sign-On GUI not showing  login button

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

Bug description:
  System Settings->Online Accounts->Ubuntu Single Sign-On

  I can enter my email address and password abd select "I have an Ubuntu
  Single Sign-On account". But there is no "Save" or "Login" or any
  other button. I can only close the window.

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

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

[Desktop-packages] [Bug 1811596] Re: Ubuntu Single Sign-On GUI not showing login button

[Launchpad Bug Tracker]

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

** Changed in: unity-control-center (Ubuntu)
   Status: New => Confirmed

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

Title:
  Ubuntu  Single Sign-On GUI not showing  login button

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

Bug description:
  System Settings->Online Accounts->Ubuntu Single Sign-On

  I can enter my email address and password abd select "I have an Ubuntu
  Single Sign-On account". But there is no "Save" or "Login" or any
  other button. I can only close the window.

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

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

[Desktop-packages] [Bug 1768597] Re: [needs-packaging] package filemanager-actions missing

[Bug Watch Updater]

** Changed in: filemanager-actions (Debian)
   Status: New => Fix Released

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

Title:
  [needs-packaging] package filemanager-actions missing

Status in filemanager-actions package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Invalid
Status in filemanager-actions package in Debian:
  Fix Released

Bug description:
  nautilus-actions was deprecated in favour of filemanager-actions (see
  https://github.com/GNOME/nautilus-actions ).

  But 18.04 repositories do not have either of the packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/filemanager-actions/+bug/1768597/+subscriptions

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

[Desktop-packages] [Bug 1821820] Re: Cannot boot or install - have to use nomodeset

[Timo Aaltonen]

the reason why it hasn't landed yet is that there have been other bugs
that meant the kernel had to be respun a few times, but 5.0.0-11.12 is
finally in proposed and should be the final kernel for the release..

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

Title:
  Cannot boot or install - have to use nomodeset

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Fix Committed

Bug description:
  On this 19.04 beta I have to use nomodeset to boot & install Ubuntu
  Budgie.

  This is different behaviour from 18.04 and 18.10 where it booted and
  installed just fine without nomodeset.

  Without nomodeset, grub/efi disappears, and after a while a solid
  rather than blinking cursor on a black screen is seen.  It does not
  boot into a live session, nor displays the ubiquity window

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 26 23:40:49 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf]
  InstallationDate: Installed on 2019-03-26 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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