date:20180403

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

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 #1755064, 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/1761057/+attachment/5100789/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1755064
   gnome-software crashed with signal 5 in g_wakeup_new → g_main_context_new → 
pk_client_resolve → gs_plugin_packagekit_resolve_packages_with_filter → 
gs_plugin_packagekit_resolve_packages

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

Title:
  gnome-software crashed with signal 5

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Was using apt on the command line when gnome-software crashed

  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: Wed Apr  4 01:21:03 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-04-03 (0 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
   pk_client_resolve () at /usr/lib/x86_64-linux-gnu/libpackagekit-glib2.so.18
   () at 
/usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_packagekit-refine.so
   gs_plugin_refine () at 
/usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_packagekit-refine.so
  Title: gnome-software crashed with signal 5
  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-software/+bug/1761057/+subscriptions

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

[Desktop-packages] [Bug 1490738] Re: Lithuanian keyboard doesn't switch on

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

** Changed in: xkeyboard-config (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Lithuanian keyboard doesn't switch on

Status in xkeyboard-config package in Ubuntu:
  Expired

Bug description:
  Lithuanian keyboard gives no Lithuanian symbols. Using SUPER+SPACE it
  does change language indicator on the upper right corner of the
  desktop, but there's no Lt symbols where they are supposed to be.

  Lt symbols should be on the keyboard's upper number line. The symbol
  map still claims they are there. In matter of fact, when I switch to
  Lt keyboard, it still uses Finnish symbols. Finnish is my main
  keyboard at the moment.

  Before that, there were Russian symbols instead of Lt. So I
  uninstalled Rus keyboard. That caused Lt keyboard to show English
  symbols. After uninstalling Eng, now Lt keyboard is sticking with Fin.
  Adding new languages doesn't change behaviour (still Fi).

  Other languages on keyboard work fine. Uninstalling all keyboards
  except Lt, still makes no Lithuanian symbols.

  I tried uninstall Lithuanian keyboard (with reboot) and install again.
  Also tried different Lithuanian keyboards.

  Ubuntu 14.04.3 LTS 64-bit on MSI GE620DX laptop.

  (That's my first bug report, hope I'm doing it as it's supposed to be
  done.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1490738/+subscriptions

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

[Desktop-packages] [Bug 1757321] Re: udisks2 must depend on libblockdev-crypto2 and libblockdev-mdraid2 instead of suggests [Can't mount encrypted USB drive after upgrade to bionic]

2018-04-03 Thread Stuart Bishop

This also affects the Live CD, where attempting to mount encrypted
volumes for testing or rescue purposes fails with this rather scary
error.

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

Title:
  udisks2 must depend on libblockdev-crypto2 and libblockdev-mdraid2
  instead of suggests [Can't mount encrypted USB drive after upgrade to
  bionic]

Status in udisks2 package in Ubuntu:
  Triaged

Bug description:
  after upgrading to bionic, attempts to mount an encrypted USB drive
  fail with the error "function bd_crypto_luks_open_blob called but not
  implemented"

  Installing libblockdev-crypto2 and libblockdev-crypto-dev and
  rebooting appears to have fixed it, but should that be necessary?  or
  at least better documented?
  (https://www.distrowatch.com/weekly.php?issue=20171113 is the only
  reference I could find on the error)

  [Workaround]
  1. Install libblockdev-crypto2
  2. Restart udisks:
$ systemctl restart udisks2

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udisks2 2.7.6-2ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  CustomUdevRuleFiles: 90-xhc_sleep.rules 70-snap.core.rules
  Date: Tue Mar 20 20:28:39 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-08-21 (942 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  MachineType: Apple Inc. MacBookPro11,4
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=1
  SourcePackage: udisks2
  UpgradeStatus: Upgraded to bionic on 2018-03-20 (0 days ago)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0172.B04.1506051511
  dmi.board.name: Mac-06F11FD93F0323C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,4
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11FD93F0323C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro11,4
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Desktop-packages] [Bug 1761044] [NEW] xorg error

2018-04-03 Thread swaroopbigboy

Public bug reported:

when ever the system is recovered from the sleep mod due to inactivity i
get an xorg error msg ...

ProblemType: Bug
DistroRelease: elementary 0.4.1
Package: xorg 1:7.7+13ubuntu3 [origin: Ubuntu]
ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Apr  4 09:06:22 2018
DistUpgraded: Fresh install
DistroCodename: loki
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:832b]
   Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 
M330] [103c:832b]
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1bcf:2c9b Sunplus Innovation Technology Inc.
 Bus 001 Device 002: ID 8087:0aa7 Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Laptop 15-bs0xx
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed 
root=UUID=cb67384c-374d-4721-a7b6-d21e48bc769a ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.21
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 832B
dmi.board.vendor: HP
dmi.board.version: 23.37
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd07/04/2017:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn832B:rvr23.37:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP Laptop 15-bs0xx
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Apr  4 08:55:42 2018
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug loki third-party-packages ubuntu

** Attachment added: "screen shot off error msg"
   https://bugs.launchpad.net/bugs/1761044/+attachment/5100673/+files/xorg.png

** Description changed:

- 
- when ever the is recovered from the sleep mod due to inactivity i get an xorg 
error ...
+ when ever the system is recovered from the sleep mod due to inactivity i
+ get an xorg error msg ...
  
  ProblemType: Bug
  DistroRelease: elementary 0.4.1
  Package: xorg 1:7.7+13ubuntu3 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Apr  4 09:06:22 2018
  DistUpgraded: Fresh install
  DistroCodename: loki
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
-Subsystem: Hewlett-Packard Company Device [103c:832b]
-Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / 
R5 M330] [103c:832b]
+  Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
+    Subsystem: Hewlett-Packard Company Device [103c:832b]
+    Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / 
R5 M330] [103c:832b]
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 1bcf:2c9b Sunplus Innovation Technology Inc. 
-  Bus 001 Device 002: ID 8087:0aa7 Intel Corp. 
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 1bcf:2c9b Sunplus Innovation Technology Inc.
+  Bus 001 Device 002: ID 8087:0aa7 Intel Corp.
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 15-bs0xx
  ProcEnviron:
-

[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

Some more: touching the system cache files doesn't make it work.

Binary diff on the cache files before and after running fc-cache shows
this:

63 c7 c3 5a 00 00 00 00  47 72 ce 15 00 00 00 00
63 c7 c3 5a 00 00 00 00  00 00 00 00 00 00 00 00

Before, at offset 0x38, the "bad" cache files have a non-zero 32 bit
number. The number is different in every "bad" cache file. It is always
zero in the "good" files. This is the only difference. The rest of each
file is identical.

I don't know what this field represents. Need a fontconfig expert to
look at this.

-- 
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 1761040] Re: gnome-shell crashed with signal 5

*** 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/1761040/+attachment/5100648/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1761040/+attachment/5100658/+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/1761040

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  crash report after boot

  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: Wed Apr  4 09:49:59 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-27 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  ProcCmdline: /usr/bin/gnome-shell
  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
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () 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/1761040/+subscriptions

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

[Desktop-packages] [Bug 1761038] Re: nautilus crashed with signal 5 when trying gnome music in ubuntu 18.04

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

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 #1692469, 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/1761038/+attachment/5100637/+files/CoreDump.gz

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

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

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

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

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

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

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

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

Title:
  nautilus crashed with signal 5 when trying gnome music in ubuntu
  18.04

Status in nautilus package in Ubuntu:
  New

Bug description:
  nautilus crashed with signal 5 when trying gnome music in ubuntu 18.04
  to play a MP3 file.

  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: Tue Apr  3 22:16:25 2018
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2018-03-29 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  Signal: 5
  SourcePackage: nautilus
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   tracker_tokenizer_initialize () at 
/usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so.0
  Title: nautilus crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

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

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

Another piece of the puzzle: if you run:

sudo fc-cache -fv

this will rebuild the system font cache in /var/cache/fontconfig

If you then delete the user's cache in ~/.cache/fontconfig and re-log,
there is no delay... and the user's font cache will NOT be rebuilt.

After a delayed login, user's cache and the system cache appear to
contain the same files.

So it looks as if something thinks the system cache is out of date and
wants to rebuild it. Whatever it is only has user permissions, so
rebuilds the font cache in the user's .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 1760934] Re: Sound not working on HP x2 10-p030nl - Realtek rt5640

This sounds like it might be a duplicate of bug 1720519. Please try the
workaround in comment 4 here:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1720519/comments/4

** Changed in: pulseaudio (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/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 1760201] Re: ubuntu 18.04 GDM - missing icons and letters

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

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

** Summary changed:

- ubuntu 18.04 GDM - missing icons and letters
+ ubuntu 18.04 GDM - missing icons and letters in Turkish system language

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

Title:
  ubuntu 18.04 GDM - missing icons and letters in Turkish system
  language

Status in gdm3 package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04(Updated 30.03.2018)
  System Language: Turkish
  Please check screenshots
  --- 
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-24 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180324)
  Package: gnome-shell
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1724439] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call()

** Changed in: gnome-shell (Ubuntu Bionic)
 Assignee: Daniel van Vugt (vanvugt) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from
  ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from
  function_call()

Status in Mutter:
  In Progress
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Bionic:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/3e662975e4b7e6829b9d68d1c2b06f429e44c854

  ---

  left virtual box to update win10 came back and got error message

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 23:37:32 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-04-18 (182 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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: 0x7feb2ed42d94 :mov
0x18(%rax),%eax
   PC (0x7feb2ed42d94) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_window_get_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/libgjs.so.0
   ?? () from /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
  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/mutter/+bug/1724439/+subscriptions

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

[Desktop-packages] [Bug 1748450] Re: 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

Nobody needs to provide more information here, thanks.

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

Title:
  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 

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  *** This is a duplicate of bug 1505409, but is being kept separate so
  as to automatically collect duplicate reports since the stacktrace
  signature has changed recently. Any resolution and discussion should
  occur in bug 1505409. ***

  See also:
  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
  Uname: Linux 4.13.0-33-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Feb  8 23:50:23 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2016-03-21 (690 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  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-1.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () 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: Upgraded to bionic on 2018-02-08 (0 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1730540] Re: gnome-shell freezes after resume then unlock

OK. Please provide some/all of the information requested in comment #2.

I suggest the next steps are:

1. Apply the workaround from bug 994921 first.

2. Then next time the problem happens look in /var/crash for relevant
crash files and if found then run:   ubuntu-bug
/var/crash/YOURFILE.crash

3. If there were no crash files then please run 'kill -ABRT ' on
the hung gnome-shell process. Then goto step 2.

4. Tell us here the IDs of any new bugs opened via 'ubuntu-bug'.

5. After the problem happens next time, please run these commands and send us 
the resulting files:
  dmesg > dmesg.txt
  journalctl -b > journal.txt


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

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

Title:
  gnome-shell freezes after resume then unlock

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Often after resuming and then entering my password to unlock gnome-
  shell, when I press the enter key gnome-shell immediately freezes. The
  lock screen is still displayed, the mouse no longer responds, and the
  keys no longer respond (I can't even get a tty console with CTRL-ALT-
  Fn key). I have to perform a hard reset at this point because gnome-
  shell remains frozen even after leaving the PC alone for 15 minutes.

  I haven't been able to find any crash files or error logs.

  It seems that this freeze is much more likely to occur if I have
  changed location between suspending and resuming and am therefore
  connecting to a different wifi router. Once, however, it happened at
  home on the same router and I was able to log in via ssh from another
  machine (so only gnome-shell was frozen, not the kernel). However, I
  couldn't see any messages or reason that gnome-shell had crashed, so
  all I could do was reboot (any hints as to what I should try at this
  stage are welcome).

  Bug #1709994 looks similar but in that case a) the user is using Xorg,
  not Wayland, b) he also gets past the lock screen, and c) gnome-shell
  eventually restarts.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  Uname: Linux 4.14.0-rc8-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 08:46:43 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-16 (82 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-08-17 (81 days ago)

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

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

seems related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845058

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

As far as the original bug with delayed login goes... it seems that the
Bluetooth stuff is a red herring.

Since it only happens on first login, I deleted the contents of ~ and
relogged. The delay came back, so I bisected the files until I arrived
at the single file which needs to be deleted in order for the delay to
happen. And that file is:

   ~/.cache/fontconfig/9b89f8e3dae116d678bbf48e5f21f69b-le32d4.cache-7

This cache file is associated with the Noto CJK fonts at:

/usr/share/fonts/opentype/noto

(You can see this by running strings on it.)

Deleting this file while the user is not logged in causes the next login
to take 60 seconds.

** Bug watch added: Debian Bug tracker #845058
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845058

-- 
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 1761032] Re: gnome-shell crashed with signal 5

*** 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/1761032/+attachment/5100601/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1761032/+attachment/5100610/+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/1761032

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Error message keeps popping up.

  System:

  Linux ubuntu1804 4.15.0-14-generic #15-Ubuntu SMP Mon Apr 2 19:50:19
  UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  Codename: bionic

  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-14-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Apr  3 20:16:06 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-31 (3 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180331)
  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
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () 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/1761032/+subscriptions

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

[Desktop-packages] [Bug 1730540] Re: gnome-shell freezes after resume then unlock

2018-04-03 Thread Rocko

