[Desktop-packages] [Bug 1761385] Re: gnome-software crashed with signal 5

2018-04-04 Thread Apport retracing service 
*** This bug is a duplicate of bug 1756339 ***
https://bugs.launchpad.net/bugs/1756339

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 #1756339, 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/1761385/+attachment/5102281/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1756339
   gnome-software crashed with signal 5 in g_main_context_new → start_sync → 
snapd_client_list_one_sync → gs_plugin_refine_app → gs_plugin_loader_call_vfunc

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-software crashed with signal 5

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Unknown cause

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Thu Apr  5 02:19:50 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-04-03 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.28.0-0ubuntu7
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu7
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-software
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_new () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   snapd_client_list_one_sync () at /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   gs_plugin_refine_app () at 
/usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_snap.so
  Title: gnome-software crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1761360] Re: chromium-browser crashed with SIGABRT

2018-04-04 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  chromium-browser crashed with SIGABRT

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  The browser crashed upon start when I first booted my computer.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 65.0.3325.181-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAw5CUFAAAaAQSVIhN4CkLlkVhVjygeUFQBAQEBAQEBAQEBAQEBAQEB0B1W9FAAFjAwIDUAWMIQAAAa2RdW9FAAFjAwIDUAWMIQAAAa/gBIOTdIMYAxNTZXSFUKQTGUABkBCiAgAI0=
   modes: 1366x768 1366x768
  Date: Tue Apr  3 23:18:02 2018
  Desktop-Session:
   'xubuntu'
   '/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg'
   
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2017-10-24 (162 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Load-Avg-1min: 3.49
  Load-Processes-Running-Percent:   0.2%
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --enable-pinch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: chromium-browser
  StacktraceTop:
   ()
   ()
   ()
   dbus_connection_dispatch () at /lib/x86_64-linux-gnu/libdbus-1.so.3
   ()
  Title: chromium-browser crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-02-19 (44 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 01/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 01W6F7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd01/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5567
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1761382] Re: Unable to connect to ibus: Could not connect: Connection refused

2018-04-04 Thread dino99 
@Daniel

ibus:  It provides full featured and user friendly input method user
interface.

i cant tell it breaks something, but probably does not provide internal outputs 
needed by the system. Otherwise tell me why ubuntu has decided to add ibus 
packages to the required package list ?
Actually used by: 'indicator-keyboard' 'gnome-control-center' at least.
So how to know those really work as they might ?

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

Title:
  Unable to connect to ibus: Could not connect: Connection refused

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Get this logged:

  oem@ubuntu:~$ journalctl -b | grep ibus

  dbus-daemon[1074]: [session uid=120 pid=1074] Activating service
  name='org.freedesktop.portal.IBus' requested by ':1.18' (uid=120
  pid=1135 comm="ibus-daemon --xim --panel disable " label="unconfined")

  gnome-shell[1084]: Unable to connect to ibus: Could not connect:
  Connection refused

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting QT_IM_MODULE=ibus

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting XMODIFIERS=@im=ibus

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting GTK_IM_MODULE=ibus

  dbus-daemon[1293]: [session uid=1000 pid=1293] Activating service
  name='org.freedesktop.portal.IBus' requested by ':1.27' (uid=1000
  pid=1458 comm="ibus-daemon --xim --panel disable " label="unconfined")

  gnome-shell[1435]: Unable to connect to ibus: Could not connect:
  Connection refused

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr  5 07:43:59 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1761382] Re: Unable to connect to ibus: Could not connect: Connection refused

2018-04-04 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Unable to connect to ibus: Could not connect: Connection refused

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Get this logged:

  oem@ubuntu:~$ journalctl -b | grep ibus

  dbus-daemon[1074]: [session uid=120 pid=1074] Activating service
  name='org.freedesktop.portal.IBus' requested by ':1.18' (uid=120
  pid=1135 comm="ibus-daemon --xim --panel disable " label="unconfined")

  gnome-shell[1084]: Unable to connect to ibus: Could not connect:
  Connection refused

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting QT_IM_MODULE=ibus

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting XMODIFIERS=@im=ibus

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting GTK_IM_MODULE=ibus

  dbus-daemon[1293]: [session uid=1000 pid=1293] Activating service
  name='org.freedesktop.portal.IBus' requested by ':1.27' (uid=1000
  pid=1458 comm="ibus-daemon --xim --panel disable " label="unconfined")

  gnome-shell[1435]: Unable to connect to ibus: Could not connect:
  Connection refused

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr  5 07:43:59 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1761382] Re: Unable to connect to ibus: Could not connect: Connection refused

2018-04-04 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Unable to connect to ibus: Could not connect: Connection refused

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Get this logged:

  oem@ubuntu:~$ journalctl -b | grep ibus

  dbus-daemon[1074]: [session uid=120 pid=1074] Activating service
  name='org.freedesktop.portal.IBus' requested by ':1.18' (uid=120
  pid=1135 comm="ibus-daemon --xim --panel disable " label="unconfined")

  gnome-shell[1084]: Unable to connect to ibus: Could not connect:
  Connection refused

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting QT_IM_MODULE=ibus

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting XMODIFIERS=@im=ibus

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting GTK_IM_MODULE=ibus

  dbus-daemon[1293]: [session uid=1000 pid=1293] Activating service
  name='org.freedesktop.portal.IBus' requested by ':1.27' (uid=1000
  pid=1458 comm="ibus-daemon --xim --panel disable " label="unconfined")

  gnome-shell[1435]: Unable to connect to ibus: Could not connect:
  Connection refused

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr  5 07:43:59 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1761382] Re: Unable to connect to ibus: Could not connect: Connection refused

2018-04-04 Thread Daniel van Vugt 
Confirmed. But is it breaking anything?

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

Title:
  Unable to connect to ibus: Could not connect: Connection refused

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Get this logged:

  oem@ubuntu:~$ journalctl -b | grep ibus

  dbus-daemon[1074]: [session uid=120 pid=1074] Activating service
  name='org.freedesktop.portal.IBus' requested by ':1.18' (uid=120
  pid=1135 comm="ibus-daemon --xim --panel disable " label="unconfined")

  gnome-shell[1084]: Unable to connect to ibus: Could not connect:
  Connection refused

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting QT_IM_MODULE=ibus

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting XMODIFIERS=@im=ibus

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting GTK_IM_MODULE=ibus

  dbus-daemon[1293]: [session uid=1000 pid=1293] Activating service
  name='org.freedesktop.portal.IBus' requested by ':1.27' (uid=1000
  pid=1458 comm="ibus-daemon --xim --panel disable " label="unconfined")

  gnome-shell[1435]: Unable to connect to ibus: Could not connect:
  Connection refused

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr  5 07:43:59 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1761382] Re: Unable to connect to ibus: Could not connect: Connection refused

2018-04-04 Thread Daniel van Vugt 
** Also affects: ibus (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Unable to connect to ibus: Could not connect: Connection refused

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Get this logged:

  oem@ubuntu:~$ journalctl -b | grep ibus

  dbus-daemon[1074]: [session uid=120 pid=1074] Activating service
  name='org.freedesktop.portal.IBus' requested by ':1.18' (uid=120
  pid=1135 comm="ibus-daemon --xim --panel disable " label="unconfined")

  gnome-shell[1084]: Unable to connect to ibus: Could not connect:
  Connection refused

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting QT_IM_MODULE=ibus

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting XMODIFIERS=@im=ibus

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting GTK_IM_MODULE=ibus

  dbus-daemon[1293]: [session uid=1000 pid=1293] Activating service
  name='org.freedesktop.portal.IBus' requested by ':1.27' (uid=1000
  pid=1458 comm="ibus-daemon --xim --panel disable " label="unconfined")

  gnome-shell[1435]: Unable to connect to ibus: Could not connect:
  Connection refused

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr  5 07:43:59 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1761382] [NEW] Unable to connect to ibus: Could not connect: Connection refused

2018-04-04 Thread dino99 
Public bug reported:

Get this logged:

oem@ubuntu:~$ journalctl -b | grep ibus

dbus-daemon[1074]: [session uid=120 pid=1074] Activating service
name='org.freedesktop.portal.IBus' requested by ':1.18' (uid=120
pid=1135 comm="ibus-daemon --xim --panel disable " label="unconfined")

gnome-shell[1084]: Unable to connect to ibus: Could not connect:
Connection refused

/usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
setting QT_IM_MODULE=ibus

/usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
setting XMODIFIERS=@im=ibus

/usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
setting GTK_IM_MODULE=ibus

dbus-daemon[1293]: [session uid=1000 pid=1293] Activating service
name='org.freedesktop.portal.IBus' requested by ':1.27' (uid=1000
pid=1458 comm="ibus-daemon --xim --panel disable " label="unconfined")

gnome-shell[1435]: Unable to connect to ibus: Could not connect:
Connection refused

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.0-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Apr  5 07:43:59 2018
DisplayManager: gdm3
EcryptfsInUse: Yes
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Unable to connect to ibus: Could not connect: Connection refused

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Get this logged:

  oem@ubuntu:~$ journalctl -b | grep ibus

  dbus-daemon[1074]: [session uid=120 pid=1074] Activating service
  name='org.freedesktop.portal.IBus' requested by ':1.18' (uid=120
  pid=1135 comm="ibus-daemon --xim --panel disable " label="unconfined")

  gnome-shell[1084]: Unable to connect to ibus: Could not connect:
  Connection refused

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting QT_IM_MODULE=ibus

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting XMODIFIERS=@im=ibus

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting GTK_IM_MODULE=ibus

  dbus-daemon[1293]: [session uid=1000 pid=1293] Activating service
  name='org.freedesktop.portal.IBus' requested by ':1.27' (uid=1000
  pid=1458 comm="ibus-daemon --xim --panel disable " label="unconfined")

  gnome-shell[1435]: Unable to connect to ibus: Could not connect:
  Connection refused

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr  5 07:43:59 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1761374] Re: Scrolling the app grid incurs very high CPU usage

2018-04-04 Thread Daniel van Vugt 
Upstream:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/174

** Description changed:

+ https://gitlab.gnome.org/GNOME/gnome-shell/issues/174
+ 
  Scrolling the app grid incurs very high CPU usage. On an i7-7700 desktop
  it uses 47% CPU (compared to 17% to display a maximized glxgears).
  
  I imagine most machines can't scroll the app grid smoothly. It doesn't
  appear smooth on this machine so I would look at the CPU usage problem
  first.

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

Title:
  Scrolling the app grid incurs very high CPU usage

Status in gnome-shell package in Ubuntu:
  New

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

  Scrolling the app grid incurs very high CPU usage. On an i7-7700
  desktop it uses 47% CPU (compared to 17% to display a maximized
  glxgears).

  I imagine most machines can't scroll the app grid smoothly. It doesn't
  appear smooth on this machine so I would look at the CPU usage problem
  first.

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

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

[Desktop-packages] [Bug 1761374] [NEW] Scrolling the app grid incurs very high CPU usage

2018-04-04 Thread Daniel van Vugt 
Public bug reported:

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

Scrolling the app grid incurs very high CPU usage. On an i7-7700 desktop
it uses 47% CPU (compared to 17% to display a maximized glxgears).

I imagine most machines can't scroll the app grid smoothly. It doesn't
appear smooth on this machine so I would look at the CPU usage problem
first.

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


** Tags: performance

** Tags added: performance

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

Title:
  Scrolling the app grid incurs very high CPU usage

Status in gnome-shell package in Ubuntu:
  New

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

  Scrolling the app grid incurs very high CPU usage. On an i7-7700
  desktop it uses 47% CPU (compared to 17% to display a maximized
  glxgears).

  I imagine most machines can't scroll the app grid smoothly. It doesn't
  appear smooth on this machine so I would look at the CPU usage problem
  first.

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

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

[Desktop-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate servic

2018-04-04 Thread Daniel van Vugt 
*** This bug is a duplicate of bug 1749546 ***
https://bugs.launchpad.net/bugs/1749546

OK, let's track this in bug 1749546 unless/until the fix for that proves
to not help with this one.

** Changed in: bluez (Ubuntu)
   Importance: Critical => High

** This bug has been marked a duplicate of bug 1749546
   Booting a live session is slow - fontconfig regenerates its font cache

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Also causing the long time to desktop from try/install livesession
  dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:

  rfkill:

  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: 
  [1520681416.8951] Loaded device plugin: NMBluezManager
  (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-
  bluetooth.so)

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

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

[Desktop-packages] [Bug 1760435] Re: Use Ubuntu language packs for various Unity packages

2018-04-04 Thread Simon Quigley 
I have uploaded these packages to Bileto, and I would like an ACK before
landing them.

https://bileto.ubuntu.com/#/ticket/3221

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

Title:
  Use Ubuntu language packs for various Unity packages

Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  New
Status in unity-greeter package in Ubuntu:
  New
Status in unity-lens-applications package in Ubuntu:
  New
Status in unity-lens-files package in Ubuntu:
  New
Status in unity-lens-music package in Ubuntu:
  New
Status in unity-lens-photos package in Ubuntu:
  New
Status in unity-lens-video package in Ubuntu:
  New
Status in unity-scope-calculator package in Ubuntu:
  New
Status in unity-scope-devhelp package in Ubuntu:
  New
Status in unity-scope-home package in Ubuntu:
  New
Status in unity-scope-manpages package in Ubuntu:
  New

Bug description:
  The Unity family of packages was previously part of standard Ubuntu.
  Thus all the translation templates were made available to the
  translators via Launchpad, and the translations were included in the
  language packs.

  Since those packages are no longer part of standard Ubuntu, they have
  been moved from main to universe. And translations are dropped.

  At the moment, it is feasible for us to keep using langpacks.

  That means adding "X-Ubuntu-Use-Langpack: yes" to their debian/control
  and doing an upload.

  See: https://community.ubuntu.com/t/translation-of-unity-packages/4919

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1760435/+subscriptions

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

[Desktop-packages] [Bug 1436509] Re: cursor not visible but mouse moves on first login after install

2018-04-04 Thread Simon Quigley 
Reversing the status change because Lyn informed me she is still
affected.

** Changed in: lubuntu-meta (Ubuntu)
   Status: Incomplete => New

** Changed in: xserver-xorg-input-mouse (Ubuntu)
   Status: Incomplete => New

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

Title:
  cursor not visible but mouse moves on first login after install

Status in lubuntu-meta package in Ubuntu:
  New
Status in xserver-xorg-input-mouse package in Ubuntu:
  New

Bug description:
  To reproduce install the Lubuntu amd 64 iso from this zsync link zsync 
http://cdimage.ubuntu.com/lubuntu/daily-live/20150324.2/vivid-desktop-amd64.iso.zsync.
 Then install it with manaul partioning and an ext4 / partion. Then the install 
completes and restart now and login. No cursor will appear on the screen at 
first login. 
  is the mouse from lsusb. 
  Bus 001 Device 002: ID 045e:0053 Microsoft Corp. Optical Mouse

  xserver-xorg-input-mouse:
Installed: 1:1.9.1-1
Candidate: 1:1.9.1-1
Version table:
   *** 1:1.9.1-1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  
  I expected to boot up and have a cursor. Instead for the first time I logged 
into lubuntu I had no cursor but after I logged out a cursor appeared and 
contiues to appear for succesive secessions. ISO tracker hardware profile is 
here  https://gist.github.com/56618cd1ed68e5b63a0c

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-input-mouse 1:1.9.1-1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Mar 25 11:57:31 2015
  InstallationDate: Installed on 2015-03-25 (0 days ago)
  InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324.2)
  SourcePackage: xserver-xorg-input-mouse
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1436509/+subscriptions

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

[Desktop-packages] [Bug 1674057] Re: [FFe] upgrade libzip to version 1.5.0

2018-04-04 Thread Tim Lunn 
** Description changed:

  Feature Freeze Justification
  
  This release fixes to two CVE's and most notably has removed its custom AES 
crypto implementation with using openssl libraries. It is for the security 
reasons I am requesting this FFe this late in the cycle.
  
  Other Changes:
  - A bunch of bug fixes
  - A number of new features like bzip2 (this optional and could be disabled 
for 18.04), improved AES encryption support, some of the new features are other 
platforms only
  - Breaks API (only 1 symbol was removed though), soname bump, so will require 
a mini transition, all the 24 reverse-depends that I count are in universe. 
Some are seeded in flavours (see below)
  - Build system switched to Cmake in latest release
  - Ark will build with libzip support where it didnt before
  
  Testing:
