[Desktop-packages] [Bug 1731941] [NEW] duplicity should be installed by default as a dependency of deja-dup

[Robert Orzanna]

Public bug reported:

Just tested my Deja-dup backup configuration on a fresh install of
18.04.

I was prompted to install duplicity.

I am wondering whether duplicity should not better be installed as a
dependency of deja-dup which is the default backup tool.

What do you think?

** Affects: deja-dup (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: linphone (Ubuntu) => deja-dup (Ubuntu)

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

Title:
  duplicity should be installed by default as a dependency of deja-dup

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Just tested my Deja-dup backup configuration on a fresh install of
  18.04.

  I was prompted to install duplicity.

  I am wondering whether duplicity should not better be installed as a
  dependency of deja-dup which is the default backup tool.

  What do you think?

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

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

[Desktop-packages] [Bug 1731862] [NEW] old printer epson epl-6200 doesn't work on 16.04

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

My old printer epson epl-6200 doesn't work on 16.04. It seems that there
are solution for older version of Ubuntu:
https://ubuntuforums.org/showthread.php?t=1558950 but I tried and I
couldn't solve it.

** Affects: foomatic-db (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment
-- 
old printer epson epl-6200 doesn't work on 16.04
https://bugs.launchpad.net/bugs/1731862
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to foomatic-db in Ubuntu.

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

[Desktop-packages] [Bug 1386257] Re: intel-microcode should be installed by default, when the CPU is GenuineIntel

[Dimitri John Ledkov]

** Description changed:

  intel-microcode should be installed by default on the bare-metal systems
  which are running on GenuineIntel CPUs, by the installers.
  
  Similarly other microcode packages for other CPUs brands should be
  considered for inclusion (e.g. amd64-microcode).
  
  I hope that ubuntu-drivers-common can gain ability to detect cpu series
  and/or vendors, packages that provide microcodes similarly declare
  support for cpu series and/or vendors, the microcode packages are
  shipped on the CDs in the pool directory, and installed on to the target
  machines as part of the installation.
  
  This should help with rapid correction of bugs and behaviour of the CPUs
  in the field.
+ 
+ 2017 update, amd64-microcode should also be seeded, as it is useful to
+ have it autoinstallable. In the recent years there have been critical
+ CPU security vulnerabilities which got fixed with microcode updates.

** Also affects: amd64-microcode (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  intel-microcode should be installed by default, when the CPU is
  GenuineIntel

Status in intel:
  Fix Released
Status in Ubuntu Kylin:
  Fix Released
Status in amd64-microcode package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntukylin-meta package in Ubuntu:
  Fix Released

Bug description:
  intel-microcode should be installed by default on the bare-metal
  systems which are running on GenuineIntel CPUs, by the installers.

  Similarly other microcode packages for other CPUs brands should be
  considered for inclusion (e.g. amd64-microcode).

  I hope that ubuntu-drivers-common can gain ability to detect cpu
  series and/or vendors, packages that provide microcodes similarly
  declare support for cpu series and/or vendors, the microcode packages
  are shipped on the CDs in the pool directory, and installed on to the
  target machines as part of the installation.

  This should help with rapid correction of bugs and behaviour of the
  CPUs in the field.

  2017 update, amd64-microcode should also be seeded, as it is useful to
  have it autoinstallable. In the recent years there have been critical
  CPU security vulnerabilities which got fixed with microcode updates.

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

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

[Desktop-packages] [Bug 1731911] [NEW] Xwayland crashed with SIGABRT in OsAbort()

[Jean-Baptiste Lallement]

Public bug reported:

no idea how to reproduce

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: xwayland 2:1.19.5-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-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME-Greeter:GNOME
Date: Mon Nov 13 13:55:16 2017
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.13.0-15-generic, x86_64: installed
 bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
ExecutablePath: /usr/bin/Xwayland
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller 
[1043:1507]
InstallationDate: Installed on 2013-09-03 (1531 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
MachineType: ASUSTeK COMPUTER INC. UX32VD
ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -core -listen 4 
-listen 5 -displayfd 6
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/false
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 OsAbort ()
 ?? ()
 FatalError ()
 ?? ()
 ?? ()
Title: Xwayland crashed with SIGABRT in OsAbort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 01/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX32VD.214
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX32VD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: UX
dmi.product.name: UX32VD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.85-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-crash bionic need-amd64-retrace single-occurrence 
third-party-packages ubuntu

** Information type changed from Private to Public

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

Title:
  Xwayland crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  no idea how to reproduce

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.5-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-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Nov 13 13:55:16 2017
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-15-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:1507]
  InstallationDate: Installed on 2013-09-03 (1531 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -core -listen 4 
-listen 5 -displayfd 6
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/false
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart
  

[Desktop-packages] [Bug 1731910] [NEW] gnome-shell-calendar-server assert failure: *** Error in `/usr/lib/gnome-shell/gnome-shell-calendar-server': free(): invalid pointer: 0x0000559ef762f960 ***

[Jean-Baptiste Lallement]

Public bug reported:

no idea how to reproduce.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.26.1-0ubuntu6
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu4
Architecture: amd64
AssertionMessage: *** Error in 
`/usr/lib/gnome-shell/gnome-shell-calendar-server': free(): invalid pointer: 
0x559ef762f960 ***
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  8 10:13:10 2017
DisplayManager: gdm3
ExecutablePath: /usr/lib/gnome-shell/gnome-shell-calendar-server
InstallationDate: Installed on 2013-09-03 (1531 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcCmdline: /usr/lib/gnome-shell/gnome-shell-calendar-server
ProcEnviron:
 XDG_RUNTIME_DIR=
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=fr_FR.UTF-8
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f6c814714e8 
"*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (action=, str=0x7f6c8146de6e "free(): invalid 
pointer", ptr=, ar_ptr=) at malloc.c:5425
 _int_free (av=0x7f6c816a3c20 , p=, have_lock=0) at 
malloc.c:4174
 __GI___libc_free (mem=) at malloc.c:3144
 e_cal_component_free_datetime () at /usr/lib/x86_64-linux-gnu/libecal-1.2.so.19
Title: gnome-shell-calendar-server assert failure: *** Error in 
`/usr/lib/gnome-shell/gnome-shell-calendar-server': free(): invalid pointer: 
0x559ef762f960 ***
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

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


** Tags: amd64 apport-crash bionic need-amd64-retrace third-party-packages

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

Title:
  gnome-shell-calendar-server assert failure: *** Error in `/usr/lib
  /gnome-shell/gnome-shell-calendar-server': free(): invalid pointer:
  0x559ef762f960 ***

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  no idea how to reproduce.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.1-0ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  AssertionMessage: *** Error in 
`/usr/lib/gnome-shell/gnome-shell-calendar-server': free(): invalid pointer: 
0x559ef762f960 ***
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 10:13:10 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-calendar-server
  InstallationDate: Installed on 2013-09-03 (1531 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-calendar-server
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=fr_FR.UTF-8
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f6c814714e8 
"*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (action=, str=0x7f6c8146de6e "free(): invalid 
pointer", ptr=, ar_ptr=) at malloc.c:5425
   _int_free (av=0x7f6c816a3c20 , p=, have_lock=0) 
at malloc.c:4174
   __GI___libc_free (mem=) at malloc.c:3144
   e_cal_component_free_datetime () at 
/usr/lib/x86_64-linux-gnu/libecal-1.2.so.19
  Title: gnome-shell-calendar-server assert failure: *** Error in 
`/usr/lib/gnome-shell/gnome-shell-calendar-server': free(): invalid pointer: 
0x559ef762f960 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

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

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

[Desktop-packages] [Bug 1710370] Re: Cheese crashes on launch in Ubuntu 17.10 if no camera device is present

[Bug Watch Updater]

** Changed in: cheese
   Status: Unknown => Confirmed

** Changed in: cheese
   Importance: Unknown => Medium

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

Title:
  Cheese crashes on launch in Ubuntu 17.10 if no camera device is
  present

Status in Cheese:
  Confirmed
Status in cheese package in Ubuntu:
  New

Bug description:
  Cheese crashes on launch in Ubuntu 17.10 if the computer does not have
  any camera device connected.

  
  (cheese:3620): cheese-CRITICAL **: cheese_camera_device_get_name: assertion 
'CHEESE_IS_CAMERA_DEVICE (device)' failed

  (cheese:3620): GLib-CRITICAL **: g_variant_new_string: assertion
  'string != NULL' failed

  (cheese:3620): GLib-CRITICAL **: g_variant_ref_sink: assertion 'value
  != NULL' failed

  (cheese:3620): GLib-GIO-CRITICAL **: g_settings_schema_key_type_check:
  assertion 'value != NULL' failed

  (cheese:3620): GLib-CRITICAL **: g_variant_get_type_string: assertion
  'value != NULL' failed

  (cheese:3620): GLib-GIO-CRITICAL **: g_settings_set_value: key
  'camera' in 'org.gnome.Cheese' expects type 's', but a GVariant of
  type '(null)' was given

  (cheese:3620): GLib-CRITICAL **: g_variant_unref: assertion 'value !=
  NULL' failed

  ** (cheese:3620): CRITICAL **:
  cheese_preferences_dialog_setup_resolutions_for_device: assertion
  'device != NULL' failed

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

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

[Desktop-packages] [Bug 1713457] Re: DNS search domain not removed from resolv.conf on disconnect

[Laurent Bigonville]

OK I can confirm that uninstalling resolvconf is fixing that behavior
here

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

Title:
  DNS search domain not removed from resolv.conf on disconnect

Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  When I connect to a wireless network that sets a DNS search domain
  name via DHCP, the line 'search ' is added to /etc/resolv.conf
  as expected.  But if I then disconnect and connect to a different
  network, it is not removed from resolv.conf.  If the second network
  also sets a search domain name, that one gets appended to resolv.conf
  along with the first one, and so on.  Depending on the network, this
  can cause DNS leaks, name resolution failures, or other misbehavior.

  To be sure this wasn't some kind of user configuration issue, I
  reproduced this on the artful daily live image (artful-desktop-
  amd64.iso, 2017-08-27), from which I'm writing this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 28 10:34:22 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 172.20.20.1 dev wlp3s0 proto static metric 600
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
   172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170827)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlp3s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
xfinitywifi  39ffbbfc-1c1e-41c9-b3eb-c513065c3ea6  
/org/freedesktop/NetworkManager/ActiveConnection/2
   enp0s31f6  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--   ----
   lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

-- 
Mailing list: https://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 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while

[Kasey Erickson]

When I upgraded to 17.10 I made sure it was a fresh install, not an
in-place upgrade.  Sometimes broken configurations are left over when
upgrading in place.


On Mon, Nov 13, 2017 at 3:50 AM, Alexander Adam <1575...@bugs.launchpad.net>
wrote:

> I can't confirm what Kasey (kasey-erickson) wrote: issue still appears in
> Ubuntu 17.10.
> I upgraded from 17.04. So if it really should be fixed in 17.10 I'm very
> open to hints for particular config purges/reinstallations or actually
> anything that could help.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1575078
>
> Title:
>   [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a
>   while
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+
> bug/1575078/+subscriptions
>

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

Title:
  [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a
  while

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I'm experiencing a strange behavior with a headphone jack on my
  laptop.

  I have an external audio speaker connected to it. When I disconnect the 
speaker and reconnect it again it stops working.
  Even more, laptop audio stops working too. And after the reboot, I don't even 
see any of the audio devices.

  I've googled a lot and tried different fixes from forums with no luck.
  After a while, I've accidentally discovered that putting the laptop to
  the sleep mode and rebooting system after brings audio back to live.
  Even more, if speakers were attached during this sleep-reboot
  procedure, they are starting to work as well.

  However, after the next reboot speakers are not working again. And if
  I will plug them out and in - problem with completely missing audio
  returns.

  P.S. I'm using laptop-mode-tools package on my laptop. Recovery after
  hibernation made me believe that it's somehow related. But after
  uninstalling this package nothing really changed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   kop3224 F...m pulseaudio
   /dev/snd/controlC0:  kop3224 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr 26 12:17:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Встроенное аудио - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Sound works for a while, then breaks
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after 
a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1731460] Re: Click on desktop folders

[Epifani Andrea]

I have same behaviors.
The different icons on my desktop not working. (home, trash and any folder)
also with right click and select Open or open in new window or in new panel.
The Other icons works successfully: *.desktop and files with default 
application.

In my syslog:
Unable to create File Manager freedesktop proxy: Errore nel chiamare 
StartServiceByName per org.freedesktop.FileManager1: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute 
program org.freedesktop.FileManager1: No such file or directory

and:
WARNING: Application 'nautilus-classic.desktop' killed by signal 9
Unrecoverable failure in required component nautilus-classic.desktop

and:
cannot open folder on desktop, freedesktop bus not ready

My configuration is:
Ubuntu 17.10
Gnome-Flashback
GNOME nautilus 3.26.0

ps:
nautilus-desktop --force
/usr/bin/nautilus --gapplication-service

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

Title:
  Click on desktop folders

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  On my Ubuntu 17.10, sometimes when I click (double click) on a folder
  on the gnome desktop, nautilus doesn't start showing the directory
  content.

  Nautilus version is 1:3.26.0-0ubuntu1

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

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

[Desktop-packages] [Bug 1713457] Re: DNS search domain not removed from resolv.conf on disconnect

[Paul Natsuo Kishimoto]

Is this reported upstream?

Could be one of:
https://bugzilla.gnome.org/show_bug.cgi?id=712818
https://bugzilla.gnome.org/show_bug.cgi?id=778004
https://bugzilla.gnome.org/show_bug.cgi?id=782469

I notice per the first one that "nmcli dev show" (not "… list", the
report is old and I guess the semantics of nmcli have changed) will show
me the search domain when I'm connected to a network that sets it:

=
$ nmcli -f IP4.ADDRESS,IP4.DOMAIN dev show
IP4.ADDRESS[1]: 18.142.15.92/16
IP4.DOMAIN[1]:  mit.edu

IP4.ADDRESS[1]: 18.189.91.11/19
IP4.DOMAIN[1]:  mit.edu


IP4.ADDRESS[1]: 127.0.0.1/8
=


So I guess if I try this the next time this bug crops up and nmcli disagrees 
with the contents of resolv.conf, I will mark the first URL as the upstream bug.

Or if someone who understands this better wants to open a new upstream
bug, please go ahead.

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

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

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

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

Title:
  DNS search domain not removed from resolv.conf on disconnect

Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  When I connect to a wireless network that sets a DNS search domain
  name via DHCP, the line 'search ' is added to /etc/resolv.conf
  as expected.  But if I then disconnect and connect to a different
  network, it is not removed from resolv.conf.  If the second network
  also sets a search domain name, that one gets appended to resolv.conf
  along with the first one, and so on.  Depending on the network, this
  can cause DNS leaks, name resolution failures, or other misbehavior.

  To be sure this wasn't some kind of user configuration issue, I
  reproduced this on the artful daily live image (artful-desktop-
  amd64.iso, 2017-08-27), from which I'm writing this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 28 10:34:22 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 172.20.20.1 dev wlp3s0 proto static metric 600
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
   172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170827)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlp3s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
xfinitywifi  39ffbbfc-1c1e-41c9-b3eb-c513065c3ea6  
/org/freedesktop/NetworkManager/ActiveConnection/2
   enp0s31f6  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--   ----
   lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1730728] Re: gnome-shell crashes randomly, error in libgobject-2.0.so.0.5400.1

[John Leach]

Looks a duplicate of #1730554

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

Title:
  gnome-shell crashes randomly, error in libgobject-2.0.so.0.5400.1

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  It happens daily, 2 or 3 times. But I don't know what triggers it, and
  I can't reproduce it. Last time it happened I wasn't even in front of
  the computer, and only firefox, thunderbird and skypeforlinux were
  opened (if I'm not mistaken). clamd was running as well. But each time
  it happened, the following has been logged in syslog:

  kernel: [22818.213847] traps: gnome-shell[3063] general protection
  ip:7f58ba1eacdf sp:7fff1dad5578 error:0 in
  libgobject-2.0.so.0.5400.1[7f58ba1b5000+52000]

  Opening a virtual console (like ctrl+shift+f3) was still possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 16:36:22 2017
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['pomod...@arun.codito.in']"
   b'org.gnome.shell' b'command-history' b"['firefox', 'thunderbird', 
'dropboxd', 'firefox', 'skypeforlinux', 'thunderbird', 'darktable', 'dropboxd']"
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'gnome-control-center.desktop', 'gnome-system-monitor.desktop', 
'org.gnome.Software.desktop', 'firefox.desktop', 'keepass2.desktop', 
'evince.desktop', 'org.gnome.Terminal.desktop', 'thunderbird.desktop', 
'skype.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-03-01 (616 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-26 (11 days ago)

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

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

[Desktop-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started

[Paul Smith]

Hi Sebastien, thanks for your interest.  This issue is causing me
extreme pain.  I believe I'm going to have to reconfigure N-M to use the
old-style dnsmasq setup and throw out systemd-resolve pretty soon.

It's not clear to me whether this is an N-M bug vs. a systemd bug, but
I'm happy to file more bugs.  Did you want me to file a bug with N-M?

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

Title:
  DNS domain search paths not updated when VPN started

Status in network-manager package in Ubuntu:
  New
Status in network-manager-openvpn package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I connect to work with openvpn through network-manager-openvpn.  I'm
  selecting automatic (DHCP) to get an IP address, and "Use this
  connection only for resources on its network" to support split
  tunneling.

  In the last few versions of Ubuntu I used, this all worked fine.  In
  Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both
  my VPN network and the internet, BUT I have to use FQDN for my VPN
  network hosts: the updates to the DNS search path provided by my VPN
  DHCP server are never being applied.

  Investigating the system I see that /etc/resolv.conf is pointing to
  /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not
  have any of the VPN's search path settings in it:

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual 
nameservers.
nameserver 127.0.0.53

search home

  In previous versions of Ubuntu, where NetworkManager controlled the
  resolver not systemd, /etc/resolv.conf pointed to
  /run/NetworkManager/resolv.conf and there was a local dnsmasq instance
  that managed all the complexity.  In Ubuntu 17.10 when I look in
  /run/NetworkManager/resolv.conf file, I see that the search paths ARE
  properly updated there:

$ cat /run/NetworkManager/resolv.conf 
# Generated by NetworkManager
search internal.mycorp.com other.mycorp.com home
nameserver 127.0.1.1

  However this file isn't being used, and also there's no dnsmasq
  running on the system so if I switch my /etc/resolv.conf to point to
  this file instead, then all lookups fail.

  Strangely, if I look at the systemd-resolv status I see that in theory
  systemd-resolve does seem to know about the proper search paths:

$ systemd-resolve --status
   ...
Link 3 (tun0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 10.3.0.10
  10.8.42.2
  DNS Domain: ~internal.mycorp.com
  ~other.mycorp.com

  but for whatever reason the search domains are not getting put into
  the resolv.conf file:

$ host mydesk
;; connection timed out; no servers could be reached

$ host mydesk.internal.mycorp.com
mydesk.internal.mycorp.com has address 10.8.37.74

  (BTW, the timeout in the failed attempt above takes 10s: it is SUPER
  frustrating when all your host lookups are taking that long just to
  fail).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 22 15:08:57 2017
  InstallationDate: Installed on 2017-10-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

[CaptSaltyJack]

I actually don't think uninstalling nvidia & reinstalling is good
enough. gdm3 has to be removed.

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS.

  * Add 'nomodeset' to your kernel command line.

  
  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

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

[Desktop-packages] [Bug 1724250] Re: gnome-terminal graphic artifact

[Kim Phillips]

exactly the same problem: it seems that the graphic file that is
supposed to represent the terminal icon is not referencing the file with
the right graphic for terminal?  Note: vanilla 4.13.12 kernel, with
NVIDIA Corporation GK107GL [Quadro K600] and the nvidia-387 driver.

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

Title:
  gnome-terminal graphic artifact

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Opening gnome-terminal in Ubuntu 17.10 shows the terminal window with
  a graphic artifact on the right of the title bar, where the window
  buttons to minimize, maximize and close are.

  The window buttons are working so this is just a visual glitch and
  does not otherwise affect gnome-terminal functionalities.

  It does not matter whether the gnome-terminal window is maximized or
  not, the graphic artifact is always present and does not disappear
  hovering on it with the mouse.

  Other applications do not appear to be affected, only gnome-terminal.

  I'm using NVIDIA Corporation GM204M [GeForce GTX 970M] with the NVIDIA
  binary driver 384.90.

  See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 15:37:42 2017
  InstallationDate: Installed on 2017-10-01 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1731929] Re: cairomm drops v5, whilst debian didn't

[Steve Langasek]

Removing packages from bionic-proposed:
cairomm 1.12.2-1ubuntu1 in bionic
libcairomm-1.0-1 1.12.2-1ubuntu1 in bionic amd64
libcairomm-1.0-1 1.12.2-1ubuntu1 in bionic arm64
libcairomm-1.0-1 1.12.2-1ubuntu1 in bionic armhf
libcairomm-1.0-1 1.12.2-1ubuntu1 in bionic i386
libcairomm-1.0-1 1.12.2-1ubuntu1 in bionic ppc64el
libcairomm-1.0-1 1.12.2-1ubuntu1 in bionic s390x
libcairomm-1.0-dev 1.12.2-1ubuntu1 in bionic amd64
libcairomm-1.0-dev 1.12.2-1ubuntu1 in bionic arm64
libcairomm-1.0-dev 1.12.2-1ubuntu1 in bionic armhf
libcairomm-1.0-dev 1.12.2-1ubuntu1 in bionic i386
libcairomm-1.0-dev 1.12.2-1ubuntu1 in bionic ppc64el
libcairomm-1.0-dev 1.12.2-1ubuntu1 in bionic s390x
libcairomm-1.0-doc 1.12.2-1ubuntu1 in bionic amd64
libcairomm-1.0-doc 1.12.2-1ubuntu1 in bionic arm64
libcairomm-1.0-doc 1.12.2-1ubuntu1 in bionic armhf
libcairomm-1.0-doc 1.12.2-1ubuntu1 in bionic i386
libcairomm-1.0-doc 1.12.2-1ubuntu1 in bionic ppc64el
libcairomm-1.0-doc 1.12.2-1ubuntu1 in bionic s390x
Comment: wrong Ubuntu-specific revert of package rename; LP: #1731929
1 package successfully removed.


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

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

Title:
  cairomm drops v5, whilst debian didn't

Status in cairomm package in Ubuntu:
  Fix Released

Bug description:
  cairomm drops v5, whilst debian didn't

  cairomm (1.12.2-1ubuntu1) bionic; urgency=medium

* Revert package rename for g++5 ABI transition, since the affected symbols
  were not part of the ABI; Provide: the renamed package for compatibility,
  and Conflicts/Replaces the old package. These changes can be dropped after
  the 18.04 release.

   -- Simon Quigley   Thu, 09 Nov 2017 20:51:35
  -0600

  
  clarification is needed, if we want to do this or not.

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

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

[Desktop-packages] [Bug 1731941] Re: duplicity should be installed by default as a dependency of deja-dup

[Michael Terry]

It isn’t installed by default for two reasons: not everyone uses a
backup, and we didn’t want python2 on the default install disk. So this
is intentional. Though if duplicity ever gets ported to python3, we may
reevaluate.

** Changed in: deja-dup (Ubuntu)
   Status: New => Won't Fix

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

Title:
  duplicity should be installed by default as a dependency of deja-dup

Status in deja-dup package in Ubuntu:
  Won't Fix

Bug description:
  Just tested my Deja-dup backup configuration on a fresh install of
  18.04.

  I was prompted to install duplicity.

  I am wondering whether duplicity should not better be installed as a
  dependency of deja-dup which is the default backup tool.

  What do you think?

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

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

[Desktop-packages] [Bug 1730196] Re: system slowness, delayed response, mouse stuttered movement

[Peter Ch]

** Package changed: firefox (Ubuntu) => ubuntu

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

Title:
  system slowness, delayed response, mouse stuttered movement

Status in Ubuntu:
  New

Bug description:
  After leaving Ubuntu 17.10 on and running on my Asus laptop for over 24 hours 
I found the whole system performing poorly.
  The only applications I have left running are FireFox, Terminal, and Polari. 
Skype might be running in the background.

  The system is slow and delayed in it's response, the mouse stutters as
  it moves across the desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: firefox 56.0+build6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mptz991 F pulseaudio
   /dev/snd/controlC0:  mptz991 F pulseaudio
  BuildID: 20171003222101
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  5 09:31:21 2017
  ExecutablePath: /usr/lib/firefox/firefox
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-10-29 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  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.106 metric 
600
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=56.0/20171003222101 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/16/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Q550LF.215
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Q550LF
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrQ550LF.215:bd06/16/2014:svnASUSTeKCOMPUTERINC.:pnQ550LF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ550LF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: Q
  dmi.product.name: Q550LF
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1731985] [NEW] Nautilus now makes random beeps on some navigation actions, and I can't turn it off

[teo1978]

Public bug reported:

Since a recent update, Nautilus has begun to make sounds as I navigate
folders.

(1) There is NO WAY AT ALL to turn these sounds off, without turning off
also other unrelated and useful sounds, see
https://bugs.launchpad.net/ubuntu/+source/systemsettings/+bug/1731982

Besides:

(2) Navigating through folders in a file explorer is something too common to 
have sounds on by default. It's annoying. They should be DISABLED BY DEFAULT, 
period. I understand there might be a handful of people in the world who may 
like them (not these ones in particular, of course), but the default should be 
Off.
(3) These sounds are CRAP. They don't sound like anything that you may find in 
other OSes for this kind of scenario, they are too loud and bold, and they are 
nothing that remotely conveys the action that is being performed. Something 
reasonable would be a "click" sound, which would also be less annoying
(4) The behavior is inconsistent and stupid: When you double click on a folder 
within the window to open it, it doesn't make any sound. But when you click on 
an item in the "breadcrumbs" on the top of the window, then it does make a 
sound. That makes no sense. Either you play sounds at all navigating actions, 
or none.


I reported this upstream, but this has been their answer:
https://gitlab.gnome.org/GNOME/nautilus/issues/118

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Nov 13 18:34:38 2017
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
 b'org.gnome.nautilus.window-state' b'geometry' b"'1277x824+493+148'"
 b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
InstallationDate: Installed on 2013-10-11 (1494 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Summary changed:

- Nautilus has suddenly started making random beeps, and I can't stop it
+ Nautilus now makes random beeps on some navigation actions, and I can't turn 
it off

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

Title:
  Nautilus now makes random beeps on some navigation actions, and I
  can't turn it off

Status in nautilus package in Ubuntu:
  New

Bug description:
  Since a recent update, Nautilus has begun to make sounds as I navigate
  folders.

  (1) There is NO WAY AT ALL to turn these sounds off, without turning
  off also other unrelated and useful sounds, see
  https://bugs.launchpad.net/ubuntu/+source/systemsettings/+bug/1731982

  Besides:

  (2) Navigating through folders in a file explorer is something too common to 
have sounds on by default. It's annoying. They should be DISABLED BY DEFAULT, 
period. I understand there might be a handful of people in the world who may 
like them (not these ones in particular, of course), but the default should be 
Off.
  (3) These sounds are CRAP. They don't sound like anything that you may find 
in other OSes for this kind of scenario, they are too loud and bold, and they 
are nothing that remotely conveys the action that is being performed. Something 
reasonable would be a "click" sound, which would also be less annoying
  (4) The behavior is inconsistent and stupid: When you double click on a 
folder within the window to open it, it doesn't make any sound. But when you 
click on an item in the "breadcrumbs" on the top of the window, then it does 
make a sound. That makes no sense. Either you play sounds at all navigating 
actions, or none.

  
  I reported this upstream, but this has been their answer:
  https://gitlab.gnome.org/GNOME/nautilus/issues/118

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov 13 18:34:38 2017
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1277x824+493+148'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 

[Desktop-packages] [Bug 1386257] Re: intel-microcode should be installed by default, when the CPU is GenuineIntel

[Alberto Salvia Novella]

** Changed in: amd64-microcode (Ubuntu)
   Status: New => Confirmed

** Changed in: amd64-microcode (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-drivers-common (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-meta (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntukylin-meta (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  intel-microcode should be installed by default, when the CPU is
  GenuineIntel

Status in intel:
  Fix Released
Status in Ubuntu Kylin:
  Fix Released
Status in amd64-microcode package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntukylin-meta package in Ubuntu:
  Fix Released

Bug description:
  intel-microcode should be installed by default on the bare-metal
  systems which are running on GenuineIntel CPUs, by the installers.

  Similarly other microcode packages for other CPUs brands should be
  considered for inclusion (e.g. amd64-microcode).

  I hope that ubuntu-drivers-common can gain ability to detect cpu
  series and/or vendors, packages that provide microcodes similarly
  declare support for cpu series and/or vendors, the microcode packages
  are shipped on the CDs in the pool directory, and installed on to the
  target machines as part of the installation.

  This should help with rapid correction of bugs and behaviour of the
  CPUs in the field.

  2017 update, amd64-microcode should also be seeded, as it is useful to
  have it autoinstallable. In the recent years there have been critical
  CPU security vulnerabilities which got fixed with microcode updates.

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

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

[Desktop-packages] [Bug 1716009] Re: problem with the sound since the latest update

[Seth Forshee]

I'm not sure why this was reported against alsa-drivers, you didn't
report any alsa packages in those that were upgraded when the problem
started. To get the bug noticed it's helpful to report the bug against
the appropriate package. If you believe the issue is related to a linux-
firmware update then please report the bug against that package.
Changing the bug to affect linux-firmware.

Do you know what version of linux-firmware you were using before the
update which broke your audio?

Please capture dmesg on your machine and attach it to this bug; let me
know if you need instructions for how to do this. Thanks!

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

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

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

Title:
  problem with the sound since the latest update

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  i am with an old intel chipset motherboard having an integrated
  realtek alc888 sound, and Ubuntu 16.04 Desktop (64-bit); since the
  latest update there has had no effect when adjusting sound volume from
  the sound menu on the menu bar and sound settings, and no sound in
  counter strike 1.6 linux version, also, there has appeared an effect
  of a sound interruption/break (for less than a second) when switching
  between applications, however, i can still adjust the sound volume
  from gnome alsa mixer

  the latest update includes:

  snapd-login-service:amd64
  libsnapd-glib1:amd64
  linux-firmware:amd64
  libgd3:amd64

  the previous ——:

  libpackagekit-glib2-16:amd64
  gir1.2-packagekitglib-1.0:amd64

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

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

[Desktop-packages] [Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling

[Treviño]

** Tags removed: gnome-17.10
** Tags added: gnome-18.04

** Description changed:

- https://trello.com/c/TvwNvXOo
+ https://trello.com/c/r12LY9iA (for 17.04 was
+ https://trello.com/c/TvwNvXOo)
  
  ---
  
  I'm using fully updated Ubuntu GNOME 17.04.
  
  In Ubuntu Gnome, you only allow for integer scaling of things for high
  DPI monitors. While in theory this sounds good, on a 27 inch 4k monitor
  like mine, restricting it to integers is a problem. 1x is annoyingly
  small, and 2x is WAY too big. You need a 1.5x, and presumably to just
  allow most noninteger values to future proof the distribution given 8k
  monitors and all sorts of new and weird things coming out, like windows
  10 has.
  
  Photos of the two annoying sizes are available here (it won't let me
  attach two files):
  
  http://i.imgur.com/vWrvZxq.jpg
  http://i.imgur.com/11p19k7.jpg
  
  I apologize for my photography skills in advance., you'll have to look
  at the ruler for scale to see the problem. Please contact me if you need
  any more information etc.

** Tags added: highdpi

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

Title:
  GNOME Shell should support fractional (non-integer) Hi-DPI scaling

Status in Mutter:
  In Progress
Status in Ubuntu GNOME:
  Triaged
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  https://trello.com/c/r12LY9iA (for 17.04 was
  https://trello.com/c/TvwNvXOo)

  ---

  I'm using fully updated Ubuntu GNOME 17.04.

  In Ubuntu Gnome, you only allow for integer scaling of things for high
  DPI monitors. While in theory this sounds good, on a 27 inch 4k
  monitor like mine, restricting it to integers is a problem. 1x is
  annoyingly small, and 2x is WAY too big. You need a 1.5x, and
  presumably to just allow most noninteger values to future proof the
  distribution given 8k monitors and all sorts of new and weird things
  coming out, like windows 10 has.

  Photos of the two annoying sizes are available here (it won't let me
  attach two files):

  http://i.imgur.com/vWrvZxq.jpg
  http://i.imgur.com/11p19k7.jpg

  I apologize for my photography skills in advance., you'll have to look
  at the ruler for scale to see the problem. Please contact me if you
  need any more information etc.

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

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

[Desktop-packages] [Bug 1713457] Re: DNS search domain not removed from resolv.conf on disconnect

[Laurent Bigonville]

I cannot reproduce this on debian.

It seems that one of the difference is that resolvconf support is
disabled in the ubuntu package. I feel that the problem comes from here.
resovconf support should probably (not tested) be enabled in case it's
pulled on the system by a dependency

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

Title:
  DNS search domain not removed from resolv.conf on disconnect

Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  When I connect to a wireless network that sets a DNS search domain
  name via DHCP, the line 'search ' is added to /etc/resolv.conf
  as expected.  But if I then disconnect and connect to a different
  network, it is not removed from resolv.conf.  If the second network
  also sets a search domain name, that one gets appended to resolv.conf
  along with the first one, and so on.  Depending on the network, this
  can cause DNS leaks, name resolution failures, or other misbehavior.

  To be sure this wasn't some kind of user configuration issue, I
  reproduced this on the artful daily live image (artful-desktop-
  amd64.iso, 2017-08-27), from which I'm writing this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 28 10:34:22 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 172.20.20.1 dev wlp3s0 proto static metric 600
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
   172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170827)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlp3s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
xfinitywifi  39ffbbfc-1c1e-41c9-b3eb-c513065c3ea6  
/org/freedesktop/NetworkManager/ActiveConnection/2
   enp0s31f6  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--   ----
   lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1725238] Re: Clicking snap:// urls doesn't work

[Launchpad Bug Tracker]

** Branch linked: lp:~mozillateam/firefox/firefox.artful

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

Title:
  Clicking snap:// urls doesn't work

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

Bug description:
  I am unable to trigger GNOME Software to install snaps.

  Steps to reproduce:

  1. Visit http://snapcraft.io/zzt
  2. Click green Install button
  3. Browser is taken to snap://zzt 

  Outcome:-

  "The address wasn't understood" error page in Firefox

  Expected outcome:-

  GNOME Software launches directly on the ZZT snap app page.

  Here's a video showing it:-
  https://www.youtube.com/watch?v=rOaGt8W2zrY

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: firefox 56.0+build6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   2350 F pulseaudio
   /dev/snd/controlC1:  alan   2350 F pulseaudio
  BuildID: 20171003222101
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 12:06:27 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-08-02 (78 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=56.0/20171003222101 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET66WW (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BV001BUK
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1730728] Re: gnome-shell crashes randomly, error in libgobject-2.0.so.0.5400.1

[John Leach]

I have this same crashing problem, several times a day. Started about a
week ago.

I also have the same problem trying to report it. I have /var/crash
/_usr_bin_gnome-shell.1000.crash which is 65M. When I try report it
using either appport-bug or apport-cli, those commands just exit
silently (apport-bug prompts me if I want to report a bug report first
and then does so). They create a 0 byte _usr_bin_gnome-shell.1000.upload
file.

So I'm having trouble reporting it too.

For the record I've tried disabling all extensions, but that hasn't
helped.

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

Title:
  gnome-shell crashes randomly, error in libgobject-2.0.so.0.5400.1

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  It happens daily, 2 or 3 times. But I don't know what triggers it, and
  I can't reproduce it. Last time it happened I wasn't even in front of
  the computer, and only firefox, thunderbird and skypeforlinux were
  opened (if I'm not mistaken). clamd was running as well. But each time
  it happened, the following has been logged in syslog:

  kernel: [22818.213847] traps: gnome-shell[3063] general protection
  ip:7f58ba1eacdf sp:7fff1dad5578 error:0 in
  libgobject-2.0.so.0.5400.1[7f58ba1b5000+52000]

  Opening a virtual console (like ctrl+shift+f3) was still possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 16:36:22 2017
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['pomod...@arun.codito.in']"
   b'org.gnome.shell' b'command-history' b"['firefox', 'thunderbird', 
'dropboxd', 'firefox', 'skypeforlinux', 'thunderbird', 'darktable', 'dropboxd']"
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'gnome-control-center.desktop', 'gnome-system-monitor.desktop', 
'org.gnome.Software.desktop', 'firefox.desktop', 'keepass2.desktop', 
'evince.desktop', 'org.gnome.Terminal.desktop', 'thunderbird.desktop', 
'skype.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-03-01 (616 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-26 (11 days ago)

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

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

[Desktop-packages] [Bug 1727390] Re: New bugfix release 17.2.4

[Luca Tansini]

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

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

Title:
  New bugfix release 17.2.4

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

Bug description:
  [Impact]

  A new upstream bugfix release is available. Release note diff compared
  to 17.2.2:

  "Mesa 17.2.3 is now available.

  In this release we have:

  The Vulkan drivers ANV and RADV have multiple small fixes.

  The EGL code has improved handling of the new wl_dmabuf codepath.

  SWR no longer crashes when checking environment variables.

  Other gallium drivers have also seen updates - freedreno, nouveau and
  radeonsi. The gallivm module, used by llvmpipe et al. has gained little
  endian PPC64 fixes.

  The VA and VDPAU state-trackers have seems improvements handling
  interlaced videos.

  We're using python3 compatible constructs which gives us SCons 3.0
  support."

  "Mesa 17.2.4 is now available.

  In this release we have:

  In Mesa Core we have included a change to prevent KOTOR from breaking
  when in combination with the ATI fragment shader extension. 
  Additionally, NIR has also received a correction.

  Mesa's state tracker has gotten a patch to avoid leaks in certain
  situations like when resizing a window.

  Intel drivers have received several fixes.  The compiler has gotten a
  couple, while anv also received one.  i965 got a patch to avoid VA-
  API, Beignet and other contexts in the system to break when in
  combination with previous versions of Mesa 17.2.x.

  AMD's compiler has received a couple of fixes while radv has also
  received another couple, including one to avoid a hang due to an
  overflow on huge textures.

  Broadcom's vc4 has corrected a problem when compiling with Android's
  clang.

  clover has also seen fixed a problem compiling after a specific clang
  revision.

  Vulkan's WSI has gotten plugged a memory leak for X11."

  
  [Test case]

  Test typical use cases on the most common hw/driver combinations:
  intel/i965
  nvidia/nouveau
  radeon/radeonsi

  [Regression potential]

  These releases are tested against compliance, bugfix releases in
  particular have minimal risk of regressing anything major at least.

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

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

[Desktop-packages] [Bug 358825] Re: rhythmbox stops playing after some time

[Danil]

Same for me on Ubuntu 17.10

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

Title:
  rhythmbox stops playing after some time

Status in Rhythmbox:
  New
Status in rhythmbox package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: rhythmbox

  When I play an album with rhythmbox, it stops playing after 1 or 2 tracks 
without reason and if I try to select another track after that it doesn't 
respond anymore. I have to terminate the application and restart it.
  For information, all my music is in wavpack and crossfading is enabled.
  Also I'm using rhythmbox 0.12.0-0ubuntu4 on Jaunty.

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  Package: rhythmbox 0.12.0-0ubuntu4
  ProcEnviron:
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: rhythmbox
  Uname: Linux 2.6.28-11-generic i686

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

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

[Desktop-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started

[Sebastien Bacher]

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

** Changed in: network-manager-openvpn (Ubuntu)
   Importance: Undecided => High

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

Title:
  DNS domain search paths not updated when VPN started

Status in network-manager package in Ubuntu:
  New
Status in network-manager-openvpn package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I connect to work with openvpn through network-manager-openvpn.  I'm
  selecting automatic (DHCP) to get an IP address, and "Use this
  connection only for resources on its network" to support split
  tunneling.

  In the last few versions of Ubuntu I used, this all worked fine.  In
  Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both
  my VPN network and the internet, BUT I have to use FQDN for my VPN
  network hosts: the updates to the DNS search path provided by my VPN
  DHCP server are never being applied.

  Investigating the system I see that /etc/resolv.conf is pointing to
  /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not
  have any of the VPN's search path settings in it:

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual 
nameservers.
nameserver 127.0.0.53

search home

  In previous versions of Ubuntu, where NetworkManager controlled the
  resolver not systemd, /etc/resolv.conf pointed to
  /run/NetworkManager/resolv.conf and there was a local dnsmasq instance
  that managed all the complexity.  In Ubuntu 17.10 when I look in
  /run/NetworkManager/resolv.conf file, I see that the search paths ARE
  properly updated there:

$ cat /run/NetworkManager/resolv.conf 
# Generated by NetworkManager
search internal.mycorp.com other.mycorp.com home
nameserver 127.0.1.1

  However this file isn't being used, and also there's no dnsmasq
  running on the system so if I switch my /etc/resolv.conf to point to
  this file instead, then all lookups fail.

  Strangely, if I look at the systemd-resolv status I see that in theory
  systemd-resolve does seem to know about the proper search paths:

$ systemd-resolve --status
   ...
Link 3 (tun0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 10.3.0.10
  10.8.42.2
  DNS Domain: ~internal.mycorp.com
  ~other.mycorp.com

  but for whatever reason the search domains are not getting put into
  the resolv.conf file:

$ host mydesk
;; connection timed out; no servers could be reached

$ host mydesk.internal.mycorp.com
mydesk.internal.mycorp.com has address 10.8.37.74

  (BTW, the timeout in the failed attempt above takes 10s: it is SUPER
  frustrating when all your host lookups are taking that long just to
  fail).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 22 15:08:57 2017
  InstallationDate: Installed on 2017-10-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System 

[Desktop-packages] [Bug 1730748] Re: gnome-shell froze and crashed

[Domagoj Tršan]

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

It happened today again. When I ran "ubuntu-bug /var/crash
/_usr_bin_gnome-shell.1000.crash" I had more details. By the stacktrace
it looks exactly as #1714989. I think we can mark this one as duplicate
and close it.

** This bug has been marked a duplicate of bug 1714989
   gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from 
st_label_set_text() from ffi_call_unix64() [Global App Menu specific?]

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

Title:
  gnome-shell froze and crashed

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Cannot say much except that I had opened gnome-terminal and suddenly
  the session just froze and crashed. I lost Wayland session and had to
  login again.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  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: ubuntu:GNOME
  Date: Tue Nov  7 20:15:07 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-21 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1724250] Re: gnome-terminal graphic artifact

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-terminal graphic artifact

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Opening gnome-terminal in Ubuntu 17.10 shows the terminal window with
  a graphic artifact on the right of the title bar, where the window
  buttons to minimize, maximize and close are.

  The window buttons are working so this is just a visual glitch and
  does not otherwise affect gnome-terminal functionalities.

  It does not matter whether the gnome-terminal window is maximized or
  not, the graphic artifact is always present and does not disappear
  hovering on it with the mouse.

  Other applications do not appear to be affected, only gnome-terminal.

  I'm using NVIDIA Corporation GM204M [GeForce GTX 970M] with the NVIDIA
  binary driver 384.90.

  See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 15:37:42 2017
  InstallationDate: Installed on 2017-10-01 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1686623] Re: Gnome terminal window shrink on exit focus with wayland

[Albert Tomanek]

This happend to me too.
I'm running Ubuntu Budgie 16.04 using the Elementary GTK theme.
Switching to a different theme seemed to stop this unwanted behavior, so in my 
case it must be a bug in the Elementary theme.

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

Title:
  Gnome terminal window shrink on exit focus with wayland

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Gnome terminal window shrink each time the window is unfocused. It
  only happen with Wayland.

  Workaround:
  Maximize the terminal window.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-terminal 3.20.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr 27 14:10:17 2017
  EcryptfsInUse: Yes
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to zesty on 2017-03-28 (29 days ago)

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

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

[Desktop-packages] [Bug 1630218] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

[Alexander-Shariff-Vetter]

my real distro release is Ubuntu 18.04 LTS Bionic Beaver Alpha 1

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

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  The system is reporting this issue when I get logged into GNOME X11
  session and I can't speak for if it is same using the Wayland session.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: gnome-shell 3.20.3-1ubuntu2
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat Oct  1 18:55:43 2016
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2015-10-26 (344 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 
(20151017.1)
  LocalLibraries: /usr/local/lib/libfreetype.so.6.12.2
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter.so.0
   ?? ()
   ?? ()
   g_log_writer_journald () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: Upgraded to yakkety on 2016-10-01 (2 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1732038] [NEW] evince spams stderr with messages about "Allocating size to EvWindow"

[Paul]

Public bug reported:

Open a PDF and search it, for instance for the letter 'e'. evince prints
numerous error messages to stderr of the form:

(evince:30830): Gtk-WARNING **: Allocating size to EvWindow
0x559a7c972f10 without calling gtk_widget_get_preferred_width/height().
How does the code know the size to allocate?

The more common the search term, the more errors.

There is also always one similar error about EvSidebar every time evince
starts.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: evince 3.26.0-1
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: Tue Nov 14 09:54:55 2017
InstallationDate: Installed on 2016-12-02 (345 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
KernLog:
 
SourcePackage: evince
UpgradeStatus: Upgraded to artful on 2017-10-12 (32 days ago)

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


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

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

Title:
  evince spams stderr with messages about "Allocating size to EvWindow"

Status in evince package in Ubuntu:
  New

Bug description:
  Open a PDF and search it, for instance for the letter 'e'. evince
  prints numerous error messages to stderr of the form:

  (evince:30830): Gtk-WARNING **: Allocating size to EvWindow
  0x559a7c972f10 without calling
  gtk_widget_get_preferred_width/height(). How does the code know the
  size to allocate?

  The more common the search term, the more errors.

  There is also always one similar error about EvSidebar every time
  evince starts.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.26.0-1
  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: Tue Nov 14 09:54:55 2017
  InstallationDate: Installed on 2016-12-02 (345 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  KernLog:
   
  SourcePackage: evince
  UpgradeStatus: Upgraded to artful on 2017-10-12 (32 days ago)

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

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

[Desktop-packages] [Bug 1392012] Re: [MIR] libteam

[Tony Espy]

Re-opened, as there's some interest from OEMs in seeing NM teaming
support land in 18.04.

** Description changed:

  Availability:
  The package is available in universe, built on all architectures.
  
  Rationale:
- The package is a new (Build-)Depends for network-manager, for network device 
bonding support.
+ The package is a new (Build-)Depends for network-manager, for network device 
teaming (aka user-space bonding) support.
  
  Security:
  Could not find any related security advisories.
  
  Quality assurance:
  The package is well-maintained in Debian and expected to not require 
extensive effort to maintain in Ubuntu.
  
  UI standards:
  Not applicable.
  
  Dependencies:
- All build and binary dependencies are in main; with one exception:
-  - Build-Depends: libjeansson-dev (bug 1392023)
+ All build and binary dependencies are in main.
  
  Standards compliance:
  The package meets requirements.
  
  Maintenance:
  The package meets requirements.
  
  Background information:
  libteam is a library for communicating with the netlink kernel layer in order 
to create bonded interfaces.

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

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

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

Title:
  [MIR] libteam

Status in libteam package in Ubuntu:
  New

Bug description:
  Availability:
  The package is available in universe, built on all architectures.

  Rationale:
  The package is a new (Build-)Depends for network-manager, for network device 
teaming (aka user-space bonding) support.

  Security:
  Could not find any related security advisories.

  Quality assurance:
  The package is well-maintained in Debian and expected to not require 
extensive effort to maintain in Ubuntu.

  UI standards:
  Not applicable.

  Dependencies:
  All build and binary dependencies are in main.

  Standards compliance:
  The package meets requirements.

  Maintenance:
  The package meets requirements.

  Background information:
  libteam is a library for communicating with the netlink kernel layer in order 
to create bonded interfaces.

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

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

[Desktop-packages] [Bug 1732012] [NEW] After turning display (LCD TV) off and then back on, session ends and Ubuntu goes back to the logon screen

[Jonathan Avraham]

Public bug reported:

TV is an old Toshiba LCD connected via HDMI. Problem first appeared
after upgrade to Artful.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xwayland 2:1.19.5-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3.2
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,decor,compiztoolbox,imgpng,obs,gnomecompat,vpswitch,regex,resize,move,place,mousepoll,animation,grid,workarounds,session,wobbly,fade,cube,rotate,expo,scale,unitymtgrabhandles,ezoom,unityshell]
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 13 21:56:50 2017
DistUpgraded: 2017-10-21 11:42:55,395 DEBUG icon theme changed, re-reading
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.1.30, 4.10.0-38-generic, x86_64: installed
 virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed
 virtualbox, 5.1.30, 4.13.0-17-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6530D] 
[1002:964a] (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd BeaverCreek [Radeon HD 6530D] 
[1458:d000]
InstallationDate: Installed on 2012-05-29 (1994 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
MachineType: Gigabyte Technology Co., Ltd. GA-A75M-D2H
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=ce7c3cb8-c699-4b71-8e50-d1a46484f917 ro quiet splash
SourcePackage: xorg-server
UpgradeStatus: Upgraded to artful on 2017-10-21 (23 days ago)
dmi.bios.date: 11/03/2011
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F5
dmi.board.name: GA-A75M-D2H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd11/03/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75M-D2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75M-D2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-A75M-D2H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Wed Oct 18 21:11:02 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.3
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug artful ubuntu wayland-session

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

Title:
  After turning display (LCD TV) off and then back on, session ends and
  Ubuntu goes back to the logon screen

Status in xorg-server package in Ubuntu:
  New

Bug description:
  TV is an old Toshiba LCD connected via HDMI. Problem first appeared
  after upgrade to Artful.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xwayland 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,compiztoolbox,imgpng,obs,gnomecompat,vpswitch,regex,resize,move,place,mousepoll,animation,grid,workarounds,session,wobbly,fade,cube,rotate,expo,scale,unitymtgrabhandles,ezoom,unityshell]
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 13 21:56:50 2017
  DistUpgraded: 2017-10-21 11:42:55,395 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.30, 4.10.0-38-generic, x86_64: installed
   virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed
   virtualbox, 5.1.30, 4.13.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6530D] 
[1002:964a] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd BeaverCreek [Radeon HD 6530D] 
[1458:d000]
  InstallationDate: Installed on 2012-05-29 (1994 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Gigabyte Technology Co., Ltd. GA-A75M-D2H
  ProcKernelCmdLine: 

[Desktop-packages] [Bug 1731933] Re: System totally locked up. Hard shutdown only available.

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  System totally locked up. Hard shutdown only available.

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Strangely, I was running Firefox, PCFileFM and a terminal window in a
  LXDE desktop environment. I woke up and the computer was locked up
  completely (about 8 hours running unattented). Upon reboot, Ubuntu
  generated the error report.

  Subsequently, I have completely uninstalled chromium-browser-l10n due
  to issues of a corruption error reported by Synaptic.

  Please contact me if you have any other questions.

  Regards,
  Stephen Dittoe 
  13219 Taylorcrest Road
  Houston, TX 77079

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser-l10n 62.0.3202.75-0ubuntu0.16.04.1313
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   chromium-browser-l10n: Remove
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Nov  9 08:40:09 2017
  DpkgTerminalLog:
   dpkg: error processing package chromium-browser-l10n (--remove):
package is in a very bad inconsistent state; you should
reinstall it before attempting a removal
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  InstallationDate: Installed on 2014-05-11 (1280 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: chromium-browser
  Title: package chromium-browser-l10n 62.0.3202.75-0ubuntu0.16.04.1313 failed 
to install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1581160] Re: Switch to Noto Sans as default font for Japanese and/or Korean?

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-budgie-meta - 0.21

---
ubuntu-budgie-meta (0.21) bionic; urgency=medium

  * Refreshed dependencies
  * Removed fonts-nanum from desktop-recommends (LP: #1581160)
  * Removed fonts-takao-pgothic from desktop-recommends
  * Packaging Changes:
- debian/control: Bump Standards-Version; no additional changes required

 -- David Mohammed   Mon, 13 Nov 2017 19:22:28
+

** Changed in: ubuntu-budgie-meta (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Switch to Noto Sans as default font for Japanese and/or Korean?

Status in language-selector package in Ubuntu:
  In Progress
Status in lubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntukylin-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu 16.04 Noto Sans CJK is the default font for rendering
  Chinese. After having struggled with a few issues, I believe that we
  finally achieved the desired improvement of the rendering experience.

  So now I ask: Is there an interest from Japanese and Korean users to
  consider a switch to Noto Sans? (The fonts are already installed for
  all users on Ubuntu 16.04.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1581160/+subscriptions

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

[Desktop-packages] [Bug 1726616] Re: Firefox crashes repeatedly after system update

[MATE Desktop]

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

** Changed in: ubuntu-mate
   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/1726616

Title:
  Firefox crashes repeatedly after system update

Status in ubuntu-mate:
  Invalid
Status in firefox package in Ubuntu:
  New

Bug description:
  How to reproduce:
  - Download and install Ubuntu Mate 16.04.2 LTS, Raspberry Edition, on a micro 
SD card.
  - Boot the Pi with that card, and launch Firefox. Everything's OK so far. By 
the way, it's FF 54.0.
  - Update everything either with Software Updater or with apt-get update + 
apt-get upgrade.
  - (Attempt to) launch Firefox again. It won't start at all, and all you'll 
get will be a window repeatedly saying that Firefox has crashed, and proposing 
to send a bug report.

  I've initially noticed this issue on the latest (LTS) version of the
  Raspberry Edition of Ubuntu Mate (16.04.2), and afterwards reproduced
  it on the 32-bit version of the Desktop Edition (16.04.3), so it's not
  a Raspberry-specific issue. But, oddly enough, not on the 64-bit
  version, where Firefox was updated from 54.0 to 56.0 and kept running
  fine. I did not try more recent versions of the Desktop Edition (17.04
  or 17.10) because the latest available for the Pi is the 16.04.2.

  I wish I could help more, by pinpointing precisely what has gone
  wrong, but this is the first time I report a bug in Ubuntu, and I
  don't know where to start the debugging.

  Thanks for reading,

  Marc

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

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

[Desktop-packages] [Bug 1732031] Re: Xorg crashed with SIGABRT

[Apport retracing service]

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

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 #1725324, 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/1732031/+attachment/5008493/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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 nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/1732031

Title:
  Xorg crashed with SIGABRT

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

Bug description:
  Crash following hang and attempt to suspend.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: xserver-xorg-core 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.104  Thu Sep 14 17:13:13 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Nov 13 20:08:25 2017
  DistUpgraded: 2017-10-24 12:57:12,413 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 330M] [10de:0a29] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Samsung Electronics Co Ltd GT216M [GeForce GT 330M] [144d:c08e]
  InstallationDate: Installed on 2015-04-06 (952 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Beta amd64 (20150402)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF510/RF410/RF710
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=5eb5ba6c-2032-4b8f-bc4c-401b1320b167 ro quiet splash zswap.enabled=1 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M
  Signal: 6
  SourcePackage: nvidia-graphics-drivers
  StacktraceTop:
   ()
   ()
   ()
   ()
   ()
  Title: Xorg crashed with SIGABRT
  UpgradeStatus: Upgraded to artful on 2017-10-24 (20 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  dmi.bios.date: 10/27/2010
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 02GB.M025.20101027.hkk
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: RF510/RF410/RF710
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr02GB.M025.20101027.hkk:bd10/27/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnRF510/RF410/RF710:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnRF510/RF410/RF710:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: RF510/RF410/RF710
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1