It's still happening every now and again.

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

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

Title:
  gnome-shell freezes after resume then unlock

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Often after resuming and then entering my password to unlock gnome-
  shell, when I press the enter key gnome-shell immediately freezes. The
  lock screen is still displayed, the mouse no longer responds, and the
  keys no longer respond (I can't even get a tty console with CTRL-ALT-
  Fn key). I have to perform a hard reset at this point because gnome-
  shell remains frozen even after leaving the PC alone for 15 minutes.

  I haven't been able to find any crash files or error logs.

  It seems that this freeze is much more likely to occur if I have
  changed location between suspending and resuming and am therefore
  connecting to a different wifi router. Once, however, it happened at
  home on the same router and I was able to log in via ssh from another
  machine (so only gnome-shell was frozen, not the kernel). However, I
  couldn't see any messages or reason that gnome-shell had crashed, so
  all I could do was reboot (any hints as to what I should try at this
  stage are welcome).

  Bug #1709994 looks similar but in that case a) the user is using Xorg,
  not Wayland, b) he also gets past the lock screen, and c) gnome-shell
  eventually restarts.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  Uname: Linux 4.14.0-rc8-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 08:46:43 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-16 (82 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-08-17 (81 days ago)

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

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

[Desktop-packages] [Bug 1760887] Re: Copy not working

2018-04-03 Thread skaller

Could be a dup indeed, wouldn't be surprised. What's Bionic? How can I
get it?

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

Title:
  Copy not working

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Copying marked text sometimes does not work. It fails for keyboard
  shortcut, main menu, and right click menu. Paste seems to work.

  Ubuntu 17.10

  gnome-terminal:
Installed: 3.24.2-0ubuntu4
Candidate: 3.24.2-0ubuntu4
Version table:
   *** 3.24.2-0ubuntu4 500
  500 http://au.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  (Hey, copy worked for the above text!)

  What should happen: the text is copied to a clipboard.
  What happened: nothing. Paste pasted the previous contents of the clipboard.

  The fault is NOT intermittent. If I do this: cat ~/.profile and the try to 
  copy the last line (excluding the leading #) then the text is sometimes 
copied:

  # . /home/skaller/.opam/opam-init/init.sh > /dev/null 2> /dev/null ||
  true

  Note, the above text was copied .. this time. However when it fails,
  it fails repeatedly.

  This is a critical bug. The terminal is more or less useless without a
  correctly operating copy function.

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

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

[Desktop-packages] [Bug 1760807] Re: Unable to rearrange monitor layout

2018-04-03 Thread Jack Bonwick

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

** This bug has been marked a duplicate of bug 1724955
   unable to drag monitors in Display Arrangement

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

Title:
  Unable to rearrange monitor layout

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

Bug description:
  I have a quad monitor setup and I'm unable to rearrange the monitor
  layout fully. Two of the monitors are 1680x1050 and the other two are
  1920x1080. I can rearrange the monitors in their pairs or resolutions
  but cannot rearrange between the two pairs.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 08:46:11 2018
  ExecutablePath: /usr/bin/gnome-control-center
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1760807] Re: Unable to rearrange monitor layout

2018-04-03 Thread Jack Bonwick

** Attachment added: "GIF of behavior"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1760807/+attachment/5100517/+files/Buggy-Monitor-Rearranging.gif

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

Title:
  Unable to rearrange monitor layout

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

Bug description:
  I have a quad monitor setup and I'm unable to rearrange the monitor
  layout fully. Two of the monitors are 1680x1050 and the other two are
  1920x1080. I can rearrange the monitors in their pairs or resolutions
  but cannot rearrange between the two pairs.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 08:46:11 2018
  ExecutablePath: /usr/bin/gnome-control-center
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1760998] Re: Libreoffice doesn't starts on kubuntu 18.04 32bit

2018-04-03 Thread Olivier Tilloy

This is most likely a duplicate of bug #1726145 (which itself is bug
#1699772).

What's the output of

grep enabled
~/.config/libreoffice/4/user/config/javasettings_Linux_*.xml

If it looks like:



Can you edit that file with a text editor and change it to:

false

And see if that makes the crash go away?

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

Title:
  Libreoffice doesn't starts on kubuntu 18.04 32bit

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Any time I try to run any libreoffice package I can see just the
  loader image, starts loading and than crash

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic i686
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: i386
  CurrentDesktop: KDE
  Date: Tue Apr  3 23:43:48 2018
  InstallationDate: Installed on 2018-03-28 (6 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha i386 (20180327)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: i386
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-28 (6 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha i386 (20180327)
  Package: libreoffice 1:6.0.2-0ubuntu1
  PackageArchitecture: i386
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

Re: [Desktop-packages] [Bug 1758306] Re: Cannot switch mouse primary button in GCC

Well I don't know what to say - I'm using Ubuntu's environment. Somehow
over time I didn't notice that the vanilla-gnome-session was
removed/replaced. Now I have packages that I didn't have before. I'll
delete the gnome environment settings I have in my ~/home and see what
happens. These wouldn't have any effect on the plymouth-bug or losing
keyboard and mouse focus on gdm3. This iteration isn't worthy of a 'LTS'
release.

On Tue, Apr 3, 2018 at 6:11 PM Gunnar Hjalmarsson <
1758...@bugs.launchpad.net> wrote:

> I'm using real installs, not virtual.
>
> I suppose you are talking about the vanilla-gnome-desktop package, then,
> i.e. a meta package whose purpose is to install GNOME packages. The
> login options are provided by the gnome-session package, and the options
> are:
>
> GNOME
> GNOME on Xorg
>
> I had gnome-session installed already, chose the GNOME option (which
> means GNOME on Wayland), and could still successfully change the mouse
> behavior via g-c-c.
>
> So I couldn't reproduce the issue you described this time either, and
> I'm out of ideas.
>
> ** Changed in: gnome-control-center (Ubuntu)
>Status: Incomplete => New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1758306
>
> Title:
>   Cannot switch mouse primary button in GCC
>
> Status in gnome-control-center package in Ubuntu:
>   New
>
> Bug description:
>   Prior to yesterday's (March 22/18) Bionic update, I had my mouse
> configured for left handed use. That is the mouse primary button being
> switched to the right. GCC doesn't seem to work for this now. I don't know
> if it's related to evdev or what.
>   Held back reporting this in case it was fixed by changes overnight.
> Updated this morning and problem persists.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-control-center 1:3.28.0-0ubuntu3
>   ProcVersionSignature: Ubuntu
> 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
>   Uname: Linux 4.13.0-36201803011620-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Fri Mar 23 07:07:02 2018
>   InstallationDate: Installed on 2018-01-19 (62 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170920)
>   SourcePackage: gnome-control-center
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1758306/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.

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

Title:
  Cannot switch mouse primary button in GCC

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

Bug description:
  Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured 
for left handed use. That is the mouse primary button being switched to the 
right. GCC doesn't seem to work for this now. I don't know if it's related to 
evdev or what.
  Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 23 07:07:02 2018
  InstallationDate: Installed on 2018-01-19 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1760998] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1760998/+attachment/5100427/+files/ProcCpuinfoMinimal.txt

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

Title:
  Libreoffice doesn't starts on kubuntu 18.04 32bit

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Any time I try to run any libreoffice package I can see just the
  loader image, starts loading and than crash

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic i686
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: i386
  CurrentDesktop: KDE
  Date: Tue Apr  3 23:43:48 2018
  InstallationDate: Installed on 2018-03-28 (6 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha i386 (20180327)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: i386
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-28 (6 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha i386 (20180327)
  Package: libreoffice 1:6.0.2-0ubuntu1
  PackageArchitecture: i386
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1760998] Re: Libreoffice doesn't starts on kubuntu 18.04 32bit

apport information

** Tags added: apport-collected

** Description changed:

  Any time I try to run any libreoffice package I can see just the loader
  image, starts loading and than crash
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic i686
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: i386
  CurrentDesktop: KDE
  Date: Tue Apr  3 23:43:48 2018
  InstallationDate: Installed on 2018-03-28 (6 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha i386 (20180327)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ApportVersion: 2.20.9-0ubuntu2
+ Architecture: i386
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-03-28 (6 days ago)
+ InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha i386 (20180327)
+ Package: libreoffice 1:6.0.2-0ubuntu1
+ PackageArchitecture: i386
+ ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
+ Tags:  bionic
+ Uname: Linux 4.15.0-13-generic i686
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1760998/+attachment/5100426/+files/Dependencies.txt

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

Title:
  Libreoffice doesn't starts on kubuntu 18.04 32bit

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Any time I try to run any libreoffice package I can see just the
  loader image, starts loading and than crash

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic i686
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: i386
  CurrentDesktop: KDE
  Date: Tue Apr  3 23:43:48 2018
  InstallationDate: Installed on 2018-03-28 (6 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha i386 (20180327)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: i386
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-28 (6 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha i386 (20180327)
  Package: libreoffice 1:6.0.2-0ubuntu1
  PackageArchitecture: i386
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

** Attachment added: "Tail -n200 of kern.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1761003/+attachment/5100425/+files/kernlogtail.txt

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

Title:
  Bionic Beaver - not able to connect to WPA Enterprise EAP-TLS

Status in gnome-control-center 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/gnome-control-center/+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 1758306] Re: Cannot switch mouse primary button in GCC

I'm using real installs, not virtual.

I suppose you are talking about the vanilla-gnome-desktop package, then,
i.e. a meta package whose purpose is to install GNOME packages. The
login options are provided by the gnome-session package, and the options
are:

GNOME
GNOME on Xorg

I had gnome-session installed already, chose the GNOME option (which
means GNOME on Wayland), and could still successfully change the mouse
behavior via g-c-c.

So I couldn't reproduce the issue you described this time either, and
I'm out of ideas.

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

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

Title:
Cannot switch mouse primary button in GCC

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

Bug description:
Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured
for left handed use. That is the mouse primary button being switched to the
right. GCC doesn't seem to work for this now. I don't know if it's related to
evdev or what.
Held back reporting this in case it was fixed by changes overnight. Updated
this morning and problem persists.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.0-0ubuntu3
ProcVersionSignature: Ubuntu
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
Uname: Linux 4.13.0-36201803011620-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Mar 23 07:07:02 2018
InstallationDate: Installed on 2018-01-19 (62 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1760998] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1760998/+attachment/5100428/+files/ProcEnviron.txt

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

Title:
  Libreoffice doesn't starts on kubuntu 18.04 32bit

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Any time I try to run any libreoffice package I can see just the
  loader image, starts loading and than crash

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic i686
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: i386
  CurrentDesktop: KDE
  Date: Tue Apr  3 23:43:48 2018
  InstallationDate: Installed on 2018-03-28 (6 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha i386 (20180327)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: i386
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-28 (6 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha i386 (20180327)
  Package: libreoffice 1:6.0.2-0ubuntu1
  PackageArchitecture: i386
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~desktop-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] [NEW] Bionic Beaver - not able to connect to WPA Enterprise EAP-TLS

2018-04-03 Thread Kitsab

Public bug reported:

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)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "Tail -n 200 of syslog"
   
https://bugs.launchpad.net/bugs/1761003/+attachment/5100418/+files/syslogtail.txt

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

Title:
  Bionic Beaver - not able to connect to WPA Enterprise EAP-TLS

Status in gnome-control-center 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/gnome-control-center/+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 1760998] Re: Libreoffice doesn't starts on kubuntu 18.04 32bit

2018-04-03 Thread Simon Quigley

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please execute the following command only once, as it will 
automatically gather debugging information, in a terminal:
apport-collect 1760998

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

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

Title:
  Libreoffice doesn't starts on kubuntu 18.04 32bit

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Any time I try to run any libreoffice package I can see just the
  loader image, starts loading and than crash

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic i686
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: i386
  CurrentDesktop: KDE
  Date: Tue Apr  3 23:43:48 2018
  InstallationDate: Installed on 2018-03-28 (6 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha i386 (20180327)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1760998] [NEW] Libreoffice doesn't starts on kubuntu 18.04 32bit

Public bug reported:

Any time I try to run any libreoffice package I can see just the loader
image, starts loading and than crash

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libreoffice 1:6.0.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic i686
ApportVersion: 2.20.9-0ubuntu2
Architecture: i386
CurrentDesktop: KDE
Date: Tue Apr  3 23:43:48 2018
InstallationDate: Installed on 2018-03-28 (6 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha i386 (20180327)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libreoffice (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: apport-bug bionic i386

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

Title:
  Libreoffice doesn't starts on kubuntu 18.04 32bit

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Any time I try to run any libreoffice package I can see just the
  loader image, starts loading and than crash

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic i686
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: i386
  CurrentDesktop: KDE
  Date: Tue Apr  3 23:43:48 2018
  InstallationDate: Installed on 2018-03-28 (6 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha i386 (20180327)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

That behavior (pausing resolved by having the Chrome Task window open
via shift-esc only to have pausing stop when that task window is closed)
I verified in Chrome deb and Chromium snap both.

-- 
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 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load

2018-04-03 Thread Péter Prőhle

Today I got similar result:

$ /usr/lib/gnome-settings-daemon/gsd-media-keys

(gsd-media-keys:2834): GLib-GIO-WARNING **: 23:34:21.130: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})

(gsd-media-keys:2834): GLib-GIO-WARNING **: 23:34:37.681: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})

(gsd-media-keys:2834): GLib-GIO-WARNING **: 23:34:44.777: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})