- It has a fairly comprehensive test suite, but I did have to disable for now, 
a few problematic tests that fail in the launchpad buildd chroots, but not 
elsewhere like local machine or Debian schroot.
+ It has a fairly comprehensive test suite, all tests are now passing.
  
  I have run a test rebuild for all the rdepends in ppa:darkxst/libzip.
  All built successfully, except for 2 packages, cbmc and plume-creater
  that had unrelated fallout due to gcc7 and other packaging changes.
  
  Other Notes:
  - There are a bunch of presumably private symbols leaked into the debian 
symbols file. Not ideal, but probably not the only package in the archive like 
that.
- - I will follow up with upstream issues for the RPATH stuff, tests and 
symbols later
+ - Have forwarded upstream a couple of patches and will follow symbols later
  - I will also push for the update into Debian
  
  Build Logs:
  
https://launchpadlibrarian.net/363222435/buildlog_ubuntu-bionic-amd64.libzip_1.5.0-0ubuntu1~bionic3_BUILDING.txt.gz
  
  Reverse-depends of libzip4 that are seeded:
  ark (from ark) is seeded in:
    kubuntu: daily-live
    lubuntu-next: daily-live
  ideviceinstaller is seeded in:
    ubuntu-mate: daily-live
  libepub0 is seeded in:
    kubuntu: daily-live
    ubuntustudio: dvd
  libpstoedit0c2a is seeded in:
    kubuntu: supported
  okular-extra-backends is seeded in:
    kubuntu: daily-live
  
  Upstream Changelog
  ==
  1.5.0 [2018-03-11]
  ==
  
  * Use standard cryptographic library instead of custom AES implementation.
    This also simplifies the license.
  * Use `clang-format` to format the source code.
  * More Windows improvements.
  
  1.4.0 [2017-12-29]
  ==
  
  * Improve build with cmake
  * Retire autoconf/automake build system
  * Add `zip_source_buffer_fragment()`.
  * Add support to clone unchanged beginning of archive (instead of rewriting 
it).
    Supported for buffer sources and on Apple File System.
  * Add support for Microsoft Universal Windows Platform.
  
  1.3.2 [2017-11-20]
  ==
  * Fix bug introduced in last: zip_t was erroneously freed if zip_close() 
failed.
  
  1.3.1 [2017-11-19]
  ==
  
  * Install zipconf.h into ${PREFIX}/include
  * Add zip_libzip_version()
  * Fix AES tests on Linux
  
  1.3.0 [2017-09-02]
  ==
  
  * Support bzip2 compressed zip archives
  * Improve file progress callback code
  * Fix zip_fdopen()
  * CVE-2017-12858: Fix double free()
  * CVE-2017-14107: Improve EOCD64 parsing
  
  1.2.0 [2017-02-19]
  ==
  
  * Support for AES encryption (Winzip version), both encryption
    and decryption
  * Support legacy zip files with >64k entries
  * Fix seeking in zip_source_file if start > 0
  * Add zip_fseek() for seeking in uncompressed data
  * Add zip_ftell() for telling position in uncompressed data
  * Add zip_register_progress_callback() for UI updates during zip_close()
  
  1.1.3 [2016-05-28]
  ==
  
  * Fix build on Windows when using autoconf

** Patch added: "debdiff against version 1.3.2 in Debian experimental"
   
https://bugs.launchpad.net/ubuntu/+source/libzip/+bug/1674057/+attachment/5102221/+files/libzip_1.5.0-r2.debdiff

** Patch removed: "debdiff against version 1.3.2 in Debian experimental"
   
https://bugs.launchpad.net/ubuntu/+source/libzip/+bug/1674057/+attachment/5101199/+files/libzip_1.5.debdiff

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

Title:
  [FFe] upgrade libzip to version 1.5.0

Status in libzip package in Ubuntu:
  New
Status in libzip package in Debian:
  New

Bug description:
  Feature Freeze Justification
  
  This release fixes to two CVE's and most notably has removed its custom AES 
crypto implementation with using openssl libraries. It is for the security 
reasons I am requesting this FFe this late in the cycle.

  Other Changes:
  - A bunch of bug fixes
  - A number of new features like bzip2 (this optional and could be disable

[Desktop-packages] [Bug 1761368] Re: nautilus crashed with SIGABRT in g_assertion_message()

2018-04-04 Thread Apport retracing service 
*** This bug is a duplicate of bug 1725783 ***
https://bugs.launchpad.net/bugs/1725783

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 #1725783, 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/1761368/+attachment/5102211/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1725783
   nautilus crashed with SIGABRT in g_assertion_message() (location != NULL)

** 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 nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1761368

Title:
  nautilus crashed with SIGABRT in g_assertion_message()

Status in nautilus package in Ubuntu:
  New

Bug description:
  Got this bug while using nautilus.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  4 22:26:22 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'196'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x549+321+62'"
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'"
  InstallationDate: Installed on 2018-03-26 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
  Signal: 6
  SourcePackage: nautilus
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: nautilus crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1761344] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

2018-04-04 Thread dino99 
*** This bug is a duplicate of bug 1725928 ***
https://bugs.launchpad.net/bugs/1725928

** This bug has been marked a duplicate of bug 1725928
   package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with 
differing files  '/lib/udev/hwdb.d/20-sane.hwdb'

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I do not know what happened, lubuntu caught an error upon reboot. It
  may be good to know I am booting from a hard drive that is connected
  to usb through usb to sata adapter.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Tue Apr  3 11:18:07 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-yEjTeS/133-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2017-10-28 (158 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1761344/+subscriptions

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

[Desktop-packages] [Bug 1761346] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

2018-04-04 Thread dino99 
*** This bug is a duplicate of bug 1725928 ***
https://bugs.launchpad.net/bugs/1725928

** This bug has been marked a duplicate of bug 1725928
   package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with 
differing files  '/lib/udev/hwdb.d/20-sane.hwdb'

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Thu Apr  5 08:17:49 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-UEKgyx/134-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Tidak ada berkas atau direktori seperti itu: "/root/Error: 
command ['which', 'python'] failed with exit code 1:": "/root/Error: command 
['which', 'python'] failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1761346/+subscriptions

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

[Desktop-packages] [Bug 1761367] Re: found solution rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()

2018-04-04 Thread Apport retracing service 
*** This bug is a duplicate of bug 1726398 ***
https://bugs.launchpad.net/bugs/1726398

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 #1726398, 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/1761367/+attachment/5102197/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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 rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/1761367

Title:
  found solution rhythmbox crashed with SIGSEGV in
  gtk_tree_view_get_column()

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Ubuntu Mate 18.04 Beta. I de-installed the alternative toolbar. Now
  everything works for me.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: rhythmbox 3.4.2-4ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: MATE
  Date: Thu Apr  5 05:48:37 2018
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2018-03-18 (18 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180307.1)
  ProcCmdline: rhythmbox
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f7992d49724 :  mov
(%rax),%rax
   PC (0x7f7992d49724) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: rhythmbox
  StacktraceTop:
   gtk_tree_view_get_column () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_tree_view_set_model () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/librhythmbox-core.so.10
  Title: rhythmbox crashed with SIGSEGV in gtk_tree_view_get_column()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1760661] Re: Chromium and Chrome pausing

2018-04-04 Thread Bret Ancowitz 
Not the entire browser UI, but the contents freeze for a period of time
- videos, scrolling, animations, etc.  If I open the Chrome/Chromium
task window, everything is fine.

This doesn't happen in 18.04 Gnome/Pop.  I'm going to reinstall 18.04
Budgie from scratch tonight (new Beta) and see if the problem persists
on total distro reinstall...

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

Title:
  Chromium and Chrome pausing

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  18.04 Budgie

  Chrome and Chromium installed via debs and snaps are pausing for
  variable seconds at a time, many times a minute.  Happens with or
  without any extensions.  Firefox is fine.  CPU usage seems to go up
  with the pauses.  Here is the snap run chromium output:

  ATTENTION: default value of option force_s3tc_enable overridden by 
environment.
  Gkr-Message: secret service operation failed: An AppArmor policy prevents 
this sender from sending this message to this recipient; type="method_call", 
sender=":1.143" (uid=1000 pid=5932 
comm="/snap/chromium/266/usr/lib/chromium-browser/chromi" 
label="snap.chromium.chromium (enforce)") interface="org.freedesktop.DBus.Peer" 
member="Ping" error name="(unset)" requested_reply="0" 
destination="org.freedesktop.secrets" (uid=1000 pid=1245 
comm="/usr/bin/gnome-keyring-daemon --daemonize --login " label="unconfined")
  Gkr-Message: secret service operation failed: An AppArmor policy prevents 
this sender from sending this message to this recipient; type="method_call", 
sender=":1.143" (uid=1000 pid=5932 
comm="/snap/chromium/266/usr/lib/chromium-browser/chromi" 
label="snap.chromium.chromium (enforce)") 
interface="org.freedesktop.Secret.Service" member="SearchItems" error 
name="(unset)" requested_reply="0" destination="org.freedesktop.secrets" 
(uid=1000 pid=1245 comm="/usr/bin/gnome-keyring-daemon --daemonize --login " 
label="unconfined")
  [5932:6071:0402/134337.573104:ERROR:udev_watcher.cc(60)] Failed to begin udev 
enumeration.

  Thank you.

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

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

[Desktop-packages] [Bug 1574593] Re: gdm and lightdm stop after upgrade

2018-04-04 Thread Daniel van Vugt 
** Summary changed:

- gdm and lightdm stop afetr upgrade
+ gdm and lightdm stop after upgrade

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

Title:
  gdm and lightdm stop after upgrade

Status in gdm package in Ubuntu:
  Incomplete

Bug description:
  After upgrade to 16.04 from 15.10 Ubuntu 64bit, with gnome desktop,
  gdm stop working.

  I had this error:
  [OK] started  GNOME display Manager.kernel modulect mapper.ndemand" 
link was shut down

  and the GDM graphical login screen don't appear.
  I've tried to switch to lightdm, the login screen appear, but it's impossible 
to start any installed dtm (gnome/gnome classic or ubuntu/unity)

  Than i've tried to install also swift, but i've found the same
  problem.

  Now, i've tried to install the complete lubuntu-desktop, it's also don't 
start, but the LDXE desktop yes, 
  For now im'using LDXE, but I need to reuturn to gnome...
  Please help !

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

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

[Desktop-packages] [Bug 1744366] Re: xfce power manager shows wrong battery life information (Lbuntu 16.04.3)

2018-04-04 Thread Simon Quigley 
Have you tried live CDs of other operating systems to see if this is a
Lubuntu-specific issue?

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

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

Title:
  xfce power manager shows wrong battery life information (Lbuntu
  16.04.3)

Status in upower package in Ubuntu:
  Incomplete

Bug description:
  As per title xfce power manager (version 1.4.4-4ubuntu2) on my Lubuntu
  16.04.3 shows a wrong battery life. What happens is that I plug in the
  laptop, it tells me the battery is 100% I unplug the write and I can
  see after maybe 10 minutes that the battery level lowered.

  I check and it gives me something like 80% and then, suddenly the
  laptop turns of because the battery is discharged.

  When i plug it back it shows as the battery is either charging
  correctly or charging and the percentage is over 70%.

  The battery is a few months old, so I think the problem lies in xfce
  power manager which displays the wrong information.Bug #1216594 opened
  in 2013 is very similar to my case, however that bug report was closed
  not because it was fixed but because it expired after 60 days.

  I tried 'upower -d' and it gives me the same info as the power manager.
  The output was:
  Device: /org/freedesktop/UPower/devices/line_power_ADP1
native-path:  ADP1
power supply: yes
updated:  XX XX XXX  17:58:48 GMT (815 seconds ago)
has history:  no
has statistics:   no
line-power
  warning-level:   none
  online:  yes
  icon-name:  'ac-adapter-symbolic'

  Device: /org/freedesktop/UPower/devices/battery_BAT0
native-path:  BAT0
vendor:   Hewlett-Packard
model:Primary
power supply: yes
updated:  Fri 19 Jan 2018 18:10:34 GMT (109 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   charging
  warning-level:   none
  energy:  22.2592 Wh
  energy-empty:0 Wh
  energy-full: 26.048 Wh
  energy-full-design:  26.048 Wh
  energy-rate: 20.0392 W
  voltage: 16.444 V
  time to full:11.3 minutes
  percentage:  85%
  capacity:100%
  technology:  lithium-ion
  icon-name:  'battery-full-charging-symbolic'
History (charge):
  151638543485.000  charging
History (rate):
  151638543420.039  charging

  Device: /org/freedesktop/UPower/devices/DisplayDevice
power supply: yes
updated:  XX XX XXX  18:10:34 GMT (109 seconds ago)
has history:  no
has statistics:   no
battery
  present: yes
  state:   charging
  warning-level:   none
  energy:  22.2592 Wh
  energy-full: 26.048 Wh
  energy-rate: 20.0392 W
  time to full:11.3 minutes
  percentage:  85%
  icon-name:  'battery-full-charging-symbolic'

  Daemon:
daemon-version:  0.99.4
on-battery:  no
lid-is-closed:   no
lid-is-present:  yes
critical-action: HybridSleep

  Any ideas?

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

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

[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2018-04-04 Thread Rocko 
I sometimes find that not only mouse clicks get blocked, but everything
except ubuntu-dock and the Activities overview stops accepting input. (I
can't ALT-F2 to restart gnome, and I can't ALT-tab between apps.) On a
couple of occasions I found that it was a single app that had captured
input (and crashed), and quitting the rogue app via ubuntu-dock or the
Activities overview fixed the issue. But this isn't always possible
because some applications put up a dialog asking if you want to quit,
and since you can't click on the dialog box, you can't quit them.

Is the bug I'm describing related to this one, or something different?

FWIW, I did find that "killall -3 gnome-shell" will restart the shell
without closing your applications if you can manage to get to a tty
console. Is there a way to restart the shell from the Activities
overview? That would be a good workaround for this bug.

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, but it seems to happen
  upon opening a new window, changing windows, closing windows, or
  opening the activities pane (whether a change of window is thus
  instigated or not)

  ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
  and to log in again, but that is also less than ideal

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1761364] Re: gnome-shell crashed with signal 5

2018-04-04 Thread Apport retracing service 
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450

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 #1748450, 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/1761364/+attachment/5102167/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Crashed when launching slack as installed from Software in daily
  bionic build

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Apr  5 11:34:04 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-04-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1434240] Re: nm-applet icon missing from lxpanel in Lubuntu 14.04

2018-04-04 Thread Simon Quigley 
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 1434240

and any other logs that are relevant for this particular issue.

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

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

Title:
  nm-applet icon missing from lxpanel in Lubuntu 14.04

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

Bug description:
  Somehow recently my network applet disappeared from LXpanel. I could
  not figure out what caused this or what to do to restore it. nm-applet
  is still in my autostart and does seem to be working on boot up.
  However, I found Bug #1302462 which seems to fit the problem I am
  facing. Using the workaround mentioned in comment #15 of that bug does
  work. So I believe Lubuntu is also affected by Bug #1302462 since it
  uses the same network manager applet.

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

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

[Desktop-packages] [Bug 1436509] Re: cursor not visible but mouse moves on first login after install

2018-04-04 Thread Simon Quigley 
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 1436509

and any other logs that are relevant for this particular issue.

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

Title:
  cursor not visible but mouse moves on first login after install

Status in lubuntu-meta package in Ubuntu:
  Incomplete
Status in xserver-xorg-input-mouse package in Ubuntu:
  Incomplete

Bug description:
  To reproduce install the Lubuntu amd 64 iso from this zsync link zsync 
http://cdimage.ubuntu.com/lubuntu/daily-live/20150324.2/vivid-desktop-amd64.iso.zsync.
 Then install it with manaul partioning and an ext4 / partion. Then the install 
completes and restart now and login. No cursor will appear on the screen at 
first login. 
  is the mouse from lsusb. 
  Bus 001 Device 002: ID 045e:0053 Microsoft Corp. Optical Mouse

  xserver-xorg-input-mouse:
Installed: 1:1.9.1-1
Candidate: 1:1.9.1-1
Version table:
   *** 1:1.9.1-1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  
  I expected to boot up and have a cursor. Instead for the first time I logged 
into lubuntu I had no cursor but after I logged out a cursor appeared and 
contiues to appear for succesive secessions. ISO tracker hardware profile is 
here  https://gist.github.com/56618cd1ed68e5b63a0c

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-input-mouse 1:1.9.1-1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Mar 25 11:57:31 2015
  InstallationDate: Installed on 2015-03-25 (0 days ago)
  InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324.2)
  SourcePackage: xserver-xorg-input-mouse
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1436509/+subscriptions

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

[Desktop-packages] [Bug 1574593] Re: gdm and lightdm stop afetr upgrade

