date:20180614

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

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

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

Title:
  Launcher Type=link, can not be opened with other application

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  If you right click on a desktop launcher and select an application to
  launch it e.g. Text Editor, some launchers do not populate the
  application. For example:

  [Desktop Entry]
  Encoding=UTF-8
  Name=Calendar
  Type=Link
  URL=https://calendar.google.com/calendar/render?tab=mc#main_7
  Icon=/home/rob/user1/Graphics/calendar.png

  This happens in both budgie and gnome shell on 17.04. If you change
  the file name from calendar.desktop to calendar.txt it works
  correctly.

  Secondly, if you look at the permissions for this type of launcher,
  you get the message "The permissions of "ServiceLogin" could not be
  determined."

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: nautilus 1:3.20.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sun Apr  9 13:21:05 2017
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
   b'org.gnome.nautilus.preferences' b'show-create-link' b'true'
   b'org.gnome.nautilus.window-state' b'geometry' b"'965x550+0+32'"
   b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'true'
   b'org.gnome.nautilus.desktop' b'volumes-visible' b'true'
  InstallationDate: Installed on 2017-02-08 (60 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Alpha amd64 (20170208)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu7

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

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

[Desktop-packages] [Bug 1762168] Re: package libmutter-1-0:amd64 (not installed) failed to install/upgrade: no package named 'libmutter-1-0:amd64' is installed, cannot configure

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

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

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

Title:
  package libmutter-1-0:amd64 (not installed) failed to install/upgrade:
  no package named 'libmutter-1-0:amd64' is installed, cannot configure

Status in mutter package in Ubuntu:
  Expired

Bug description:
  package libmutter-1-0:amd64 (not installed) failed to install/upgrade:
  no package named 'libmutter-1-0:amd64' is installed, cannot configure

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libmutter-1-0:amd64 (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Apr  8 17:49:30 2018
  ErrorMessage: no package named 'libmutter-1-0:amd64' is installed, cannot 
configure
  InstallationDate: Installed on 2018-03-31 (8 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: mutter
  Title: package libmutter-1-0:amd64 (not installed) failed to install/upgrade: 
no package named 'libmutter-1-0:amd64' is installed, cannot configure
  UpgradeStatus: Upgraded to artful on 2018-04-08 (0 days ago)

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

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

[Desktop-packages] [Bug 1776901] Re: Startup or Reboot GDM3 Keyboard/Mouse Not Working

It sounds like you mean you just can't click on things.

There is a whole family of those bugs to check out here:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bugs?field.tag=noclick
https://bugs.launchpad.net/ubuntu/+source/mutter/+bugs?field.tag=noclick

** Tags added: noclick

** Also 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/1776901

Title:
  Startup or Reboot GDM3 Keyboard/Mouse Not Working

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

Bug description:
  I don't reboot often due to running LTS. However over the past month
  or so, on subsequent reboots after upgrades, GDM3 accepts focus but
  won't accept any input either from keyboard or mouse.

  The work-a-round that works for me is to 'Ctl+Alt+F(number) to get to
  a console, which won't give me a login prompt until I hit the 'return'
  key. Then I can go back to the GDM3 session and login normally.

  I'm reporting this from Vanilla Gnome Ubuntu 18.04, all current
  updates applied.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 
4.15.0-20201805060708.0+mediatree+hauppauge-generic 4.15.17
  Uname: Linux 4.15.0-20201805060708-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jun 14 08:44:36 2018
  InstallationDate: Installed on 2018-01-19 (146 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 889889] Re: Use PNG or SVG instead of GIF

2018-06-14 Thread Nazo

$ dpkg -L blender | grep \\.gif
$ dpkg -L blender-data | grep \\.gif

no more gifs in blender

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

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

Title:
  Use PNG or SVG instead of GIF

Status in Adium Theme Ubuntu:
  Fix Released
Status in OpenSSL:
  New
Status in ace package in Ubuntu:
  New
Status in app-install-data-ubuntu package in Ubuntu:
  Confirmed
Status in blender package in Ubuntu:
  Fix Released
Status in chardet package in Ubuntu:
  New
Status in cups package in Ubuntu:
  New
Status in dvd+rw-tools package in Ubuntu:
  New
Status in foo2zjs package in Ubuntu:
  New
Status in libcgi-pm-perl package in Ubuntu:
  New
Status in openssl package in Ubuntu:
  Won't Fix
Status in python3.4 package in Ubuntu:
  Won't Fix
Status in software-center package in Ubuntu:
  Invalid

Bug description:
  Use modern file formats such as PNG or SVG instead of the legacy GIF
  file formats.

  $ find /usr -name "*.gif"

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

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

[Desktop-packages] [Bug 1776916] Re: gnome-shell crashed with SIGSEGV [Creating pipes for GWakeup: Too many open files]

Or just keep an eye on the list of descriptors in:

/proc/PIDOFGNOMESHELL/fd/

and see if it grows with any duplicates.

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

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

Title:
  gnome-shell crashed with SIGSEGV [Creating pipes for GWakeup: Too many
  open files]

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Crashed when changing the volume with the keyboard's function keys.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 14 15:41:10 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-07-15 (1430 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f3548500351:rep movsq %ds:(%rsi),%es:(%rdi)
   PC (0x7f3548500351) ok
   source "%ds:(%rsi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%es:(%rdi)" (0x7f34c56fd7e0) ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_new () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_initable_new_valist () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_initable_new () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: Upgraded to cosmic on 2018-03-24 (81 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

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

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

[Desktop-packages] [Bug 1776916] Re: gnome-shell crashed with SIGSEGV [Creating pipes for GWakeup: Too many open files\n"]

jibel, it sounds like you might have a file descriptor leak, which is
something I don't ever recall seeing in gnome-shell before.

If you can reproduce the issue in future then please try eliminating
extensions:

b'org.gnome.shell' b'enabled-extensions' b"['alternate-tab@gnome-shell-
extensions.gcampax.github.com', 'bettervol...@tudmotu.com', 'dash-to-
d...@micxgx.gmail.com', 'mediapla...@patapon.info',
'nohotcor...@azuri.free.fr', 'sound-output-device-choo...@kgshank.net',
'topic...@phocean.net', 'system-moni...@paradoxxx.zero.gmail.com',
'ubuntu-appindicat...@ubuntu.com', 'ubuntu-d...@ubuntu.com']"

** Summary changed:

- gnome-shell crashed with SIGSEGV
+ gnome-shell crashed with SIGSEGV [Creating pipes for GWakeup: Too many open 
files\n"]

** Summary changed:

- gnome-shell crashed with SIGSEGV [Creating pipes for GWakeup: Too many open 
files\n"]
+ gnome-shell crashed with SIGSEGV [Creating pipes for GWakeup: Too many open 
files]

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

Title:
  gnome-shell crashed with SIGSEGV [Creating pipes for GWakeup: Too many
  open files]

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Crashed when changing the volume with the keyboard's function keys.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 14 15:41:10 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-07-15 (1430 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f3548500351:rep movsq %ds:(%rsi),%es:(%rdi)
   PC (0x7f3548500351) ok
   source "%ds:(%rsi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%es:(%rdi)" (0x7f34c56fd7e0) ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_new () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_initable_new_valist () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_initable_new () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: Upgraded to cosmic on 2018-03-24 (81 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

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

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

[Desktop-packages] [Bug 1768588] Re: Blender is missing parts of the "System" tab panel and some configurations.

2018-06-14 Thread Nazo

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

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

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

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

Title:
  Blender is missing parts of the "System" tab panel and some
  configurations.

Status in blender package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  (*)Ubuntu 18.04 (any flavor).

  Blender 3D Modeler is missing 2/3 the "System tab" panel options
  regarding to OpenGL, localization, font overrides, translations, lamp
  directions and options to use custom colors for bone weights.

  Since 18.04 beta 1 and 2, I have been comparing the blender 2.79b
  present at the 18.04LTS obtained via apt-get to the one downloaded
  directly from Blender Foundation. If you install Blender from apt-get
  first, and then download and extract Blender from Blender Foundation
  in any folder, running the software you can go to the "User
  preference" options using CTRL U, and navigate to the "System tab"
  options.

  Now, compare the system tab of both. 2/3 of the options are missing in
  the default apt-get (*)ubuntu install.

  Many thanks for fixing this !

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

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

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

Such freezes are more likely a kernel issue. Do you have any sign of
life from the machine when frozen, like being able to login remotely?

Please try installing 'openssh-server' and see if you can still log in
to that when it appears frozen.

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Summary changed:

- Xorg freeze
+ Xorg freeze after wakeup from hibernate

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

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

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

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

Title:
  Xorg freeze after wakeup from hibernate

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Happens mostly after wakeup from hibernate

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jun 15 03:21:59 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: bbswitch, 0.8, 4.13.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:837f]
 Subsystem: Hewlett-Packard Company Device [103c:8380]
  InstallationDate: Installed on 2018-02-13 (121 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: HP HP ProBook 470 G5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed 
root=UUID=0f2b268a-ea3c-40bf-a329-13b1447b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2017
  dmi.bios.vendor: HP
  dmi.bios.version: Q85 Ver. 01.01.07
  dmi.board.name: 837F
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 02.21.00
  dmi.chassis.asset.tag: 5CD7497QSD
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ85Ver.01.01.07:bd10/17/2017:svnHP:pnHPProBook470G5:pvr:rvnHP:rn837F:rvrKBCVersion02.21.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 470 G5
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Jun 15 03:21:12 2018
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

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

2018-06-14 Thread Joe Mau

Public bug reported:

Happens mostly after wakeup from hibernate

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-43-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Jun 15 03:21:59 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: bbswitch, 0.8, 4.13.0-43-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a week
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Within the last week or two
GraphicsCard:
 Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:837f]
   Subsystem: Hewlett-Packard Company Device [103c:8380]
InstallationDate: Installed on 2018-02-13 (121 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: HP HP ProBook 470 G5
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed 
root=UUID=0f2b268a-ea3c-40bf-a329-13b1447b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2017
dmi.bios.vendor: HP
dmi.bios.version: Q85 Ver. 01.01.07
dmi.board.name: 837F
dmi.board.vendor: HP
dmi.board.version: KBC Version 02.21.00
dmi.chassis.asset.tag: 5CD7497QSD
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrQ85Ver.01.01.07:bd10/17/2017:svnHP:pnHPProBook470G5:pvr:rvnHP:rn837F:rvrKBCVersion02.21.00:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ProBook
dmi.product.name: HP ProBook 470 G5
dmi.sys.vendor: HP
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Fri Jun 15 03:21:12 2018
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: modeset

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


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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Happens mostly after wakeup from hibernate

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jun 15 03:21:59 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: bbswitch, 0.8, 4.13.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:837f]
 Subsystem: Hewlett-Packard Company Device [103c:8380]
  InstallationDate: Installed on 2018-02-13 (121 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: HP HP ProBook 470 G5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed 
root=UUID=0f2b268a-ea3c-40bf-a329-13b1447b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log

[Desktop-packages] [Bug 1777018] Re: gnome-terminal-server crashed with SIGSEGV in gdk_display_get_event()

2018-06-14 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1664613, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1777018/+attachment/5152784/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1777018/+attachment/5152786/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1777018/+attachment/5152789/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1777018/+attachment/5152790/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1777018/+attachment/5152791/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1777018/+attachment/5152792/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1777018/+attachment/5152793/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1664613

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-terminal-server crashed with SIGSEGV in gdk_display_get_event()

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I wish I could provide more details, but as best I can tell everything
  just froze and apport started consuming 100% of my CPU. The display no
  longer updated but I could access a VTTY. Until I killed apport I
  could do nothing at all.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 14 20:38:00 2018
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2017-05-28 (382 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f3ce7c2f618:mov0x90(%r14),%rsi
   PC (0x7f3ce7c2f618) ok
   source "0x90(%r14)" (0x0090) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-terminal
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-terminal-server crashed with SIGSEGV in gdk_display_get_event()
  UpgradeStatus: Upgraded to bionic on 2018-05-13 (32 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1777013] Re: /usr/bin/nautilus:11:g_type_check_instance:g_signal_connect_data:set_pending_icon_to_reveal:end_renaming_mode:nautilus_canvas_container_clear

2018-06-14 Thread Brian Murray

This are still occurring quite regularly on an LTS release, Ubuntu
16.04, of Ubuntu.

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

Title:
  
/usr/bin/nautilus:11:g_type_check_instance:g_signal_connect_data:set_pending_icon_to_reveal:end_renaming_mode:nautilus_canvas_container_clear

Status in nautilus package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
nautilus.  This problem was most recently seen with package version 
1:3.18.4.is.3.14.3-0ubuntu6, the problem page at 
https://errors.ubuntu.com/problem/0e3038b0c9af56d760909f8c27a8d125eb09d8dc 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1777013] [NEW] /usr/bin/nautilus:11:g_type_check_instance:g_signal_connect_data:set_pending_icon_to_reveal:end_renaming_mode:nautilus_canvas_container_clear

2018-06-14 Thread errors.ubuntu.com bug bridge

Public bug reported:

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

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


** Tags: kylin-14.10 kylin-15.04 raring saucy trusty utopic vivid wily xenial

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

Title:
  
/usr/bin/nautilus:11:g_type_check_instance:g_signal_connect_data:set_pending_icon_to_reveal:end_renaming_mode:nautilus_canvas_container_clear

Status in nautilus package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
nautilus.  This problem was most recently seen with package version 
1:3.18.4.is.3.14.3-0ubuntu6, the problem page at 
https://errors.ubuntu.com/problem/0e3038b0c9af56d760909f8c27a8d125eb09d8dc 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1761554] Re: [bionic] Extended characters in GNOME screen keyboard don't get entered

2018-06-14 Thread Gunnar Hjalmarsson

Installed im-config 0.34-1ubuntu1.2 from bionic-proposed, rebooted, and
started a Wayland session. Could input Japanese and Chinese characters
in LO Writer using ibus-mozc respective ibus-libpinyin without LO Writer
crashing, so this version fixes the regression reported in comment #17.

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

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

Title:
  [bionic] Extended characters in GNOME screen keyboard don't get
  entered

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-user-docs package in Ubuntu:
  New
Status in im-config package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Triaged
Status in gnome-user-docs source package in Bionic:
  New
Status in im-config source package in Bionic:
  Fix Committed

Bug description:
  im-config SRU request
  =

  [Impact]

  When in a Wayland session, accented characters as well as some special
  characters can't be entered via the screen keyboard. The issue is
  fixed via the proposed upload of im-config, which has been changed to
  not set the GTK_IM_MODULE environment variable for IBus on Wayland
  (previously GTK_IM_MODULE was set to "ibus").

  Making this accessibility tool work without issues on Wayland is
  important enough to justify this SRU.

  [Test Case]

  1. Log in to an Ubuntu on Wayland session

  2. Open gedit and enable the screen keyboard
 (Settings -> Universal Access -> Typing)

  -> Accented characters via long-press does not work.
 Example: long-press a and select à from the popup

 Also, certain keys for special characters result in incorrect
 characters or nothing. Examples: ~, √, ÷, ×, <, >, ¢

  3. Install im-config from bionic-proposed

  4. Relogin and repeat step 2.

  -> Everything works as expected

  [Regression Potential]

  There are reasons to presuppose that GTK_IM_MODULE does not need to be
  set at all for IBus on a GNOME desktop:

  * GTK has a mechanism for selecting a built-in IM.

  * IBus is default in GNOME, and vanilla GNOME (which does not make use
of im-config) does not set the GTK_IM_MODULE environment variable.

  But the change is only made for Wayland sessions, which is not default
  in 18.04. Given this limitation, the regression risk is deemed to be
  low.

  [Original description]

  I filed this bug upstream last month but it hasn't gotten much
  attention so I'm filing it here because I think we need to track this
  issue for the Ubuntu 18.04 release

  https://gitlab.gnome.org/GNOME/gnome-shell/issues/109

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

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

  Nothing is entered in Step 5.

  This bug affects any of the "extended characters" clicked on from the
  long-press popup in the Screen Keyboard.

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

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

[Desktop-packages] [Bug 698244] Re: Right hand scroll bar causes screen to go black

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.
Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.
Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011.
Ubuntu 9.04 (jaunty) reached end-of-life on October 23, 2010.
Ubuntu 8.10 (intrepid) reached end-of-life on April 30, 2010.
Ubuntu 8.04 (hardy) reached end-of-life on May 12, 2011.
Ubuntu 7.10 (gutsy) reached end-of-life on April 18th, 2009.
Ubuntu 7.04 (feisty) reached end-of-life on October 19, 2008.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: firefox (Ubuntu)
   Status: New => Invalid

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

Title:
  Right hand scroll bar causes screen to go black

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: firefox

  Firefox 3.6.13
  Ubuntu 10.10 / Gnome

  This problem has actually been plaguing me for a while, through
  previous versions of Ubuntu and Firefox, but it took me a while to
  figure out how to reliably reproduce the problem and trace it back to
  Firefox.

  I use two Viewsonic 22" 1680x1050 monitors on my Ubuntu box that are
  attached using an ATI Technologies RV516 [Radeon X1300/X1550 Series]
  video card with 2 DVI ports. I use Ubuntu's System > Preferences >
  Monitors to set the monitors in a side by side (left/right)
  configuration.

  If I maximize Firefox on the right hand screen and pull up a tab with
  enough content to display a right-hand scroll bar, when I scroll to
  the bottom of the window the entire right hand screen goes black. If I
  use the mouse wheel to scroll up the right hand screen comes back to
  life. Scroll down, screen goes black, scroll up, screen comes back.

  I have tried repeating this with other browsers and other programs
  that have scroll bars. The error only happens with Firefox, and only
  if Firefox is maximized on the right-hand screen. If Firefox is not
  maximized or if I have Firefox maximized on the left hand screen I
  cannot reproduce the problem.

  I have tried swapping video cables and swapping monitors to make sure
  that this is not a hardware problem but the problem always happens on
  the right hand screen regardless of what hardware I'm using.

  It does not happen with every HTML page that scrolls, but it happens
  often, and when it does happen I can reproduce the problem again and
  again.

  I suspect that there's a math or rounding error somewhere in the
  scroll bar code that for certain HTML page sizes, when the page size
  is divided into the available window area, you end up with a rounding
  error that manifests itself when the scroll bar handle reaches the
  bottom of the page. At that point Firefox attempts to display the
  scroll bar handle below the end of the scroll bar, and that causes the
  window manager to blank the screen. I suspect that the error is
  ignored by most window managers and if it wasn't for the fact that I'm
  using a two-screen setup I probably wouldn't see it either.

  Could someone familiar with the code that calculates the scrolling of
  windows check the code and verify that the math is correct for when a
  scroll bar handle is pulled to the bottom of the screen in all cases?

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: firefox 3.6.13+build3+nobinonly-0ubuntu0.10.10.1
  ProcVersionSignature: Ubuntu 2.6.35-24.42-server 2.6.35.8
  Uname: Linux 2.6.35-24-server x86_64
  Architecture: amd64
  Date: Thu Jan  6 10:46:40 2011
  FirefoxPackages:
   firefox 3.6.13+build3+nobinonly-0ubuntu0.10.10.1
   firefox-gnome-support 3.6.13+build3+nobinonly-0ubuntu0.10.10.1
   firefox-branding 3.6.13+build3+nobinonly-0ubuntu0.10.10.1
   abroswer N/A
   abrowser-branding N/A
  ProcEnviron:
   PATH=(custom, user)

[Desktop-packages] [Bug 700233] Re: crash when i go to rutracker.org

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.
Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.
Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011.
Ubuntu 9.04 (jaunty) reached end-of-life on October 23, 2010.
Ubuntu 8.10 (intrepid) reached end-of-life on April 30, 2010.
Ubuntu 8.04 (hardy) reached end-of-life on May 12, 2011.
Ubuntu 7.10 (gutsy) reached end-of-life on April 18th, 2009.
Ubuntu 7.04 (feisty) reached end-of-life on October 19, 2008.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: firefox (Ubuntu)
   Status: New => Invalid

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

Title:
  crash when i go to rutracker.org

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: firefox

  crash when i go to rutracker.org
  FireFox do not answer.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: firefox 3.6.13+build3+nobinonly-0ubuntu0.10.10.1
  ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
  Uname: Linux 2.6.35-24-generic x86_64
  Architecture: amd64
  Date: Sat Jan  8 13:53:12 2011
  FirefoxPackages:
   firefox 3.6.13+build3+nobinonly-0ubuntu0.10.10.1
   firefox-gnome-support 3.6.13+build3+nobinonly-0ubuntu0.10.10.1
   firefox-branding 3.6.13+build3+nobinonly-0ubuntu0.10.10.1
   abroswer N/A
   abrowser-branding N/A
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  ProcEnviron:
   LANG=ru_RU.utf8
   SHELL=/bin/bash
  SourcePackage: firefox

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

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

[Desktop-packages] [Bug 697224] Re: Audacity : under UNE 10.10 the access line missing

Thank you for reporting this bug to Ubuntu.

Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.
Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.
Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011.
Ubuntu 9.04 (jaunty) reached end-of-life on October 23, 2010.
Ubuntu 8.10 (intrepid) reached end-of-life on April 30, 2010.
Ubuntu 8.04 (hardy) reached end-of-life on May 12, 2011.
Ubuntu 7.10 (gutsy) reached end-of-life on April 18th, 2009.
Ubuntu 7.04 (feisty) reached end-of-life on October 19, 2008.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: firefox (Ubuntu)
   Status: New => Invalid

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

Title:
  Audacity : under UNE 10.10 the access line missing

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: firefox

  I have two computers one with ubuntu 10.04 LTS, the other with ubuntu netbook 
edition 10.10 (both with audacity 1.3.12.7)
  Under U 10.04, audacity is completed but under the netbook the first line of 
the window ( with "file, edition and so on") is missing. So I can't used it : 
there is no way to open a music file, to export it ...

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: firefox 3.6.13+build3+nobinonly-0ubuntu0.10.10.1
  ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
  Uname: Linux 2.6.35-24-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Tue Jan  4 14:29:49 2011
  FirefoxPackages:
   firefox 3.6.13+build3+nobinonly-0ubuntu0.10.10.1
   firefox-gnome-support 3.6.13+build3+nobinonly-0ubuntu0.10.10.1
   firefox-branding 3.6.13+build3+nobinonly-0ubuntu0.10.10.1
   abroswer N/A
   abrowser-branding N/A
  InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 
(20101007)
  ProcEnviron:
   LANG=fr_FR.utf8
   SHELL=/bin/bash
  SourcePackage: firefox

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

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

[Desktop-packages] [Bug 698118] Re: No minimise and maximise buttons available

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.
Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.
Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011.
Ubuntu 9.04 (jaunty) reached end-of-life on October 23, 2010.
Ubuntu 8.10 (intrepid) reached end-of-life on April 30, 2010.
Ubuntu 8.04 (hardy) reached end-of-life on May 12, 2011.
Ubuntu 7.10 (gutsy) reached end-of-life on April 18th, 2009.
Ubuntu 7.04 (feisty) reached end-of-life on October 19, 2008.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: firefox (Ubuntu)
   Status: New => Invalid

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

Title:
  No minimise and maximise buttons available

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: firefox

  1. Ubuntu 10.10 maverick meerkat

  No min max buttons. Firefox displays max size always. So forced to
  close Firefox if I need to refer to some other window.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: firefox 3.6.13+build3+nobinonly-0ubuntu0.10.10.1
  ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
  Uname: Linux 2.6.35-24-generic i686
  NonfreeKernelModules: wl
  Architecture: i386
  Date: Thu Jan  6 19:19:05 2011
  FirefoxPackages:
   firefox 3.6.13+build3+nobinonly-0ubuntu0.10.10.1
   firefox-gnome-support 3.6.13+build3+nobinonly-0ubuntu0.10.10.1
   firefox-branding 3.6.13+build3+nobinonly-0ubuntu0.10.10.1
   abroswer N/A
   abrowser-branding N/A
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
  ProcEnviron:
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: firefox

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

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

[Desktop-packages] [Bug 1761554] Re: [bionic] Extended characters in GNOME screen keyboard don't get entered

2018-06-14 Thread Brian Murray

Hello Jeremy, or anyone else affected,

Accepted im-config into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/im-
config/0.34-1ubuntu1.2 in a few hours, and then in the -proposed
repository.

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

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

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

** Changed in: im-config (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags removed: verification-done 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 im-config in Ubuntu.
https://bugs.launchpad.net/bugs/1761554

Title:
  [bionic] Extended characters in GNOME screen keyboard don't get
  entered

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-user-docs package in Ubuntu:
  New
Status in im-config package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Triaged
Status in gnome-user-docs source package in Bionic:
  New
Status in im-config source package in Bionic:
  Fix Committed

Bug description:
  im-config SRU request
  =

  [Impact]

  When in a Wayland session, accented characters as well as some special
  characters can't be entered via the screen keyboard. The issue is
  fixed via the proposed upload of im-config, which has been changed to
  not set the GTK_IM_MODULE environment variable for IBus on Wayland
  (previously GTK_IM_MODULE was set to "ibus").

  Making this accessibility tool work without issues on Wayland is
  important enough to justify this SRU.

  [Test Case]

  1. Log in to an Ubuntu on Wayland session

  2. Open gedit and enable the screen keyboard
 (Settings -> Universal Access -> Typing)

  -> Accented characters via long-press does not work.
 Example: long-press a and select à from the popup

 Also, certain keys for special characters result in incorrect
 characters or nothing. Examples: ~, √, ÷, ×, <, >, ¢

  3. Install im-config from bionic-proposed

  4. Relogin and repeat step 2.

  -> Everything works as expected

  [Regression Potential]

  There are reasons to presuppose that GTK_IM_MODULE does not need to be
  set at all for IBus on a GNOME desktop:

  * GTK has a mechanism for selecting a built-in IM.

  * IBus is default in GNOME, and vanilla GNOME (which does not make use
of im-config) does not set the GTK_IM_MODULE environment variable.

  But the change is only made for Wayland sessions, which is not default
  in 18.04. Given this limitation, the regression risk is deemed to be
  low.

  [Original description]

  I filed this bug upstream last month but it hasn't gotten much
  attention so I'm filing it here because I think we need to track this
  issue for the Ubuntu 18.04 release

  https://gitlab.gnome.org/GNOME/gnome-shell/issues/109

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

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

  Nothing is entered in Step 5.

  This bug affects any of the "extended characters" clicked on from the
  long-press popup in the Screen Keyboard.

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

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

[Desktop-packages] [Bug 1773213] Re: U1 login dialog missing link to the privacy policy

2018-06-14 Thread Brian Murray

Hello Will, or anyone else affected,

Accepted gnome-online-accounts into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-online-accounts/3.28.0-0ubuntu2.1 in a few hours, and then in the
-proposed repository.

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

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

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

** Changed in: gnome-online-accounts (Ubuntu Bionic)
   Status: New => Fix Committed

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

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

Title:
  U1 login dialog missing link to the privacy policy

Status in gnome-online-accounts package in Ubuntu:
  Fix Released
Status in gnome-online-accounts source package in Bionic:
  Fix Committed

Bug description:
  The U1 login for g-o-a is missing a link to the privacy policy.

  [Impact]

   * No way to view the privacy policy for Ubuntu One
   
  [Test Case]

   * Open gnome-control-center
   * Select "Online Accounts" on the left
   * Select "Ubuntu Single Sign-On" under "Add an account"
   * Not you should see a link to open the Privacy Policy on the bottom left of 
the dialog.
   * Verify when clicking the window a browser window opens with our data 
privacy page
   
  [Regression Potential] 

   * None

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

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

[Desktop-packages] [Bug 1774810] Re: Nautilus shows wrong trash icon if not emptied before unplugging external drive

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

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

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

Title:
  Nautilus shows wrong trash icon if not emptied before unplugging
  external drive

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  What ends up happening:
  - You have a "full" trash icon
  - You can see zero files in the trash
  - Emptying the trash has no effect, whether from GUI, from gvfs-trash 
--empty, or gio trash --empty.
  - Terminal shows "files", "expunged", and "info" folders all completely empty 
at ~/.local/share/Trash. - Even deleting the ~/.local/share/Trash folder 
entirely has no effect.
  - Killing and restarting Nautilus has no effect.

  How to reproduce:
  1. Delete a file from an external drive
  2. Remove the external drive from the machine
  3. Attempt to empty the trash and observe this behavior

  Ubuntu 18.04 LTS
  GNOME nautilus 3.26.3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  2 13:37:55 2018
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'196'
   b'org.gnome.nautilus.window-state' b'geometry' b"'875x389+208+310'"
   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 2017-11-25 (188 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to bionic on 2018-05-04 (28 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1776978] [NEW] Update to calendar invitations cannot be processes

2018-06-14 Thread Jürgen Kübler

Public bug reported:

I am using a caldav calendar on a synology NAS and observed issues with 
calendar invitations I previously received. When I open one of these events I 
get the warning 'Event cannot be fully edited, because you are not the 
organizer' which I can live with. However, I cannot process any update I 
receive to these invitation.
The calendar entry is identified. Message: 
  Found the appointment in the calendar “myCal”
When I click on 'Accept' I get the message:
  Unable to send item to calendar “mycal”. Cannot receive calendar objects: 
Failed to put data: HTTP error code 412 (Precondition Failed): Existing 
resource matches "If-None-Match" header - not accepted.[if-none-match]
and the event remains unchanged.

Updates are both possible with Thunderbird on the same machine and on my
iPhone

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: evolution 3.28.1-2
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 14 21:59:26 2018
InstallationDate: Installed on 2018-05-02 (42 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: evolution
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: evolution (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 evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1776978

Title:
  Update to calendar invitations cannot be processes

Status in evolution package in Ubuntu:
  New

Bug description:
  I am using a caldav calendar on a synology NAS and observed issues with 
calendar invitations I previously received. When I open one of these events I 
get the warning 'Event cannot be fully edited, because you are not the 
organizer' which I can live with. However, I cannot process any update I 
receive to these invitation.
  The calendar entry is identified. Message: 
Found the appointment in the calendar “myCal”
  When I click on 'Accept' I get the message:
Unable to send item to calendar “mycal”. Cannot receive calendar objects: 
Failed to put data: HTTP error code 412 (Precondition Failed): Existing 
resource matches "If-None-Match" header - not accepted.[if-none-match]
  and the event remains unchanged.

  Updates are both possible with Thunderbird on the same machine and on
  my iPhone

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evolution 3.28.1-2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 14 21:59:26 2018
  InstallationDate: Installed on 2018-05-02 (42 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open

2018-06-14 Thread Bug Watch Updater

** Changed in: xorg-server
   Status: Confirmed => Invalid

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

Title:
  screen doesn't lock when some menu is open

Status in GNOME Screensaver:
  Expired
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in Unity:
  Triaged
Status in Unity 7.2 series:
  Triaged
Status in X.Org X server:
  Invalid
Status in gnome-screensaver package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Triaged
Status in gnome-screensaver source package in Precise:
  Triaged
Status in unity source package in Precise:
  Triaged
Status in gnome-screensaver source package in Xenial:
  Triaged
Status in unity source package in Xenial:
  Triaged
Status in xorg-server package in Debian:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  I'm running a fresh install of Dapper with screensaver set to 'blank
  screen', and 'lock screen when screensaver is active' enabled.

  If a panel menu (e.g. Applications) is open and the machine is left
  idle, the screen fails to lock. It fades out after the time period as
  expected, but the desktop reappears after a few seconds.

  Ben (comments / criticism welcome, this is my first bug report)

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

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

[Desktop-packages] [Bug 1755536] Re: gnome-control-center is not open ubuntu 18.04

2018-06-14 Thread Loren Pearson

Thanks Abhishek AN (darkabhi) . That fixed it for me.

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

Title:
   gnome-control-center is not open ubuntu 18.04

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

Bug description:
   gnome-control-center is not working when open. it will not open on
  ubuntu 18.04 even after reinstall

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.27.92-1ubuntu1
  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: ubuntu:GNOME
  Date: Tue Mar 13 23:28:27 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-03-04 (374 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 49579]

2018-06-14 Thread Ajax-a

*** This bug has been marked as a duplicate of bug 4286 ***

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

Title:
  screen doesn't lock when some menu is open

Status in GNOME Screensaver:
  Expired
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in Unity:
  Triaged
Status in Unity 7.2 series:
  Triaged
Status in X.Org X server:
  Invalid
Status in gnome-screensaver package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Triaged
Status in gnome-screensaver source package in Precise:
  Triaged
Status in unity source package in Precise:
  Triaged
Status in gnome-screensaver source package in Xenial:
  Triaged
Status in unity source package in Xenial:
  Triaged
Status in xorg-server package in Debian:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  I'm running a fresh install of Dapper with screensaver set to 'blank
  screen', and 'lock screen when screensaver is active' enabled.

  If a panel menu (e.g. Applications) is open and the machine is left
  idle, the screen fails to lock. It fades out after the time period as
  expected, but the desktop reappears after a few seconds.

  Ben (comments / criticism welcome, this is my first bug report)

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

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

Re: [Desktop-packages] [Bug 934291] Re: Deleting or stopping print jobs does not work

2018-06-14 Thread Chris Hermansen

I would like to briefly intrude to say "thanks to everyone" for this.

On Thu, Jun 14, 2018 at 12:46 PM, Till Kamppeter <934...@bugs.launchpad.net>
wrote:

> I have tested the package from -proposed now and it solves the problem.
> Everything is working as intended. Marking the fix verified ...
>
> ** Tags removed: verification-needed verification-needed-bionic
> ** Tags added: verification-done verification-done-bionic
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/934291
>
> Title:
>   Deleting or stopping print jobs does not work
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions
>

-- 
Chris Hermansen · clhermansen "at" gmail "dot" com

C'est ma façon de parler.

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

Title:
  Deleting or stopping print jobs does not work

Status in gnome-control-center:
  Unknown
Status in cups-pk-helper package in Ubuntu:
  Fix Released
Status in cups-pk-helper source package in Bionic:
  Fix Committed
Status in cups-pk-helper package in Debian:
  New

Bug description:
  Deleting or stopping print jobs through the "gnome-control-center -> 
printers" menu is not possible.
  (Black rectangle for stopping can be pressed, nothing happens.)

  Deleting with cups via webinterface does work. ( http://localhost:631/
  )

  Please let me know which information to provide.

  Cheers

  [Impact]

  The most intuitive way for users to maintain printers and look after
  print jobs is the printing part of the GNOME Control Center. As this
  tool makes use of cups-pk-helper for authentication, a lot of its
  functionality is not working dur to the non-working in cups-pk-helper
  package.

  This way a key functionality in Ubuntu Desktop is not working which
  may people turn away from Linux on the desktop.

  [Test Case]

  Do job operations (remove, move to other printer, ...) with print jobs
  using the printing tool of GNOME Control Center ("Devices" ->
  "Printers"). You will see that most or all of these operations do not
  work.

  They will work after installing this update.

  [Regression Potential]

  cups-pk-helper is only used by some graphical user interfaces for
  printer operations, like the mentioned GNOME tool. It does not impact
  printing itself, CUPS command line operations, or the CUPS web admin
  interface.

  Also the changes on cups-pk-helper are not done in its code or its way
  how it works but only in its configuration (using a system user).

  This way the regression potential is low.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.2.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 17 16:47:32 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago)
  usr_lib_gnome-control-center:
   deja-dup   22.0~bzr1290.37~oneiric1
   gnome-bluetooth3.2.0-0ubuntu2
   indicator-datetime 0.3.1-0ubuntu1.1

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

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

[Desktop-packages] [Bug 1775798] Re: Inappropriately uses Snapcraft icon when snap is missing an icon

2018-06-14 Thread Adolfo Jayme

** Changed in: gnome-software (Ubuntu)
   Status: New => Triaged

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

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

Title:
  Inappropriately uses Snapcraft icon when snap is missing an icon

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  When a snap does not have an icon, gnome-software uses the Snapcraft
  logo as a substitute.

  This is not a good idea, because:
  - It gives the Snapcraft logo an association of “something is missing”.
  - It gives the Snapcraft logo an association with a snap that might be 
terrible.

  What should happen: Snaps without icons should have a generic icon
  that does not include the Snapcraft logo.

  (The snapcraft.io equivalent is .)

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

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

[Desktop-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

2018-06-14 Thread Timo Aaltonen

also, it actually ships stuff in /etc/X11/Xsession.d

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

Title:
  leftover conffile forces GNOME is software rendering

Status in mesa package in Ubuntu:
  New
Status in nux package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  New
Status in nux source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  New
Status in nux source package in Artful:
  Fix Committed
Status in mesa source package in Bionic:
  New
Status in nux source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case ]

  · Install xenial
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
in an environment with no 3d support (VMs are easy tests)

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  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: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

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

[Desktop-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

2018-06-14 Thread Timo Aaltonen

I'd rather put it in x11-common (src:xorg), which already is full of
distro specific things and is installed on every system

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

Title:
  leftover conffile forces GNOME is software rendering

Status in mesa package in Ubuntu:
  New
Status in nux package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  New
Status in nux source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  New
Status in nux source package in Artful:
  Fix Committed
Status in mesa source package in Bionic:
  New
Status in nux source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case ]

  · Install xenial
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
in an environment with no 3d support (VMs are easy tests)

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  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: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

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

[Desktop-packages] [Bug 1753954] Re: Intel Whiskey Lake (WHL) graphics support

Hello Timo, or anyone else affected,

Accepted mesa into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/18.0.5-0ubuntu0~16.04.1 in a
few hours, and then in the -proposed repository.

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

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

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

** Changed in: mesa (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  Intel Whiskey Lake (WHL) graphics support

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libdrm source package in Xenial:
  Fix Committed
Status in linux-oem source package in Xenial:
  Won't Fix
Status in mesa source package in Xenial:
  Fix Committed
Status in xorg-server source package in Xenial:
  Invalid
Status in xorg-server-hwe-16.04 source package in Xenial:
  New
Status in libdrm source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  Fix Released
Status in xorg-server-hwe-16.04 source package in Bionic:
  Invalid

Bug description:
  [Impact]
  WHL is basically CFL-U with new PCI-ID's that are needed in the kernel, 
libdrm, mesa and xserver.

  [Test Case]

  Test the installation on a WHL machine, the graphical session should
  have full acceleration after these updates.

  [Regression Potential]

  None, just adds PCI-ID's to existing drivers.

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

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

[Desktop-packages] [Bug 1772632] Re: Backport packages for 16.04.5 HWE stack

Hello Timo, or anyone else affected,

Accepted mesa into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/18.0.5-0ubuntu0~16.04.1 in a
few hours, and then in the -proposed repository.

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

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

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

** Changed in: mesa (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  Backport packages for 16.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-6.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-16.04 package in Ubuntu:
  New
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-16.04 package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in xserver-xorg-video-intel-hwe-16.04 package in Ubuntu:
  New
Status in libclc source package in Xenial:
  Fix Committed
Status in libdrm source package in Xenial:
  Fix Committed
Status in llvm-toolchain-6.0 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in xorg-server-hwe-16.04 source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-amdgpu source package in Xenial:
  New
Status in xserver-xorg-video-amdgpu-hwe-16.04 source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-ati source package in Xenial:
  New
Status in xserver-xorg-video-ati-hwe-16.04 source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-intel source package in Xenial:
  New
Status in xserver-xorg-video-intel-hwe-16.04 source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.5 ***

  A minor update, only xserver sync, some driver updates plus a newer
  Mesa.

  Mesa needs llvm-toolchain-6.0 and libclc, libdrm, updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  libdrm:
  Slim to none, changes from 2.4.83 to 2.4.91
  - amdgpu: new pci-ids, bugfixes
  - intel: new pci-ids
  - drm: some new ioctl's
  - exynos, etnaviv, freedreno, android: fixes, new stuff

  llvm-toolchain-6.0:
  None, a new package

  libclc:
  I'd say none, very little has changed, added support for llvm-6 is the main 
reason for this slightly newer snapshot

  xorg-server:
  Slim, it's an upstream bugfix release, changes from 1.19.5 to 1.19.6+git 
include:
  - security fixes
  - backported bugfixes to glamor, modesetting driver, xwayland etc

  mesa:
  New major release plus a few bugfix updates after that. Regressions at this 
point are less likely. Upstream is tested by Intel CI system for instance. And 
we're already testing it via a ppa on OEM systems for 16.04.5. Tracking bug for 
the bugfix release (bionic) is bug 1772607

  [Other info]

  build order: [libdrm, llvm-toolchain-6.0], [libclc, xorg-server], mesa

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

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

[Desktop-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.

2018-06-14 Thread gouri

Bug still regularly observed.

This is not the same bug as #1656399 though it share some
characteristics.

In particular, the fact that both bugs do not always occur (but somehow
randomly) suggests that both are linked to a race condition somewhere in
lightdm logic.

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

Title:
  Unlocking existing session often requires several attempts.

Status in lightdm package in Ubuntu:
  New

Bug description:
  # Context

  * Computer with several X sessions opened.
  * Users switching from one opened session to another.
  * Lightdm opens new greeter, wait for typing password.
  * User types password.
  * Password is accepted.
  * System closes the current greeter (screen gets black for an instant).

  # Expected

  * User gets back to their already opened session.

  # Observed

  * System immediately opens another greeter.
  * User has to type password again.

  # Reproducible

  * Not always. At times, often, at other times, rare.

  # Additional information

  Users switch session via 
  dm-tool switch-to-user $OTHERUSER
  but I guess bug appears with other means (like menu item like "lock screen", 
etc).

  # Information requested

  lsb_release -rd

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  LC_ALL=C apt-cache policy lightdm

  lightdm:
Installed: 1.26.0-0ubuntu1
Candidate: 1.26.0-0ubuntu1
Version table:
   *** 1.26.0-0ubuntu1 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jun 12 14:14:52 2018
  ExecutablePath: /usr/sbin/lightdm
  InstallationDate: Installed on 2018-05-25 (18 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.logrotate.d.lightdm: [modified]
  mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830

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

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

[Desktop-packages] [Bug 1772632] Re: Backport packages for 16.04.5 HWE stack

Hello Timo, or anyone else affected,

Accepted xorg-server-hwe-16.04 into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source/xorg-
server-hwe-16.04/2:1.19.6-1ubuntu4~16.04.1 in a few hours, and then in
the -proposed repository.

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

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

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

** Changed in: xorg-server-hwe-16.04 (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  Backport packages for 16.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-6.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-16.04 package in Ubuntu:
  New
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-16.04 package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in xserver-xorg-video-intel-hwe-16.04 package in Ubuntu:
  New
Status in libclc source package in Xenial:
  Fix Committed
Status in libdrm source package in Xenial:
  Fix Committed
Status in llvm-toolchain-6.0 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-amdgpu source package in Xenial:
  New
Status in xserver-xorg-video-amdgpu-hwe-16.04 source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-ati source package in Xenial:
  New
Status in xserver-xorg-video-ati-hwe-16.04 source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-intel source package in Xenial:
  New
Status in xserver-xorg-video-intel-hwe-16.04 source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.5 ***

  A minor update, only xserver sync, some driver updates plus a newer
  Mesa.

  Mesa needs llvm-toolchain-6.0 and libclc, libdrm, updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  libdrm:
  Slim to none, changes from 2.4.83 to 2.4.91
  - amdgpu: new pci-ids, bugfixes
  - intel: new pci-ids
  - drm: some new ioctl's
  - exynos, etnaviv, freedreno, android: fixes, new stuff

  llvm-toolchain-6.0:
  None, a new package

  libclc:
  I'd say none, very little has changed, added support for llvm-6 is the main 
reason for this slightly newer snapshot

  xorg-server:
  Slim, it's an upstream bugfix release, changes from 1.19.5 to 1.19.6+git 
include:
  - security fixes
  - backported bugfixes to glamor, modesetting driver, xwayland etc

  mesa:
  New major release plus a few bugfix updates after that. Regressions at this 
point are less likely. Upstream is tested by Intel CI system for instance. And 
we're already testing it via a ppa on OEM systems for 16.04.5. Tracking bug for 
the bugfix release (bionic) is bug 1772607

  [Other info]

  build order: [libdrm, llvm-toolchain-6.0], [libclc, xorg-server], mesa

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

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

[Desktop-packages] [Bug 934291] Re: Deleting or stopping print jobs does not work

2018-06-14 Thread Till Kamppeter

I have tested the package from -proposed now and it solves the problem.
Everything is working as intended. Marking the fix verified ...

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

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

Title:
  Deleting or stopping print jobs does not work

Status in gnome-control-center:
  Unknown
Status in cups-pk-helper package in Ubuntu:
  Fix Released
Status in cups-pk-helper source package in Bionic:
  Fix Committed
Status in cups-pk-helper package in Debian:
  New

Bug description:
  Deleting or stopping print jobs through the "gnome-control-center -> 
printers" menu is not possible.
  (Black rectangle for stopping can be pressed, nothing happens.)

  Deleting with cups via webinterface does work. ( http://localhost:631/
  )

  Please let me know which information to provide.

  Cheers

  
  [Impact]

  The most intuitive way for users to maintain printers and look after
  print jobs is the printing part of the GNOME Control Center. As this
  tool makes use of cups-pk-helper for authentication, a lot of its
  functionality is not working dur to the non-working in cups-pk-helper
  package.

  This way a key functionality in Ubuntu Desktop is not working which
  may people turn away from Linux on the desktop.

  [Test Case]

  Do job operations (remove, move to other printer, ...) with print jobs
  using the printing tool of GNOME Control Center ("Devices" ->
  "Printers"). You will see that most or all of these operations do not
  work.

  They will work after installing this update.

  [Regression Potential]

  cups-pk-helper is only used by some graphical user interfaces for
  printer operations, like the mentioned GNOME tool. It does not impact
  printing itself, CUPS command line operations, or the CUPS web admin
  interface.

  Also the changes on cups-pk-helper are not done in its code or its way
  how it works but only in its configuration (using a system user).

  This way the regression potential is low.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.2.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 17 16:47:32 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago)
  usr_lib_gnome-control-center:
   deja-dup   22.0~bzr1290.37~oneiric1
   gnome-bluetooth3.2.0-0ubuntu2
   indicator-datetime 0.3.1-0ubuntu1.1

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

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

[Desktop-packages] [Bug 1776935] Re: package python3-louis 3.5.0-1ubuntu0.2 failed to install/upgrade: installed python3-louis package post-installation script subprocess returned error exit status 1

2018-06-14 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package python3-louis 3.5.0-1ubuntu0.2 failed to install/upgrade:
  installed python3-louis package post-installation script subprocess
  returned error exit status 1

Status in liblouis package in Ubuntu:
  New

Bug description:
  package python3-louis 3.5.0-1ubuntu0.2 failed to install/upgrade:
  installed python3-louis package post-installation script subprocess
  returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3-louis 3.5.0-1ubuntu0.2
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jun 12 14:51:13 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
   liblouis-data 3.5.0-1ubuntu0.2
   liblouis14 3.5.0-1ubuntu0.2
  ErrorMessage: installed python3-louis package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-05-15 (30 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: liblouis
  Title: package python3-louis 3.5.0-1ubuntu0.2 failed to install/upgrade: 
installed python3-louis package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1776935] [NEW] package python3-louis 3.5.0-1ubuntu0.2 failed to install/upgrade: installed python3-louis package post-installation script subprocess returned error exit status

2018-06-14 Thread John D

Public bug reported:

package python3-louis 3.5.0-1ubuntu0.2 failed to install/upgrade:
installed python3-louis package post-installation script subprocess
returned error exit status 1

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: python3-louis 3.5.0-1ubuntu0.2
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Tue Jun 12 14:51:13 2018
Dependencies:
 gcc-8-base 8-20180414-1ubuntu2
 libc6 2.27-3ubuntu1
 libgcc1 1:8-20180414-1ubuntu2
 liblouis-data 3.5.0-1ubuntu0.2
 liblouis14 3.5.0-1ubuntu0.2
ErrorMessage: installed python3-louis package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2018-05-15 (30 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: liblouis
Title: package python3-louis 3.5.0-1ubuntu0.2 failed to install/upgrade: 
installed python3-louis package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package python3-louis 3.5.0-1ubuntu0.2 failed to install/upgrade:
  installed python3-louis package post-installation script subprocess
  returned error exit status 1

Status in liblouis package in Ubuntu:
  New

Bug description:
  package python3-louis 3.5.0-1ubuntu0.2 failed to install/upgrade:
  installed python3-louis package post-installation script subprocess
  returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3-louis 3.5.0-1ubuntu0.2
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jun 12 14:51:13 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
   liblouis-data 3.5.0-1ubuntu0.2
   liblouis14 3.5.0-1ubuntu0.2
  ErrorMessage: installed python3-louis package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-05-15 (30 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: liblouis
  Title: package python3-louis 3.5.0-1ubuntu0.2 failed to install/upgrade: 
installed python3-louis package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1776933] [NEW] xdg-screensaver suspend doesn't work in Ubuntu 16.04

2018-06-14 Thread Ed B

Public bug reported:

1) The version of Ubuntu I am using is 
cat /etc/issue Ubuntu 16.04.4 LTS \n \l

2) The package version is 1.1.1-1ubuntu1.16.04.3


3) The expected behavior of the command

xdg-screensaver suspend 0x3a00010
(here 0x3a00010 is a window ID of an existing window)
shoud keep the screen saver from starting while that window is open.

4) The actual behavior

The screen saver starts after certain time of inactivity.  I also get an
error message

org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager wa
s not provided by any .service files

** Affects: xdg-utils (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  xdg-screensaver suspend doesn't work in Ubuntu 16.04

Status in xdg-utils package in Ubuntu:
  New

Bug description:
  1) The version of Ubuntu I am using is 
  cat /etc/issue Ubuntu 16.04.4 LTS \n \l

  2) The package version is 1.1.1-1ubuntu1.16.04.3

  
  3) The expected behavior of the command

  xdg-screensaver suspend 0x3a00010
  (here 0x3a00010 is a window ID of an existing window)
  shoud keep the screen saver from starting while that window is open.

  4) The actual behavior

  The screen saver starts after certain time of inactivity.  I also get
  an error message

  org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager 
wa
  s not provided by any .service files

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

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

[Desktop-packages] [Bug 1776563] Re: Ubuntu 18.04 can't load kernel on Acer Aspire A315 (Ryzen5/Radeon/FHD)

** Attachment added: "35241499_10216166779031575_5796073510006685696_n.jpg"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776563/+attachment/5152604/+files/35241499_10216166779031575_5796073510006685696_n.jpg

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

Title:
Ubuntu 18.04 can't load kernel on Acer Aspire A315 (Ryzen5/Radeon/FHD)

Status in amd:
New
Status in linux package in Ubuntu:
Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
New

Bug description:
CPU: Ryzen 5 2500U
VGA: Radeon 535
Notebook: Acer Aspire A315
I've just bought a new AMD Ryzen/Radeon notebook (Acer Aspire 3) and I wanted
to install an Ubuntu/Kubuntu 18.04 on it. I checked the bios settings and uefi
was the only boot option, so there is no legacy mode what I had used with my
old computer before. I downloaded the normal iso image and made an usb boot
pendrive using mkusb. The boot was okay, I got an uefi type menu but after
starting the kernel it paniced(?) instantly.
Error messages: ACPI Error [MAC0] Namespace lookup failure
ACPI ERROR 1 table load failures, 13 successful
BUG: soft lockup CPU#0 stuck for 22s
...
...
EFI VGA framebuffer device
clocksource tsc mask
Switching to colour framebuffer device
[28.040001] ...
...
...

I've tried to boot the same pendrive on my girlfriend's Acer
Travelmate with uefi and worked well.

I searched and I found that the problem is maybe in connection with
uefi framebuffer but I am not sure.

Ubuntu 16.04 can be loaded with nomodeset and noacpi parameters but
for 18.04 none of them are working. I tried 4.16,4.17 kernels too
(replaced on live usb) but without any success. The result is totally
equivalent.

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

[Desktop-packages] [Bug 1776563] Re: Ubuntu 18.04 can't load kernel on Acer Aspire A315 (Ryzen5/Radeon/FHD)

** Attachment added: "35236658_10216166799272081_8319003953274552320_n.jpg"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776563/+attachment/5152603/+files/35236658_10216166799272081_8319003953274552320_n.jpg

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

Title:
Ubuntu 18.04 can't load kernel on Acer Aspire A315 (Ryzen5/Radeon/FHD)

Status in amd:
New
Status in linux package in Ubuntu:
Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
New

I've tried to boot the same pendrive on my girlfriend's Acer
Travelmate with uefi and worked well.

I searched and I found that the problem is maybe in connection with
uefi framebuffer but I am not sure.

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

[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

2018-06-14 Thread Aron Bohl

Thank you @egor-tensin! I've been struggling with this problem for
years. This is the first work around that actually works! I added that
line under the [ipv4] section of my VPN connection file and then
restarted the network manager with:

   sudo systemctl restart NetworkManager.service

Now it's actually using the DNS specified by the VPN rather than just my
default ISP's DNS.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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

[Desktop-packages] [Bug 1754458] Re: nm-applet symbol not displayed on mate (18.04)

2018-06-14 Thread David Rennie-Waldock

Created a new account and works fine.
So after a little bit of digging, the only relevant difference was dconf.

dconf reset -f /org/mate/panel/
And it still works after a reboot.

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

Title:
  nm-applet symbol not displayed on mate (18.04)

Status in ubuntu-mate:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 18.04, the network manager applet symbol
  isn't displayed any longer. The other functionality (asking for
  credentials) is working. I also see other symbols.

  
  aptitude show network-manager-gnome
  Paket: network-manager-gnome
  Version: 1.8.10-2ubuntu1
  Neu: ja
  Zustand: Installiert

  
  stdout/stderr:
  Gtk-Message: 21:28:14.411: Failed to load module "appmenu-gtk-module"
  Gtk-Message: 21:28:14.431: Failed to load module "topmenu-gtk-module"
  Gtk-Message: 21:28:14.431: Failed to load module "appmenu-gtk-module"
  Gtk-Message: 21:28:14.432: Failed to load module "topmenu-gtk-module"

  ** (nm-applet:29524): WARNING **: 21:28:14.668: Couldn't register with
  accessibility bus: Did not receive a reply. Possible causes include:
  the remote application did not send a reply, the message bus security
  policy blocked the reply, the reply timeout expired, or the network
  connection was broken.

  (nm-applet:29524): nm-applet-WARNING **: 21:28:15.987: Cannot grab
  information for modem at /org/freedesktop/ModemManager1/Modem/6: No
  ModemManager support

  (nm-applet:29524): nm-applet-WARNING **: 21:28:16.124: ModemManager is
  not available for modem at /org/freedesktop/ModemManager1/Modem/6

  (nm-applet:29524): Gtk-WARNING **: 21:28:16.127: Can't set a parent on
  widget which has a parent

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-WARNING **: 21:28:16.171: Can't set a parent on
  widget which has a parent

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-WARNING **: 21:28:21.570: Can't set a parent on
  widget which has a parent

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-WARNING **: 21:28:24.655: Can't set a parent on
  widget which has a parent

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager-gnome 1.8.10-2ubuntu1
  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: MATE
  Date: Thu Mar  8 21:27:56 2018
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  WpaSupplicantLog:
   
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1771976] Re: Collect physical screen size

2018-06-14 Thread Nafallo Bjälevik

Before:
  "Screens": [
{
  "Resolution": "1920x1080",
  "Frequency": "60.00"
} 
  ],   

After:
  "Screens": [
{
  "Size": "294mmx165mm",
  "Resolution": "1920x1080",
  "Frequency": "60.00"
}
  ],


** Tags removed: 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 ubuntu-report in Ubuntu.
https://bugs.launchpad.net/bugs/1771976

Title:
  Collect physical screen size

Status in ubuntu-report:
  Fix Released
Status in ubuntu-report package in Ubuntu:
  Fix Released
Status in ubuntu-report source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * ubuntu-report collects the current resolution, it would be useful
  to collect the physical screen size and be able to compute pixel
  density for example.

  [Test Case]

   * Run ubuntu-report show
   * Check that there is now a new field reporting the screen physical size 
alongside the resolution.

  [Regression Potential]

   * Everything that isn't matched is just ignored ant not part of the finale 
json report.
   * We have an extensive testsuite covering the previous supported case and 
now this one that was added.

  

  ubuntu-report collects the current resolution, it would be useful to
  collect the physical screen size and be able to compute pixel density
  for example.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubuntu-report 1.0.11
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 18 11:17:10 2018
  Dependencies:
   gcc-8-base 8.1.0-2ubuntu1
   libc6 2.27-3ubuntu1
   libgcc1 1:8.1.0-2ubuntu1
  InstallationDate: Installed on 2014-07-15 (1403 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  SourcePackage: ubuntu-report
  UpgradeStatus: Upgraded to cosmic on 2018-03-24 (54 days ago)

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

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

[Desktop-packages] [Bug 1772632] Re: Backport packages for 16.04.5 HWE stack

Hello Timo, or anyone else affected,

Accepted xserver-xorg-video-intel-hwe-16.04 into xenial-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/xserver-xorg-video-intel-
hwe-16.04/2:2.99.917+git20171229-1~16.04.1 in a few hours, and then in
the -proposed repository.

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

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

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

** Changed in: xserver-xorg-video-intel-hwe-16.04 (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  Backport packages for 16.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-6.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-16.04 package in Ubuntu:
  New
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-16.04 package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in xserver-xorg-video-intel-hwe-16.04 package in Ubuntu:
  New
Status in libclc source package in Xenial:
  Fix Committed
Status in libdrm source package in Xenial:
  Fix Committed
Status in llvm-toolchain-6.0 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  In Progress
Status in xserver-xorg-video-amdgpu source package in Xenial:
  New
Status in xserver-xorg-video-amdgpu-hwe-16.04 source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-ati source package in Xenial:
  New
Status in xserver-xorg-video-ati-hwe-16.04 source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-intel source package in Xenial:
  New
Status in xserver-xorg-video-intel-hwe-16.04 source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.5 ***

  A minor update, only xserver sync, some driver updates plus a newer
  Mesa.

  Mesa needs llvm-toolchain-6.0 and libclc, libdrm, updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  libdrm:
  Slim to none, changes from 2.4.83 to 2.4.91
  - amdgpu: new pci-ids, bugfixes
  - intel: new pci-ids
  - drm: some new ioctl's
  - exynos, etnaviv, freedreno, android: fixes, new stuff

  llvm-toolchain-6.0:
  None, a new package

  libclc:
  I'd say none, very little has changed, added support for llvm-6 is the main 
reason for this slightly newer snapshot

  xorg-server:
  Slim, it's an upstream bugfix release, changes from 1.19.5 to 1.19.6+git 
include:
  - security fixes
  - backported bugfixes to glamor, modesetting driver, xwayland etc

  mesa:
  New major release plus a few bugfix updates after that. Regressions at this 
point are less likely. Upstream is tested by Intel CI system for instance. And 
we're already testing it via a ppa on OEM systems for 16.04.5. Tracking bug for 
the bugfix release (bionic) is bug 1772607

  [Other info]

  build order: [libdrm, llvm-toolchain-6.0], [libclc, xorg-server], mesa

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

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

[Desktop-packages] [Bug 1736164] Re: deja-dup/duplicity backup fails with UnicodeDecodeError

2018-06-14 Thread James Walters

UPDATE: In my situation, the problem was caused by using a backup
directory ("/var/backups") that my user did not have permission to write
to. A simple chmod fixed the issue, but this manifested itself in deja-
dup as a unicode error. Please consider adding a check/caveat to the
code to provide a more helpful error message in cases where permission
is denied.

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

Title:
  deja-dup/duplicity backup fails with UnicodeDecodeError

Status in Déjà Dup:
  Triaged
Status in Duplicity:
  New
Status in deja-dup package in Ubuntu:
  New
Status in deja-dup package in Fedora:
  In Progress

Bug description:
  See: https://bugzilla.redhat.com/show_bug.cgi?id=1470873

  
  Description of problem:
  With the update from Fedora 25 to Fedora 26 Workstation, backups with 
deja-dup/duplicity are failing

  
  Version-Release number of selected component (if applicable):
  duplicity 0.7.13.1
  deja-dup 34.3

  How reproducible:
  Always (scheduled and manually started backup)

  
  Steps to Reproduce:
  1. Wait for the scheduled backup to start or start it via the "Backup now" 
button
  2. Some or a large number of files might get backed up, then the backup stops 
with "Failed with an unknown error"
  3.

  Actual results:
  Backup fails

  Expected results:
  Backup completes as it always did

  
  Additional info:
  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1540, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1534, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1385, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1516, in do_backup
  incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
  globals.backend)
File "/usr/bin/duplicity", line 453, in write_multivol
  (tdp, dest_filename, vol_num)))
File "/usr/lib64/python2.7/site-packages/duplicity/asyncscheduler.py", line 
146, in schedule_task
  return self.__run_synchronously(fn, params)
File "/usr/lib64/python2.7/site-packages/duplicity/asyncscheduler.py", line 
172, in __run_synchronously
  ret = fn(*params)
File "/usr/bin/duplicity", line 452, in 
  vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 341, in put
  backend.put(tdp, dest_filename)
File "/usr/lib64/python2.7/site-packages/duplicity/backend.py", line 376, 
in inner_retry
  % exception_traceback())
File "/usr/lib64/python2.7/site-packages/duplicity/util.py", line 51, in 
exception_traceback
  return uexc(msg)
File "/usr/lib64/python2.7/site-packages/duplicity/util.py", line 79, in 
uexc
  e = unicode(e).encode('utf-8')
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 746: 
ordinal not in range(128)

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

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

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

2018-06-14 Thread Phil Wolff

It appears that the dialog is system-wide modal. Is that really
necessary? If so, it should also appear on top of *every* window stack
in the system, not just the stack containing the offender.

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

Title:
   is not respoding window is constantly showing when
  debugging a program in Eclipse

Status in mutter package in Ubuntu:
  Confirmed

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

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

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

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

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

[Desktop-packages] [Bug 1570227] Re: Open Recent Items show as always empty in Gedit

2018-06-14 Thread jimmack

I'm using Linux Mint 18.1 (based on Ubuntu 16.04).
I was experiencing the same problem with gedit and I noticed that GIMP was also 
not populating the document history.  A search for this issue with GIMP found a 
post that explained that under Preferences -> System Settings -> Privacy, there 
is an option to "Remember recently accessed files" (defaulting to "Off").  I've 
enabled that and now I'm getting my history lists again, although on gedit, 
it's only through the Open \/ menu.
Personally, I'd prefer it if the File menu was fixed, but if we're going to 
have to use the new open drop-down, then the "Open Recent" option needs to be 
removed to avoid further confusion.

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

Title:
  Open Recent Items show as always empty in Gedit

Status in gedit:
  New
Status in gedit package in Ubuntu:
  Confirmed

Bug description:
  Gedit doesn't show the recently opened files under File -> Open
  Recent. In Open Recent it only shows Reopen Closed Tabs but that is
  also not active (i.e not clickable).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic i686
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Apr 14 13:16:33 2016
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1762307] Re: Cannot access encrypted volume

2018-06-14 Thread Phillip Susi

If you wish to reproduce it then yes, but it probably isn't necessary if
it is no longer an issue for you.


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

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

Title:
  Cannot access encrypted volume

Status in udisks2 package in Ubuntu:
  Incomplete

Bug description:
  At the screen preparing to install Kubuntu, I selected the button
  "Guided - use entire disk and set up encrypted LVM". System has two
  hard drives, sda with both Mint 18.3 and Bionic 18.04; sdb with Bionic
  18.04. The installer graphic showed it would use all of sda for
  Kubuntu.

  In Dolphin, trying to access the encrypted volume on sda returns:
  An error occurred while accessing '58.9 GiB Encrypted Drive', the system 
responded: The requested operation has failed: Error unlocking /dev/sda5: The 
function 'bd_crypto_luks_open_blob' called, but not implemented!

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

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

[Desktop-packages] [Bug 1776916] Re: gnome-shell crashed with SIGSEGV

2018-06-14 Thread Jean-Baptiste Lallement

** Information type changed from Private to Public

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

Title:
  gnome-shell crashed with SIGSEGV

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Crashed when changing the volume with the keyboard's function keys.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 14 15:41:10 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-07-15 (1430 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f3548500351:rep movsq %ds:(%rsi),%es:(%rdi)
   PC (0x7f3548500351) ok
   source "%ds:(%rsi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%es:(%rdi)" (0x7f34c56fd7e0) ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_new () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_initable_new_valist () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_initable_new () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: Upgraded to cosmic on 2018-03-24 (81 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

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

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

[Desktop-packages] [Bug 1749283] Re: configured stats_temp_directory does not get created after reboot

2018-06-14 Thread Eric Desrochers

** Changed in: resource-agents (Ubuntu)
 Assignee: Eric Desrochers (slashd) => Mario Splivalo (mariosplivalo)

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

Title:
  configured stats_temp_directory does not get created after reboot

Status in postgresql-common package in Ubuntu:
  Won't Fix
Status in resource-agents package in Ubuntu:
  In Progress
Status in postgresql-common source package in Xenial:
  Won't Fix
Status in resource-agents source package in Xenial:
  New
Status in postgresql-common source package in Artful:
  Won't Fix
Status in resource-agents source package in Artful:
  New
Status in postgresql-common source package in Bionic:
  Won't Fix
Status in resource-agents source package in Bionic:
  New
Status in postgresql-common package in Debian:
  New

Bug description:
  Default postgres installation in Ubuntu (and Debian) configures
  stats_temp_directory inside /var/run/postgresql:

  $ grep stats_temp /etc/postgresql/10/main/postgresql.conf 
  stats_temp_directory = '/var/run/postgresql/10-main.pg_stat_tmp'

  However, this directory is not created after reboot.

  In most cases this is not a problem as systemd starts postgres via
  pg_ctlcluster, a "multiversion/cluster aware pg_ctl wrapper", and
  pg_ctlcluster will create missing directories before starting
  postgres.

  But in cases where systemd is not starting postgres this is a problem.
  Specifically, when postgres is controlled by pacemaker (using postgres 
resource agent for pacemaker) it is started using pg_ctl wrapper. pg_ctl won't 
create missing directories and therefore postgres fails to start.

  The simplest solution for this issue is to have systemd recreate
  missing directories via /usr/lib/tmpfiles.d/postgresql.conf file.

  Currently only /var/run/postgresql and /var/log/postgresql are created
  using systemd-tmpfiles.

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

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

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

Hello Timo, or anyone else affected,

Accepted xserver-xorg-video-amdgpu-hwe-16.04 into xenial-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu-
hwe-16.04/18.0.1-1~16.04.1 in a few hours, and then in the -proposed
repository.

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

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

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

** Also affects: xserver-xorg-video-amdgpu-hwe-16.04 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: xserver-xorg-video-ati-hwe-16.04 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: xserver-xorg-video-intel-hwe-16.04 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xserver-xorg-video-ati-hwe-16.04 (Ubuntu Xenial)
   Status: New => Fix Committed

** Changed in: xserver-xorg-video-amdgpu-hwe-16.04 (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  Backport packages for 16.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-6.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-16.04 package in Ubuntu:
  New
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-16.04 package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in xserver-xorg-video-intel-hwe-16.04 package in Ubuntu:
  New
Status in libclc source package in Xenial:
  Fix Committed
Status in libdrm source package in Xenial:
  Fix Committed
Status in llvm-toolchain-6.0 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  In Progress
Status in xserver-xorg-video-amdgpu source package in Xenial:
  New
Status in xserver-xorg-video-amdgpu-hwe-16.04 source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-ati source package in Xenial:
  New
Status in xserver-xorg-video-ati-hwe-16.04 source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-intel source package in Xenial:
  New
Status in xserver-xorg-video-intel-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.5 ***

  A minor update, only xserver sync, some driver updates plus a newer
  Mesa.

  Mesa needs llvm-toolchain-6.0 and libclc, libdrm, updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  libdrm:
  Slim to none, changes from 2.4.83 to 2.4.91
  - amdgpu: new pci-ids, bugfixes
  - intel: new pci-ids
  - drm: some new ioctl's
  - exynos, etnaviv, freedreno, android: fixes, new stuff

  llvm-toolchain-6.0:
  None, a new package

  libclc:
  I'd say none, very little has changed, added support for llvm-6 is the main 
reason for this slightly newer snapshot

  xorg-server:
  Slim, it's an upstream bugfix release, changes from 1.19.5 to 1.19.6+git 
include:
  - security fixes
  - backported bugfixes to glamor, modesetting driver, xwayland etc

  mesa:
  New major release plus a few bugfix updates after that. Regressions at this 
point are less likely. Upstream is tested by Intel CI system for instance. And 
we're already testing it via a ppa on OEM systems for 16.04.5. Tracking bug for 
the bugfix release (bionic) is bug 1772607

  [Other info]

  build order: [libdrm, llvm-toolchain-6.0], [libclc, xorg-server], mesa

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

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

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

Hello Timo, or anyone else affected,

Accepted xserver-xorg-video-ati-hwe-16.04 into xenial-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/xserver-xorg-video-ati-
hwe-16.04/1:18.0.1-1~16.04.1 in a few hours, and then in the -proposed
repository.

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

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

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

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

Title:
  Backport packages for 16.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-6.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Fix Committed
Status in libdrm source package in Xenial:
  Fix Committed
Status in llvm-toolchain-6.0 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  In Progress
Status in xserver-xorg-video-amdgpu source package in Xenial:
  New
Status in xserver-xorg-video-ati source package in Xenial:
  New
Status in xserver-xorg-video-intel source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.5 ***

  A minor update, only xserver sync, some driver updates plus a newer
  Mesa.

  Mesa needs llvm-toolchain-6.0 and libclc, libdrm, updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  libdrm:
  Slim to none, changes from 2.4.83 to 2.4.91
  - amdgpu: new pci-ids, bugfixes
  - intel: new pci-ids
  - drm: some new ioctl's
  - exynos, etnaviv, freedreno, android: fixes, new stuff

  llvm-toolchain-6.0:
  None, a new package

  libclc:
  I'd say none, very little has changed, added support for llvm-6 is the main 
reason for this slightly newer snapshot

  xorg-server:
  Slim, it's an upstream bugfix release, changes from 1.19.5 to 1.19.6+git 
include:
  - security fixes
  - backported bugfixes to glamor, modesetting driver, xwayland etc

  mesa:
  New major release plus a few bugfix updates after that. Regressions at this 
point are less likely. Upstream is tested by Intel CI system for instance. And 
we're already testing it via a ppa on OEM systems for 16.04.5. Tracking bug for 
the bugfix release (bionic) is bug 1772607

  [Other info]

  build order: [libdrm, llvm-toolchain-6.0], [libclc, xorg-server], mesa

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

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

[Desktop-packages] [Bug 26662] Re: using the filename to get the mimetype is not always correct

2018-06-14 Thread Merlijn Sebrechts

Marked as fix released because the original issue is fixed.

** Changed in: file-roller (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: file-roller (Ubuntu)
 Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned)

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

Title:
  using the filename to get the mimetype is not always correct

Status in File Roller:
  Confirmed
Status in file-roller package in Ubuntu:
  Fix Released

Bug description:
  When opening a file with the extension .z file-roller checks for the
  presence of the compress and uncompress binaries. A normal Ubuntu
  includes uncompress via gzip, but not compress. When file-roller can't
  locate compress, it refuses to open the .z file even though it is
  capable of uncompressing it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/26662/+subscriptions

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

[Desktop-packages] [Bug 1572762] Re: File-roller shows home folder in each zip

2018-06-14 Thread Merlijn Sebrechts

** Changed in: file-roller (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  File-roller shows home folder in each zip

Status in File Roller:
  Fix Released
Status in file-roller package in Ubuntu:
  Fix Released

Bug description:
  In every .zip file, file-roller shows that the file contains a "home"
  folder which weights 0 bytes.

  $ file-roller --version
  file-roller 3.16.4, Copyright © 2001-2012 Free Software Foundation, Inc.

  It seems a problem in the interaction between file-roller and 7zip.
  Package versions:

  -  p7zip-full15.09+dfsg-2~eugenesan~xenial1
  -  unzip6.0-20ubuntu1
  -  zip 3.0-11

  It is already reported in the following bugzillas:

  https://bugzilla.gnome.org/show_bug.cgi?id=757793
  https://bugzilla.redhat.com/show_bug.cgi?id=1284665

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/1572762/+subscriptions

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

[Desktop-packages] [Bug 1772632] Re: Backport packages for 16.04.5 HWE stack

Hello Timo, or anyone else affected,

Accepted libclc into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libclc/0.2.0+git20180312-1~16.04.1
in a few hours, and then in the -proposed repository.

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

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

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

** Changed in: libclc (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  Backport packages for 16.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-6.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Fix Committed
Status in libdrm source package in Xenial:
  Fix Committed
Status in llvm-toolchain-6.0 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  In Progress
Status in xserver-xorg-video-amdgpu source package in Xenial:
  New
Status in xserver-xorg-video-ati source package in Xenial:
  New
Status in xserver-xorg-video-intel source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.5 ***

  A minor update, only xserver sync, some driver updates plus a newer
  Mesa.

  Mesa needs llvm-toolchain-6.0 and libclc, libdrm, updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  libdrm:
  Slim to none, changes from 2.4.83 to 2.4.91
  - amdgpu: new pci-ids, bugfixes
  - intel: new pci-ids
  - drm: some new ioctl's
  - exynos, etnaviv, freedreno, android: fixes, new stuff

  llvm-toolchain-6.0:
  None, a new package

  libclc:
  I'd say none, very little has changed, added support for llvm-6 is the main 
reason for this slightly newer snapshot

  xorg-server:
  Slim, it's an upstream bugfix release, changes from 1.19.5 to 1.19.6+git 
include:
  - security fixes
  - backported bugfixes to glamor, modesetting driver, xwayland etc

  mesa:
  New major release plus a few bugfix updates after that. Regressions at this 
point are less likely. Upstream is tested by Intel CI system for instance. And 
we're already testing it via a ppa on OEM systems for 16.04.5. Tracking bug for 
the bugfix release (bionic) is bug 1772607

  [Other info]

  build order: [libdrm, llvm-toolchain-6.0], [libclc, xorg-server], mesa

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

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

[Desktop-packages] [Bug 1776912] Re: chromium-browser package does NOT install an AppData file

2018-06-14 Thread Mario Sánchez Prada

Note that the Fedora package is installing this file into the deprecated
path /usr/share/appdata, instead of using the one specified by AppStream
since a while ago: /usr/share/metainfo.

I've filed a bug for Fedora in
https://bugzilla.redhat.com/show_bug.cgi?id=1591306, but I'm commenting
this explicitly here to prevent confusion, and to be clear on that
/usr/share/metainfo should be the right place to install this file into.

** Bug watch added: Red Hat Bugzilla #1591306
   https://bugzilla.redhat.com/show_bug.cgi?id=1591306

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

Title:
  chromium-browser package does NOT install an AppData file

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  In order for Chromium Browser to integrate properly with software
  centers (e.g. GNOME Software), an additional XML file with metadata
  needs to be installed under /usr/share/metainfo, in the form of an
  "AppData file", containing the relevant bits according to the
  AppStream specification:

https://www.freedesktop.org/software/appstream/docs

  Fortunately, upstream has included that file in the chromium
  repository for a while (since [1]) and, as far as I can see, Fedora is
  already installing that file in its place, see
  
https://src.fedoraproject.org/rpms/chromium/blob/9cdea2b9/f/chromium.spec#_1462

  I have quickly looked into the .install and rules files in of the
  chromium-browser package for Ubuntu [2][3] and I could not find any
  trace of this happening, so I guess all that would remain here would
  be to adapt the debian packaging files to make sure that it gets
  installed too for Ubuntu, similar to what Fedora and other distros do
  already.

  [1] 
https://chromium.googlesource.com/chromium/src.git/+/d6807b9a7da70dae9191b93d4ec6157187515078%5E%21
  [2] 
https://bazaar.launchpad.net/~chromium-team/chromium-browser/chromium-browser.head/view/head:/debian/chromium-browser.install
  [3] 
https://bazaar.launchpad.net/~chromium-team/chromium-browser/chromium-browser.head/view/head:/debian/rules

  
  
https://www.freedesktop.org/software/appstream/docs/chap-Quickstart.html#sect-Quickstart-DesktopApps

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

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

[Desktop-packages] [Bug 26662] Re: using the filename to get the mimetype is not always correct

2018-06-14 Thread Merlijn Sebrechts

I created a new issue for this: https://gitlab.gnome.org/GNOME/file-
roller/issues/2

Although I'm not sure this issue and the new issue are related.

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

Title:
  using the filename to get the mimetype is not always correct

Status in File Roller:
  Confirmed
Status in file-roller package in Ubuntu:
  Fix Released

Bug description:
  When opening a file with the extension .z file-roller checks for the
  presence of the compress and uncompress binaries. A normal Ubuntu
  includes uncompress via gzip, but not compress. When file-roller can't
  locate compress, it refuses to open the .z file even though it is
  capable of uncompressing it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/26662/+subscriptions

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

[Desktop-packages] [Bug 1776912] [NEW] chromium-browser package does NOT install an AppData file

2018-06-14 Thread Mario Sánchez Prada

Public bug reported:

In order for Chromium Browser to integrate properly with software
centers (e.g. GNOME Software), an additional XML file with metadata
needs to be installed under /usr/share/metainfo, in the form of an
"AppData file", containing the relevant bits according to the AppStream
specification:

  https://www.freedesktop.org/software/appstream/docs

Fortunately, upstream has included that file in the chromium repository
for a while (since [1]) and, as far as I can see, Fedora is already
installing that file in its place, see
https://src.fedoraproject.org/rpms/chromium/blob/9cdea2b9/f/chromium.spec#_1462

I have quickly looked into the .install and rules files in of the
chromium-browser package for Ubuntu [2][3] and I could not find any
trace of this happening, so I guess all that would remain here would be
to adapt the debian packaging files to make sure that it gets installed
too for Ubuntu, similar to what Fedora and other distros do already.

[1] 
https://chromium.googlesource.com/chromium/src.git/+/d6807b9a7da70dae9191b93d4ec6157187515078%5E%21
[2] 
https://bazaar.launchpad.net/~chromium-team/chromium-browser/chromium-browser.head/view/head:/debian/chromium-browser.install
[3] 
https://bazaar.launchpad.net/~chromium-team/chromium-browser/chromium-browser.head/view/head:/debian/rules


https://www.freedesktop.org/software/appstream/docs/chap-Quickstart.html#sect-Quickstart-DesktopApps

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  chromium-browser package does NOT install an AppData file

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  In order for Chromium Browser to integrate properly with software
  centers (e.g. GNOME Software), an additional XML file with metadata
  needs to be installed under /usr/share/metainfo, in the form of an
  "AppData file", containing the relevant bits according to the
  AppStream specification:

https://www.freedesktop.org/software/appstream/docs

  Fortunately, upstream has included that file in the chromium
  repository for a while (since [1]) and, as far as I can see, Fedora is
  already installing that file in its place, see
  
https://src.fedoraproject.org/rpms/chromium/blob/9cdea2b9/f/chromium.spec#_1462

  I have quickly looked into the .install and rules files in of the
  chromium-browser package for Ubuntu [2][3] and I could not find any
  trace of this happening, so I guess all that would remain here would
  be to adapt the debian packaging files to make sure that it gets
  installed too for Ubuntu, similar to what Fedora and other distros do
  already.

  [1] 
https://chromium.googlesource.com/chromium/src.git/+/d6807b9a7da70dae9191b93d4ec6157187515078%5E%21
  [2] 
https://bazaar.launchpad.net/~chromium-team/chromium-browser/chromium-browser.head/view/head:/debian/chromium-browser.install
  [3] 
https://bazaar.launchpad.net/~chromium-team/chromium-browser/chromium-browser.head/view/head:/debian/rules

  
  
https://www.freedesktop.org/software/appstream/docs/chap-Quickstart.html#sect-Quickstart-DesktopApps

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

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

[Desktop-packages] [Bug 1776878] Re: package nvidia-opencl-icd-340 340.96-0ubuntu3.16.04.1 failed to install/upgrade: there is no script in the new version of the package - giving up

2018-06-14 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package nvidia-opencl-icd-340 340.96-0ubuntu3.16.04.1 failed to
  install/upgrade: there is no script in the new version of the package
  - giving up

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

Bug description:
  keep getting this error when i start up my pc

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-opencl-icd-340 340.96-0ubuntu3.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic i686
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:06:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  340.102  Mon Jan 16 12:20:46 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Oct 23 14:34:16 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
   ocl-icd-libopencl1 2.2.8-1
  DistUpgraded: 2016-06-20 16:12:06,620 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: xenial
  DistroVariant: ubuntu
  ErrorMessage: there is no script in the new version of the package - giving up
  GraphicsCard:
   NVIDIA Corporation G80 [GeForce 8800 GTX] [10de:0191] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation G80 [GeForce 8800 GTX] [10de:039c]
  InstallationDate: Installed on 2015-02-27 (1202 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic 
root=UUID=bbebdfae-3012-4160-aeb4-d92437c8fd75 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.25
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-opencl-icd-340 340.96-0ubuntu3.16.04.1 failed to 
install/upgrade: there is no script in the new version of the package - giving 
up
  UpgradeStatus: Upgraded to xenial on 2016-06-20 (723 days ago)
  dmi.bios.date: 03/07/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2004
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2004:bd03/07/2007:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Jun 14 10:53:11 2018
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Desktop-packages] [Bug 1776878] Re: package nvidia-opencl-icd-340 340.96-0ubuntu3.16.04.1 failed to install/upgrade: there is no script in the new version of the package - giving up

2018-06-14 Thread Leonidas S. Barbosa

** Information type changed from Private Security to Public

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

Title:
  package nvidia-opencl-icd-340 340.96-0ubuntu3.16.04.1 failed to
  install/upgrade: there is no script in the new version of the package
  - giving up

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

Bug description:
  keep getting this error when i start up my pc

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-opencl-icd-340 340.96-0ubuntu3.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic i686
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:06:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  340.102  Mon Jan 16 12:20:46 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Oct 23 14:34:16 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
   ocl-icd-libopencl1 2.2.8-1
  DistUpgraded: 2016-06-20 16:12:06,620 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: xenial
  DistroVariant: ubuntu
  ErrorMessage: there is no script in the new version of the package - giving up
  GraphicsCard:
   NVIDIA Corporation G80 [GeForce 8800 GTX] [10de:0191] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation G80 [GeForce 8800 GTX] [10de:039c]
  InstallationDate: Installed on 2015-02-27 (1202 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic 
root=UUID=bbebdfae-3012-4160-aeb4-d92437c8fd75 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.25
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-opencl-icd-340 340.96-0ubuntu3.16.04.1 failed to 
install/upgrade: there is no script in the new version of the package - giving 
up
  UpgradeStatus: Upgraded to xenial on 2016-06-20 (723 days ago)
  dmi.bios.date: 03/07/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2004
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2004:bd03/07/2007:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Jun 14 10:53:11 2018
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Desktop-packages] [Bug 1776901] [NEW] Startup or Reboot GDM3 Keyboard/Mouse Not Working

2018-06-14 Thread Stephen Allen

Public bug reported:

I don't reboot often due to running LTS. However over the past month or
so, on subsequent reboots after upgrades, GDM3 accepts focus but won't
accept any input either from keyboard or mouse.

The work-a-round that works for me is to 'Ctl+Alt+F(number) to get to a
console, which won't give me a login prompt until I hit the 'return'
key. Then I can go back to the GDM3 session and login normally.

I'm reporting this from Vanilla Gnome Ubuntu 18.04, all current updates
applied.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdm3 3.28.2-0ubuntu1.2
ProcVersionSignature: Ubuntu 
4.15.0-20201805060708.0+mediatree+hauppauge-generic 4.15.17
Uname: Linux 4.15.0-20201805060708-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Jun 14 08:44:36 2018
InstallationDate: Installed on 2018-01-19 (146 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic gnome3-ppa third-party-packages

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

Title:
  Startup or Reboot GDM3 Keyboard/Mouse Not Working

Status in gdm3 package in Ubuntu:
  New

Bug description:
  I don't reboot often due to running LTS. However over the past month
  or so, on subsequent reboots after upgrades, GDM3 accepts focus but
  won't accept any input either from keyboard or mouse.

  The work-a-round that works for me is to 'Ctl+Alt+F(number) to get to
  a console, which won't give me a login prompt until I hit the 'return'
  key. Then I can go back to the GDM3 session and login normally.

  I'm reporting this from Vanilla Gnome Ubuntu 18.04, all current
  updates applied.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 
4.15.0-20201805060708.0+mediatree+hauppauge-generic 4.15.17
  Uname: Linux 4.15.0-20201805060708-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jun 14 08:44:36 2018
  InstallationDate: Installed on 2018-01-19 (146 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

2018-06-14 Thread Andreas Schildbach

I'm trying the bionic version of the proposed nux-tools
(4.0.8+18.04.20180613.5-0ubuntu1) and it works fine so far.

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

Title:
  leftover conffile forces GNOME is software rendering

Status in mesa package in Ubuntu:
  New
Status in nux package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  New
Status in nux source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  New
Status in nux source package in Artful:
  Fix Committed
Status in mesa source package in Bionic:
  New
Status in nux source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case ]

  · Install xenial
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
in an environment with no 3d support (VMs are easy tests)

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  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: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

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

[Desktop-packages] [Bug 1719038] Re: X Server crashes during log in VM since 16.04.2

2018-06-14 Thread RussianNeuroMancer

>  Is this still an issue for 16.04

Not for 16.04.0-16.04.2 as far I remember, but still issue for 16.0.3
and 16.04.4. I guess as soon as 16.04.5 get released this issue should
be harder to reproduce, just like in 18.04 now.

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

Title:
  X Server crashes during log in VM since 16.04.2

Status in X.Org X server:
  Unknown
Status in qemu package in Ubuntu:
  New
Status in spice package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  If I change screen resolution in my VM with Kubuntu 16.04.3 and then
  make log off and then log on X server is crashes doesn't able me to
  log in.

  Please, look in Xorg.0.log.old for backtrace.

  Also the appropriate report on freedesktop.org:
  https://bugs.freedesktop.org/show_bug.cgi?id=102554

  Host:
  Kubuntu 17.04
  Linux 4.13.2
  libvirt-bin 3.6.0
  qemu 2.10

  
  Guest:
  Kubuntu 16.04.3
  Linux 4.10.0-35-generic
  xserver-xorg-video-qxl 0.1.4-3ubuntu3
  xserver-common 1.18.4-0ubuntu0.3

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 23 01:27:49 2017
  InstallationDate: Installed on 2016-09-16 (371 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

Marco, I don't think there is a solution that satisfies all the
requirements and doesn't involve nux cooperating in some way. I've given
you mostly-working debdiffs now - can we please move forward with them?

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

Title:
  leftover conffile forces GNOME is software rendering

Status in mesa package in Ubuntu:
  New
Status in nux package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  New
Status in nux source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  New
Status in nux source package in Artful:
  Fix Committed
Status in mesa source package in Bionic:
  New
Status in nux source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case ]

  · Install xenial
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
in an environment with no 3d support (VMs are easy tests)

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  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: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

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

[Desktop-packages] [Bug 1776447]

2018-06-14 Thread Steve Dodd

I've hit this on Ubuntu 18.04 (xorg 1.19.6), modesetting driver. I have
opened a bug over there in case someone on that side has time to
investigate (https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1776447)

Interestingly, if I use VirtualGL as a true GLX proxy..

VGL_READBACK=sync LIBGL_ALWAYS_INDIRECT=1 VGL_DISPLAY=192.168.128.163:0
VGL_LOGO=1 vglrun +v /opt/VirtualGL/bin/glxspheres64

.. which I'm pretty sure it was never designed to do, things run
successfully. So IGLX obviously isn't catastrophically broken ..

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

Title:
  Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to
  crash

Status in X.Org X server:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  There's already an upstream bug report here:

  https://bugs.freedesktop.org/show_bug.cgi?id=99555

  Basically, with Option "IndirectGLX" "True" and
  LIBGL_ALWAYS_INDIRECT=1 I get immediate crashes e.g. with glxgear:

  steved@xubuntu:~$ LIBGL_ALWAYS_INDIRECT=true glxgears 
  Running synchronized to the vertical refresh.  The framerate should be
  approximately the same as the monitor refresh rate.
  X Error of failed request:  255
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  1 (X_GLXRender)
Serial number of failed request:  42
Current serial number in output stream:  936

  I am trying to run what is effectively a traditional X Terminal, but
  as the hardware I am using has a 3D accelerated chipset it seems
  sensible to try to use it..

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Tue Jun 12 10:09:30 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-22-generic, x86_64: installed
   rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Device [8086:2212]
  InstallationDate: Installed on 2018-05-31 (11 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: AZW S I
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=/dev/mapper/xubuntu--vg-root ro noresume
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 00.12
  dmi.board.asset.tag: Default string
  dmi.board.name: AB1
  dmi.board.vendor: IP3 Tech
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr00.12:bd12/18/2017:svnAZW:pnSI:pvrDefaultstring:rvnIP3Tech:rnAB1:rvrDefaultstring:cvnDefaultstring:ct35:cvrDefaultstring:
  dmi.product.family: Mini PC
  dmi.product.name: S I
  dmi.product.version: Default string
  dmi.sys.vendor: AZW
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1728764] Re: gnome-screenshot will no longer save screenshots anywhere

2018-06-14 Thread Che

I've managed to reproduce this bug by changing the default hotkey of
"Save a screenshot of an area to pictures" from `Shift + Print` to
`Shift + Ctrl + Print`.

I also would hear the shutter noise and see a screen flash without any
picture being saved.

After changing the hotkey back to its default the screenshots started
working again.

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

Title:
  gnome-screenshot will no longer save screenshots anywhere

Status in gnome-screenshot package in Ubuntu:
  Confirmed

Bug description:
  It was working quite alright 2 weeks ago. I have changed nothing since
  then.

  Tonight, when trying to screencap for the gnome-sushi bug, it would
  flash as if taking a screencap for both fullscreen, and selected area
  style screenshots.

  However, it wouldn't save the screenshot anywhere.

  I'm not certain where it used to save (by default, up until 2 weeks
  ago), but I think it was Pictures.

  If I search in Nautilus for "Screenshot from 2017-10-30" I see
  previous screenshots, up until 10-30, and there are no screenshots
  saved from today, or anything since 2 weeks ago.

  I tried changing the auto-save-directory in gconf, as well as via
  terminal commands. I tried with different styles: "file:///.." as
  well as simply "/home" No matter what, screenshots still flash and
  make the click sound, but do not save in the directory. Not Desktop,
  Pictures, /tmp, Downloads.

  If I call "gnome-screenshot --interactive" from Terminal, the save
  dialog does successfully save the screenshot.

  I have no idea how to replicate this bug, because I did nothing to
  create this bug. Just 2 weeks after taking several successful
  screenshots, gnome-screenshot no longer saves screenshots. Anywhere.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-screenshot 3.25.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 30 22:11:36 2017
  InstallationDate: Installed on 2017-09-20 (40 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screenshot
  UpgradeStatus: Upgraded to artful on 2017-10-04 (26 days ago)

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

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

[Desktop-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

2018-06-14 Thread Treviño

Yeah, I basically did the same too, but honestly I didn't want to change
nux again with another SRU (I preferred to fix this with just one on
that side); and most importantly in a such way. As it would now include
some checks that depends on changes done in other packages, making from
my POV things even more hackish and annoy to matain and easy to be
broken.

Not that other solutions wouldn't involve the other package (say mesa)
to act on nux file, but that should be in a way that nux is not aware of
that, creating any kind of "inter-dependency" in between them.

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

Title:
  leftover conffile forces GNOME is software rendering

Status in mesa package in Ubuntu:
  New
Status in nux package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  New
Status in nux source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  New
Status in nux source package in Artful:
  Fix Committed
Status in mesa source package in Bionic:
  New
Status in nux source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case ]

  · Install xenial
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
in an environment with no 3d support (VMs are easy tests)

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  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: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

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

[Desktop-packages] [Bug 1776563] Re: Ubuntu 18.04 kernel can't load kernel on Acer Aspire A315 (Ryzen5/Radeon/FHD)

** Summary changed:

- Acer Aspire A315 (Ryzen5/Radeon/FHD) Ubuntu 18.04 kernel cant load
+ Ubuntu 18.04 kernel can't load kernel on Acer Aspire A315 (Ryzen5/Radeon/FHD)

** Summary changed:

- Ubuntu 18.04 kernel can't load kernel on Acer Aspire A315 (Ryzen5/Radeon/FHD)
+ Ubuntu 18.04 can't load kernel on Acer Aspire A315 (Ryzen5/Radeon/FHD)

** No longer affects: bugzilla (Ubuntu)

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

Title:
  Ubuntu 18.04 can't load kernel on Acer Aspire A315 (Ryzen5/Radeon/FHD)

Status in amd:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315
  I've just bought a new AMD Ryzen/Radeon notebook (Acer Aspire 3) and I wanted 
to install an Ubuntu/Kubuntu 18.04 on it. I checked the bios settings and uefi 
was the only boot option, so there is no legacy mode what I had used with my 
old computer before. I downloaded the normal iso image and made an usb boot 
pendrive using mkusb. The boot was okay, I got an uefi type menu but after 
starting the kernel it paniced(?) instantly. 
  Error messages: ACPI Error [MAC0] Namespace lookup failure 
  ACPI ERROR 1 table load failures, 13 successful 
  BUG: soft lockup CPU#0 stuck for 22s
  ...
  ...
  EFI VGA framebuffer device
  clocksource tsc mask
  Switching to colour framebuffer device
  [28.040001] ...
  ...
  ...

  I've tried to boot the same pendrive on my girlfriend's Acer
  Travelmate with uefi and worked well.

  I searched and I found that the problem is maybe in connection with
  uefi framebuffer but I am not sure.

  Ubuntu 16.04 can be loaded with nomodeset and noacpi parameters but
  for 18.04 none of them are working. I tried 4.16,4.17 kernels too
  (replaced on live usb) but without any success. The result is totally
  equivalent.

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

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

[Desktop-packages] [Bug 1776563] Re: Acer Aspire A315 (Ryzen5/Radeon/FHD) Ubuntu 18.04 kernel cant load

apport-collect 1776563 can't be entered because the kernel can not load.

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

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

Title:
  Ubuntu 18.04 can't load kernel on Acer Aspire A315 (Ryzen5/Radeon/FHD)

Status in amd:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315
  I've just bought a new AMD Ryzen/Radeon notebook (Acer Aspire 3) and I wanted 
to install an Ubuntu/Kubuntu 18.04 on it. I checked the bios settings and uefi 
was the only boot option, so there is no legacy mode what I had used with my 
old computer before. I downloaded the normal iso image and made an usb boot 
pendrive using mkusb. The boot was okay, I got an uefi type menu but after 
starting the kernel it paniced(?) instantly. 
  Error messages: ACPI Error [MAC0] Namespace lookup failure 
  ACPI ERROR 1 table load failures, 13 successful 
  BUG: soft lockup CPU#0 stuck for 22s
  ...
  ...
  EFI VGA framebuffer device
  clocksource tsc mask
  Switching to colour framebuffer device
  [28.040001] ...
  ...
  ...

  I've tried to boot the same pendrive on my girlfriend's Acer
  Travelmate with uefi and worked well.

  I searched and I found that the problem is maybe in connection with
  uefi framebuffer but I am not sure.

  Ubuntu 16.04 can be loaded with nomodeset and noacpi parameters but
  for 18.04 none of them are working. I tried 4.16,4.17 kernels too
  (replaced on live usb) but without any success. The result is totally
  equivalent.

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

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

[Desktop-packages] [Bug 1743736] Re: In overview, windows from all workspaces are shown for the second display (when using "Workspaces span displays")

2018-06-14 Thread Alexander

I can confirm it as well. Occurred after upgrade to 18.04 (X and
Wayland), worked fine with 16.04 (on Gnome). Unfortunately this is a
core feature to my workflow, is there a workaround?

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

Title:
  In overview, windows from all workspaces are shown for the second
  display (when using "Workspaces span displays")

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

Bug description:
  I have disabled workspaces on primary display only, and I have enabled
  workspaces to span displays, in tweak tool.

  Now things mostly work how I expect. Windows are isolated to the
  workspace they are and I can move them between displays (monitors).
  The issue is if I go into an overview mode. Then, for the primary
  display, I see only windows from my current workspace. But for the
  secondary display, I see windows from all workspaces being shown in
  the overview mode.

  I would expect that only the windows from the current workspace are
  shown also on the secondary display in the overview mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 02:19:13 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-11-20 (57 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

  This bug also affects the new LTS release:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 23 15:25:07 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-05-18 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 970686] Re: Activities search does not complete recent documents anymore

2018-06-14 Thread Stu

Confirming.

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

Title:
  Activities search does not complete recent documents anymore

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

Bug description:
  In Gnome 3.2/Ubuntu 11.10, typing recent document name displayed the document 
in suggested programs/files to open.
  This no longer happens in 3.4/12.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-shell 3.4.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-21.34-generic-pae 3.2.13
  Uname: Linux 3.2.0-21-generic-pae i686
  ApportVersion: 2.0-0ubuntu2
  Architecture: i386
  Date: Sun Apr  1 11:17:18 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to precise on 2012-03-31 (0 days ago)

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

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

[Desktop-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

** Patch added: "mesa.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+attachment/5152448/+files/mesa.debdiff

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

Title:
  leftover conffile forces GNOME is software rendering

Status in mesa package in Ubuntu:
  New
Status in nux package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  New
Status in nux source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  New
Status in nux source package in Artful:
  Fix Committed
Status in mesa source package in Bionic:
  New
Status in nux source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case ]

  · Install xenial
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
in an environment with no 3d support (VMs are easy tests)

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  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: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

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

[Desktop-packages] [Bug 1760450] Re: [nvidia] Xorg crashed with signal 7 in _dl_fixup() from _dl_runtime_resolve_xsavec() called from nvidia_drv.so

2018-06-14 Thread Julien Olivier

I confirm that adding "scsi_mod.scan=sync" does indeed fix this bug.

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

Title:
  [nvidia] Xorg crashed with signal 7 in _dl_fixup() from
  _dl_runtime_resolve_xsavec() called from nvidia_drv.so

Status in xorg-server package in Ubuntu:
  Confirmed
Status in Fedora:
  Unknown

Bug description:
  after login session(suspend mode)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  Date: Sun Apr  1 20:34:29 2018
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  InstallationDate: Installed on 2017-09-02 (211 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:
   
  Signal: 7
  SourcePackage: xorg-server
  StacktraceTop:
   _dl_fixup (l=0x559c10faa5a0, reloc_arg=) at 
../elf/dl-runtime.c:84
   _dl_runtime_resolve_xsavec () at ../sysdeps/x86_64/dl-trampoline.h:125
   ?? () from /usr/lib/xorg/modules/libwfb.so
   wfbComposite () from /usr/lib/xorg/modules/libwfb.so
   ?? () from /usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so
  Title: Xorg crashed with signal 7 in _dl_fixup()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

This is the solution that I proposed to you in private. It is a fix to
mesa (a "common" package) and a followup to nux-tools.

It needs some testing. In particular I don't think I picked the right
mesa package to use, and we also need to check with the mesa maintainer.
There are various version numbers in there that need to be correct for
the target release.

A basic test worked OK though (libegl1-mesa is because I had it in an
even more wrong package at the time). Remove nux-tools, broken conffile
is left around, upgrade mesa, it's fixed, install new nux-tools and it's
installed with the right content and no prompt:

root@nux-tools-test:~# apt remove nux-tools
...
root@nux-tools-test:~# ls /etc/X11/Xsession.d/50_check_unity_support 
/etc/X11/Xsession.d/50_check_unity_support
root@nux-tools-test:~# sudo apt full-upgrade
...
Broken /etc/X11/Xsession.d/50_check_unity_support and removed nux-tools found, 
moving aside...
root@nux-tools-test:~# sudo apt install nux-tools
Found saved /etc/X11/Xsession.d/50_check_unity_support.mesa-save file, moving 
it back in place...
Unpacking nux-tools (4.0.8+18.04.20180613.5-0ubuntu2) ...
Setting up nux-tools (4.0.8+18.04.20180613.5-0ubuntu2) ...
Installing new version of config file 
/etc/X11/Xsession.d/50_check_unity_support ...
root@nux-tools-test:~# cat /etc/X11/Xsession.d/50_check_unity_support
# This file is sourced by Xsession(5), not executed.
# If the hardware does not pass unity_support_test, fall back to LLVMpipe
# which does.

if [ "x$DESKTOP_SESSION" = "xubuntu" ] && [ -x 
"/usr/lib/nux/unity_support_test" ]; then
(
IFS=':'
for d in $XDG_CURRENT_DESKTOP; do
if [ "x$d" = "xUnity" ] || [ "x$d" = "xUnity7" ]; then
return 0
fi
done
return 1
)

if [ $? = 0 ]; then
/usr/lib/nux/unity_support_test || export LIBGL_ALWAYS_SOFTWARE=1
fi
fi

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

Title:
  leftover conffile forces GNOME is software rendering

Status in mesa package in Ubuntu:
  New
Status in nux package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  New
Status in nux source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  New
Status in nux source package in Artful:
  Fix Committed
Status in mesa source package in Bionic:
  New
Status in nux source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case ]

  · Install xenial
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
in an environment with no 3d support (VMs are easy tests)

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  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: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)

[Desktop-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

** Patch added: "nux.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+attachment/5152447/+files/nux.debdiff

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

Title:
  leftover conffile forces GNOME is software rendering

Status in mesa package in Ubuntu:
  New
Status in nux package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  New
Status in nux source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  New
Status in nux source package in Artful:
  Fix Committed
Status in mesa source package in Bionic:
  New
Status in nux source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case ]

  · Install xenial
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
in an environment with no 3d support (VMs are easy tests)

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  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: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

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

[Desktop-packages] [Bug 1736690] Re: [Bionic] WiFi connection keeps dropping after some time

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

Title:
  [Bionic] WiFi connection keeps dropping after some time

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  From time to time my wireless network connection drops. It works again
  for some time and then it suddenly drops again.

  When this happens, I switch the wifi setting off and on again (from
  GNOME settings). As wifi is on again, I get connected again and
  everything works again for some time (could be half an hour as few
  hours).

  This bug is a possible duplicate of 1710382, but I'm reporting it from
  bionic.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3
  Uname: Linux 4.14.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Dec  6 11:26:06 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-08-21 (106 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0 proto static metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.202 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICETYPE  STATEDBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   wlp3s0wifi  connected/org/freedesktop/NetworkManager/Devices/3  
~ ~ S h i n w a r y o k u ~ ~  46fc1e57-8d59-4681-b79a-13f8504317ce  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   enp4s0f1  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
-- ---- 

   loloopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
-- ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1776862] [NEW] package gdm3 3.28.2-0ubuntu1.2 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 127

2018-06-14 Thread golomb

Public bug reported:

no more comment

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: gdm3 3.28.2-0ubuntu1.2
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Thu Jun 14 10:37:54 2018
ErrorMessage: installed gdm3 package post-installation script subprocess 
returned error exit status 127
InstallationDate: Installed on 2018-05-29 (16 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: gdm3
Title: package gdm3 3.28.2-0ubuntu1.2 failed to install/upgrade: installed gdm3 
package post-installation script subprocess returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.gdm3.custom.conf: [modified]
mtime.conffile..etc.gdm3.custom.conf: 2018-05-29T07:41:49.115219

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


** Tags: amd64 apport-package bionic

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

Title:
  package gdm3 3.28.2-0ubuntu1.2 failed to install/upgrade: installed
  gdm3 package post-installation script subprocess returned error exit
  status 127

Status in gdm3 package in Ubuntu:
  New

Bug description:
  no more comment

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Thu Jun 14 10:37:54 2018
  ErrorMessage: installed gdm3 package post-installation script subprocess 
returned error exit status 127
  InstallationDate: Installed on 2018-05-29 (16 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: gdm3
  Title: package gdm3 3.28.2-0ubuntu1.2 failed to install/upgrade: installed 
gdm3 package post-installation script subprocess returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.gdm3.custom.conf: [modified]
  mtime.conffile..etc.gdm3.custom.conf: 2018-05-29T07:41:49.115219

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

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

[Desktop-packages] [Bug 1776863] [NEW] package gdm3 3.28.2-0ubuntu1.2 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 127

2018-06-14 Thread golomb

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

Public bug reported:

no more info

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: gdm3 3.28.2-0ubuntu1.2
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Thu Jun 14 10:37:54 2018
ErrorMessage: installed gdm3 package post-installation script subprocess 
returned error exit status 127
InstallationDate: Installed on 2018-05-29 (16 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: gdm3
Title: package gdm3 3.28.2-0ubuntu1.2 failed to install/upgrade: installed gdm3 
package post-installation script subprocess returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.gdm3.custom.conf: 2018-05-29T07:41:49.115219

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


** Tags: amd64 apport-package bionic

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

Title:
  package gdm3 3.28.2-0ubuntu1.2 failed to install/upgrade: installed
  gdm3 package post-installation script subprocess returned error exit
  status 127

Status in gdm3 package in Ubuntu:
  New

Bug description:
  no more info

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Thu Jun 14 10:37:54 2018
  ErrorMessage: installed gdm3 package post-installation script subprocess 
returned error exit status 127
  InstallationDate: Installed on 2018-05-29 (16 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: gdm3
  Title: package gdm3 3.28.2-0ubuntu1.2 failed to install/upgrade: installed 
gdm3 package post-installation script subprocess returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2018-05-29T07:41:49.115219

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

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

[Desktop-packages] [Bug 1769954] Re: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

This bug was fixed in the package desktop-file-utils -
0.23-1ubuntu3.18.04.1

---
desktop-file-utils (0.23-1ubuntu3.18.04.1) bionic; urgency=medium

  * Use noawait trigger (LP: #1769954)

 -- Julian Andres Klode   Tue, 05 Jun 2018 10:30:25
-0700

** Changed in: desktop-file-utils (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in desktop-file-utils package in Ubuntu:
  Fix Released
Status in desktop-file-utils source package in Xenial:
  Fix Released
Status in desktop-file-utils source package in Artful:
  Fix Released
Status in desktop-file-utils source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  dist-upgrade from artful to bionic fails with attached tarball

  [Test case]
  artful:
  1. Install new desktop-file-utils
  2. check that dist-upgrade works
  bionic:
  1. Download new deb
  2. Run apt-get dist-upgrade path/to/deb in xenial to trigger upgrade with 
that deb being upgraded too.

  [Regression potential]
  Packages installing desktop files to /usr/share/applications won't get put in 
triggers-awaited state due to d-f-u.

  [Other info]
  Just fixing bionic makes an apt dist-upgrade work (not sure about 
do-release-upgrade); but it might not work in other circumstances I guess, so 
it might make sense to upload the fix to older releases.

  We can only verify artful and bionic, though, so xenial would have to
  go in unchecked.

  The trigger causes the desktop database to be updated, as such it is
  possible to use noawait here, as there's no reason for packages
  shipping .desktop files to be not configured just because the database
  has not been updated yet.

  The same change has been made in Debian in 0.23-2.

  [Original bug report]
  run `sudo do-release-upgrade` on a relativity new 16.04 EC2 instance.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: desktop-file-utils 0.23-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Tue May  8 16:59:12 2018
  Ec2AMI: ami-70873908
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2a
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ErrorMessage: dependency problems - leaving triggers unprocessed
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: desktop-file-utils
  Title: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: 
dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-05-08 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1769954/+subscriptions

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

[Desktop-packages] [Bug 1769954] Re: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

This bug was fixed in the package desktop-file-utils -
0.23-1ubuntu3.17.10.1

---
desktop-file-utils (0.23-1ubuntu3.17.10.1) artful; urgency=medium

  * Use noawait trigger (LP: #1769954)

 -- Julian Andres Klode   Tue, 05 Jun 2018 10:30:25
-0700

** Changed in: desktop-file-utils (Ubuntu Artful)
   Status: Fix Committed => Fix Released

** Changed in: desktop-file-utils (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in desktop-file-utils package in Ubuntu:
  Fix Released
Status in desktop-file-utils source package in Xenial:
  Fix Released
Status in desktop-file-utils source package in Artful:
  Fix Released
Status in desktop-file-utils source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  dist-upgrade from artful to bionic fails with attached tarball

  [Test case]
  artful:
  1. Install new desktop-file-utils
  2. check that dist-upgrade works
  bionic:
  1. Download new deb
  2. Run apt-get dist-upgrade path/to/deb in xenial to trigger upgrade with 
that deb being upgraded too.

  [Regression potential]
  Packages installing desktop files to /usr/share/applications won't get put in 
triggers-awaited state due to d-f-u.

  [Other info]
  Just fixing bionic makes an apt dist-upgrade work (not sure about 
do-release-upgrade); but it might not work in other circumstances I guess, so 
it might make sense to upload the fix to older releases.

  We can only verify artful and bionic, though, so xenial would have to
  go in unchecked.

  The trigger causes the desktop database to be updated, as such it is
  possible to use noawait here, as there's no reason for packages
  shipping .desktop files to be not configured just because the database
  has not been updated yet.

  The same change has been made in Debian in 0.23-2.

  [Original bug report]
  run `sudo do-release-upgrade` on a relativity new 16.04 EC2 instance.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: desktop-file-utils 0.23-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Tue May  8 16:59:12 2018
  Ec2AMI: ami-70873908
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2a
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ErrorMessage: dependency problems - leaving triggers unprocessed
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: desktop-file-utils
  Title: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: 
dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-05-08 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1769954/+subscriptions

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

[Desktop-packages] [Bug 1769954] Re: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

This bug was fixed in the package desktop-file-utils - 0.22-1ubuntu5.2

---
desktop-file-utils (0.22-1ubuntu5.2) xenial; urgency=medium

  * Use noawait trigger (LP: #1769954)

 -- Julian Andres Klode   Tue, 05 Jun 2018 11:43:53
-0700

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

Title:
  package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in desktop-file-utils package in Ubuntu:
  Fix Released
Status in desktop-file-utils source package in Xenial:
  Fix Released
Status in desktop-file-utils source package in Artful:
  Fix Released
Status in desktop-file-utils source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  dist-upgrade from artful to bionic fails with attached tarball

  [Test case]
  artful:
  1. Install new desktop-file-utils
  2. check that dist-upgrade works
  bionic:
  1. Download new deb
  2. Run apt-get dist-upgrade path/to/deb in xenial to trigger upgrade with 
that deb being upgraded too.

  [Regression potential]
  Packages installing desktop files to /usr/share/applications won't get put in 
triggers-awaited state due to d-f-u.

  [Other info]
  Just fixing bionic makes an apt dist-upgrade work (not sure about 
do-release-upgrade); but it might not work in other circumstances I guess, so 
it might make sense to upload the fix to older releases.

  We can only verify artful and bionic, though, so xenial would have to
  go in unchecked.

  The trigger causes the desktop database to be updated, as such it is
  possible to use noawait here, as there's no reason for packages
  shipping .desktop files to be not configured just because the database
  has not been updated yet.

  The same change has been made in Debian in 0.23-2.

  [Original bug report]
  run `sudo do-release-upgrade` on a relativity new 16.04 EC2 instance.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: desktop-file-utils 0.23-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Tue May  8 16:59:12 2018
  Ec2AMI: ami-70873908
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2a
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ErrorMessage: dependency problems - leaving triggers unprocessed
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: desktop-file-utils
  Title: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: 
dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-05-08 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1769954/+subscriptions

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

[Desktop-packages] [Bug 1769954] Update Released