DO I EXECUTE THE RIGHT OR SUITABLE TEST?

Tell me what to test next time?

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

Title:
  /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/
  fails to load

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

Bug description:
  $ dconf dump /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/
  [custom1]
  binding='BackSpace'
  command='gnome-session-quit --power-off'
  name='gnome-session-quit --power-off'

  [custom0]
  binding='g'
  command='gnome-terminal --geometry=80x99-0+0'
  name='gnome-terminal --geometry=80x99-0+0'
  $

  In spite of the above, time to time, not always, but since 18.04 much
  much more frequently this settings fails to become active just after
  booting, ... my account is logged in automatically just after boot.

  If I log out and log in again, then these key bindings work.

  If I go to the system settings, and define again, then these work
  again.

  Earlier, before 18.04 this phenomenon was rare, namely once a week at
  most.

  But since 18.04 it is almost guaranteed, not deterministic, but highly
  probable, that after an initial boot or a warm reboot these key
  bindings will not work.

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

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

Ok, interesting, it only stopped because I opened the Chrome task window
as you suggested.  When the window is open, the pausing stops
completely, even if it's minimized.  But if I close the Chrome task
window, the pausing comes back!

-- 
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 1760991] [NEW] favorite applications gnome duplicated

2018-04-03 Thread Jonatan Ayllón

Public bug reported:

Favorite applications gnome duplicated

https://youtu.be/joOxaMdBqsg

Ubuntu 18.04

** Affects: ubuntu
 Importance: Undecided
 Status: New

** Package changed: xdg-utils (Ubuntu) => ubuntu

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

Title:
  favorite applications gnome duplicated

Status in Ubuntu:
  New

Bug description:
  Favorite applications gnome duplicated

  https://youtu.be/joOxaMdBqsg

  Ubuntu 18.04

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

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

[Desktop-packages] [Bug 1754356] Re: xdg-user-dirs-update does not take care of $HOME

2018-04-03 Thread Treviño

Can confirm it works.

marco@tricky:/tmp:✓ $ apt-cache policy xdg-user-dirs
xdg-user-dirs:
  Installato: 0.15-2ubuntu6.16.04.1
  Candidato:  0.15-2ubuntu6.16.04.1
  Tabella versione:
 *** 0.15-2ubuntu6.16.04.1 100

Before upgrading:

marco@tricky:/tmp:✓ $ env HOME=/tmp/temp-home xdg-user-dirs-update
marco@tricky:/tmp:✓ $ find /tmp/temp-home/
find: '/tmp/temp-home': No such file or directory

After:

marco@tricky:/tmp:✓ $ env HOME=/tmp/temp-home xdg-user-dirs-update
marco@tricky:/tmp:✓ $ find temp-home/
temp-home/
temp-home/Video
temp-home/Modelli
temp-home/.config
temp-home/.config/user-dirs.locale
temp-home/.config/user-dirs.dirs
temp-home/Documenti
temp-home/Immagini
temp-home/Scaricati
temp-home/Pubblici
temp-home/Scrivania
temp-home/Musica

marco@tricky:/tmp:✓ $ env HOME=/tmp/temp-home xdg-user-dirs-update --set 
DOWNLOADS \
 "/tmp/temp-home/sub/folder/of/it/Downloads"
marco@tricky:/tmp:✓ $ cat temp-home/.config/user-dirs.dirs
# This file is written by xdg-user-dirs-update
# If you want to change or add directories, just edit the line you're
# interested in. All local changes will be retained on the next run
# Format is XDG_xxx_DIR="$HOME/yyy", where yyy is a shell-escaped
# homedir-relative path, or XDG_xxx_DIR="/yyy", where /yyy is an
# absolute path. No other format is supported.
# 
XDG_DESKTOP_DIR="$HOME/Scrivania"
XDG_DOWNLOAD_DIR="$HOME/Scaricati"
XDG_TEMPLATES_DIR="$HOME/Modelli"
XDG_PUBLICSHARE_DIR="$HOME/Pubblici"
XDG_DOCUMENTS_DIR="$HOME/Documenti"
XDG_MUSIC_DIR="$HOME/Musica"
XDG_PICTURES_DIR="$HOME/Immagini"
XDG_VIDEOS_DIR="$HOME/Video"
XDG_DOWNLOADS_DIR="$HOME/sub/folder/of/it/Downloads"


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

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

Title:
  xdg-user-dirs-update does not take care of $HOME

Status in xdg-user-dirs package in Ubuntu:
  Fix Released
Status in xdg-user-dirs source package in Xenial:
  Fix Committed

Bug description:
  [ Impact ]

  When setting an user dir to a folder that is subfolder of $HOME (and
  when $HOME does not match the /etc/passwd defined home for the user),
  the ~/.config/user-dirs.dirs is wrongly generated.

  [ Test case ]

   1) env HOME=/tmp/temp-home xdg-user-dirs-update
   2) find /tmp/temp-home/
   3) should list generated XDG user directories
   4) /tmp/temp-home/.config/user-dirs.dirs should mention them

  Launching something like:
   - env HOME=/tmp/temp-home ./xdg-user-dirs-update --set DOWNLOADS 
"/tmp/temp-home/sub/folder/of/it/Downloads"

  Should modify /tmp/temp-home/.config/user-dirs.dirs so that it contains:
XDG_DOWNLOADS_DIR="$HOME/sub/folder/of/it/Downloads"

  [ Regression potential ]

  Xdg folders could be generated in wrong locations.

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

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

This is a command-line that is useful for manually exercising the
org.bluez DBus activiation. It might reproduce the timeout or otherwise
give useful clues. Command should be all on one line (ignore Launchpad
line wrapping):

dbus-send --system --print-reply --dest=org.bluez /
org.freedesktop.DBus.ObjectManager.GetManagedObjects

I won't reproduce the entire output here but this is the initial part
when a BT hci device is available:

method return time=1522790434.404190 sender=:1.2 -> destination=:1.399 
serial=821 reply_serial=2
   array [
  dict entry(
 object path "/org/bluez"
 array [
dict entry(
   string "org.freedesktop.DBus.Introspectable"
   array [
   ]
)
dict entry(
   string "org.bluez.AgentManager1"
   array [
   ]
)
dict entry(
   string "org.bluez.ProfileManager1"
   array [
   ]
)
 ]
  )
  dict entry(
 object path "/org/bluez/hci0"

-- 
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 1760661] Re: Chromium and Chrome pausing

It happened from the moment after launching the first time in Chromium
and Chrome.  Deb and snap both.  After happening for three days, today
it stopped and is working fine...  I will reinstall from the Deb and see
if that is working now...  Thanks.

-- 
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 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-03 Thread TJ

The Dbus bluze system config doesn't run, it has "Exec=/bin/false" --
/usr/share/dbus-1/system-services/org.bluez.service It's left to systemd
to activate it via /lib/systemd/system/bluetooth.service

[Unit]
Description=Bluetooth service
Documentation=man:bluetoothd(8)
ConditionPathIsDirectory=/sys/class/bluetooth

[Service]
Type=dbus
BusName=org.bluez
ExecStart=/usr/lib/bluetooth/bluetoothd
NotifyAccess=main
#WatchdogSec=10
#Restart=on-failure
CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_BIND_SERVICE
LimitNPROC=1
ProtectHome=true
ProtectSystem=full

[Install]
WantedBy=bluetooth.target
Alias=dbus-org.bluez.service

I would suspect if there are no BT hci devices then bluetooth.service
won't run.

So the question is, are the other flavours doing something to allow a
'dummy' BT device so bluetooth service runs and org.bluez is available
or is it that their Bluetooth tooling isn't calling the DBus interface
at all (using libbluetooth directly maybe) ?

-- 
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 1760444] Re: Snap core version 16-2.31.2 fails to open window with nvidia drivers

2018-04-03 Thread Doug McMahon

ok, setting bug to snapd, fix is update current snap core to beta or
better.

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

** Summary changed:

- Snap core version 16-2.31.2 fails to open window with nvidia drivers
+ Snap core version 16-2.31.2 fails to open chromium window with nvidia drivers

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

Title:
  Snap core version 16-2.31.2 fails to open chromium window with nvidia
  drivers

Status in chromium-browser package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  New

Bug description:
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: canonical
  contact:   https://forum.snapcraft.io/
  license:   unknown
  description: |
    An open-source browser project that aims to build a safer, faster, and more
    stable way for all Internet users to experience the web.
  commands:
    - chromium
  snap-id:   XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking:  beta
  refreshed: 2018-03-29T11:56:58-04:00
  installed:   65.0.3325.181 (270) 144MB -
  channels:
    stable:65.0.3325.181 (266) 138MB -
    candidate: 65.0.3325.181 (270) 144MB -
    beta:  ↑
    edge:  ↑

  Happens with all versions.

  Graphics:
Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller 
driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0416 
Card-2: NVIDIA GK107M [GeForce GT 755M] driver: nvidia v: 390.42 
bus ID: 01:00.0 chip ID: 10de:0fcd 
Display Server: x11 (X.Org 1.19.6) driver: modesetting,nvidia 
unloaded: fbdev,nouveau,vesa compositor: gnome-shell 
resolution: 1920x1080~60Hz 
OpenGL: renderer: GeForce GT 755M/PCIe/SSE2 v: 4.6.0 NVIDIA 390.42 
direct render: Yes 

  
  doug@doug-Lenovo-IdeaPad-Y510P:~$ snap run chromium
  Gtk-Message: Failed to load module "canberra-gtk-module"
  Gtk-Message: Failed to load module "canberra-gtk-module"
  Gkr-Message: secret service operation failed: An AppArmor policy prevents 
this sender from sending this message to this recipient; type="method_call", 
sender=":1.93" (uid=1000 pid=6866 
comm="/snap/chromium/270/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=5817 
comm="/usr/bin/gnome-keyring-daemon --daemonize --login " label="unconfined")
  ATTENTION: default value of option force_s3tc_enable overridden by 
environment.
  libGL error: No matching fbConfigs or visuals found
  libGL error: failed to load driver: swrast
  [7175:7175:0401/105124.319419:ERROR:gl_context_glx.cc(227)] Couldn't make 
context current with X drawable.
  [7175:7175:0401/105124.319444:ERROR:gpu_info_collector.cc(62)] 
gl::GLContext::MakeCurrent() failed
  Gkr-Message: secret service operation failed: An AppArmor policy prevents 
this sender from sending this message to this recipient; type="method_call", 
sender=":1.93" (uid=1000 pid=6866 
comm="/snap/chromium/270/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=5817 comm="/usr/bin/gnome-keyring-daemon --daemonize --login " 
label="unconfined")

  screenshot attached

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

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

[Desktop-packages] [Bug 1758306] Re: Cannot switch mouse primary button in GCC

Gunnar I'm on Xorg Vanilla-Gnome-Session. Jeremy had mentioned a few
weeks back that he needed testing on 'vanilla-gnome-session'(thats an
installable package, Gunnar) so I installed and am reporting bugs on it.
Hope this clears up any misunderstanding. Cheers.

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

Title:
  Cannot switch mouse primary button in GCC

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

Bug description:
  Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured 
for left handed use. That is the mouse primary button being switched to the 
right. GCC doesn't seem to work for this now. I don't know if it's related to 
evdev or what.
  Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 23 07:07:02 2018
  InstallationDate: Installed on 2018-01-19 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Desktop-packages] [Bug 1758306] Re: Cannot switch mouse primary button in GCC

No Vanilla Gnome means 'Vanilla-Gnome-Session'.

On Tue, Apr 3, 2018 at 4:39 PM Stephen 
wrote:

> Well I'm using bare metal and my ~/home is in good shape, from backups.
> In  terms of my system I'm running a vanilla Ubuntu-Gnome and the reason
> it's not in 'Good Shape' is Ubuntu bugs. ;-) quite Frankly!
> Are you running your instance on bare metal or emulation?
>
> On Tue, Apr 3, 2018 at 3:11 PM Gunnar Hjalmarsson <
> 1758...@bugs.launchpad.net> wrote:
>
>> My 'problem' is that I can't reproduce the issue.
>>
>> You now mentioned a few things, which indicate that your system isn't in
>> the best shape.
>>
>> While I have tested this on "Ubuntu with Xorg", you mentioned that you
>> use "vanilla GNOME" (I suppose that vanilla GNOME means Wayland). Any
>> chance you can log in to an "Ubuntu with Xorg" session and check if the
>> problem is present for you there?
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1758306
>>
>> Title:
>>   Cannot switch mouse primary button in GCC
>>
>> Status in gnome-control-center package in Ubuntu:
>>   Incomplete
>>
>> Bug description:
>>   Prior to yesterday's (March 22/18) Bionic update, I had my mouse
>> configured for left handed use. That is the mouse primary button being
>> switched to the right. GCC doesn't seem to work for this now. I don't know
>> if it's related to evdev or what.
>>   Held back reporting this in case it was fixed by changes overnight.
>> Updated this morning and problem persists.
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 18.04
>>   Package: gnome-control-center 1:3.28.0-0ubuntu3
>>   ProcVersionSignature: Ubuntu
>> 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
>>   Uname: Linux 4.13.0-36201803011620-generic x86_64
>>   ApportVersion: 2.20.8-0ubuntu10
>>   Architecture: amd64
>>   CurrentDesktop: GNOME
>>   Date: Fri Mar 23 07:07:02 2018
>>   InstallationDate: Installed on 2018-01-19 (62 days ago)
>>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
>> (20170920)
>>   SourcePackage: gnome-control-center
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>
>> To manage notifications about this bug go to:
>>
>> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1758306/+subscriptions
>>
> --
>
> This email is printed from 100% recycled electrons.
>
-- 