2018-04-04 Thread Simon Quigley 
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 1574593

and any other logs that are relevant for this particular issue.

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

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

Title:
  gdm and lightdm stop afetr upgrade

Status in gdm package in Ubuntu:
  Incomplete

Bug description:
  After upgrade to 16.04 from 15.10 Ubuntu 64bit, with gnome desktop,
  gdm stop working.

  I had this error:
  [OK] started  GNOME display Manager.kernel modulect mapper.ndemand" 
link was shut down

  and the GDM graphical login screen don't appear.
  I've tried to switch to lightdm, the login screen appear, but it's impossible 
to start any installed dtm (gnome/gnome classic or ubuntu/unity)

  Than i've tried to install also swift, but i've found the same
  problem.

  Now, i've tried to install the complete lubuntu-desktop, it's also don't 
start, but the LDXE desktop yes, 
  For now im'using LDXE, but I need to reuturn to gnome...
  Please help !

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

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

[Desktop-packages] [Bug 1584793] Re: Rhythmbox fails to put an icon on the system tray in Lubuntu 14.04

2018-04-04 Thread Simon Quigley 
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 1584793

and any other logs that are relevant for this particular issue.

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

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

Title:
  Rhythmbox fails to put an icon on the system tray in Lubuntu 14.04

Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  When I run Rhythmbox and close it while music is playing, I have no
  way to return to it. It should show up in the system tray. I know
  Rhythmbox is running because it's in the process list.

   edg@arthur ~ $ ps ax|grep rhythmbox
   29371 ?Sl 1:16 rhythmbox
   30029 pts/6S+ 0:00 grep --color=auto rhythmbox
   edg@arthur ~ $

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

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

[Desktop-packages] [Bug 1436509] Re: cursor not visible but mouse moves on first login after install

2018-04-04 Thread Simon Quigley 
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 1436509

and any other logs that are relevant for this particular issue.

** Changed in: lubuntu-meta (Ubuntu)
   Status: New => Incomplete

** Changed in: xserver-xorg-input-mouse (Ubuntu)
   Status: New => Incomplete

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

Title:
  cursor not visible but mouse moves on first login after install

Status in lubuntu-meta package in Ubuntu:
  Incomplete
Status in xserver-xorg-input-mouse package in Ubuntu:
  Incomplete

Bug description:
  To reproduce install the Lubuntu amd 64 iso from this zsync link zsync 
http://cdimage.ubuntu.com/lubuntu/daily-live/20150324.2/vivid-desktop-amd64.iso.zsync.
 Then install it with manaul partioning and an ext4 / partion. Then the install 
completes and restart now and login. No cursor will appear on the screen at 
first login. 
  is the mouse from lsusb. 
  Bus 001 Device 002: ID 045e:0053 Microsoft Corp. Optical Mouse

  xserver-xorg-input-mouse:
Installed: 1:1.9.1-1
Candidate: 1:1.9.1-1
Version table:
   *** 1:1.9.1-1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  
  I expected to boot up and have a cursor. Instead for the first time I logged 
into lubuntu I had no cursor but after I logged out a cursor appeared and 
contiues to appear for succesive secessions. ISO tracker hardware profile is 
here  https://gist.github.com/56618cd1ed68e5b63a0c

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-input-mouse 1:1.9.1-1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Mar 25 11:57:31 2015
  InstallationDate: Installed on 2015-03-25 (0 days ago)
  InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324.2)
  SourcePackage: xserver-xorg-input-mouse
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1436509/+subscriptions

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

[Desktop-packages] [Bug 1620092] Re: Lubuntu 14.04 HWE update problem: libgbm1-lts-xenial does not provide libgbm1

2018-04-04 Thread Simon Quigley 
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 1620092

and any other logs that are relevant for this particular issue.

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

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

Title:
  Lubuntu 14.04 HWE update problem: libgbm1-lts-xenial does not provide
  libgbm1

Status in mesa-lts-xenial package in Ubuntu:
  Incomplete

Bug description:
  Installed Lubuntu 14.04 i386.
  I used the apt line for all HWE updates from the ubuntu wiki, to update each 
stack manually.  E.g., for xenial:
  sudo apt-get install --install-recommends linux-generic-lts-xenial 
xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial 
xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial 
libwayland-egl1-mesa-lts-xenial
  ( https://wiki.ubuntu.com/Kernel/LTSEnablementStack#Desktop )

  * The kernel stacks updated with no problem.
  * When I try to update the graphics HWE stack from *-vivid to *-willy or 
*-xenial, apt wants to uninstall a lot of stuff, among them:
  abiword libabiword-3.0 audacious audacious-plugins lubuntu-desktop

  I did the update with the Xenial stack anyway, and tried to find the
  problem while installing uninstalled (non-lib) stuff back.

  Worked my way to libgbm1 through "X depends on Y, but it is not going
  to be installed" errors.

  libgbm1 has libgbm1-lts-* versions, and libgbm1-lts-xenial
  (11.2.0-1ubuntu2~trusty1) got installed with the xenial HWE stack.

  I noticed that some packages, e.g. libgbm1 and mesa-vdpau-drivers
  stayed installed although they both have -lts-* versions.

  1) Shouldn't the libgbm1-lts-* packages (that do not depend on libgbm1) 
provide libgbm1?
  Or did the API change?

  
http://answers.ros.org/question/203610/ubuntu-14042-unmet-dependencies-similar-for-14043/
  looks connected, but their solution -- to also install some -dev-lts-* pkgs 
-- seems like more of a workaround if they rebuilt the pkg, and I don't think 
it will help a more complex dependency problem.

  2) Did I update the stack incorrectly? Is there a
  better/automated/reliable method?

  Aside from libgbm1, the base mesa-vdpau-drivers stayed installed even
  though I upgraded up to the vivid graphics stack---probably mesa-
  vdpau-drivers-lts-* was missing from the apt line because it is not
  necessary to have installed (not all systems can or want to do vdpau
  accel)?

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

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

[Desktop-packages] [Bug 1633935] Re: Inkscape freezes when selecting font

2018-04-04 Thread Simon Quigley 
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 1633935

and any other logs that are relevant for this particular issue.

** Changed in: inkscape
   Status: New => Incomplete

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

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

Title:
  Inkscape freezes when selecting font

Status in Inkscape:
  Incomplete
Status in inkscape package in Ubuntu:
  Incomplete

Bug description:
  If you perform the following steps, Inkscape freezes. It's a
  showstopper of using Inkscape at all with fonts.

  1. Launch Inkscape.
  2. On the new document, click the A on the left toolbar to create a new 
textbox.
  3. Drag a marquee in your document for the size of your textbox.
  4. Type the text "This is a test" and then choose Select All to select it all.
  5. Click the T in the top toolbar to open the Text and Font control panel.
  6. Choose DejaVu Sans.
  7. Put another window on top of the current window, such as switch to a web 
browser.
  8. Come back to Inkscape -- it won't repaint the window because it's frozen.

  Alternatively, you can also recreate the bug this way too:

  1. Launch Inkscape.
  2. On the new document, click the A on the left toolbar to create a new 
textbox.
  3. Drag a marquee in your document for the size of your textbox.
  4. Type the text "This is a test" and then choose Select All to select it all.
  5. Click the T in the top toolbar to open the Text and Font control panel.
  6. Choose DejaVu Sans.
  7. Set the font size to 48 from the Font Size: selector on that control 
panel. You'll notice that the dropdown occurs, when you select it, Inkscape 
freezes.

  Note that I'm running Inkscape 0.91 on Lubuntu Desktop 16.04 inside
  Oracle Virtualbox version 5.0.26 r108824 on a Mac Air 13" running OSX
  10.12 (Sierra) and have loaded the Virtualbox extensions. Note that I
  also tried the following things to see if they fixed the problem:

  - full apt-get update; apt-get upgrade; apt-get dist-upgrade, reboot,
  and tried that again

  - apt purge fonts-noto-cjk

  - tried briefly the latest stable PPA of Inkscape from Inkscape.org in
  my apt, and upgrade to the latest Inkscape -- that failed, so I did a
  purge remove of that version of inkscape, removed the PPA, redid my
  apt-get update, and installed the version that comes with Ubuntu 16.04
  (Inkscape 0.91).

  - unset GTK_IM_MODULE && inkscape

  All failed to show any fix.

  
  All failed to show any different result.

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

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

[Desktop-packages] [Bug 997037] Re: Chromium freezes on play at youtube.com/xl on LXDE

2018-04-04 Thread Simon Quigley 
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 997037

and any other logs that are relevant for this particular issue.

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

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

Title:
  Chromium freezes on play at youtube.com/xl on LXDE

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Start Chromium, open webpage http://www.youtube.com/xl and start any video.
  Chromium will freeze, start to behave strange on Lubuntu 12.04.

  Working normally on Ubuntu with Gnome Classic (Ubuntu 11.10 Gnome
  Classic)

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

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

[Desktop-packages] [Bug 1266911] Re: Lightdm hangs when switching sessions

2018-04-04 Thread Simon Quigley 
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 1266911

and any other logs that are relevant for this particular issue.

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

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

Title:
  Lightdm hangs when switching sessions

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Lightdm hangs when attempting to select lx Games or Lubuntu Nexus 7
  sessions. This discovered for the Lubuntu 14.04 LTS testdrive via the
  virtual machine.

  Ubuntu Trusty Tahr (development branch)
  14.04

  lightdm:
     Installed: 1.9.5-0ubuntu1
     Candidate:  1.9.5-oubuntu1
     Version table:
   *** 1.9.5-0ubuntu1 0
     500   http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 
Packages
     100   /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1310392] Re: Hardware screen scaling problems since 14.04 upgrade with Nvidia legacy driver

2018-04-04 Thread Simon Quigley 
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 1310392

and any other logs that are relevant for this particular issue.

** Changed in: nvidia-graphics-drivers-173 (Ubuntu)
   Status: New => Incomplete

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

Title:
  Hardware screen scaling problems since 14.04 upgrade with Nvidia
  legacy driver

Status in nvidia-graphics-drivers-173 package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  Just upgraded to Lubuntu 32-bit 14.04 from 13.10 on April 18th, 2014.

  - System is a P4, 2.8Ghz, 3GB RAM,
  - NVidia GeForce 5700LE AGP graphics card with proprietary legacy video 