This email is printed from 100% recycled electrons.

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

Title:
  Cannot switch mouse primary button in GCC

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

Bug description:
  Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured 
for left handed use. That is the mouse primary button being switched to the 
right. GCC doesn't seem to work for this now. I don't know if it's related to 
evdev or what.
  Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 23 07:07:02 2018
  InstallationDate: Installed on 2018-01-19 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Desktop-packages] [Bug 1758306] Re: Cannot switch mouse primary button in GCC

Well I'm using bare metal and my ~/home is in good shape, from backups. In
terms of my system I'm running a vanilla Ubuntu-Gnome and the reason it's
not in 'Good Shape' is Ubuntu bugs. ;-) quite Frankly!
Are you running your instance on bare metal or emulation?

On Tue, Apr 3, 2018 at 3:11 PM Gunnar Hjalmarsson <
1758...@bugs.launchpad.net> wrote:

> My 'problem' is that I can't reproduce the issue.
>
> You now mentioned a few things, which indicate that your system isn't in
> the best shape.
>
> While I have tested this on "Ubuntu with Xorg", you mentioned that you
> use "vanilla GNOME" (I suppose that vanilla GNOME means Wayland). Any
> chance you can log in to an "Ubuntu with Xorg" session and check if the
> problem is present for you there?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1758306
>
> Title:
>   Cannot switch mouse primary button in GCC
>
> Status in gnome-control-center package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Prior to yesterday's (March 22/18) Bionic update, I had my mouse
> configured for left handed use. That is the mouse primary button being
> switched to the right. GCC doesn't seem to work for this now. I don't know
> if it's related to evdev or what.
>   Held back reporting this in case it was fixed by changes overnight.
> Updated this morning and problem persists.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-control-center 1:3.28.0-0ubuntu3
>   ProcVersionSignature: Ubuntu
> 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
>   Uname: Linux 4.13.0-36201803011620-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Fri Mar 23 07:07:02 2018
>   InstallationDate: Installed on 2018-01-19 (62 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170920)
>   SourcePackage: gnome-control-center
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1758306/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.

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

Title:
  Cannot switch mouse primary button in GCC

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

Bug description:
  Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured 
for left handed use. That is the mouse primary button being switched to the 
right. GCC doesn't seem to work for this now. I don't know if it's related to 
evdev or what.
  Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 23 07:07:02 2018
  InstallationDate: Installed on 2018-01-19 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1760982] Re: gnome-shell crashed with signal 5 in g_log_default_handler() after I tried to reinstall Windows on dual boot

*** 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/1760982/+attachment/5100329/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1760982/+attachment/5100338/+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/1760982

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()
  after I tried to reinstall Windows on dual boot

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I hve windows on dual boot; wanted to come back to windows 7 ; went
  through the process, it couldn't finish after the reboot (probably
  because ubuntu is on dual boot), then got this when I went back to
  ubuntu

  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: Tue Apr  3 21:45:39 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-11-11 (143 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.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: Upgraded to bionic on 2018-03-28 (5 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1760947] Re: package firefox-locale-en 58.0.2+build1-0ubuntu0.17.10.1 failed to install/upgrade: underproces dpkg-deb --fsys-tarfile returnerede afslutningsstatus 2

2018-04-03 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

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

** Tags added: fsys-tarfile-error

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

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

Title:
  package firefox-locale-en 58.0.2+build1-0ubuntu0.17.10.1 failed to
  install/upgrade: underproces dpkg-deb --fsys-tarfile returnerede
  afslutningsstatus 2

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Failed during update

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: firefox-locale-en 58.0.2+build1-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.7-0ubuntu3.7
  AptOrdering:
   firefox-locale-en:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  BuildID: 20180326160923
  Channel: Unavailable
  Date: Tue Apr  3 19:33:47 2018
  Dependencies:
   
  DpkgTerminalLog:
   Gør klar til at udpakke 
.../firefox-locale-en_59.0.2+build1-0ubuntu0.17.10.1_amd64.deb ...
   Udpakker firefox-locale-en (59.0.2+build1-0ubuntu0.17.10.1) over 
(58.0.2+build1-0ubuntu0.17.10.1) ...
   dpkg-deb: fejl: kunne ikke læse arkivet 
'/var/cache/apt/archives/firefox-locale-en_59.0.2+build1-0ubuntu0.17.10.1_amd64.deb':
 Ingen sådan fil eller filkatalog
   dpkg: fejl under behandling af arkivet 
/var/cache/apt/archives/firefox-locale-en_59.0.2+build1-0ubuntu0.17.10.1_amd64.deb
 (--unpack):
underproces dpkg-deb --fsys-tarfile returnerede afslutningsstatus 2
  ErrorMessage: underproces dpkg-deb --fsys-tarfile returnerede 
afslutningsstatus 2
  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 2016-10-31 (518 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
   default via 192.168.1.1 dev enp3s0 proto static metric 100 
   169.254.0.0/16 dev enp3s0 scope link metric 1000 
   192.168.1.0/24 dev enp3s0 proto kernel scope link src 192.168.1.35 metric 100
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  Plugins:
   VLC Web Plugin - /usr/lib/mozilla/plugins/libvlcplugin.so
   iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so
   Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=47.0/20160606113944 (Out of date)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  Title: package firefox-locale-en 58.0.2+build1-0ubuntu0.17.10.1 failed to 
install/upgrade: underproces dpkg-deb --fsys-tarfile returnerede 
afslutningsstatus 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.30
  dmi.board.name: Z77 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd04/18/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4:rvr:cvnToBeFilledByO.E.M.: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: To Be Filled By O.E.M.

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

[Desktop-packages] [Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

2018-04-03 Thread Balint Reczey

@jarnos Verification is needed only for update-manager for now, thus I
think you verified that the fix worked for Xenial. Could you please
change the tag to reflect that or you would like to wait for the u-u
fix, - which may come later?

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Xenial:
  Fix Committed
Status in apt source package in Artful:
  Confirmed
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  In Progress
Status in update-manager source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

     sudo apt-get install -y --allow-downgrades ca-
  certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

    sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades, the fix comes in an update of u-u) Run
  unattended-upgrades manually and observe the removal of the
  autoremovable kernel packages:

    sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]

  The unattended-upgrades fix is uploaded with many other fixes and
  those may cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1748876] Re: One by Wacom (medium tablet) not reported by libwacom

2018-04-03 Thread Timo Aaltonen

bionic has libwacom 0.29-1

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

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

Title:
  One by Wacom (medium tablet) not reported by libwacom

Status in libwacom package in Ubuntu:
  Fix Released

Bug description:
  uname -r 
  4.4.0-98-generic

  
  lsusb
  Bus 001 Device 013: ID 056a:037b Wacom Co., Ltd
  xsetwacom --list devices
  #null output
  /usr/bin/libwacom-list-local-devices
  #always the same output regardless connected tablet or not
  [Device]
  Name=Wacom Serial Tablet WACf004
  DeviceMatch=serial::;
  Class=ISDV4
  Width=0
  Height=0
  IntegratedIn=Display;System;
  Styli=0xf;0xe;

  [Features]
  Reversible=false
  Stylus=true
  Ring=false
  Ring2=false
  Touch=false
  TouchSwitch=false
  StatusLEDs=
  NumStrips=0
  Buttons=0

  dmesg

  [15336.978171] usb 1-1.1: new full-speed USB device number 13 using ehci-pci
  [15337.076227] usb 1-1.1: New USB device found, idVendor=056a, idProduct=037b
  [15337.076239] usb 1-1.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [15337.076244] usb 1-1.1: Product: CTL-672
  [15337.076249] usb 1-1.1: Manufacturer: Wacom Co.,Ltd.
  [15337.076253] usb 1-1.1: SerialNumber: 7HE00M100462
  [15337.145463] wacom: module verification failed: signature and/or required 
key missing - tainting kernel
  [15337.147120] input: Wacom CTL-672 Pen as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/0003:056A:037B.0003/input/input41
  [15337.147324] wacom 0003:056A:037B.0003: hidraw2: USB HID v1.10 Mouse [Wacom 
Co.,Ltd. CTL-672] on usb-:00:1a.0-1.1/input0
  [15337.147424] wacom 0003:056A:037B.0004: Unknown device_type for 'Wacom 
Co.,Ltd. CTL-672'. Ignoring.

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

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

It happened from the moment after launching the first time in Chromium
and Chrome.  Deb and snap both.  After happening for three days, today
it stopped and is working fine...  I will reinstall from the Deb and see
if that is working now...  Thanks.

-- 
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 1760977] Re: evolution-calendar-factory-subprocess crashed with SIGSEGV in g_main_context_ref()

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

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 #1744818, 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/1760977/+attachment/5100292/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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 evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1760977

Title:
  evolution-calendar-factory-subprocess crashed with SIGSEGV in
  g_main_context_ref()

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  This crashed in the background.  I do not know additional details
  other than what is included in the automatic report.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: evolution-data-server 3.28.0-2ubuntu2
  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: MATE
  Date: Tue Apr  3 14:45:01 2018
  ExecutablePath: /usr/lib/evolution/evolution-calendar-factory-subprocess
  InstallationDate: Installed on 2018-02-22 (40 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180221)
  ProcCmdline: /usr/lib/evolution/evolution-calendar-factory-subprocess 
--factory all --bus-name 
org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx2636x2 --own-path 
/org/gnome/evolution/dataserver/Subprocess/Backend/Calendar/2636/2
  ProcEnviron:
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7fadad17d767 :lock 
addl $0x1,(%rdx)
   PC (0x7fadad17d767) ok
   source "$0x1" ok
   destination "(%rdx)" (0x7fadac0ef978) in non-writable VMA region: 
0x7fadac057000-0x7fadac124000 r-xp 
/usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1.8.0
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing VMA /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1.8.0
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_main_context_ref () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   soup_socket_new () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
  Title: evolution-calendar-factory-subprocess crashed with SIGSEGV in 
g_main_context_ref()
  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/ubuntu/+source/evolution-data-server/+bug/1760977/+subscriptions

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

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

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

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 #1724439, 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/1760969/+attachment/5100264/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1724439
   gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from 
ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from 
function_call()

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