drivers manually installed from Nvidia site (VERSION 173.14.39, RELEASE: 
2013.12.6 - the latest possible version available for my graphics card).
  - Motherboard is ASUS P4P800-E upgraded to the latest BIOS available.

  Prior to the upgrade, the arcade emulator MAME, the Commodore 64
  emulator VICE, and the Commodore Amiga emulator FS-UAE worked
  fantastically in full screen scaled mode. No delay, smooth
  performance. Reasonably low CPU usage for a processor of this vintage.

  After the upgrade to 14.04, all full screen modes (1080x1920) in these
  emulators bring the system to a crawl. Sound from the emulator is
  broken up, framerates are terrible (like two frames a second), CPU
  usage is near or past 100%. I suspect other OpenGL software using
  full-screen scaling would also be affected, but these are the only
  three pieces of software I have to test with.

  I've found that in MAME and VICE, I can work-around this problem but
  shutting off "hardware scaling". Essentially (I think), this takes my
  graphics card out of the loop and does the scaling in software/CPU.
  Scaling down the resolution of the emulation helps too. Frame-rates
  are better, CPU usage is lower by a factor of 30 to 40%. However,
  because of these "work around measure" the overall user experience of
  the emulators is severely impeded.

  I also ran glxgears as a test and resized the window from its original
  small size, a little bigger every five seconds, until it was the full
  height of the screen (1080 lines) and got the following results:

  Code:

  brent@Brent-Lubuntu:~$ glxgears
  552 frames in 5.0 seconds = 110.342 FPS
  593 frames in 5.0 seconds = 118.471 FPS
  416 frames in 5.0 seconds = 83.071 FPS
  315 frames in 5.0 seconds = 62.810 FPS
  287 frames in 5.0 seconds = 57.252 FPS
  197 frames in 5.0 seconds = 39.354 FPS
  165 frames in 5.0 seconds = 32.789 FPS
  130 frames in 5.0 seconds = 25.937 FPS
  124 frames in 5.0 seconds = 24.781 FPS
  117 frames in 5.0 seconds = 23.274 FPS
  XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 25689 requests (25666 known processed) with 0 events remaining.

  I had originally switched to the Nvidia proprietary driver from
  Nouveau because of slight artifacts and stuttering in the latter. The
  proprietary driver mentioned above worked like a dream in 13.10.

  MP4 videos played in VLC VideoLAN player still play well, with low CPU
  usage.

  Based on my limited knowledge, this seems to be a problem with the
  graphics card full-screen scaling to 1080x1920 (desktop & monitor
  screenmode) under 14.04. Might have to do something with OpenGL?

  The system works very well, other than when these emulators try to go
  into full screen mode.

  My Xorg.0.log file shows the following (notice the error lines):

  (II) LoadModule: "nvidia"
  (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
  (II) Module nvidia: vendor="NVIDIA Corporation"
  compiled for 4.0.2, module version = 1.0.0
  Module class: X.Org Video Driver
  (II) NVIDIA dlloader X Driver 173.14.39 Wed Nov 27 15:02:30 PST 2013
  (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs

  ...

  (**) NVIDIA(0): Enabling RENDER acceleration
  (EE) NVIDIA(0): Failed to initialize the GLX module; please check in
  your X
  (EE) NVIDIA(0): log file that the GLX module has been loaded in your X
  (EE) NVIDIA(0): server, and that the module is the NVIDIA GLX
  module. If
  (EE) NVIDIA(0): you continue to encounter problems, Please try
  (EE) NVIDIA(0): reinstalling the NVIDIA driver.
  (II) NVIDIA(0): NVIDIA GPU GeForce FX 5700LE (NV36) at PCI:1:0:0 (GPU-0)
  (--) NVIDIA(0): Memory: 262144 kBytes
  (--) NVIDIA(0): VideoBIOS: 04.36.20.35.00
  (II) NVIDIA(0): D

[Desktop-packages] [Bug 1761361] [NEW] chrome browser freeze after ubuntu wakeup from sleeping

2018-04-04 Thread 张云峰 
Public bug reported:

steps:
1. open chrome browser
2. sleep laptap by closing its cover
3. wakeup laptap, then found chrome browser is frozen.

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

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

Title:
  chrome browser freeze after ubuntu wakeup from sleeping

Status in gnome-software package in Ubuntu:
  New

Bug description:
  steps:
  1. open chrome browser
  2. sleep laptap by closing its cover
  3. wakeup laptap, then found chrome browser is frozen.

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

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

[Desktop-packages] [Bug 282954] Re: Wish: Quiet installation option

2018-04-04 Thread Simon Quigley 
I believe that Ubiquity is now quiet, and really doesn't emit any noise.

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

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

Title:
  Wish: Quiet installation option

Status in pulseaudio package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: ubiquity

  I often test new systems (alphas, betas, mockups) when the house is
  asleep. Therefore, it is essential to me that the system not beep or
  be otherwise noisy. I propose an option in the Advanced dialog (at the
  end of the installation wizard) for disabling the PC Speaker and
  desktop (Gnome/KDE) sound theme. The advanced dialog contains only two
  options at the moment, so clutter is not a worry.

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

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

[Desktop-packages] [Bug 1761360] ThreadStacktrace.txt

2018-04-04 Thread Apport retracing service 
** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1761360/+attachment/5102166/+files/ThreadStacktrace.txt

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

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

** Tags removed: need-amd64-retrace

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

Title:
  chromium-browser crashed with SIGABRT

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  The browser crashed upon start when I first booted my computer.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 65.0.3325.181-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAw5CUFAAAaAQSVIhN4CkLlkVhVjygeUFQBAQEBAQEBAQEBAQEBAQEB0B1W9FAAFjAwIDUAWMIQAAAa2RdW9FAAFjAwIDUAWMIQAAAa/gBIOTdIMYAxNTZXSFUKQTGUABkBCiAgAI0=
   modes: 1366x768 1366x768
  Date: Tue Apr  3 23:18:02 2018
  Desktop-Session:
   'xubuntu'
   '/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg'
   
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2017-10-24 (162 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Load-Avg-1min: 3.49
  Load-Processes-Running-Percent:   0.2%
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --enable-pinch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: chromium-browser
  StacktraceTop:
   ()
   ()
   ()
   dbus_connection_dispatch () at /lib/x86_64-linux-gnu/libdbus-1.so.3
   ()
  Title: chromium-browser crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-02-19 (44 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 01/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 01W6F7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd01/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5567
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1761360] chromium-browser crashed with SIGABRT

2018-04-04 Thread Apport retracing service 
StacktraceTop:
 base::debug::BreakDebugger() () at ../../base/debug/debugger_posix.cc:258
 ~LogMessage () at ../../base/logging.cc:842
 OnConnectionDisconnectedFilter () at ../../dbus/bus.cc:1151
 dbus_connection_dispatch (connection=0x5640fd53e890) at 
../../../dbus/dbus-connection.c:4703
 dbus::Bus::ProcessAllIncomingDataIfAny() () at ../../dbus/bus.cc:781

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

Title:
  chromium-browser crashed with SIGABRT

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  The browser crashed upon start when I first booted my computer.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 65.0.3325.181-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAw5CUFAAAaAQSVIhN4CkLlkVhVjygeUFQBAQEBAQEBAQEBAQEBAQEB0B1W9FAAFjAwIDUAWMIQAAAa2RdW9FAAFjAwIDUAWMIQAAAa/gBIOTdIMYAxNTZXSFUKQTGUABkBCiAgAI0=
   modes: 1366x768 1366x768
  Date: Tue Apr  3 23:18:02 2018
  Desktop-Session:
   'xubuntu'
   '/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg'
   
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2017-10-24 (162 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Load-Avg-1min: 3.49
  Load-Processes-Running-Percent:   0.2%
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --enable-pinch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: chromium-browser
  StacktraceTop:
   ()
   ()
   ()
   dbus_connection_dispatch () at /lib/x86_64-linux-gnu/libdbus-1.so.3
   ()
  Title: chromium-browser crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-02-19 (44 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 01/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 01W6F7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd01/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5567
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1761360] StacktraceSource.txt

2018-04-04 Thread Apport retracing service 
** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1761360/+attachment/5102165/+files/StacktraceSource.txt

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

Title:
  chromium-browser crashed with SIGABRT

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  The browser crashed upon start when I first booted my computer.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 65.0.3325.181-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAw5CUFAAAaAQSVIhN4CkLlkVhVjygeUFQBAQEBAQEBAQEBAQEBAQEB0B1W9FAAFjAwIDUAWMIQAAAa2RdW9FAAFjAwIDUAWMIQAAAa/gBIOTdIMYAxNTZXSFUKQTGUABkBCiAgAI0=
   modes: 1366x768 1366x768
  Date: Tue Apr  3 23:18:02 2018
  Desktop-Session:
   'xubuntu'
   '/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg'
   
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2017-10-24 (162 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Load-Avg-1min: 3.49
  Load-Processes-Running-Percent:   0.2%
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --enable-pinch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: chromium-browser
  StacktraceTop:
   ()
   ()
   ()
   dbus_connection_dispatch () at /lib/x86_64-linux-gnu/libdbus-1.so.3
   ()
  Title: chromium-browser crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-02-19 (44 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 01/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 01W6F7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd01/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5567
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1761360] Stacktrace.txt

2018-04-04 Thread Apport retracing service 
** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1761360/+attachment/5102164/+files/Stacktrace.txt

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

Title:
  chromium-browser crashed with SIGABRT

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  The browser crashed upon start when I first booted my computer.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 65.0.3325.181-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAw5CUFAAAaAQSVIhN4CkLlkVhVjygeUFQBAQEBAQEBAQEBAQEBAQEB0B1W9FAAFjAwIDUAWMIQAAAa2RdW9FAAFjAwIDUAWMIQAAAa/gBIOTdIMYAxNTZXSFUKQTGUABkBCiAgAI0=
   modes: 1366x768 1366x768
  Date: Tue Apr  3 23:18:02 2018
  Desktop-Session:
   'xubuntu'
   '/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg'
   
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2017-10-24 (162 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Load-Avg-1min: 3.49
  Load-Processes-Running-Percent:   0.2%
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --enable-pinch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: chromium-browser
  StacktraceTop:
   ()
   ()
   ()
   dbus_connection_dispatch () at /lib/x86_64-linux-gnu/libdbus-1.so.3
   ()
  Title: chromium-browser crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-02-19 (44 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 01/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 01W6F7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd01/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5567
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1761360] [NEW] chromium-browser crashed with SIGABRT

2018-04-04 Thread Stephen Michael Kellat 
Public bug reported:

The browser crashed upon start when I first booted my computer.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: chromium-browser 65.0.3325.181-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
DRM.card0-HDMI-A-1:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64: 
 modes:
DRM.card0-eDP-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: 
AP///wAw5CUFAAAaAQSVIhN4CkLlkVhVjygeUFQBAQEBAQEBAQEBAQEBAQEB0B1W9FAAFjAwIDUAWMIQAAAa2RdW9FAAFjAwIDUAWMIQAAAa/gBIOTdIMYAxNTZXSFUKQTGUABkBCiAgAI0=
 modes: 1366x768 1366x768
Date: Tue Apr  3 23:18:02 2018
Desktop-Session:
 'xubuntu'
 '/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg'
 
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
DetectedPlugins:
 
Env:
 'None'
 'None'
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationDate: Installed on 2017-10-24 (162 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
Load-Avg-1min: 3.49
Load-Processes-Running-Percent:   0.2%
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 5567
ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --enable-pinch
ProcEnviron:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
Signal: 6
SourcePackage: chromium-browser
StacktraceTop:
 ()
 ()
 ()
 dbus_connection_dispatch () at /lib/x86_64-linux-gnu/libdbus-1.so.3
 ()
Title: chromium-browser crashed with SIGABRT
UpgradeStatus: Upgraded to bionic on 2018-02-19 (44 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
dmi.bios.date: 01/12/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.0
dmi.board.name: 01W6F7
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd01/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5567
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.default.chromium-browser: [deleted]

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


** Tags: amd64 apport-crash bionic

** Information type changed from Private to Public

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

Title:
  chromium-browser crashed with SIGABRT

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  The browser crashed upon start when I first booted my computer.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 65.0.3325.181-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAw5CUFAAAaAQSVIhN4CkLlkVhVjygeUFQBAQEBAQEBAQEBAQEBAQEB0B1W9FAAFjAwIDUAWMIQAAAa2RdW9FAAFjAwIDUAWMIQAAAa/gBIOTdIMYAxNTZXSFUKQTGUABkBCiAgAI0=
   modes: 1366x768 1366x768
  Date: Tue Apr  3 23:18:02 2018
  Desktop-Session:
   'xubuntu'
   '/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg'
   
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2017-10-24 (162 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Load-Avg-1min: 3.49
  Load-Processes-Running-Percent:   0.2%
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --enable-pinch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePack

[Desktop-packages] [Bug 1760983] Re: nvidia-kernel-source-390 390.42-0ubuntu1: nvidia kernel module failed to build [Makefile:976: "Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, lib

2018-04-04 Thread Daniel van Vugt 
*** This bug is a duplicate of bug 1760876 ***
https://bugs.launchpad.net/bugs/1760876

** This bug has been marked a duplicate of bug 1753114
   DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please 
install libelf-dev, libelf-devel or elfutils-libelf-devel

** This bug is no longer a duplicate of bug 1753114
   DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please 
install libelf-dev, libelf-devel or elfutils-libelf-devel
** This bug has been marked a duplicate of bug 1760876
   DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please 
install libelf-dev, libelf-devel or elfutils-libelf-devel

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

Title:
  nvidia-kernel-source-390 390.42-0ubuntu1: nvidia kernel module failed
  to build [Makefile:976: "Cannot use CONFIG_STACK_VALIDATION=y, please
  install libelf-dev, libelf-devel or elfutils-libelf-devel"]

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

Bug description:
  Report generated automatically by the system

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-kernel-source-390 390.42-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-14.15-generic 4.15.15
  Uname: Linux 4.15.0-14-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-14-generic
  Date: Tue Apr  3 17:25:35 2018
  Dependencies:
   
  InstallationDate: Installed on 2018-04-03 (0 days ago)
  InstallationMedia:
   
  PackageVersion: 390.42-0ubuntu1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No existe el archivo o el directorio: "/root/Error: 
command ['which', 'python'] failed with exit code 1:": "/root/Error: command 
['which', 'python'] failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: nvidia-graphics-drivers-390
  Title: nvidia-kernel-source-390 390.42-0ubuntu1: nvidia kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1753114] Re: DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel

2018-04-04 Thread Daniel van Vugt 
*** This bug is a duplicate of bug 1760876 ***
https://bugs.launchpad.net/bugs/1760876

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

** This bug has been marked a duplicate of bug 1760876
   DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please 
install libelf-dev, libelf-devel or elfutils-libelf-devel

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

Title:
  DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y,
  please install libelf-dev, libelf-devel or elfutils-libelf-devel

Status in bcmwl package in Ubuntu:
  Confirmed
Status in dkms package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in r8168 package in Ubuntu:
  Confirmed

Bug description:
  Had the need to install r8168-dkms, but got a make.log error:

  
  DKMS make.log for r8168-8.045.08 for kernel 4.15.0-11-generic (x86_64)
  Sat Mar  3 16:08:17 CET 2018
  make: Entering directory '/usr/src/linux-headers-4.15.0-11-generic'
  Makefile:962: "Cannot use CONFIG_STACK_VALIDATION=y, please install 
libelf-dev, libelf-devel or elfutils-libelf-devel"
CC [M]  /var/lib/dkms/r8168/8.045.08/build/r8168_n.o
CC [M]  /var/lib/dkms/r8168/8.045.08/build/r8168_asf.o
CC [M]  /var/lib/dkms/r8168/8.045.08/build/rtl_eeprom.o
CC [M]  /var/lib/dkms/r8168/8.045.08/build/rtltool.o
LD [M]  /var/lib/dkms/r8168/8.045.08/build/r8168.o
Building modules, stage 2.
MODPOST 1 modules
CC  /var/lib/dkms/r8168/8.045.08/build/r8168.mod.o
LD [M]  /var/lib/dkms/r8168/8.045.08/build/r8168.ko
  make: Leaving directory '/usr/src/linux-headers-4.15.0-11-generic'
  

  so i have installed libelf-dev, and reinstalled r8168-dkms again. Next
  the make.log looks:

  ***
  DKMS make.log for r8168-8.045.08 for kernel 4.15.0-11-generic (x86_64)
  Sat Mar  3 16:15:11 CET 2018
  make: Entering directory '/usr/src/linux-headers-4.15.0-11-generic'
CC [M]  /var/lib/dkms/r8168/8.045.08/build/r8168_n.o
CC [M]  /var/lib/dkms/r8168/8.045.08/build/r8168_asf.o
CC [M]  /var/lib/dkms/r8168/8.045.08/build/rtl_eeprom.o
CC [M]  /var/lib/dkms/r8168/8.045.08/build/rtltool.o
LD [M]  /var/lib/dkms/r8168/8.045.08/build/r8168.o
Building modules, stage 2.
MODPOST 1 modules
CC  /var/lib/dkms/r8168/8.045.08/build/r8168.mod.o
LD [M]  /var/lib/dkms/r8168/8.045.08/build/r8168.ko
  make: Leaving directory '/usr/src/linux-headers-4.15.0-11-generic'
  **

  So please, add libelf-dev as r8168-dkms dependency.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: r8168-dkms 8.045.08-2
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Mar  3 16:11:00 2018
  EcryptfsInUse: Yes
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: r8168
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1753114] Re: DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel

2018-04-04 Thread Daniel van Vugt 
*** This bug is a duplicate of bug 1760876 ***
https://bugs.launchpad.net/bugs/1760876

** Summary changed:

- Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev
+ DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please 
install libelf-dev, libelf-devel or elfutils-libelf-devel

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

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

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

** Also affects: nvidia-graphics-drivers-340 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: New => Confirmed

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: New => Confirmed

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

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

Title:
  DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y,
  please install libelf-dev, libelf-devel or elfutils-libelf-devel

Status in bcmwl package in Ubuntu:
  Confirmed
Status in dkms package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in r8168 package in Ubuntu:
  Confirmed

Bug description:
  Had the need to install r8168-dkms, but got a make.log error:

  
  DKMS make.log for r8168-8.045.08 for kernel 4.15.0-11-generic (x86_64)
  Sat Mar  3 16:08:17 CET 2018
  make: Entering directory '/usr/src/linux-headers-4.15.0-11-generic'
  Makefile:962: "Cannot use CONFIG_STACK_VALIDATION=y, please install 
libelf-dev, libelf-devel or elfutils-libelf-devel"
CC [M]  /var/lib/dkms/r8168/8.045.08/build/r8168_n.o
CC [M]  /var/lib/dkms/r8168/8.045.08/build/r8168_asf.o
CC [M]  /var/lib/dkms/r8168/8.045.08/build/rtl_eeprom.o
CC [M]  /var/lib/dkms/r8168/8.045.08/build/rtltool.o
LD [M]  /var/lib/dkms/r8168/8.045.08/build/r8168.o
Building modules, stage 2.
MODPOST 1 modules
CC  /var/lib/dkms/r8168/8.045.08/build/r8168.mod.o
LD [M]  /var/lib/dkms/r8168/8.045.08/build/r8168.ko
  make: Leaving directory '/usr/src/linux-headers-4.15.0-11-generic'
  

  so i have installed libelf-dev, and reinstalled r8168-dkms again. Next
  the make.log looks:

  ***
  DKMS make.log for r8168-8.045.08 for kernel 4.15.0-11-generic (x86_64)
  Sat Mar  3 16:15:11 CET 2018
  make: Entering directory '/usr/src/linux-headers-4.15.0-11-generic'
CC [M]  /var/lib/dkms/r8168/8.045.08/build/r8168_n.o
CC [M]  /var/lib/dkms/r8168/8.045.08/build/r8168_asf.o
CC [M]  /var/lib/dkms/r8168/8.045.08/build/rtl_eeprom.o
CC [M]  /var/lib/dkms/r8168/8.045.08/build/rtltool.o
LD [M]  /var/lib/dkms/r8168/8.045.08/build/r8168.o
Building modules, stage 2.
MODPOST 1 modules
CC  /var/lib/dkms/r8168/8.045.08/build/r8168.mod.o
LD [M]  /var/lib/dkms/r8168/8.045.08/build/r8168.ko
  make: Leaving directory '/usr/src/linux-headers-4.15.0-11-generic'
  **

  So please, add libelf-dev as r8168-dkms dependency.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: r8168-dkms 8.045.08-2
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Mar  3 16:11:00 2018
  EcryptfsInUse: Yes
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: r8168
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1761131] Re: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output()

2018-04-04 Thread Daniel van Vugt 
The artful version of this bug is bug 1703668.

** Summary changed:

- gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output()
+ gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() from 
meta_monitor_get_vendor() from logical_monitor_find_monitor() from 
meta_input_settings_find_monitor() from update_device_display()

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

Title:
  gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output()
  from meta_monitor_get_vendor() from logical_monitor_find_monitor()
  from meta_input_settings_find_monitor() from update_device_display()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/dd87180eee24f496777a479c52715703596eb268

  ---

  happened on screensaver activation

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  4 11:13:09 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['keepaw...@jepfa.de']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Software.desktop', 
'org.gnome.Nautilus.desktop', 'google-chrome.desktop', 'firefox.desktop', 
'org.gnome.Terminal.desktop', 'jetbrains-phpstorm.desktop', 
'skypeforlinux.desktop', 'gnome-control-center.desktop', 
'org.gnome.gedit.desktop', 'dbeaver.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-03-13 (21 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fecaee5fe53 :   
jmpq   *0x88(%rax)
   PC (0x7fecaee5fe53) ok
   source "*0x88(%rax)" ok
   SP (0x7ffd4e598cd8) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_monitor_get_main_output () from 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   meta_monitor_get_vendor () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1753114] Re: DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel

2018-04-04 Thread Launchpad Bug Tracker 
*** This bug is a duplicate of bug 1760876 ***
https://bugs.launchpad.net/bugs/1760876

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

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

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

Title:
  DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y,
  please install libelf-dev, libelf-devel or elfutils-libelf-devel

Status in bcmwl package in Ubuntu:
  Confirmed
Status in dkms package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in r8168 package in Ubuntu:
  Confirmed

Bug description:
  Had the need to install r8168-dkms, but got a make.log error:

  
  DKMS make.log for r8168-8.045.08 for kernel 4.15.0-11-generic (x86_64)
  Sat Mar  3 16:08:17 CET 2018
  make: Entering directory '/usr/src/linux-headers-4.15.0-11-generic'
  Makefile:962: "Cannot use CONFIG_STACK_VALIDATION=y, please install 
libelf-dev, libelf-devel or elfutils-libelf-devel"
CC [M]  /var/lib/dkms/r8168/8.045.08/build/r8168_n.o
CC [M]  /var/lib/dkms/r8168/8.045.08/build/r8168_asf.o
CC [M]  /var/lib/dkms/r8168/8.045.08/build/rtl_eeprom.o
CC [M]  /var/lib/dkms/r8168/8.045.08/build/rtltool.o
LD [M]  /var/lib/dkms/r8168/8.045.08/build/r8168.o
Building modules, stage 2.
MODPOST 1 modules
CC  /var/lib/dkms/r8168/8.045.08/build/r8168.mod.o
LD [M]  /var/lib/dkms/r8168/8.045.08/build/r8168.ko
  make: Leaving directory '/usr/src/linux-headers-4.15.0-11-generic'
  

  so i have installed libelf-dev, and reinstalled r8168-dkms again. Next
  the make.log looks:

  ***
  DKMS make.log for r8168-8.045.08 for kernel 4.15.0-11-generic (x86_64)
  Sat Mar  3 16:15:11 CET 2018
  make: Entering directory '/usr/src/linux-headers-4.15.0-11-generic'
CC [M]  /var/lib/dkms/r8168/8.045.08/build/r8168_n.o
CC [M]  /var/lib/dkms/r8168/8.045.08/build/r8168_asf.o
CC [M]  /var/lib/dkms/r8168/8.045.08/build/rtl_eeprom.o
CC [M]  /var/lib/dkms/r8168/8.045.08/build/rtltool.o
LD [M]  /var/lib/dkms/r8168/8.045.08/build/r8168.o
Building modules, stage 2.
MODPOST 1 modules
CC  /var/lib/dkms/r8168/8.045.08/build/r8168.mod.o
LD [M]  /var/lib/dkms/r8168/8.045.08/build/r8168.ko
  make: Leaving directory '/usr/src/linux-headers-4.15.0-11-generic'
  **

  So please, add libelf-dev as r8168-dkms dependency.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: r8168-dkms 8.045.08-2
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Mar  3 16:11:00 2018
  EcryptfsInUse: Yes
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: r8168
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1761131] Re: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output()

2018-04-04 Thread Daniel van Vugt 
Also tracking in:
https://errors.ubuntu.com/problem/dd87180eee24f496777a479c52715703596eb268


** Information type changed from Private to Public

** Description changed:

+ https://errors.ubuntu.com/problem/dd87180eee24f496777a479c52715703596eb268
+ 
+ ---
+ 
  happened on screensaver activation
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  4 11:13:09 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
-  b'org.gnome.shell' b'enabled-extensions' b"['keepaw...@jepfa.de']"
-  b'org.gnome.shell' b'app-picker-view' b'uint32 1'
-  b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Software.desktop', 
'org.gnome.Nautilus.desktop', 'google-chrome.desktop', 'firefox.desktop', 
'org.gnome.Terminal.desktop', 'jetbrains-phpstorm.desktop', 
'skypeforlinux.desktop', 'gnome-control-center.desktop', 
'org.gnome.gedit.desktop', 'dbeaver.desktop']"
-  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
+  b'org.gnome.shell' b'enabled-extensions' b"['keepaw...@jepfa.de']"
+  b'org.gnome.shell' b'app-picker-view' b'uint32 1'
+  b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Software.desktop', 
'org.gnome.Nautilus.desktop', 'google-chrome.desktop', 'firefox.desktop', 
'org.gnome.Terminal.desktop', 'jetbrains-phpstorm.desktop', 
'skypeforlinux.desktop', 'gnome-control-center.desktop', 
'org.gnome.gedit.desktop', 'dbeaver.desktop']"
+  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-03-13 (21 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
-  LANGUAGE=en_GB:en
-  PATH=(custom, user)
-  XDG_RUNTIME_DIR=
-  LANG=en_GB.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_GB:en
+  PATH=(custom, user)
+  XDG_RUNTIME_DIR=
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
  SegvAnalysis:
-  Segfault happened at: 0x7fecaee5fe53 :   
jmpq   *0x88(%rax)
-  PC (0x7fecaee5fe53) ok
-  source "*0x88(%rax)" ok
-  SP (0x7ffd4e598cd8) ok
-  Reason could not be automatically determined.
+  Segfault happened at: 0x7fecaee5fe53 :   
jmpq   *0x88(%rax)
+  PC (0x7fecaee5fe53) ok
+  source "*0x88(%rax)" ok
+  SP (0x7ffd4e598cd8) ok
+  Reason could not be automatically determined.
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
-  meta_monitor_get_main_output () from 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
-  meta_monitor_get_vendor () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
-  ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
-  ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
-  ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
+  meta_monitor_get_main_output () from 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
+  meta_monitor_get_vendor () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
+  ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
+  ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
+  ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

Title:
  gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output()
  from meta_monitor_get_vendor() from logical_monitor_find_monitor()
  from meta_input_settings_find_monitor() from update_device_display()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/dd87180eee24f496777a479c52715703596eb268

  ---

  happened on screensaver activation

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  4 11:13:09 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['keepaw...@jepfa.de']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Software.desktop', 
'org.gnome.Nautilus.desktop', 'google-chrome.desktop', 'firefox.desktop', 
'org.gnome.Terminal.desktop', 'jetbrains-phpstorm.desktop', 
'skypeforlinux.desktop', 'gnome-control-center.desktop', 
'org.gnome.gedit.desktop', 'dbeaver.desktop']"
   b'org.

[Desktop-packages] [Bug 1761291] Re: nvidia-340 340.106-0ubuntu3: nvidia-340 kernel module failed to build at the upgrade

2018-04-04 Thread Daniel van Vugt 
*** This bug is a duplicate of bug 1760876 ***
https://bugs.launchpad.net/bugs/1760876

** This bug is no longer a duplicate of bug 1760983
   nvidia-kernel-source-390 390.42-0ubuntu1: nvidia kernel module failed to 
build [Makefile:976: "Cannot use CONFIG_STACK_VALIDATION=y, please install 
libelf-dev, libelf-devel or elfutils-libelf-devel"]
** This bug has been marked a duplicate of bug 1753114
   DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please 
install libelf-dev, libelf-devel or elfutils-libelf-devel

** This bug is no longer a duplicate of bug 1753114
   DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please 
install libelf-dev, libelf-devel or elfutils-libelf-devel
** This bug has been marked a duplicate of bug 1760876
   DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please 
install libelf-dev, libelf-devel or elfutils-libelf-devel

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

Title:
  nvidia-340 340.106-0ubuntu3: nvidia-340 kernel module failed to build
  at the upgrade

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

Bug description:
  Ubuntu Bionic Beaver (development branch) Release:18.04
  nvidia-340 340.106-0ubuntu3

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 340.106-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-14-generic
  Date: Wed Apr  4 22:54:20 2018
  InstallationDate: Installed on 2016-03-26 (739 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  PackageVersion: 340.106-0ubuntu3
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.106-0ubuntu3: nvidia-340 kernel module failed to build
  UpgradeStatus: Upgraded to bionic on 2018-03-09 (26 days ago)

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

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

[Desktop-packages] [Bug 1703668] Re: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() from meta_monitor_get_vendor() from meta_input_settings_find_logical_monitor()

2018-04-04 Thread Daniel van Vugt 
The bionic version of this bug is bug 1761131.

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

Title:
  gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output()
  from meta_monitor_get_vendor() from
  meta_input_settings_find_logical_monitor()

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

Bug description:
  https://errors.ubuntu.com/problem/bfdb8ffc57978ae7c23f78fdf44266fa56985fe9

  ---

  The only thing i recognize from the crash is the crash report.
  everything works as expected

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.12.0-6.7-generic 4.12.0
  Uname: Linux 4.12.0-6-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Jul  9 21:56:54 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2017-07-07 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170630)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fd10dc9e103 :   
jmpq   *0x88(%rax)
   PC (0x7fd10dc9e103) ok
   source "*0x88(%rax)" ok
   SP (0x7ffe42d50508) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_monitor_get_main_output () from 
/usr/lib/x86_64-linux-gnu/libmutter-0.so.0
   meta_monitor_get_vendor () from /usr/lib/x86_64-linux-gnu/libmutter-0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1760983] Re: nvidia-kernel-source-390 390.42-0ubuntu1: nvidia kernel module failed to build [Makefile:976: "Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, lib

2018-04-04 Thread Daniel van Vugt 
*** This bug is a duplicate of bug 1753114 ***
https://bugs.launchpad.net/bugs/1753114

** Also affects: nvidia-graphics-drivers-340 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: New => Confirmed

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

Title:
  nvidia-kernel-source-390 390.42-0ubuntu1: nvidia kernel module failed
  to build [Makefile:976: "Cannot use CONFIG_STACK_VALIDATION=y, please
  install libelf-dev, libelf-devel or elfutils-libelf-devel"]

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

Bug description:
  Report generated automatically by the system

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-kernel-source-390 390.42-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-14.15-generic 4.15.15
  Uname: Linux 4.15.0-14-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-14-generic
  Date: Tue Apr  3 17:25:35 2018
  Dependencies:
   
  InstallationDate: Installed on 2018-04-03 (0 days ago)
  InstallationMedia:
   
  PackageVersion: 390.42-0ubuntu1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No existe el archivo o el directorio: "/root/Error: 
command ['which', 'python'] failed with exit code 1:": "/root/Error: command 
['which', 'python'] failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: nvidia-graphics-drivers-390
  Title: nvidia-kernel-source-390 390.42-0ubuntu1: nvidia kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1745355] Re: gnome-software does not show the right version of a snap when open with xdg-open

2018-04-04 Thread hackel 
Interestingly, for a snap installed with --edge, gnome-software is
showing the stable version installed.  This integration is clearly
rather broken.

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

Title:
  gnome-software does not show the right version of a snap when open
  with xdg-open

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  With spotify installed on my system as a snap, I've the following versions:
  tracking:stable
  installed:   1.0.70.399.g5ffabd56-26 (5) 167MB -
  refreshed:   2017-12-20 16:00:00 +0100 CET
  channels:
    stable:1.0.70.399.g5ffabd56-26 (5) 167MB -
    candidate: 1.0.72.117.g6bd7cc73-35 (6) 170MB -
    beta:  ↑
    edge:  1.0.72.117.g6bd7cc73-35 (6) 170MB -

  If I start gnome-software, search for spotify and go to the details
  page, the version is 1.0.70.399.g5ffabd56-26 (which is expected)

  But if I open gnome-software with xdg-open ( xdg-open snap://spotify )
  which is the method used from spotify.com, the version of the snap
  displayed is 1.0.72.117.g6bd7cc73-35 (cf screenshot)

  It should be the version from stable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.26.3-2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 25 12:01:01 2018
  InstallationDate: Installed on 2013-09-03 (1604 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.26.3-2ubuntu1
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.3-2ubuntu1
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1761358] Re: /usr/bin/gnome-shell:11:meta_monitor_get_main_output:meta_monitor_get_vendor:logical_monitor_find_monitor:meta_input_settings_find_monitor:update_device_display

2018-04-04 Thread Daniel van Vugt 
*** This bug is a duplicate of bug 1761131 ***
https://bugs.launchpad.net/bugs/1761131

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

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

Title:
  /usr/bin/gnome-
  
shell:11:meta_monitor_get_main_output:meta_monitor_get_vendor:logical_monitor_find_monitor:meta_input_settings_find_monitor:update_device_display

Status in gnome-shell package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1761291] Re: nvidia-340 340.106-0ubuntu3: nvidia-340 kernel module failed to build at the upgrade

2018-04-04 Thread Daniel van Vugt 
*** This bug is a duplicate of bug 1753114 ***
https://bugs.launchpad.net/bugs/1753114

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


** This bug has been marked a duplicate of bug 1760983
   nvidia-kernel-source-390 390.42-0ubuntu1: nvidia kernel module failed to 
build [Makefile:976: "Cannot use CONFIG_STACK_VALIDATION=y, please install 
libelf-dev, libelf-devel or elfutils-libelf-devel"]

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

Title:
  nvidia-340 340.106-0ubuntu3: nvidia-340 kernel module failed to build
  at the upgrade

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

Bug description:
  Ubuntu Bionic Beaver (development branch) Release:18.04
  nvidia-340 340.106-0ubuntu3

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 340.106-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-14-generic
  Date: Wed Apr  4 22:54:20 2018
  InstallationDate: Installed on 2016-03-26 (739 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  PackageVersion: 340.106-0ubuntu3
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.106-0ubuntu3: nvidia-340 kernel module failed to build
  UpgradeStatus: Upgraded to bionic on 2018-03-09 (26 days ago)

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

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

[Desktop-packages] [Bug 1761358] [NEW] /usr/bin/gnome-shell:11:meta_monitor_get_main_output:meta_monitor_get_vendor:logical_monitor_find_monitor:meta_input_settings_find_monitor:update_device_display

2018-04-04 Thread errors.ubuntu.com bug bridge 
*** This bug is a duplicate of bug 1761131 ***
https://bugs.launchpad.net/bugs/1761131

Public bug reported:

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

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


** Tags: bionic

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

Title:
  /usr/bin/gnome-
  
shell:11:meta_monitor_get_main_output:meta_monitor_get_vendor:logical_monitor_find_monitor:meta_input_settings_find_monitor:update_device_display

Status in gnome-shell package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1760934] Re: Sound not working on HP x2 10-p030nl - Realtek rt5640

2018-04-04 Thread Daniel van Vugt 
If pulseaudio isn't running then that's the main issue. It's hard to
declare a bug is in a program when that program isn't even running yet.

Please try:

1. Run 'journalctl -b > journal.txt' and attach the resulting file here.

2. Run 'pulseaudio -vv' and paste the output here.

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

Title:
  Sound not working on HP x2 10-p030nl - Realtek rt5640

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Audio doesn't work on every kernel I tried. I also used this
  https://github.com/plbossart/UCM, but this results in a pulseaudio
  crash. See this for more information:
  https://github.com/plbossart/UCM/issues/27

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  Uname: Linux 4.16.0-rc6+ x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer', 
'/dev/sequencer2', '/dev/sequencer'] failed with exit code 1:
  CurrentDesktop: KDE
  Date: Tue Apr  3 19:19:35 2018
  InstallationDate: Installed on 2018-03-27 (6 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827C
  dmi.board.vendor: HP
  dmi.board.version: 93.23
  dmi.chassis.type: 32
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.30:bd10/25/2017:svnHP:pnHPx2Detachable10-p0XX:pvr:rvnHP:rn827C:rvr93.23:cvnHP:ct32:cvrChassisVersion:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP x2 Detachable 10-p0XX
  dmi.sys.vendor: HP

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

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

[Desktop-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

2018-04-04 Thread Daniel van Vugt 
*** This bug is a duplicate of bug 1710637 ***
https://bugs.launchpad.net/bugs/1710637

Takis,

The fix for bug 1710637 is only in Ubuntu 17.10 and later, so please try
17.10 or 18.04.

Please also open a new bug if you think you have a new issue.

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I'm used to using alt+left/right arrow to navigate back and forward in
  web browsers and elsewhere (nautilus)...  But on this fresh install of
  Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty
  consoles (the ctrl+alt+f1 ones).  But it's not listed as one of the
  shortcuts in the "keyboard" menu, so I don't know how to disable it...

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

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

[Desktop-packages] [Bug 1761346] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

2018-04-04 Thread Apport retracing service 
** Tags removed: need-duplicate-check

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Thu Apr  5 08:17:49 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-UEKgyx/134-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Tidak ada berkas atau direktori seperti itu: "/root/Error: 
command ['which', 'python'] failed with exit code 1:": "/root/Error: command 
['which', 'python'] failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1761346/+subscriptions

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

[Desktop-packages] [Bug 1761346] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from o

2018-04-04 Thread asep 
Public bug reported:

package libsane1 1.0.27-1~experimental2ubuntu2.1 failed

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Thu Apr  5 08:17:49 2018
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental2ubuntu2.1
 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-UEKgyx/134-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
  trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Tidak ada berkas atau direktori seperti itu: "/root/Error: 
command ['which', 'python'] failed with exit code 1:": "/root/Error: command 
['which', 'python'] failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful package-conflict

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Thu Apr  5 08:17:49 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-UEKgyx/134-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Tidak ada berkas atau direktori seperti itu: "/root/Error: 
command ['which', 'python'] failed with exit code 1:": "/root/Error: command 
['which', 'python'] failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1761346/+subscriptions

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

[Desktop-packages] [Bug 1177267] Re: Inconsistency in passwords strength assessment

2018-04-04 Thread Simon Quigley 
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect https://api.launchpad.net/1.0/bugs/1177267

and any other logs that are relevant for this particular issue.

** Changed in: ubuntu-gnome
   Status: New => Incomplete

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

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

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

Title:
  Inconsistency in passwords strength assessment

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

Bug description:
  The password strength assessment is inconsistent between Ubiquity and
  the Gnome "User Accounts" applet.

  For example, I use a pretty short but complicated password:
  - Ubiquity evaluates this password as "Good password" or "strong" (don't 
really remember)
  - Gnome "User Accounts" applet evaluates this same password as "weak".

  Ubuntu Gnome 13.04 + Gnome 3 PPA.

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

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

[Desktop-packages] [Bug 1187981] Re: symbol conflicts in libtimezonemap1

2018-04-04 Thread Simon Quigley 
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect https://api.launchpad.net/1.0/bugs/1187981

and any other logs that are relevant for this particular issue.

** Changed in: gnome-control-center
   Status: Confirmed => Incomplete

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

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

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

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

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

Title:
  symbol conflicts in libtimezonemap1

Status in gnome-control-center:
  Incomplete
Status in gnome-control-center package in Ubuntu:
  Incomplete
Status in libtimezonemap package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Incomplete
Status in unity-control-center package in Ubuntu:
  Incomplete

Bug description:
  In gnome-control-center 3.8 all built in panels are statically linked.
  When the indicator-datetime panel loads it is picking up the symbols
  from the gnome datetime panel rather than the ones in libtimezonemap1,
  causing g-c-c to segfault.

  All public symbols in libtimezonemap1 need to renamed to avoid
  conflict. Likewise this might apply to any other g-c-c plugins that
  have code cut+paste from the built in gnome panels.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-datetime 12.10.3daily13.05.06.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3
  Uname: Linux 3.9.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  Date: Thu Jun  6 12:35:40 2013
  InstallationDate: Installed on 2012-09-23 (256 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha 
amd64(20120922)
  MarkForUpload: True
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1066284] Re: Add keyboard layout button disabled in default live session

2018-04-04 Thread Simon Quigley 
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect https://api.launchpad.net/1.0/bugs/1066284

and any other logs that are relevant for this particular issue.

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

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

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

Title:
  Add keyboard layout button disabled in default live session

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

Bug description:
  When booting the quantal iso testing images and selecting Try Ubuntu
  without changing the language or keyboard layout, it is impossible to
  add keyboard layouts. In system settings -> keyboard layout there are
  only four English layouts listed and the + button that should add a
  layout is grayed out.

  When selecting a non-English layout by pressing F3 during boot the
  button is usable.

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

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

[Desktop-packages] [Bug 1761344] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

2018-04-04 Thread Apport retracing service 
** Tags removed: need-duplicate-check

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I do not know what happened, lubuntu caught an error upon reboot. It
  may be good to know I am booting from a hard drive that is connected
  to usb through usb to sata adapter.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Tue Apr  3 11:18:07 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-yEjTeS/133-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2017-10-28 (158 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1761344/+subscriptions

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

[Desktop-packages] [Bug 1761344] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from o

2018-04-04 Thread Venancio da Silva 
Public bug reported:

I do not know what happened, lubuntu caught an error upon reboot. It may
be good to know I am booting from a hard drive that is connected to usb
through usb to sata adapter.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Tue Apr  3 11:18:07 2018
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental2ubuntu2.1
 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-yEjTeS/133-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
  trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
InstallationDate: Installed on 2017-10-28 (158 days ago)
InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful package-conflict

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I do not know what happened, lubuntu caught an error upon reboot. It
  may be good to know I am booting from a hard drive that is connected
  to usb through usb to sata adapter.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Tue Apr  3 11:18:07 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-yEjTeS/133-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2017-10-28 (158 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1761344/+subscriptions

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

[Desktop-packages] [Bug 1761121] Re: Latest intel ucode update halts my system during boot to graphic session

2018-04-04 Thread Aalok Sathe 
*** This bug is a duplicate of bug 1759920 ***
https://bugs.launchpad.net/bugs/1759920

** This bug has been marked a duplicate of bug 1759920
   intel-microcode 3.20180312.0 causes lockup at login screen(w/ 
linux-image-4.13.0-37-generic)

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

Title:
  Latest intel ucode update halts my system during boot to graphic
  session

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  It seems that this 
  iucode_tool -lS /lib/firmware/intel-ucode/
  iucode_tool: system has processor(s) with signature 0x000306a9
  selected microcodes:
  001: sig 0x000306a9, pf mask 0x12, 2018-02-07, rev 0x001f, size 13312
  microcode update prevents me to boot to graphic session on any(4.13.0.38[37]) 
kernel.
  I can successfully boot to the recovery console.
  In some of failed attempts i got "NMI deadlock detected on CPU0,1,3 in mkswap"
  I guess nvidia-384 has some issues and conflicts with updated microcode.
  I have to disable microcode update with 
IUCODE_TOOL_EXTRA_OPTIONS="--date-after=2018-02-07" to get my unity session 
back.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  BootLog:
   lvmetad is not active yet, using direct activation during sysinit
   /dev/mapper/lmvg-ubunturoot: clean, 421309/1310720 files, 3715643/5242880 
blocks
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr  4 12:39:37 2018
  DistUpgraded: 2016-04-19 13:48:02,030 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Не удалось выполнить 
процесс-потомок «./xorg_fix_proprietary.py» (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GT 640] [10de:0fc1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GK107 [GeForce GT 640] [1458:353e]
  InstallationDate: Installed on 2012-09-26 (2015 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=/dev/mapper/lmvg-ubunturoot ro nouveau.modeset=0 
rd.driver.blacklist=nouveau video=vesa:off nvidia_drm.modeset=1 zswap.enabled=0 
quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-19 (714 days ago)
  dmi.bios.date: 10/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-DS2 DVI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/12/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-DS2DVI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-

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

2018-04-04 Thread Apport retracing service 
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450

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 #1748450, 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/1761339/+attachment/5102070/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Not aware of any cause

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-14.15-generic 4.15.15
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Apr  5 09:14:19 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-23 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1256201] Re: Installation xubuntu crash

2018-04-04 Thread Simon Quigley 
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. We are sorry that we do not always have the capacity to look at all 
reported bugs in a timely manner. There have been many changes in Ubuntu since 
that time you reported the bug and your problem may have been fixed with some 
of the updates. It would help us a lot if you could test it on a currently 
supported Ubuntu version. If you test it and it is still an issue, kindly 
upload the updated logs by running only once:
apport-collect 1256201

and any other logs that are relevant for this particular issue.

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

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

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

Title:
  Installation xubuntu crash

Status in network-manager package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Incomplete

Bug description:
  Failed installation ... sistem installation crash

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: ubiquity 2.15.26
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.336ubuntu1
  Date: Fri Nov 29 06:29:12 2013
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash -- debian-installer/language=it 
keyboard-configuration/layoutcode?=it
  LiveMediaBuild: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=it_IT.UTF-8
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1761338] [NEW] Login screen upside down(reversed)

2018-04-04 Thread roussel geoffrey 
Public bug reported:

Ubuntu 17.10, Nvidia drivers installed (official package nvidia-384).
Computer: HP laptop: HP 14-008nf (with graphics: integrated + NVidia Geforce 
940mx)

Sometimes when i reboot the Ubuntu login screen is reversed, all the
screen is upside down, then just rebooting without changing anything and
it's back to normal...but not all the time (sometimes after booting to
Windows also, cause i have dual boot)

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
 GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr  5 01:55:57 2018
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.13.0-21-generic, x86_64: installed
 bbswitch, 0.8, 4.13.0-37-generic, x86_64: installed
 nvidia-384, 384.111, 4.13.0-21-generic, x86_64: installed
 nvidia-384, 384.111, 4.13.0-37-generic, x86_64: installed
 virtualbox, 5.1.34, 4.13.0-37-generic, x86_64: installed
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 520 [103c:820a]
   Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:820a]
InstallationDate: Installed on 2018-03-16 (19 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. 
 Bus 001 Device 002: ID 05c8:038e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Pavilion Notebook
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic.efi.signed 
root=UUID=ce30d1fb-9d99-4019-8b24-6cd1462d771d ro quiet splash pci=noaer 
vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.08
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 820A
dmi.board.vendor: HP
dmi.board.version: 82.26
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.08:bd07/04/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn820A:rvr82.26:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
dmi.product.name: HP Pavilion Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
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 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful ubuntu

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

Title:
  Login screen upside down(reversed)

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10, Nvidia drivers installed (official package nvidia-384).
  Computer: HP laptop: HP 14-008nf (with graphics: integrated + NVidia Geforce 
940mx)

  Sometimes when i reboot the Ubuntu login screen is reversed, all the
  screen is upside down, then just rebooting without changing anything
  and it's back to normal...but not all the time (sometimes after
  booting to Windows also, cause i have dual boot)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:

[Desktop-packages] [Bug 1761278] Re: Thunderbird time zone data has not been updated since March 2017

2018-04-04 Thread Bug Watch Updater 
** Changed in: thunderbird
   Status: Unknown => Fix Released

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

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

Title:
  Thunderbird time zone data has not been updated since March 2017

Status in Mozilla Thunderbird:
  Fix Released
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Thunderbird maintains its own copy of the timezone data, which in
  Bionic has not been updated since March 2017. This has been fixed
  upstream starting with 52.7.

  As a result events may not display at the correct time; for example,
  events sent with the timezone Africa/Khartoum will display offset by
  one hour.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:52.6.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 1819 F pulseaudio
   /dev/snd/controlC0:  vectro 1819 F pulseaudio
  BuildID: 20180131200234
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Wed Apr  4 15:01:38 2018
  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 2018-03-23 (12 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  IpRoute:
   default via 192.168.0.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.7 metric 600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-7b6eaa7d-0844-455b-a589-5a9030180404
  PrefSources:
   prefs.js
   
/usr/lib/thunderbird/extensions/{a62ef8ec-5fdc-40c2-873c-223b8a6925cc}/defaults/preferences/preferences.js
   
/usr/lib/thunderbird/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
  Profiles: Profile0 (Default) - LastVersion=52.6.0/20180131200234 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1761313] Re: installer crashed

2018-04-04 Thread Simon Quigley 
** Package changed: ubiquity (Ubuntu) => appstream (Ubuntu)

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

Title:
  installer crashed

Status in appstream package in Ubuntu:
  New

Bug description:
  error copying files but cd check is ok

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubiquity 2.21.63 [modified: 
lib/partman/automatically_partition/question]
  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
  CasperVersion: 1.376
  Date: Wed Apr  4 22:24:39 2018
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  LiveMediaBuild: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1761299] Re: telepathy-idle crashed with SIGSEGV in tp_handle_inspect()

2018-04-04 Thread Bug Watch Updater 
** Changed in: telepathy-idle
   Status: Unknown => Confirmed

** Changed in: telepathy-idle
   Importance: Unknown => Medium

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

Title:
  telepathy-idle crashed with SIGSEGV in tp_handle_inspect()

Status in telepathy-idle:
  Confirmed
Status in telepathy-idle package in Ubuntu:
  Invalid

Bug description:
  Hello,

  I do not know why that happened...

  Regards,
  -
  Cristian Aravena Romero (caravena)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: telepathy-idle 0.2.0-2
  Uname: Linux 4.16.0-041600-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Wed Apr  4 17:25:06 2018
  ExecutablePath: /usr/lib/telepathy/telepathy-idle
  InstallationDate: Installed on 2017-10-13 (173 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: /usr/lib/telepathy/telepathy-idle
  SegvAnalysis:
   Segfault happened at: 0x7f20185ea5e0 : mov
(%rbx),%rdi
   PC (0x7f20185ea5e0) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: telepathy-idle
  StacktraceTop:
   tp_handle_inspect () at /usr/lib/x86_64-linux-gnu/libtelepathy-glib.so.0
   ()
   ()
   ()
   ()
  Title: telepathy-idle crashed with SIGSEGV in tp_handle_inspect()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/telepathy-idle/+bug/1761299/+subscriptions

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

[Desktop-packages] [Bug 1761313] [NEW] installer crashed

2018-04-04 Thread Launchpad Bug Tracker 
You have been subscribed to a public bug:

error copying files but cd check is ok

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63 [modified: 
lib/partman/automatically_partition/question]
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
CasperVersion: 1.376
Date: Wed Apr  4 22:24:39 2018
InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
LiveMediaBuild: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug ubiquity-2.21.63 xenial xubuntu
-- 
installer crashed
https://bugs.launchpad.net/bugs/1761313
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to appstream 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 1756098] Re: Potential cache upgrade issue in 3.28 results in unable to install flatpakref due to remote already existing

2018-04-04 Thread Andrew Hayzen 
I've not yet been able to reproduce this yet, but while investigating
I've found that the cache folder for gnome-software (and therefore the
gnome software flatpak plugin) has changed from 17.10 to 18.04 - so it
might not be an issue for "real" users upgrading from 17.10?

Eg the flatpak plugin cache folder has changed in the following ways for me:
17.10 ~/.cache/gnome-software/3.26/flatpak
18.04 ~/.cache/gnome-software/flatpak

Although this does raise, why is the cache folder not ~/.cache/gnome-
software/3.28 ? What will happen with 3.30 ?

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

Title:
  Potential cache upgrade issue in 3.28 results in unable to install
  flatpakref due to remote already existing

Status in gnome-software package in Ubuntu:
  New

Bug description:
  What happened
  1) Open your browser, navigate to flathub.org, find an app and click to 
install it
  2) Open the resulting flatpakref in gnome-software.
  3) Notice how the app info is correctly displayed
  4) Try to click install, notice how now you get "cannot install source from 
https://dl.flathub.org/repo/: flatpak source flathub already exists"

  Note that I have 3.27.92 installed first and then upgraded to 3.28.
  After removing all installed apps and remotes I have not been able to
  reproduce the issue. It has been suggested that it is an issue in
  cache cleanup between versions - probably within ~/.cache/gnome-
  software/flatpak/

  Furthermore note the actual issue was likely fixed in 3.28, so this is
  upgrades from lower than 3.28 to 3.28 which will be affected by cache
  upgrade issues.

  I have reported the bug upstream here https://gitlab.gnome.org/GNOME
  /gnome-software/issues/328

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

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

[Desktop-packages] [Bug 1761310] Re: transmission-gtk crashed with SIGSEGV in __GI___pthread_mutex_lock()

2018-04-04 Thread Apport retracing service 
*** This bug is a duplicate of bug 1300619 ***
https://bugs.launchpad.net/bugs/1300619

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 #1300619, 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/1761310/+attachment/5101962/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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 transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1761310

Title:
  transmission-gtk crashed with SIGSEGV in __GI___pthread_mutex_lock()

Status in transmission package in Ubuntu:
  New

Bug description:
  right after opening from magnet, attempting to cancel the download and
  restart app, as the disk has not been mounted yet

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: transmission-gtk 2.92-3ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  4 23:00:18 2018
  ExecutablePath: /usr/bin/transmission-gtk
  InstallationDate: Installed on 2015-05-01 (1069 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: transmission-gtk 
magnet:?xt=urn:btih:1d708e632d36f7c5378689e6733f1a2404bddc5a&dn=Legion.S02E01.HDTV.x264-SVA%5Bettv%5D&tr=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969&tr=udp%3A%2F%2Fzer0day.ch%3A1337&tr=udp%3A%2F%2Fopen.demonii.com%3A1337&tr=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr=udp%3A%2F%2Fexodus.desync.com%3A6969
  SegvAnalysis:
   Segfault happened at: 0x7efe28269fa0 <__GI___pthread_mutex_lock>:mov
0x10(%rdi),%eax
   PC (0x7efe28269fa0) ok
   source "0x10(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: transmission
  StacktraceTop:
   __GI___pthread_mutex_lock (mutex=0x8) at ../nptl/pthread_mutex_lock.c:65
   tr_lockLock ()
   tr_torrentRecheckCompleteness ()
   ?? ()
   ?? ()
  Title: transmission-gtk crashed with SIGSEGV in __GI___pthread_mutex_lock()
  UpgradeStatus: Upgraded to bionic on 2018-04-04 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1761299] Re: telepathy-idle crashed with SIGSEGV in tp_handle_inspect()

2018-04-04 Thread Cristian Aravena Romero 
** Information type changed from Private to Public

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

** Also affects: telepathy-idle via
   https://bugs.freedesktop.org/show_bug.cgi?id=105890
   Importance: Unknown
   Status: Unknown

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

Title:
  telepathy-idle crashed with SIGSEGV in tp_handle_inspect()

Status in telepathy-idle:
  Unknown
Status in telepathy-idle package in Ubuntu:
  Invalid

Bug description:
  Hello,

  I do not know why that happened...

  Regards,
  -
  Cristian Aravena Romero (caravena)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: telepathy-idle 0.2.0-2
  Uname: Linux 4.16.0-041600-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Wed Apr  4 17:25:06 2018
  ExecutablePath: /usr/lib/telepathy/telepathy-idle
  InstallationDate: Installed on 2017-10-13 (173 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: /usr/lib/telepathy/telepathy-idle
  SegvAnalysis:
   Segfault happened at: 0x7f20185ea5e0 : mov
(%rbx),%rdi
   PC (0x7f20185ea5e0) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: telepathy-idle
  StacktraceTop:
   tp_handle_inspect () at /usr/lib/x86_64-linux-gnu/libtelepathy-glib.so.0
   ()
   ()
   ()
   ()
  Title: telepathy-idle crashed with SIGSEGV in tp_handle_inspect()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/telepathy-idle/+bug/1761299/+subscriptions

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

[Desktop-packages] [Bug 1761309] Re: gnome-calendar crashed with SIGSEGV in gtk_image_clear()

2018-04-04 Thread Apport retracing service 
*** This bug is a duplicate of bug 1754202 ***
https://bugs.launchpad.net/bugs/1754202

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 #1754202, 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/1761309/+attachment/5101952/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1754202
   gnome-calendar crashed with SIGSEGV in gtk_image_reset()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-calendar crashed with SIGSEGV in gtk_image_clear()

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  hung when trying to add google

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-calendar 3.28.0-1
  ProcVersionSignature: Ubuntu 4.15.0-14.15-generic 4.15.15
  Uname: Linux 4.15.0-14-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  4 16:49:10 2018
  ExecutablePath: /usr/bin/gnome-calendar
  InstallationDate: Installed on 2018-04-01 (2 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f363487c667 :mov
0x28(%rdi),%rbp
   PC (0x7f363487c667) ok
   source "0x28(%rdi)" (0x0028) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-calendar
  StacktraceTop:
   gtk_image_clear () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-calendar crashed with SIGSEGV in gtk_image_clear()
  UpgradeStatus: Upgraded to bionic on 2018-04-04 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1758647] Re: ubiquity doesn't preselect the right default keyboard layout

2018-04-04 Thread Gunnar Hjalmarsson 
I'm able to reproduce Sebastien's success by following the steps in
comment #9.

At the same time I'm able to reproduce the failure as reported by both
Pjotr12345 and myself via these steps:

- boot the iso
- patiently wait, without pressing any key, until Ubiquity boots
  [yes Seb, I can be patient sometimes]
-> Ubiquity is booted with English preselected (see attached image)
- Change to Nederlands
-> The display language changes instantly
- Click the "ubuntu installieren" button
-> The basic English (US) layout is selected

So it seems like the language must be selected before Ubiquity boots to
get a reasonably guessed preselected layout.

But how would the user know that pressing a key initially makes a
difference when they are not told so? The official installation
instruction here:

https://tutorials.ubuntu.com/tutorial/tutorial-install-ubuntu-desktop

does not mention the syslinux menu either.

The desired behavior is reasonably that when you change the language on
Ubiquity's welcome screen, the preselected layout should be changed to
match the selected language (just as the display language is).

Btw, with the press-a-key approach, "Try Ubuntu" enters a session with
the correct layout in /etc/default/keyboard. So yes, this is probably a
pure ubiquity bug, not affecting gnome-settings-daemon.

** Attachment added: "ubiquity-welcome.jpeg"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1758647/+attachment/5101934/+files/ubiquity-welcome.jpeg

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

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

** Changed in: gnome-settings-daemon (Ubuntu Bionic)
 Assignee: Sebastien Bacher (seb128) => (unassigned)

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

Title:
  ubiquity doesn't preselect the right default keyboard layout

Status in gnome-settings-daemon package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon source package in Bionic:
  Invalid
Status in ubiquity source package in Bionic:
  Confirmed

Bug description:
  In Ubuntu, Xubuntu and Lubuntu 18.04 Bionic Beaver, daily builds of
  March 25, the right default keymap isn't preselected when you select
  "Nederlands" (i.e. Dutch) as language for the installation.

  It's now "English, US" but should be:
  "English (US) - English (US, intl., with dead keys)".

  Or, in other words, it should be:
  XKBLAYOUT="us"
  XKBVARIANT="intl"

  (additional remark in order to prevent any misunderstandings: the
  original Dutch keyboard (nl) has completely disappeared long ago, so
  all keyboards sold in the Netherlands have US keyboards which need the
  "intl" xkbvariant with dead keys, in order to be able to type accents)

  This is a regression, at least compared with Ubuntu 16.04 and earlier
  (I don't know about 16.10, 17.04 and 17.10).

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

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

[Desktop-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

2018-04-04 Thread Takis Issaris 
*** This bug is a duplicate of bug 1710637 ***
https://bugs.launchpad.net/bugs/1710637

I am not sure if this is a duplicate, as I'm only experiencing the bug
with Alt+left/right. I'm on 16.04.4 LTS and started experiencing this
very recently after an update and reboot probably. I think that I
noticed this in fact as of today. I am not sure, as initially I thought
I had accidentally pressed a wrong key combo, but after 10 times,
noticed that it was the key combo for going back in my browser which
triggered it.

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I'm used to using alt+left/right arrow to navigate back and forward in
  web browsers and elsewhere (nautilus)...  But on this fresh install of
  Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty
  consoles (the ctrl+alt+f1 ones).  But it's not listed as one of the
  shortcuts in the "keyboard" menu, so I don't know how to disable it...

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

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

[Desktop-packages] [Bug 1761003] Re: Bionic Beaver - not able to connect to WPA Enterprise EAP-TLS

2018-04-04 Thread Kitsab 
Hello,

thank you fro taking care about this, I created a bug report at gnome
bugzilla as requested:

https://bugzilla.gnome.org/show_bug.cgi?id=794988

Additional Information:
Maybe the bug reporting tool reported a wrong package, eventually the 
wpa-supplicant package is causing this issue (not sure).
I've recognized the status info is possibly wrong:UpgradeStatus: No upgrade log 
present (probably fresh install)
I performed an upgrade from 16.04, and 16.04. was upgraded from 14.04, (and I 
think 14.04 from 12.04 - not sure)

Best regards

Kitsab

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

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

Title:
  Bionic Beaver - not able to connect to WPA Enterprise EAP-TLS

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hello,

  since update to Bionic Beaver I can't connect to my WPA2-Entertrise EAP TLS 
network. Running Freeradius 2.29 on a DDWRT router. In 16.04 it worked, in the 
dual boot Windows 10 environment it is still working with the same certificates.
  It is a hidden network, adding it by "connect to a hidden network" entering 
SSID, UserID, ca.pem as CA cert, user cert xxx.p12 file and user certificate 
password.
  Tried a lot not getting it working. The password entry dialog for the network 
is always popping up upon connection trials. The password is for sure the 
correct one, checked it very often.
  If I'm able to I'll attach a syslog and kern.log of error occurense.

  Thanks for investigation and inputs.

  Best regards

  Kitsab

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr  3 23:52:23 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2015-02-14 (1144 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland

2018-04-04 Thread Takis Issaris 
I'm experiencing the same thing on Ubuntu Xenial. I initially thought it
was only on using Alt+left/right, but did a Alt+F4 to close a window
just now, and the window did close but it switched to VT4 as well. I
think it started happening today on my system.

Linux 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Input falls through to gdm3 and terminates the session on Ctrl+C after
  udevadm trigger is executed under wayland

Status in Snappy:
  Won't Fix
Status in console-setup package in Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in console-setup source package in Trusty:
  New
Status in gdm3 source package in Trusty:
  New
Status in gnome-shell source package in Trusty:
  New
Status in mutter source package in Trusty:
  New
Status in systemd source package in Trusty:
  New
Status in console-setup source package in Xenial:
  New
Status in gdm3 source package in Xenial:
  New
Status in gnome-shell source package in Xenial:
  New
Status in mutter source package in Xenial:
  New
Status in systemd source package in Xenial:
  New

Bug description:
  = Test Cases =

  Test Case 1:
  - Login under Wayland (session Ubuntu)
  - Open a terminal
  - snap install gimp
  - Wait until installation finishes successfully
  - In the terminal window press CTRL+C

  Result:
  - Expected: ^C is displayed in the terminal and the prompt is at the start of 
a new line
  - Actual: The session is terminated and the login screen is displayed

  Test Case 2:
  - Login under Wayland (session Ubuntu)
  - Open a terminal and type the following command:
    $ sudo udevadm trigger
  - In the terminal window press CTRL+C

  Result
  - Expected: ^C is displayed in the terminal and the prompt is at the start of 
a new line
  - Actual: The session is terminated and the login screen is displayed

  = Original Description =

  Multiple times a day I find myself without a session after hitting
  Ctrl+C in a terminal, it seems the input falls through the
  Ubuntu/GNOME session and to gdm, which itself decides to terminate.

  Even worse, when this happens, you can briefly see your login password
  in plaintext in the virtual terminal. You can see the password however
  long you want if you stop the gdm service when this happens.

  I don't have a good way to reproduce, but it seems locking the session
  with a keyboard shortcut, subsequently unlocking it, maybe suspending,
  at some point brings this behaviour into the picture, until the
  session dies with a Ctrl+C.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Aug 14 15:54:34 2017
  InstallationDate: Installed on 2016-05-06 (464 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago)

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

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

[Desktop-packages] [Bug 1761291] [NEW] nvidia-340 340.106-0ubuntu3: nvidia-340 kernel module failed to build at the upgrade

2018-04-04 Thread Viktor Mishkovskyi 
Public bug reported:

Ubuntu Bionic Beaver (development branch) Release:  18.04
nvidia-340 340.106-0ubuntu3

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: nvidia-340 340.106-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
DKMSKernelVersion: 4.15.0-14-generic
Date: Wed Apr  4 22:54:20 2018
InstallationDate: Installed on 2016-03-26 (739 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
PackageVersion: 340.106-0ubuntu3
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt  1.6~beta1
SourcePackage: nvidia-graphics-drivers-340
Title: nvidia-340 340.106-0ubuntu3: nvidia-340 kernel module failed to build
UpgradeStatus: Upgraded to bionic on 2018-03-09 (26 days ago)

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic third-party-packages

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

Title:
  nvidia-340 340.106-0ubuntu3: nvidia-340 kernel module failed to build
  at the upgrade

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

Bug description:
  Ubuntu Bionic Beaver (development branch) Release:18.04
  nvidia-340 340.106-0ubuntu3

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 340.106-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-14-generic
  Date: Wed Apr  4 22:54:20 2018
  InstallationDate: Installed on 2016-03-26 (739 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  PackageVersion: 340.106-0ubuntu3
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.106-0ubuntu3: nvidia-340 kernel module failed to build
  UpgradeStatus: Upgraded to bionic on 2018-03-09 (26 days ago)

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

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

[Desktop-packages] [Bug 1726919] Re: Ubuntu 17.10 desktops corrupted

2018-04-04 Thread peterzay 
My test machine that had 17.10 has been overwritten with 18.04 beta.

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

Title:
  Ubuntu 17.10 desktops corrupted

Status in nautilus package in Ubuntu:
  New

Bug description:
  The following users were installed:

  admin from DVD install (login with X option)
  user id 1001 (login with default Ubuntu option)
  user id 1002 (login with default Ubuntu option)
  user id 1003 (login with default Ubuntu option)

  Desktops for admin and user 1001 are ok.

  Desktops for users 1002 and 1003 are corrupted.

  See attached screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  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 Oct 24 11:41:36 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/nautilus-desktop
  InstallationDate: Installed on 2017-10-21 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1761290] [NEW] laptop battery empty, laptop shutdown suddently, simple-scan was running

2018-04-04 Thread Jeremie 
Public bug reported:

laptop battery empty,  laptop shutdown suddently, simple-scan was running
launching simple-scan with terminal :
"segmentation error (core dumped)"

thanks in advance ;-)
JG

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: simple-scan 3.20.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic i686
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
CurrentDesktop: Unity
Date: Wed Apr  4 21:50:01 2018
MachineType: Hewlett-Packard HP ProBook 4310s
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=6aaabc63-1518-452a-a01c-cd9a6f22e385 ro quiet splash vt.handoff=7
SimpleScanLog:
 
SourcePackage: simple-scan
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/26/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PHT Ver. F.0D
dmi.board.name: 7015
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 14.10
dmi.chassis.asset.tag: CNU9475DHV
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PHTVer.F.0D:bd01/26/2010:svnHewlett-Packard:pnHPProBook4310s:pvrF.0D:rvnHewlett-Packard:rn7015:rvrKBCVersion14.10:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 4310s
dmi.product.version: F.0D
dmi.sys.vendor: Hewlett-Packard

** Affects: simple-scan (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 xenial

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

Title:
  laptop battery empty,  laptop shutdown suddently, simple-scan was
  running

Status in simple-scan package in Ubuntu:
  New

Bug description:
  laptop battery empty,  laptop shutdown suddently, simple-scan was running
  launching simple-scan with terminal :
  "segmentation error (core dumped)"

  thanks in advance ;-)
  JG

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: simple-scan 3.20.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: Unity
  Date: Wed Apr  4 21:50:01 2018
  MachineType: Hewlett-Packard HP ProBook 4310s
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=6aaabc63-1518-452a-a01c-cd9a6f22e385 ro quiet splash vt.handoff=7
  SimpleScanLog:
   
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PHT Ver. F.0D
  dmi.board.name: 7015
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 14.10
  dmi.chassis.asset.tag: CNU9475DHV
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PHTVer.F.0D:bd01/26/2010:svnHewlett-Packard:pnHPProBook4310s:pvrF.0D:rvnHewlett-Packard:rn7015:rvrKBCVersion14.10:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4310s
  dmi.product.version: F.0D
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1761290/+subscriptions

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

[Desktop-packages] [Bug 1622499] Re: [master] package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', whi

2018-04-04 Thread Hans Joachim Desserud 
** Tags removed: yakkety
** Tags added: bionic xenial2bionic

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

Title:
  [master] package kaccounts-providers (not installed) failed to
  install/upgrade: trying to overwrite '/etc/signon-ui/webkit-
  options.d/accounts.google.com.conf', which is also in package account-
  plugin-google 0.13+16.04.20160719-0ubuntu1

Status in One Hundred Papercuts:
  Confirmed
Status in account-plugins package in Ubuntu:
  Confirmed
Status in kaccounts-providers package in Ubuntu:
  Confirmed

Bug description:
  
  kaccounts-providers packagepackage kaccounts-providers (not installed) failed 
to install/upgrade: trying to overwrite 
'/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in 
package account-plugin-google 0.13+16.04.20160719-0ubuntu1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: kaccounts-providers (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Sep 12 08:14:14 2016
  DuplicateSignature:
   package:kaccounts-providers:(not installed)
   Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb
 (--unpack):
trying to overwrite '/usr/share/accounts/services/google-im.service', which 
is also in package account-plugin-google 0.13+16.04.20160719-0ubuntu1
  ErrorMessage: trying to overwrite 
'/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in 
package account-plugin-google 0.13+16.04.20160719-0ubuntu1
  InstallationDate: Installed on 2016-09-08 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.14
  SourcePackage: kaccounts-providers
  Title: package kaccounts-providers (not installed) failed to install/upgrade: 
trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', 
which is also in package account-plugin-google 0.13+16.04.20160719-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1725312] Re: gnome-shell crashed with SIGSEGV in st_widget_style_changed()

2018-04-04 Thread Sebastien Bacher 
the e.u.c summary has some 3.28 reports

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

Title:
  gnome-shell crashed with SIGSEGV in st_widget_style_changed()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/f74709b604cdae437acbd6591fe8933bc3d8750a

  ---

  I was restoring a backup when this occurred.  I was not interacting
  with the system at the time.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  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: Fri Oct 20 06:58:55 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'firefox.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f840ef624f1 :   orb
$0x1,0x30(%rbx)
   PC (0x7f840ef624f1) ok
   source "$0x1" ok
   destination "0x30(%rbx)" (0xfbf0) not located in a known VMA 
region (needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   st_widget_style_changed () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in st_widget_style_changed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1705689] Re: When adding an app to favourites, two icons are created.

2018-04-04 Thread Sebastien Bacher 
thanks!

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

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided => Low

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

Title:
  When adding an app to favourites, two icons are created.

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Triaged

Bug description:
  On Ubuntu 17.10, I wanted to add gnome-terminal to the favorites.
  Usually in Gnome, the item gets added one times. Instead, there were
  two items of gnome-terminal in the favorites.

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

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

[Desktop-packages] [Bug 1726919] Re: Ubuntu 17.10 desktops corrupted

2018-04-04 Thread Sebastien Bacher 
Could you open the session selector on the login screen for 1002 and see
what session is selected? it looks like a GNOME session without dock and
with the GNOME theme

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

Title:
  Ubuntu 17.10 desktops corrupted

Status in nautilus package in Ubuntu:
  New

Bug description:
  The following users were installed:

  admin from DVD install (login with X option)
  user id 1001 (login with default Ubuntu option)
  user id 1002 (login with default Ubuntu option)
  user id 1003 (login with default Ubuntu option)

  Desktops for admin and user 1001 are ok.

  Desktops for users 1002 and 1003 are corrupted.

  See attached screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  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 Oct 24 11:41:36 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/nautilus-desktop
  InstallationDate: Installed on 2017-10-21 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1761267] Re: issue is regarding boot hanging between work

2018-04-04 Thread Leonidas S. Barbosa 
** Information type changed from Private Security to Public

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

Title:
  issue is regarding boot hanging between work

Status in xorg package in Ubuntu:
  New

Bug description:
  while getting started it is hanged and sometime it doesnot open the
  required folder any software downloaded from internet is not installed
  in "exe." file especially sometime keyboard stops working

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems
   UBUNTU: clean, 272012/29777920 files, 3537812/119111424 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Apr  4 23:11:32 2018
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0767]
  InstallationDate: Installed on 2018-02-22 (41 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=a581e6e4-3ec8-44a1-96df-744ef70e8b7e ro acpi_rev_override locale=en_US
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 0C6XG5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd01/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn0C6XG5:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Inspiron 5567
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Apr  4 20:29:12 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1317 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Desktop-packages] [Bug 1760282] Re: Cryptsetup does not allow storage-drive encryption, it has unfullfilled dependencies

2018-04-04 Thread Sebastien Bacher 
the suggests needs to be changed to a recommend which is pending on MIRs
review (e.g bug #1754422)

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

Title:
  Cryptsetup does not allow storage-drive encryption, it has
  unfullfilled dependencies

Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  After installing cryptsetup it was not possible to encrypt an usb-
  stick or to open an encrypted usb-stick. In case of encryption (ext4)
  with e.g. "gnome-disks" it showed the error:

  The function "bd_crypto_luks_open_blob" called, but not implemented!

  A solution for this problem was given in

  https://debianforum.de/forum/viewtopic.php?t=166920

  
  The installation of the library 

  sudo apt-get install libblockdev-crypto2

  
  was the solution. This library is not part of required dependencies of 
cryptsetup.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cryptsetup 2:2.0.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 31 11:48:14 2018
  InstallationDate: Installed on 2018-03-24 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: cryptsetup
  UpgradeStatus: No upgrade log present (probably fresh install)
  cmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=dddb12ef-69be-465c-80f8-f94714a9dcdb ro quiet splash vt.handoff=1
  crypttab: # 


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

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

[Desktop-packages] [Bug 1761278] Re: Thunderbird time zone data has not been updated since March 2017

2018-04-04 Thread Sebastien Bacher 
** Changed in: thunderbird (Ubuntu)
   Status: New => Triaged

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

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

Title:
  Thunderbird time zone data has not been updated since March 2017

Status in Mozilla Thunderbird:
  Unknown
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Thunderbird maintains its own copy of the timezone data, which in
  Bionic has not been updated since March 2017. This has been fixed
  upstream starting with 52.7.

  As a result events may not display at the correct time; for example,
  events sent with the timezone Africa/Khartoum will display offset by
  one hour.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:52.6.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 1819 F pulseaudio
   /dev/snd/controlC0:  vectro 1819 F pulseaudio
  BuildID: 20180131200234
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Wed Apr  4 15:01:38 2018
  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 2018-03-23 (12 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  IpRoute:
   default via 192.168.0.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.7 metric 600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-7b6eaa7d-0844-455b-a589-5a9030180404
  PrefSources:
   prefs.js
   
/usr/lib/thunderbird/extensions/{a62ef8ec-5fdc-40c2-873c-223b8a6925cc}/defaults/preferences/preferences.js
   
/usr/lib/thunderbird/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
  Profiles: Profile0 (Default) - LastVersion=52.6.0/20180131200234 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1726919] Re: Ubuntu 17.10 desktops corrupted

2018-04-04 Thread peterzay 
** Changed in: nautilus (Ubuntu)
   Status: Incomplete => New

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

Title:
  Ubuntu 17.10 desktops corrupted

Status in nautilus package in Ubuntu:
  New

Bug description:
  The following users were installed:

  admin from DVD install (login with X option)
  user id 1001 (login with default Ubuntu option)
  user id 1002 (login with default Ubuntu option)
  user id 1003 (login with default Ubuntu option)

  Desktops for admin and user 1001 are ok.

  Desktops for users 1002 and 1003 are corrupted.

  See attached screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  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 Oct 24 11:41:36 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/nautilus-desktop
  InstallationDate: Installed on 2017-10-21 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1709781] Re: Screenshots do not work in Wayland session

2018-04-04 Thread Dillon Mulroy 
Is there any update on this issue?  I posted a thread on /r/gnome and
didn't really get any good feedback
(https://www.reddit.com/r/gnome/comments/86dcnh/gnomescreenshot_copy_to_clipboard_fails_on_medium/)

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

Title:
  Screenshots do not work in Wayland session

Status in Gnome Screenshot:
  New
Status in gnome-screenshot package in Ubuntu:
  Incomplete

Bug description:
  With the current 17.10 builds, it's not possible to take screenshots
  when using the Wayland session.

  Expected result: Screenshot of actual screen/application/rectangle taken and 
either copied to clipboard or saved to file
  Actual result: No Image, just a black image

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

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

[Desktop-packages] [Bug 1738821] Re: Appstream data points to libreoffice-common

2018-04-04 Thread Tim Passingham 
Please forgive me, but I am not quite clear whether this bug report
suggests that the startcenter desktop should no longer exist or not, or
whether it should just be in a different package.

I am a libreoffice user, and like to keep up to date with changes and
fixes, and am on:

Version: 6.0.3.1
Build ID: 1:6.0.3~rc1-0ubuntu0.17.10.1
CPU threads: 8; OS: Linux 4.13; UI render: GL; VCL: gtk2; 
Locale: en-GB (en_GB.UTF-8); Calc: grou


Having just updated to this from 6.0.2 I no longer have a startcenter desktop.  
This is a nuisance, to say the least. I have constructed one for myself, but 
users surely should not have to do so.

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

Title:
  Appstream data points to libreoffice-common

Status in libreoffice package in Ubuntu:
  Fix Committed

Bug description:
  Searching for Libreoffice in a software centre which uses Appstream
  data (most of them) brings up Libreoffice but install libreoffice-
  common.  This is because it contains libreoffice-startcenter.desktop
  which gets extracted into the DEP-11 data.  libreoffice-common doesn't
  depend on anything useful so the user does not end up with a useful
  libreoffice install.  It would be better to move this libreoffice-
  startcenter.desktop file into the libreoffice meta package.

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

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

[Desktop-packages] [Bug 1758647] Re: ubiquity doesn't preselect the right default keyboard layout

2018-04-04 Thread Sebastien Bacher 
the scenario you describe is totally different, you don't select the
language on the "grub like menu" and you boot to the live session mode
and not to the "ubiquity only" (which is the third entry), there seems
to be an issue with ubiquity in any case because if you go back and pick
another language and do next the keyboard is not updated

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

Title:
  ubiquity doesn't preselect the right default keyboard layout

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

Bug description:
  In Ubuntu, Xubuntu and Lubuntu 18.04 Bionic Beaver, daily builds of
  March 25, the right default keymap isn't preselected when you select
  "Nederlands" (i.e. Dutch) as language for the installation.

  It's now "English, US" but should be:
  "English (US) - English (US, intl., with dead keys)".

  Or, in other words, it should be:
  XKBLAYOUT="us"
  XKBVARIANT="intl"

  (additional remark in order to prevent any misunderstandings: the
  original Dutch keyboard (nl) has completely disappeared long ago, so
  all keyboards sold in the Netherlands have US keyboards which need the
  "intl" xkbvariant with dead keys, in order to be able to type accents)

  This is a regression, at least compared with Ubuntu 16.04 and earlier
  (I don't know about 16.10, 17.04 and 17.10).

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

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

[Desktop-packages] [Bug 1757951] Re: FFE: wayland 1.15, move libwayland-egl to src:wayland

2018-04-04 Thread Timo Aaltonen 
I have the packages in ppa:canonical-x/x-staging, but wayland should
bump it's breaks/replaces against the mesa packages to fix file
conflicts (because we didn't pull in this change yet). libwayland-dev
might also need to be split to have egl frontend/backend headers in
separate packages, I'll look into that first and push it to Debian, then
sync to ppa again.

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

Title:
  FFE: wayland 1.15, move libwayland-egl to src:wayland

Status in wayland package in Ubuntu:
  New

Bug description:
  libwayland-egl was moved from mesa to wayland in 1.15rc and will be
  dropped from Mesa after 18.0.0. So in order to avoid doing this as an
  SRU later when backporting newer mesa to 18.04 we should do the
  transition in bionic before release. Debian has done this now in
  experimental.

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

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

[Desktop-packages] [Bug 1761274] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

2018-04-04 Thread dino99 
*** This bug is a duplicate of bug 1725928 ***
https://bugs.launchpad.net/bugs/1725928

** This bug has been marked a duplicate of bug 1725928
   package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with 
differing files  '/lib/udev/hwdb.d/20-sane.hwdb'

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  i was installing winehq ver 3.0 and suddenly this bug popped up.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Thu Apr  5 00:06:58 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-mQiZ5p/11-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2017-12-20 (105 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1761274/+subscriptions

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

[Desktop-packages] [Bug 1761278] [NEW] Thunderbird time zone data has not been updated since March 2017

2018-04-04 Thread Ian Turner 
Public bug reported:

Thunderbird maintains its own copy of the timezone data, which in Bionic
has not been updated since March 2017. This has been fixed upstream
starting with 52.7.

As a result events may not display at the correct time; for example,
events sent with the timezone Africa/Khartoum will display offset by one
hour.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: thunderbird 1:52.6.0+build1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  vectro 1819 F pulseaudio
 /dev/snd/controlC0:  vectro 1819 F pulseaudio
BuildID: 20180131200234
Channel: Unavailable
CurrentDesktop: KDE
Date: Wed Apr  4 15:01:38 2018
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 2018-03-23 (12 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1)
IpRoute:
 default via 192.168.0.1 dev wlo1 proto dhcp metric 600 
 169.254.0.0/16 dev wlo1 scope link metric 1000 
 192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.7 metric 600
Locales: extensions.sqlite corrupt or missing
MostRecentCrashID: bp-7b6eaa7d-0844-455b-a589-5a9030180404
PrefSources:
 prefs.js
 
/usr/lib/thunderbird/extensions/{a62ef8ec-5fdc-40c2-873c-223b8a6925cc}/defaults/preferences/preferences.js
 
/usr/lib/thunderbird/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
Profiles: Profile0 (Default) - LastVersion=52.6.0/20180131200234 (In use)
RunningIncompatibleAddons: False
SourcePackage: thunderbird
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/25/2018
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L78 Ver. 01.43
dmi.board.name: 2101
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 16.3C
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
dmi.product.name: HP ProBook 640 G1
dmi.product.version: A3009DD10303
dmi.sys.vendor: Hewlett-Packard

** Affects: thunderbird
 Importance: Unknown
 Status: Unknown

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


** Tags: amd64 apport-bug bionic

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

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

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

Title:
  Thunderbird time zone data has not been updated since March 2017

Status in Mozilla Thunderbird:
  Unknown
Status in thunderbird package in Ubuntu:
  New

Bug description:
  Thunderbird maintains its own copy of the timezone data, which in
  Bionic has not been updated since March 2017. This has been fixed
  upstream starting with 52.7.

  As a result events may not display at the correct time; for example,
  events sent with the timezone Africa/Khartoum will display offset by
  one hour.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:52.6.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 1819 F pulseaudio
   /dev/snd/controlC0:  vectro 1819 F pulseaudio
  BuildID: 20180131200234
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Wed Apr  4 15:01:38 2018
  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 2018-03-23 (12 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  IpRoute:
   default via 192.168.0.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.7 metric 600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCr

[Desktop-packages] [Bug 1761261] Re: nouveau/nvidia drivers do not work with display in Bionic on Asus GL703VD Laptop

2018-04-04 Thread Luke Williams 
** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  nouveau/nvidia drivers do not work with display in Bionic on Asus
  GL703VD Laptop

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  Tried to install Bionic Desktop on my Asus GL703VD ROG Laptop with
  NVIDIA GTX 1050M Video Card (with i915 Intel graphics card when not
  using 3D) and the installer does not display. I have tried
  nouveau.modeset=0 and nomodeset boot options to no avail. I was able
  to finally install Bionic by hooking up the laptop to a projector, but
  after a reboot, the laptop display still did not work and I had to set
  the account to autologin otherwise I could not loging to the laptop. I
  then install openssh-server so that I could ssh into the laptop and I
  installed the nvidia-390 drivers from ppa:graphic-drivers/ppa which
  installed, but still no local display.

  In Artful, I could install with the nouveau.modeset=0 and then
  installing the proprietary NVIDIA drivers and everything (except
  touchpad, LP: 1738263) worked.

  lspci shows the graphics card and NVIDIA card, and lsmod does show
  that before NVIDIA drivers install, it is using nouveau, asus_wmi, and
  i915 for graphcis, and once NVIDIA drivers are install, lsmod only
  shows i915 and asus_wmi for graphics while nvidia is used for gpu and
  3D, but still no display on the laptop.

  lsmod_prenvidia.txt shows the nouveau driver and the /proc/cmdline
  lsmod_nvidia.txt shows nvidia drivers installed and the /proc/cmdline
  lspci.txt shows the detected hardware
  lshw.txt shows the hardware in the laptop.

  Please let me know if you need any other information.

  Thanks,
  Luke

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

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

[Desktop-packages] [Bug 1761274] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

2018-04-04 Thread Apport retracing service 
** Tags removed: need-duplicate-check

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  i was installing winehq ver 3.0 and suddenly this bug popped up.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Thu Apr  5 00:06:58 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-mQiZ5p/11-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2017-12-20 (105 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1761274/+subscriptions

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

[Desktop-packages] [Bug 1761274] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from o

2018-04-04 Thread Adarsh Gupta 
Public bug reported:

i was installing winehq ver 3.0 and suddenly this bug popped up.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Thu Apr  5 00:06:58 2018
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental2ubuntu2.1
 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-mQiZ5p/11-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
  trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
InstallationDate: Installed on 2017-12-20 (105 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful package-conflict

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  i was installing winehq ver 3.0 and suddenly this bug popped up.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Thu Apr  5 00:06:58 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-mQiZ5p/11-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2017-12-20 (105 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1761274/+subscriptions

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

[Desktop-packages] [Bug 1725312] Re: gnome-shell crashed with SIGSEGV in st_widget_style_changed()

2018-04-04 Thread Apport retracing service 
** Tags added: bionic

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

Title:
  gnome-shell crashed with SIGSEGV in st_widget_style_changed()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/f74709b604cdae437acbd6591fe8933bc3d8750a

  ---

  I was restoring a backup when this occurred.  I was not interacting
  with the system at the time.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  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: Fri Oct 20 06:58:55 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'firefox.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f840ef624f1 :   orb
$0x1,0x30(%rbx)
   PC (0x7f840ef624f1) ok
   source "$0x1" ok
   destination "0x30(%rbx)" (0xfbf0) not located in a known VMA 
region (needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   st_widget_style_changed () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in st_widget_style_changed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1761268] Re: gnome-shell crashed with SIGSEGV in st_widget_style_changed()

2018-04-04 Thread Apport retracing service 
*** This bug is a duplicate of bug 1725312 ***
https://bugs.launchpad.net/bugs/1725312

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 #1725312, 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/1761268/+attachment/5101698/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1725312
   gnome-shell crashed with SIGSEGV in st_widget_style_changed()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with SIGSEGV in st_widget_style_changed()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This bug persists.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  4 10:33:24 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-03-17 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180317)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f18025d8e51 :   orb
$0x1,0x30(%rbx)
   PC (0x7f18025d8e51) ok
   source "$0x1" ok
   destination "0x30(%rbx)" (0xfbf0) not located in a known VMA 
region (needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   st_widget_style_changed () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in st_widget_style_changed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

  1   2   3   >