Title:
  gnome-shell crashed with SIGSEGV in meta_window_get_monitor()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  this occurs on a system that has DisplayPort 1.2 daisy-chained
  monitors, that are connected via a DisplayPort 1.2 compliant KVM
  switch. Crashes usually occur at the moment the switch disconnects the
  monitor chain, or restores the monitor chain, at which time the KVM
  may be suddenly reporting unusual resolutions for the DP monitor(s).

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.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
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 10:38:54 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['harddisk...@bijidroid.gmail.com']"
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'org.gnome.Terminal.desktop', 'thunderbird.desktop', 'google-chrome.desktop']"
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-10-05 (545 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fe9c42f72d4 :mov
0x18(%rax),%eax
   PC (0x7fe9c42f72d4) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_window_get_monitor () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/libgjs.so.0
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
  UpgradeStatus: Upgraded to artful on 2017-10-23 (162 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark

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

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

[Desktop-packages] [Bug 1760966] [NEW] Cannot modify group members of existing group containing underscore.

2018-04-03 Thread Kyle Horodyski

Public bug reported:

I have 2 user accounts on my system:
  1: user
  2: user_name

I want to add them to each other's groups so that by default they can
always modify each others files.

When trying to modify group "user_name"'s properties in the users admin
application, clicking OK gives me a popup window with the message:

"Group name has invalid characters 
Please set a valid group name consisting of a lower case letter followed by 
lower case letters and numbers.".

As the group name already exists and can't be changed from its
properties window this seems like a contradiction.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-system-tools 3.0.0-4ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-116.140-lowlatency 4.4.98
Uname: Linux 4.4.0-116-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: LXDE
Date: Tue Apr  3 14:58:25 2018
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/users-admin
InstallationDate: Installed on 2018-03-04 (30 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-system-tools
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  Cannot modify group members of existing group containing underscore.

Status in gnome-system-tools package in Ubuntu:
  New

Bug description:
  I have 2 user accounts on my system:
1: user
2: user_name

  I want to add them to each other's groups so that by default they can
  always modify each others files.

  When trying to modify group "user_name"'s properties in the users
  admin application, clicking OK gives me a popup window with the
  message:

  "Group name has invalid characters 
  Please set a valid group name consisting of a lower case letter followed by 
lower case letters and numbers.".

  As the group name already exists and can't be changed from its
  properties window this seems like a contradiction.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-system-tools 3.0.0-4ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-116.140-lowlatency 4.4.98
  Uname: Linux 4.4.0-116-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Tue Apr  3 14:58:25 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/users-admin
  InstallationDate: Installed on 2018-03-04 (30 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-system-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1721637] Re: can't open system settings(Ubuntu 17.10), icon is visible but settings don't display

2018-04-03 Thread Michael Rowland Hunter

** Summary changed:

- can't open  system settings(Ubuntu 17.10), icon is visible but  settings 
don't dislay
+ can't open  system settings(Ubuntu 17.10), icon is visible but  settings 
don't display

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

Title:
  can't open  system settings(Ubuntu 17.10), icon is visible but
  settings don't display

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

Bug description:
  When i click on system settings, icon is displaying but settings
  window doesn't visible. I have already reinstalled ubuntu desktop and
  gnome-control-center, but without any success.(reboot also didn't
  help).If i try to open gnome-control-center in terminal the same
  result only icon appearce

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

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

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

2018-04-03 Thread franck

What happened to this bug? Is it still being addressed? I'm also experiencing 
the same problem and the solutions above don't work for me :(

Ubuntu 16.04.4 LTS
NetworkManager 1.2.6
dnsmasq 2.76

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

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

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

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

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

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

  =

  Test steps / result:

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

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

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

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

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

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

  =

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

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

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

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

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

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

  =

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

  =

  Thanks

  Lukas

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

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

[Desktop-packages] [Bug 1758306] Re: Cannot switch mouse primary button in GCC

My 'problem' is that I can't reproduce the issue.

You now mentioned a few things, which indicate that your system isn't in
the best shape.

While I have tested this on "Ubuntu with Xorg", you mentioned that you
use "vanilla GNOME" (I suppose that vanilla GNOME means Wayland). Any
chance you can log in to an "Ubuntu with Xorg" session and check if the
problem is present for you there?

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

Title:
  Cannot switch mouse primary button in GCC

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

Bug description:
  Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured 
for left handed use. That is the mouse primary button being switched to the 
right. GCC doesn't seem to work for this now. I don't know if it's related to 
evdev or what.
  Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 23 07:07:02 2018
  InstallationDate: Installed on 2018-01-19 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

*** 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/1760959/+attachment/5100234/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1760959/+attachment/5100243/+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 

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  SMBIOS 2.8 present.

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
Manufacturer: Dell Inc.
Product Name: Vostro 3458
Version: 01
Serial Number: F792D72
UUID: 4C4C4544-0037-3910-8032-C6C04F443732
Wake-up Type: Power Switch
SKU Number: Vostro 3458
Family: Not Specified

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  Codename: bionic
  Linux matthew-Vostro-3458 4.15.0-14-generic #15-Ubuntu SMP Mon Apr 2 19:50:19 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  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: Tue Apr  3 14:36:29 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-02-09 (53 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.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/1760959/+subscriptions

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

[Desktop-packages] [Bug 1760887] Re: Copy not working

2018-04-03 Thread Egmont Koblinger

Sounds like dup of #1722121, fixed in Bionic.

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

Title:
  Copy not working

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Copying marked text sometimes does not work. It fails for keyboard
  shortcut, main menu, and right click menu. Paste seems to work.

  Ubuntu 17.10

  gnome-terminal:
Installed: 3.24.2-0ubuntu4
Candidate: 3.24.2-0ubuntu4
Version table:
   *** 3.24.2-0ubuntu4 500
  500 http://au.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  (Hey, copy worked for the above text!)

  What should happen: the text is copied to a clipboard.
  What happened: nothing. Paste pasted the previous contents of the clipboard.

  The fault is NOT intermittent. If I do this: cat ~/.profile and the try to 
  copy the last line (excluding the leading #) then the text is sometimes 
copied:

  # . /home/skaller/.opam/opam-init/init.sh > /dev/null 2> /dev/null ||
  true

  Note, the above text was copied .. this time. However when it fails,
  it fails repeatedly.

  This is a critical bug. The terminal is more or less useless without a
  correctly operating copy function.

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

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

[Desktop-packages] [Bug 1760959] [NEW] gnome-shell crashed with signal 5 in g_log_default_handler()

2018-04-03 Thread Matthew Courchesne

Public bug reported:

SMBIOS 2.8 present.

Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Dell Inc.
Product Name: Vostro 3458
Version: 01
Serial Number: F792D72
UUID: 4C4C4544-0037-3910-8032-C6C04F443732
Wake-up Type: Power Switch
SKU Number: Vostro 3458
Family: Not Specified

No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Bionic Beaver (development branch)
Release:18.04
Codename:   bionic
Linux matthew-Vostro-3458 4.15.0-14-generic #15-Ubuntu SMP Mon Apr 2 19:50:19 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

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: Tue Apr  3 14:36:29 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 
InstallationDate: Installed on 2018-02-09 (53 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.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:

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


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

** Information type changed from Private to Public

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  SMBIOS 2.8 present.

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
Manufacturer: Dell Inc.
Product Name: Vostro 3458
Version: 01
Serial Number: F792D72
UUID: 4C4C4544-0037-3910-8032-C6C04F443732
Wake-up Type: Power Switch
SKU Number: Vostro 3458
Family: Not Specified

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  Codename: bionic
  Linux matthew-Vostro-3458 4.15.0-14-generic #15-Ubuntu SMP Mon Apr 2 19:50:19 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  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: Tue Apr  3 14:36:29 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-02-09 (53 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.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/1760959/+subscriptions

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

[Desktop-packages] [Bug 1760201] ProcEnviron.txt

2018-04-03 Thread Ahmet Aksoy

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1760201/+attachment/5100230/+files/ProcEnviron.txt

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

Title:
  ubuntu 18.04 GDM - missing icons and letters

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 18.04(Updated 30.03.2018)
  System Language: Turkish
  Please check screenshots
  --- 
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-24 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180324)
  Package: gnome-shell
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1760201] Re: ubuntu 18.04 GDM - missing icons and letters

2018-04-03 Thread Ahmet Aksoy

apport information

** Tags added: apport-collected bionic

** Description changed:

  Ubuntu 18.04(Updated 30.03.2018)
  System Language: Turkish
  Please check screenshots
+ --- 
+ ApportVersion: 2.20.9-0ubuntu2
+ Architecture: amd64
+ CurrentDesktop: GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-03-24 (9 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180324)
+ Package: gnome-shell
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
+ Tags:  bionic
+ Uname: Linux 4.15.0-13-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1760201/+attachment/5100228/+files/Dependencies.txt

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

Title:
  ubuntu 18.04 GDM - missing icons and letters

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 18.04(Updated 30.03.2018)
  System Language: Turkish
  Please check screenshots
  --- 
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-24 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180324)
  Package: gnome-shell
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1760201] ProcCpuinfoMinimal.txt

2018-04-03 Thread Ahmet Aksoy

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1760201/+attachment/5100229/+files/ProcCpuinfoMinimal.txt

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

Title:
  ubuntu 18.04 GDM - missing icons and letters

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 18.04(Updated 30.03.2018)
  System Language: Turkish
  Please check screenshots
  --- 
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-24 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180324)
  Package: gnome-shell
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1747702] Re: gnome-software assert failure: * Error in `/usr/bin/gnome-software': realloc(): invalid old size: 0x00007f7381cda4b0 *

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

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

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

Title:
  gnome-software assert failure: *** Error in `/usr/bin/gnome-software':
  realloc(): invalid old size: 0x7f7381cda4b0 ***

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Software app terminates while installing Atom
  starting Atom leeds to crash
  I am trying to solve the problem using the bash

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.26.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/bin/gnome-software': realloc(): invalid 
old size: 0x7f7381cda4b0 ***
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  6 16:42:52 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-01-31 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180129)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.5-1ubuntu1
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-software
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f73b48b04e8 
"*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (action=, str=0x7f73b48acf23 "realloc(): 
invalid old size", ptr=, ar_ptr=) at malloc.c:5425
   _int_realloc (av=av@entry=0x7f738020, oldp=oldp@entry=0x7f7381cda4a0, 
oldsize=oldsize@entry=724235115076526096, nb=nb@entry=2177745088) at 
malloc.c:4574
   __GI___libc_realloc (oldmem=0x7f7381cda4b0, bytes=2177745072) at 
malloc.c:3245
   g_realloc () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-software assert failure: *** Error in `/usr/bin/gnome-software': 
realloc(): invalid old size: 0x7f7381cda4b0 ***
  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-software/+bug/1747702/+subscriptions

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

[Desktop-packages] [Bug 1748876] Re: One by Wacom (medium tablet) not reported by libwacom

2018-04-03 Thread Jason Gerecke

In addition to the Linux 4.16 requirement pointed out by Michael, Ubuntu
will need to update libwacom to at least version 0.28 for the device to
appear in the control panel.

Until Ubuntu includes updates, you can build libwacom from source[1][2]
as well as get the "input-wacom" kernel backports (version 0.39.0 added
support for these devices)[3][4].

[1]: https://github.com/linuxwacom/libwacom/releases
[2]: https://github.com/linuxwacom/libwacom/wiki
[3]: https://github.com/linuxwacom/input-wacom/releases
[4]: 
https://github.com/linuxwacom/input-wacom/wiki/Installing-input-wacom-from-source

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

Title:
  One by Wacom (medium tablet) not reported by libwacom

Status in libwacom package in Ubuntu:
  New

Bug description:
  uname -r 
  4.4.0-98-generic

  
  lsusb
  Bus 001 Device 013: ID 056a:037b Wacom Co., Ltd
  xsetwacom --list devices
  #null output
  /usr/bin/libwacom-list-local-devices
  #always the same output regardless connected tablet or not
  [Device]
  Name=Wacom Serial Tablet WACf004
  DeviceMatch=serial::;
  Class=ISDV4
  Width=0
  Height=0
  IntegratedIn=Display;System;
  Styli=0xf;0xe;

  [Features]
  Reversible=false
  Stylus=true
  Ring=false
  Ring2=false
  Touch=false
  TouchSwitch=false
  StatusLEDs=
  NumStrips=0
  Buttons=0

  dmesg

  [15336.978171] usb 1-1.1: new full-speed USB device number 13 using ehci-pci
  [15337.076227] usb 1-1.1: New USB device found, idVendor=056a, idProduct=037b
  [15337.076239] usb 1-1.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [15337.076244] usb 1-1.1: Product: CTL-672
  [15337.076249] usb 1-1.1: Manufacturer: Wacom Co.,Ltd.
  [15337.076253] usb 1-1.1: SerialNumber: 7HE00M100462
  [15337.145463] wacom: module verification failed: signature and/or required 
key missing - tainting kernel
  [15337.147120] input: Wacom CTL-672 Pen as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/0003:056A:037B.0003/input/input41
  [15337.147324] wacom 0003:056A:037B.0003: hidraw2: USB HID v1.10 Mouse [Wacom 
Co.,Ltd. CTL-672] on usb-:00:1a.0-1.1/input0
  [15337.147424] wacom 0003:056A:037B.0004: Unknown device_type for 'Wacom 
Co.,Ltd. CTL-672'. Ignoring.

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

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

[Desktop-packages] [Bug 1760947] [NEW] package firefox-locale-en 58.0.2+build1-0ubuntu0.17.10.1 failed to install/upgrade: underproces dpkg-deb --fsys-tarfile returnerede afslutningsstatus 2

2018-04-03 Thread Tom Rausner

Public bug reported:

Failed during update

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: firefox-locale-en 58.0.2+build1-0ubuntu0.17.10.1
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.7-0ubuntu3.7
AptOrdering:
 firefox-locale-en:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
BuildID: 20180326160923
Channel: Unavailable
Date: Tue Apr  3 19:33:47 2018
Dependencies:
 
DpkgTerminalLog:
 Gør klar til at udpakke 
.../firefox-locale-en_59.0.2+build1-0ubuntu0.17.10.1_amd64.deb ...
 Udpakker firefox-locale-en (59.0.2+build1-0ubuntu0.17.10.1) over 
(58.0.2+build1-0ubuntu0.17.10.1) ...
 dpkg-deb: fejl: kunne ikke læse arkivet 
'/var/cache/apt/archives/firefox-locale-en_59.0.2+build1-0ubuntu0.17.10.1_amd64.deb':
 Ingen sådan fil eller filkatalog
 dpkg: fejl under behandling af arkivet 
/var/cache/apt/archives/firefox-locale-en_59.0.2+build1-0ubuntu0.17.10.1_amd64.deb
 (--unpack):
  underproces dpkg-deb --fsys-tarfile returnerede afslutningsstatus 2
ErrorMessage: underproces dpkg-deb --fsys-tarfile returnerede afslutningsstatus 
2
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 2016-10-31 (518 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
IpRoute:
 default via 192.168.1.1 dev enp3s0 proto static metric 100 
 169.254.0.0/16 dev enp3s0 scope link metric 1000 
 192.168.1.0/24 dev enp3s0 proto kernel scope link src 192.168.1.35 metric 100
IwConfig:
 lono wireless extensions.
 
 enp3s0no wireless extensions.
Locales: extensions.sqlite corrupt or missing
Plugins:
 VLC Web Plugin - /usr/lib/mozilla/plugins/libvlcplugin.so
 iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so
 Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=47.0/20160606113944 (Out of date)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
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
RfKill:
 
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
Title: package firefox-locale-en 58.0.2+build1-0ubuntu0.17.10.1 failed to 
install/upgrade: underproces dpkg-deb --fsys-tarfile returnerede 
afslutningsstatus 2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/18/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.30
dmi.board.name: Z77 Extreme4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd04/18/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4:rvr:cvnToBeFilledByO.E.M.: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: To Be Filled By O.E.M.

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


** Tags: amd64 apport-package artful

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

Title:
  package firefox-locale-en 58.0.2+build1-0ubuntu0.17.10.1 failed to
  install/upgrade: underproces dpkg-deb --fsys-tarfile returnerede
  afslutningsstatus 2

Status in firefox package in Ubuntu:
  New

Bug description:
  Failed during update

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: firefox-locale-en 58.0.2+build1-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.7-0ubuntu3.7
  AptOrdering:
   firefox-locale-en:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  BuildID: 20180326160923
  Channel: Unavailable
  Date: Tue Apr  3 19:33:47 2018
  Dependencies:
   
  DpkgTerminalLog:
   Gør klar til at udpakke 
.../firefox-locale-en_59.0.2+build1-0ubuntu0.17.10.1_amd64.deb ...
   Udpakker firefox-locale-en (59.0.2+build1-0ubuntu0.17.10.1) over 
(58.0.2+build1-0ubuntu0.17.10.1) ...
   dpkg-deb: fejl: kunne ikke læse arkivet 
'/var/cache/apt/archives/firefox-locale-en_59.0.2+build1-0ubuntu0.17.10.1_amd64.deb':
 Ingen sådan fil eller filkatalog

[Desktop-packages] [Bug 1760941] Re: gvfsd-mtp crashed with SIGSEGV in g_vfs_job_run()

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

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 #1421050, 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/1760941/+attachment/5100162/+files/CoreDump.gz

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

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

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

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

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

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

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

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

Title:
  gvfsd-mtp crashed with SIGSEGV in g_vfs_job_run()

Status in gvfs package in Ubuntu:
  New

Bug description:
  Ocurred with samsung tablet SM-T585, running android 7.0

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gvfs-backends 1.36.0-1ubuntu1
  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: Tue Apr  3 19:31:29 2018
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2018-01-24 (68 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180121)
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.22 /org/gtk/gvfs/exec_spaw/7
  ProcEnviron:
   LANG=pl_PL.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f438052ce90:mov0x198(%rdx),%r10
   PC (0x7f438052ce90) ok
   source "0x198(%rdx)" (0x0198) not located in a known VMA region (needed 
readable region)!
   destination "%r10" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   g_vfs_job_run () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gvfsd-mtp crashed with SIGSEGV in g_vfs_job_run()
  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/gvfs/+bug/1760941/+subscriptions

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

[Desktop-packages] [Bug 1748876] Re: One by Wacom (medium tablet) not reported by libwacom

2018-04-03 Thread Michael

Looks like support was added in the following kernel patch and will be
available in kernel version 4.16:
https://patchwork.kernel.org/patch/10133291/

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

Title:
  One by Wacom (medium tablet) not reported by libwacom

Status in libwacom package in Ubuntu:
  New

Bug description:
  uname -r 
  4.4.0-98-generic

  
  lsusb
  Bus 001 Device 013: ID 056a:037b Wacom Co., Ltd
  xsetwacom --list devices
  #null output
  /usr/bin/libwacom-list-local-devices
  #always the same output regardless connected tablet or not
  [Device]
  Name=Wacom Serial Tablet WACf004
  DeviceMatch=serial::;
  Class=ISDV4
  Width=0
  Height=0
  IntegratedIn=Display;System;
  Styli=0xf;0xe;

  [Features]
  Reversible=false
  Stylus=true
  Ring=false
  Ring2=false
  Touch=false
  TouchSwitch=false
  StatusLEDs=
  NumStrips=0
  Buttons=0

  dmesg

  [15336.978171] usb 1-1.1: new full-speed USB device number 13 using ehci-pci
  [15337.076227] usb 1-1.1: New USB device found, idVendor=056a, idProduct=037b
  [15337.076239] usb 1-1.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [15337.076244] usb 1-1.1: Product: CTL-672
  [15337.076249] usb 1-1.1: Manufacturer: Wacom Co.,Ltd.
  [15337.076253] usb 1-1.1: SerialNumber: 7HE00M100462
  [15337.145463] wacom: module verification failed: signature and/or required 
key missing - tainting kernel
  [15337.147120] input: Wacom CTL-672 Pen as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/0003:056A:037B.0003/input/input41
  [15337.147324] wacom 0003:056A:037B.0003: hidraw2: USB HID v1.10 Mouse [Wacom 
Co.,Ltd. CTL-672] on usb-:00:1a.0-1.1/input0
  [15337.147424] wacom 0003:056A:037B.0004: Unknown device_type for 'Wacom 
Co.,Ltd. CTL-672'. Ignoring.

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

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

[Desktop-packages] [Bug 1748761] Re: "Open a New Private Window" Firefox Desktop Action is not translated into Czech language

Yay! :)

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

Title:
  "Open a New Private Window" Firefox Desktop Action is not translated
  into Czech language

Status in Ubuntu Translations:
  Fix Committed
Status in firefox package in Ubuntu:
  Fix Committed

Bug description:
  The "Open a New Private Window" Firefox Desktop Action is not
  translated into Czech language. The attached patch fixes this.

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

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

[Desktop-packages] [Bug 1760027] Re: system-config-printer.py crashed with NameError in /usr/share/system-config-printer/jobviewer.py: name 'Secret' is not defined

This bug was fixed in the package system-config-printer -
1.5.11-1ubuntu2

---
system-config-printer (1.5.11-1ubuntu2) bionic; urgency=low

  * Let the binary package system-config-printer-common depend
on gir1.2-secret-1 (LP: #1760027).

 -- Till Kamppeter   Tue,  3 Apr 2018 16:50:12
+0200

** Changed in: system-config-printer (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  system-config-printer.py crashed with NameError in /usr/share/system-
  config-printer/jobviewer.py: name 'Secret' is not defined

Status in system-config-printer package in Ubuntu:
  Fix Released
Status in system-config-printer source package in Bionic:
  Fix Released

Bug description:
  New error with 1.5.11-1ubuntu1

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
system-config-printer.  This problem was most recently seen with package 
version 1.5.11-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/75b6b655c24028fea9fef2b4f2bde9d4a134f3a8 
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/.

  Traceback
  Traceback (most recent call last):
    File "/usr/share/system-config-printer/system-config-printer.py", line 84, 
in 
  import jobviewer
    File "/usr/share/system-config-printer/jobviewer.py", line 76, in 
  NETWORK_PASSWORD = Secret.Schema.new("org.system.config.printer.store", 
Secret.SchemaFlags.NONE,
  NameError: name 'Secret' is not defined

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1760027/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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] [NEW] Sound not working on HP x2 10-p030nl - Realtek rt5640

2018-04-03 Thread Daniele Laudani

Public bug reported:

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

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


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

-- 
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:
  New

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 1748761] Re: "Open a New Private Window" Firefox Desktop Action is not translated into Czech language

2018-04-03 Thread AsciiWolf

Merged!

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

** Changed in: ubuntu-translations
   Status: New => Fix Committed

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

Title:
  "Open a New Private Window" Firefox Desktop Action is not translated
  into Czech language

Status in Ubuntu Translations:
  Fix Committed
Status in firefox package in Ubuntu:
  Fix Committed

Bug description:
  The "Open a New Private Window" Firefox Desktop Action is not
  translated into Czech language. The attached patch fixes this.

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

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

I have added a bunch of other affected packages, whose templates I
reactivated and where there is a need to add "X-Ubuntu-Use-Langpack:
yes". I also reactivated the templates for:

indicator-appmenu
indicator-keyboard
indicator-printers

which already have "X-Ubuntu-Use-Langpack: yes".

So now I'd say that the affected packages are ready to be uploaded. Hey
Simon, are you there? ;)

-- 
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 1760924] Re: gnome-shell crashed with signal 5

*** 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/1760924/+attachment/5100101/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1760924/+attachment/5100111/+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/1760924

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Crash while copying big files.

  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
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 17:48:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-03-11 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-shell
  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/libgio-2.0.so.0
   g_initable_new_valist () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_initable_new () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo

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

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

** Also affects: unity-lens-files (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity-lens-music (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity-lens-photos (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity-lens-video (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity-scope-calculator (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity-scope-devhelp (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity-scope-home (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity-scope-manpages (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-lens-files in Ubuntu.
Matching subscriptions: dp-unity-lens-files, dp-unity-lens-music, 
dp-unity-lens-music
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 1638983] Re: Boot splash with luks password prompt broken after nvidia upgrade to 367

2018-04-03 Thread Zurd

Bug still present, even if you do not see your password at the screen,
you can still type it in, press enter, then type your user's password if
you do not have auto-login, press enter, I've done it multiple times and
I was able to log in, the screen will stay black a long time.

After this, to patch the bug just run in terminal:
sudo sed -i -e '/s/quiet splash//g' /etc/default/grub

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

Title:
  Boot splash with luks password prompt broken after nvidia upgrade to
  367

Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Confirmed

Bug description:
  Just got the nvidia driver update from 361 to 367. Upon reboot, the
  boot splash (plymouth?) with the password prompt for the encrypted
  root is missing.

  The screen flashes dark purple and the switches to black with a
  blinking cursor echoing anything typed. Ctrl-alt-del reboots. Booting
  with kernel options "quiet splash" removed results in a text-mode boot
  process where the password prompt is present, proceeding normally.

  Wasn't sure if this was plymouth or nvidia issue, I'm guessing nvidia
  because that's what upgraded and broke functionality.

  Tried redoing update-grub and update-initramfs, didn't help. Found I
  had both nvidia-361 and nvidia-367 installed (why didn't -361
  uninstall?), but manually removing -361 (and redoing initramfs just in
  case) didn't change anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-367 367.57-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov  3 17:45:14 2016
  InstallationDate: Installed on 2016-07-23 (103 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: nvidia-graphics-drivers-367
  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-367/+bug/1638983/+subscriptions

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

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

*** 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/1760928/+attachment/5100137/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1760928/+attachment/5100146/+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/1760928

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  As per report.

  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
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Apr  2 23:05:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-30 (3 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.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/1760928/+subscriptions

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

[Desktop-packages] [Bug 1753367] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

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

** This bug has been marked a duplicate of bug 1747717
   package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers 
looping, abandoned - gnome-menus -> ufw

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

Title:
  package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
  triggers looping, abandoned

Status in gnome-menus package in Ubuntu:
  Confirmed

Bug description:
  installing 17.10 from 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gnome-menus 3.13.3-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sun Mar  4 23:23:34 2018
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2014-08-21 (1291 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2018-03-05 (0 days ago)

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

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

[Desktop-packages] [Bug 1756576] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

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

** This bug has been marked a duplicate of bug 1747717
   package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers 
looping, abandoned - gnome-menus -> ufw

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

Title:
  package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
  triggers looping, abandoned

Status in gnome-menus package in Ubuntu:
  Confirmed

Bug description:
  this error occurred when upgrading Ubntu16.04.4 -> 17.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gnome-menus 3.13.3-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sun Mar 18 03:09:47 2018
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2017-11-09 (128 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64(20160426.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.25
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2018-03-17 (0 days ago)

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

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

[Desktop-packages] [Bug 1756616] Re: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned

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

** This bug has been marked a duplicate of bug 1747717
   package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers 
looping, abandoned - gnome-menus -> ufw

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

Title:
  package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in gnome-menus package in Ubuntu:
  New

Bug description:
  upgrade to 18.04 under XFCE

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gnome-menus 3.13.3-11ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sat Mar 17 23:46:15 2018
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-09-02 (560 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  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: gnome-menus
  Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1758254] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

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

** This bug is no longer a duplicate of bug 1756576
   package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers 
looping, abandoned
** This bug has been marked a duplicate of bug 1747717
   package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers 
looping, abandoned - gnome-menus -> ufw

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

Title:
  package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
  triggers looping, abandoned

Status in bamf package in Ubuntu:
  New
Status in desktop-file-utils package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New
Status in gnome-menus package in Ubuntu:
  New
Status in mime-support package in Ubuntu:
  New

Bug description:
  i need help

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gnome-menus 3.13.3-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Mar 23 12:29:05 2018
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2017-11-21 (121 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2018-03-23 (0 days ago)

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

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

[Desktop-packages] [Bug 1760925] [NEW] CPU freezes when staring software manager

2018-04-03 Thread Thomas Terry

Public bug reported:

On a Pentium N3540, when trying to launch software install the entires
system freezes and a forced reboot is needed to restore the system. This
may be related to the bug that causes a Pentium CPU to freeze when
switching into power-save mode, but the Software Manager should not be
doing something that could crash the CPU. It could be caused by the fact
that the laptop does not have a graphics chip which could be causing the
software manager to call a rendering function that the CPU cannot
respond to.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-software 3.26.1-0ubuntu2.17.10.1
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Apr  3 11:26:15 2018
InstallationDate: Installed on 2018-03-26 (7 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.26.1-0ubuntu2.17.10.1
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  CPU freezes when staring software manager

Status in gnome-software package in Ubuntu:
  New

Bug description:
  On a Pentium N3540, when trying to launch software install the entires
  system freezes and a forced reboot is needed to restore the system.
  This may be related to the bug that causes a Pentium CPU to freeze
  when switching into power-save mode, but the Software Manager should
  not be doing something that could crash the CPU. It could be caused by
  the fact that the laptop does not have a graphics chip which could be
  causing the software manager to call a rendering function that the CPU
  cannot respond to.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.1-0ubuntu2.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Apr  3 11:26:15 2018
  InstallationDate: Installed on 2018-03-26 (7 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.1-0ubuntu2.17.10.1
  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/1760925/+subscriptions

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

[Desktop-packages] [Bug 1747717] Re: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned - gnome-menus -> ufw

I tried several times in different ways and couldn't reproduce it
either. Besides most recent duplicates in LP are 3 weeks old.

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

Title:
  package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade:
  triggers looping, abandoned - gnome-menus -> ufw

Status in dpkg package in Ubuntu:
  Invalid
Status in gnome-menus package in Ubuntu:
  Incomplete
Status in dpkg source package in Bionic:
  Invalid
Status in gnome-menus source package in Bionic:
  Incomplete

Bug description:
  using the bionic beaver version

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gnome-menus 3.13.3-11ubuntu1
  Uname: Linux 4.15.1-041501-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  Date: Tue Feb  6 23:00:47 2018
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu1
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

*** 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/1760922/+attachment/5100084/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1760922/+attachment/5100093/+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/1760922

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Gnome Shell crashed after screen look and unlock.

  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: Tue Apr  3 11:53:56 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-04-02 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  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:
   ?? () 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/1760922/+subscriptions

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

[Desktop-packages] [Bug 1759713] Re: xscreensaver eats keyboard-events after activation

2018-04-03 Thread sh-dvl

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

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

Title:
  xscreensaver eats keyboard-events after activation

Status in xscreensaver package in Ubuntu:
  New

Bug description:
  running xenial/16.04.3 with hwe-kernel with nomodeset (only
  possibility for this board with intel j4105) + -X11 with xfce.

  start remmina in either version (original-xenial, ppa and fresh from
  git) and start a rdp-session in fullscreen.

  wait for the time before xscreensaver blanks the screen.

  after that, mouse still works well, but no keys will be transferred.

  stopping xscreensaver will prevent any problem with keyboard (but let
  the screen unsaved)

  minimizing the rdp-session and then maximizing it again will also
  help, but it

  don't know, if any other applications have similar problems, because
  we use this system 99% as thin-client.

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

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

** Also affects: unity-greeter (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity-lens-applications (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
Matching subscriptions: dp-unity-lens-music
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

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

Re: [Desktop-packages] [Bug 498933] Re: Crash when restoring data KeyError

2018-04-03 Thread Kenneth Loafman

OK, this is an old bug.  The file list coming back from the remote is
truncated, however, I can clearly see vol43 in the list for
the 20171228T132324Z backup.  Very confusing.

Would you look on the remote manually and compare the number of files?  I'm
sure it is higher.


On Sun, Apr 1, 2018 at 10:41 AM, Václav Haisman 
wrote:

> Here is the result of `grep -C 10 "vol43\." deja-dup.log`. It is
> compressed because it is otherwise 5 MiB.
>
> ** Attachment added: "result of `grep -C 10 "vol43\." deja-dup.log`"
>https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/
> 498933/+attachment/5098011/+files/vol43.txt.xz
>
> --
> You received this bug notification because you are subscribed to
> Duplicity.
> https://bugs.launchpad.net/bugs/498933
>
> Title:
>   Crash when restoring data KeyError
>
> Status in Déjà Dup:
>   Invalid
> Status in Duplicity:
>   Confirmed
> Status in deja-dup package in Ubuntu:
>   Invalid
>
> Bug description:
>   Binary package hint: deja-dup
>
>   1) Ubuntu 9.10
>   2) Deja Dup 10.2-0ubuntu1.1
>   3) I expected my backup to be restored
>   4) Deja Dup crashed instead.
>
>   I just tried to restore the backup I made, and it crashes repeatedly
>   when trying to restore.
>
>   I have it setup to backup my home directory, and tried restoring to
>   both the original location as well as a completely different folder.
>   Both lead to the same error message.
>
>
>   Traceback (most recent call last):
> File "/usr/bin/duplicity", line 825, in 
>   with_tempdir(main)
> File "/usr/bin/duplicity", line 818, in with_tempdir
>   fn()
> File "/usr/bin/duplicity", line 775, in main
>   restore(col_stats)
> File "/usr/bin/duplicity", line 436, in restore
>   restore_get_patched_rop_iter(col_stats)):
> File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line
> 521, in Write_ROPaths
>   ITR(ropath.index, ropath)
> File "/usr/lib/python2.6/dist-packages/duplicity/lazy.py", line 336,
> in __call__
>   last_branch.fast_process, args)
> File "/usr/lib/python2.6/dist-packages/duplicity/robust.py", line 38,
> in check_common_error
>   return function(*args)
> File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line
> 574, in fast_process
>   ropath.copy(self.base_path.new_index(index))
> File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 412,
> in copy
>   other.writefileobj(self.open("rb"))
> File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 574,
> in writefileobj
>   buf = fin.read(_copy_blocksize)
> File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line
> 199, in read
>   if not self.addtobuffer():
> File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line
> 224, in addtobuffer
>   self.tarinfo_list[0] = self.tar_iter.next()
> File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line
> 331, in next
>   self.set_tarfile()
> File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line
> 320, in set_tarfile
>   self.current_fp = self.fileobj_iter.next()
> File "/usr/bin/duplicity", line 472, in get_fileobj_iter
>   backup_set.volume_name_dict[vol_num],
>   KeyError: 15
>
>   ProblemType: Bug
>   Architecture: i386
>   Date: Sun Dec 20 19:59:06 2009
>   DistroRelease: Ubuntu 9.10
>   ExecutablePath: /usr/bin/deja-dup
>   InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
>   Package: deja-dup 10.2-0ubuntu1.1
>   ProcEnviron:
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
>   SourcePackage: deja-dup
>   Uname: Linux 2.6.31-16-generic i686
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/deja-dup/+bug/498933/+subscriptions
>

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

Title:
  Crash when restoring data KeyError

Status in Déjà Dup:
  Invalid
Status in Duplicity:
  Confirmed
Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: deja-dup

  1) Ubuntu 9.10
  2) Deja Dup 10.2-0ubuntu1.1
  3) I expected my backup to be restored
  4) Deja Dup crashed instead.

  I just tried to restore the backup I made, and it crashes repeatedly
  when trying to restore.

  I have it setup to backup my home directory, and tried restoring to
  both the original location as well as a completely different folder.
  Both lead to the same error message.

  
  Traceback (most recent call last):
File "/usr/bin/duplicity", line 825, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 818, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 775, in main
  restore(col_stats)
File "/usr/bin/duplicity", line 436, in restore
  restore_get_patched_rop_iter(col_stats)):
File

[Desktop-packages] [Bug 1760415] Re: gnome-shell crashed with SIGSEGV in intel_miptree_supports_hiz() from needs_separate_stencil()

2018-04-03 Thread Andrea Azzarone

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

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

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

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

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

** Changed in: mesa (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

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

Title:
  gnome-shell crashed with SIGSEGV in intel_miptree_supports_hiz() from
  needs_separate_stencil()

Status in gnome-shell package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  Screen had automatically locked overnight. Bug report prompt appeared
  a few seconds after I logged in.

  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: Sat Mar 31 10:24:03 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-10-23 (159 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f8c18dbc870:mov(%rdi),%eax
   PC (0x7f8c18dbc870) ok
   source "(%rdi)" (0x0074) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: Upgraded to bionic on 2018-03-17 (14 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-shell/+bug/1760415/+subscriptions

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

[Desktop-packages] [Bug 1750583] Re: Broken panel and launcher - all black

2018-04-03 Thread Sam_

No, that was false hope, after .cache clean up and restart no real
change.

** Attachment added: "graphics-still-broken.png"
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1750583/+attachment/5100072/+files/graphics-still-broken.png

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

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

** Description changed:

- Since latest update all symbols at the launcher and search panel are black. 
(screenshot)
+ Since latest update 2018-02-15 (apt-history attached) all symbols at the 
launcher and Unity dash are black. (screenshot)
  All other applications and menues are fine, also the menues from 
unity-panel-service are ok.
  Changing the theme didn't help, restart of desktop or computer also didn't 
help.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.5+16.04.20171201.3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,imgjpeg,decor,regex,text,move,winrules,compiztoolbox,mousepoll,vpswitch,gnomecompat,obs,imgpng,grid,cube,place,resize,commands,ring,workarounds,scale,screenshot,expo,rotate,ezoom,unitymtgrabhandles,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Feb 20 15:29:39 2018
  DistUpgraded: 2016-08-01 14:42:41,957 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550] 
[1002:954f] (prog-if 00 [VGA controller])
-Subsystem: PC Partner Limited / Sapphire Technology RV710 [Radeon HD 
4350/4550] [174b:174b]
+  Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550] 
[1002:954f] (prog-if 00 [VGA controller])
+    Subsystem: PC Partner Limited / Sapphire Technology RV710 [Radeon HD 
4350/4550] [174b:174b]
  InstallationDate: Installed on 2012-02-05 (2207 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120204)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=b3e26f93-613b-48e8-96d7-9c8854fe670c ro
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-08-01 (568 days ago)
  dmi.bios.date: 07/30/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0305
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5QLD PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0305:bd07/30/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QLDPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Feb 20 15:27:07 2018
  xserver.configfile: default
  xserver.devices:
-  inputPower Button KEYBOARD, id 6
-  inputPower Button KEYBOARD, id 7
-  inputLogitech Logitech Illuminated Keyboard KEYBOARD, id 8
-  inputLogitech Logitech Illuminated Keyboard KEYBOARD, id 9
-  inputLogitech USB-PS/2 Optical Mouse MOUSE, id 10
+  inputPower Button KEYBOARD, id 6
+  inputPower Button KEYBOARD, id 7
+  inputLogitech Logitech Illuminated Keyboard KEYBOARD, id 8
+  inputLogitech Logitech Illuminated Keyboard KEYBOARD, id 9
+  inputLogitech USB-PS/2 Optical Mouse MOUSE, id 10
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: radeon

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

Title:
  Broken panel and

[Desktop-packages] [Bug 1760916] Re: gnome-shell crashed with signal 5 after login

*** 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/1760916/+attachment/5100058/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1760916/+attachment/5100067/+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/1760916

Title:
  gnome-shell crashed with signal 5 after login

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After login I get a message that an error occurred. Fresh bionic-daily
  install, installed today from latest ISO.

  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: Tue Apr  3 17:21:33 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-04-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.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
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () 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/1760916/+subscriptions

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

[Desktop-packages] [Bug 1759713] [NEW] xscreensaver eats keyboard-events after activation

You have been subscribed to a public bug:

running xenial/16.04.3 with hwe-kernel with nomodeset (only possibility
for this board with intel j4105) + -X11 with xfce.

start remmina in either version (original-xenial, ppa and fresh from
git) and start a rdp-session in fullscreen.

wait for the time before xscreensaver blanks the screen.

after that, mouse still works well, but no keys will be transferred.

stopping xscreensaver will prevent any problem with keyboard (but let
the screen unsaved)

minimizing the rdp-session and then maximizing it again will also help,
but it

don't know, if any other applications have similar problems, because we
use this system 99% as thin-client.

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


** Tags: bot-comment
-- 
xscreensaver eats keyboard-events after activation
https://bugs.launchpad.net/bugs/1759713
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xscreensaver 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 1760912] This bug is a duplicate

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

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 #1751460, 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.

** This bug has been marked a duplicate of bug 1751460
   [regression] deja-dup-monitor crashed with SIGSEGV in 
Gigacage::::operator()

** 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 deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1760912

Title:
  deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

Status in deja-dup package in Ubuntu:
  New

Bug description:
  On restart after update and upgrade .

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-2fakesync1
  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: Tue Apr  3 12:31:18 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-12-23 (100 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f8e190220a8:movl   $0x0,(%rax)
   PC (0x7f8e190220a8) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7f8e1928902c, 
init_routine=0x7f8e100c7590 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm lpadmin plugdev sambashare sudo vboxusers

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

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

[Desktop-packages] [Bug 1747717] Re: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned - gnome-menus -> ufw

It worked, sorry. Maybe this bug fixed itself?

I'll mark it Incomplete - if someone can reproduce please comment saying
how...

** Changed in: dpkg (Ubuntu Bionic)
   Status: Confirmed => Invalid

** Changed in: gnome-menus (Ubuntu Bionic)
   Status: Confirmed => Incomplete

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

Title:
  package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade:
  triggers looping, abandoned - gnome-menus -> ufw

Status in dpkg package in Ubuntu:
  Invalid
Status in gnome-menus package in Ubuntu:
  Incomplete
Status in dpkg source package in Bionic:
  Invalid
Status in gnome-menus source package in Bionic:
  Incomplete

Bug description:
  using the bionic beaver version

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gnome-menus 3.13.3-11ubuntu1
  Uname: Linux 4.15.1-041501-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  Date: Tue Feb  6 23:00:47 2018
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu1
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1631750] Re: Language installation doesn't work in Ubuntu GNOME 16.10 Settings app

This is tracked as a Trello card  and I don't think it should be a part of the
rls process.

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

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

Title:
  Language installation doesn't work in Ubuntu GNOME 16.10 Settings app

Status in Ubuntu GNOME:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  What happens
  
  1. From a terminal in Ubuntu GNOME, enter
   gnome-control-center region

  My locale is set to en_US so my terminal emits
  common-cc-panel-WARNING **: Language en_US.UTF-8 not installed, trying to 
install it

  2. Click Language.
  3. Click the 3-dot "more" button at the bottom of the popup.
  4. Select French (France). Click Done.

  My terminal emits:
  common-cc-panel-WARNING **: Language fr_FR not installed, trying to install it

  French isn't actually installed.

  What should happen
  ==
  PackageKit should install French. Language in the main window should change 
from English (United States) to French (France). Unfortunately because of how 
the system works, it would still require a log out and log in for the change to 
actually take effect.

  Other Info
  ===
  Installation of audio/video codes appears to work just fine:

  1. Uninstall the extra codecs (assuming you clicked the box in the installer 
to install third-party softwarel)
  sudo apt uninstall ubuntu-restricted-addons
  sudo apt autoremove

  Download this file
  https://archive.org/download/buckminsterfullereverythingiknow01/01001.rm

  It opens in Totem and session-installer prompts to install
  gstreamer1.0-plugins-ugly. Installation completed successfully and I
  was able to play the file.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-control-center 1:3.20.1-2ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct  9 09:52:01 2016
  InstallationDate: Installed on 2016-10-07 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20161007)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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-gnome/+bug/1631750/+subscriptions

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

[Desktop-packages] [Bug 1760906] Re: nautilus-desktop does not start at all

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

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 #1760870, 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/1760906/+attachment/519/+files/CoreDump.gz

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

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

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

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

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

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

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

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

Title:
  nautilus-desktop does not start at all

Status in nautilus package in Ubuntu:
  New

Bug description:
  Since Ubuntu 16.04 is updated to Ubuntu 18.04, Desktop does show up.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 17:13:02 2018
  ExecutablePath: /usr/bin/nautilus-desktop
  InstallationDate: Installed on 2017-04-07 (360 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: nautilus-desktop
  Signal: 5
  SourcePackage: nautilus
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_enum () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ()
   g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus-desktop crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2018-03-29 (5 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  usr_lib_nautilus:
   dropbox  2015.10.28
   nautilus-actions 3.2.3-1build3

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

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

[Desktop-packages] [Bug 1749472] Re: mesa 18.0.0 will cause rendering errors in Qt applications

That tag means we don't track this as a desktop team commitment, please
feel free to still fix the bug though if it's still relevant.

** Tags added: rls-bb-notfixing

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

Title:
  mesa 18.0.0 will cause rendering errors in Qt applications

Status in mesa package in Ubuntu:
  New
Status in mesa source package in Bionic:
  New

Bug description:
  From: https://bugreports.qt.io/browse/QTBUG-66348

  ** extract **

  The `QOpenGLShaderProgram` class in Qt can be used to compile and link
  OpenGL shaders. If the `GL_ARB_get_program_binary` OpenGL extension is
  available, it can cache those shaders on disk
  (~/.cache/qtshadercache). The i965 driver in Mesa supports this
  extension since version 18.0.0.

  When the shader is loaded using the `glProgramBinary` function, OpenGL
  can refuse it if for example some hardware or software component
  changed. Mesa refuses binaries that were created by any other build of
  Mesa (using among other things the build_id of the library).

  If the shader is refused, Qt should fallback to compiling it from
  sources, but it incorrectly calls glLinkProgram first. The
  glLinkProgram succeeds, because it actually links 0 shaders together.
  That is allowed in OpenGL compatibility profile and the resulting
  program works as a fixed pipeline. Which of course does not render as
  expected.

  This causes rendering errors in Qt applications every time Mesa is
  updated since version 18.0.0. For example white screen in sddm.

  This issue was originally reported in openSUSE
  (https://bugzilla.opensuse.org/show_bug.cgi?id=1080578).

  ** end extract **

  As this potentially effects Qt applications, and could even render
  display manager login unusable, this should be a blocking bug in mesa
  and Qt until Qt mitigations patches pass codereview and can be
  included in Qtbase for 18.04.

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

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

[Desktop-packages] [Bug 1751460] Re: [regression] deja-dup-monitor crashed with SIGSEGV in Gigacage::<lambda()>::operator()

2018-04-03 Thread Jeremy Bicha

Vej, I'm reclosing this bug for bionic. Maybe you just hadn't rebooted
since applying the update. Apport sometimes reports bugs late too.

** Changed in: deja-dup (Ubuntu Bionic)
   Status: Triaged => Fix Released

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

Title:
  [regression] deja-dup-monitor crashed with SIGSEGV in
  Gigacage::::operator()

Status in Déjà Dup:
  New
Status in WebKit:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released
Status in webkit2gtk package in Ubuntu:
  Invalid
Status in deja-dup source package in Xenial:
  Triaged
Status in deja-dup source package in Artful:
  Triaged
Status in deja-dup source package in Bionic:
  Fix Released

Bug description:
  Impact
  --
  webkit2gtk 2.20 adds a new security feature called the Gigacage that uses an 
extremely large virtual memory address space (much larger than available 
physical memory).

  Deja Dup's monitor background service had "ulimit -v 100" (that's
  1 GB) set as a workaround for a memory leak issue that the developer
  was unable to reproduce.

  After upgrading to the new webkit2gtk version, Deja Dup's monitor
  service will crash because of that virtual memory limit.

  Test Case
  -
  Install the deja-dup update.
  Install the webkit2gtk update from a PPA (not prepared yet).
  Log out. Log in.
  After a few minutes, check /var/crash/ for any Deja Dup crash reports.

  Regression Potential
  
  This could reintroduce the memory leak bug, but otherwise this is a minimal 
fix. Even if that happens, it's better than the service refusing to run.

  Other Info
  --
  https://errors.ubuntu.com/problem/27441b78823246dd5392ee29ac30546f6464289e

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  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
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat Feb 24 14:30:47 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-12-27 (59 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ff1c3dda588:movl   $0x0,(%rax)
   PC (0x7ff1c3dda588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7ff1c404202c, 
init_routine=0x7ff1baec0490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
  UpgradeStatus: Upgraded to bionic on 2018-02-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1760873] Re: nautilus-desktop crashed with signal 5

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

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 #1760870, 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/1760873/+attachment/5099868/+files/CoreDump.gz

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

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

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

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

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

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

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

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

Title:
  nautilus-desktop crashed with signal 5

Status in nautilus package in Ubuntu:
  New

Bug description:
  Occurred after updating Ubuntu 16.04 to Ubuntu 18.04

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 15:42:33 2018
  ExecutablePath: /usr/bin/nautilus-desktop
  InstallationDate: Installed on 2017-04-07 (360 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: nautilus-desktop
  Signal: 5
  SourcePackage: nautilus
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_enum () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ()
   g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus-desktop crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2018-03-29 (4 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  usr_lib_nautilus:
   dropbox  2015.10.28
   nautilus-actions 3.2.3-1build3

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

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

[Desktop-packages] [Bug 1749688] Re: 16.04 HWE -> 18.04 = xorg held back (+ partial breakage because of it)

2018-04-03 Thread Brian Murray

Upgrade log from a success.

** Attachment added: "20180403 upgrade success"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1749688/+attachment/5099943/+files/main.log

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

Title:
  16.04 HWE -> 18.04 = xorg held back (+ partial breakage because of it)

Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in xorg-lts-transitional package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Bionic:
  Fix Released
Status in xorg-lts-transitional source package in Bionic:
  Fix Released

Bug description:
  When upgrading from a 16.04 installation which had HWE (later point
  releases) xorg is getting held back as apt is having trouble resolving
  the path from xserver-xorg-core-hwe-16.04 to xserver-xorg-core.

  In at least one instance I've seen a system from a user POV completely
  break because of that as it failed to get any keyboard input. Forcing
  xorg to get properly installed fixes any and all issues as expected.

  - devel upgrade from xenial to bionic
  - restart
  - xorg not upgraded
  - try to get a hold of tty or repair mode
  - sudo apt install dist-upgrade && sudo apt install xorg
  - restart
  - working system

  I am going to attach logs for an ubuntu-desktop system, but I've also
  seen this with kubuntu-desktop and the derived neon-desktop. It's a
  bit unclear to me why apt is having trouble with the resolution, it
  does seem like a fairly serious problem though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1749688/+subscriptions

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

[Desktop-packages] [Bug 1749688] Re: 16.04 HWE -> 18.04 = xorg held back (+ partial breakage because of it)

2018-04-03 Thread Brian Murray

I tested an upgrade today from Ubuntu 16.04 (with plymouth packages from
xenial-proposed and xserver-xorg-core-hwe-16.04 installed) to Ubuntu
18.04. There were no errors during the upgrade process and I was able to
log into a functioning Ubuntu desktop environment after rebooting when
the upgrade was complete.

** Changed in: ubuntu-release-upgrader (Ubuntu Bionic)
   Status: Triaged => Fix Released

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

Title:
  16.04 HWE -> 18.04 = xorg held back (+ partial breakage because of it)

Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in xorg-lts-transitional package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Bionic:
  Fix Released
Status in xorg-lts-transitional source package in Bionic:
  Fix Released

Bug description:
  When upgrading from a 16.04 installation which had HWE (later point
  releases) xorg is getting held back as apt is having trouble resolving
  the path from xserver-xorg-core-hwe-16.04 to xserver-xorg-core.

  In at least one instance I've seen a system from a user POV completely
  break because of that as it failed to get any keyboard input. Forcing
  xorg to get properly installed fixes any and all issues as expected.

  - devel upgrade from xenial to bionic
  - restart
  - xorg not upgraded
  - try to get a hold of tty or repair mode
  - sudo apt install dist-upgrade && sudo apt install xorg
  - restart
  - working system

  I am going to attach logs for an ubuntu-desktop system, but I've also
  seen this with kubuntu-desktop and the derived neon-desktop. It's a
  bit unclear to me why apt is having trouble with the resolution, it
  does seem like a fairly serious problem though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1749688/+subscriptions

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

[Desktop-packages] [Bug 1760308] Re: Unicode input not working on Bionic with CTRL-SHIFT-U

2018-04-03 Thread Will Cooke

** Also affects: ibus (Ubuntu Bionic)
   Importance: Undecided
   Status: Confirmed

** Changed in: ibus (Ubuntu Bionic)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

** Tags removed: rls-bb-incoming

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

Title:
  Unicode input not working on Bionic with CTRL-SHIFT-U

Status in ibus package in Ubuntu:
  Confirmed
Status in ibus source package in Bionic:
  Confirmed

Bug description:
  I need to enter Unicode with Unicode escape codes and the Ubuntu
  prescribed way is to use CTRL-SHIFT-U and then enter some numbers to
  input.  This doesn't do anything in the Ubuntu Bionic beta.

  Potentially related the ALT-TAB window switching is delayed in
  recognizing the occurrence of the keys being pressed such that I have
  to hold ALT-TAB instead of quickly hitting both simultaneously.

  This is from a system that was upgraded from a previous Ubuntu version
  without any issues.

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

  The "Affects" package may not be accurate as I don't know what the
  cause application is for this.

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

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

[Desktop-packages] [Bug 1760871] Re: nautilus-desktop crashed with signal 5

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

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 #1760870, 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/1760871/+attachment/5099850/+files/CoreDump.gz

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

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

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

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

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

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

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

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

Title:
  nautilus-desktop crashed with signal 5

Status in nautilus package in Ubuntu:
  New

Bug description:
  Occurred after updating Ubuntu 16.04 to Ubuntu 18.04

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 15:42:33 2018
  ExecutablePath: /usr/bin/nautilus-desktop
  ExecutableTimestamp: 1521922016
  InstallationDate: Installed on 2017-04-07 (360 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: nautilus-desktop
  ProcCwd: /home/jkalliau
  Signal: 5
  SourcePackage: nautilus
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_enum () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ()
   g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus-desktop crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2018-03-29 (4 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  usr_lib_nautilus:
   dropbox  2015.10.28
   nautilus-actions 3.2.3-1build3

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

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

[Desktop-packages] [Bug 1760795] Re: gnome-software leaks file descriptors

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

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

Title:
  gnome-software leaks file descriptors

Status in gnome-software package in Ubuntu:
  Invalid
Status in snapd-glib package in Ubuntu:
  In Progress
Status in gnome-software source package in Bionic:
  Invalid
Status in snapd-glib source package in Bionic:
  In Progress

Bug description:
  To verify the bug:
  1) killall gnome-software
  2) lsof -p $(pidof gnome-software) | wc -l
  3) Use gnome-software for a while (search for snaps, etc.)
  4) Again: lsof -p $(pidof gnome-software) | wc -l

  As you can seen the list of open files grows overtime.

  This (https://paste.ubuntu.com/p/rF5tHn5BwG/) also shows the problem,
  just compile it, get the pid and check with lsof the number of open
  files.

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

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

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