[Desktop-packages] [Bug 1755970] Re: No home directory created for new user and account won't delete

[Ubuntu QA Website]

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

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

** Tags added: iso-testing

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

Title:
  No home directory created for new user and account won't delete

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

Bug description:
  I'm using Xubuntu 18.04, the iso uploaded at 2:19 UTC, 15/3/2018(as of
  posting, the latest release), running in Virtualbox 5.28 host on a
  newly installed Xubuntu 18.04 system using the Beta 1 ISO.

  I was running through the QA testing for a new install, and got to the
  point where I need to create an account, log out, and log into the new
  account.  It went well the first time, the old and the new user
  accounts worked.  I logged back into the original account (created at
  install), deleted the other account, started Firefox (to have an app
  running for the session to be saved), created the account with the
  same name, logged out of my first account, and logged into the newly
  created account.

  The account wouldn't log in.  Checking /home, there should be two home
  folders, /home/arin (the home folder for the account created by the
  installer), and /home/knock, the account I had created, deleted, and
  created again.  /home/knock did not exist this second time.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-system-tools 3.0.0-6ubuntu1
  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: Wed Mar 14 20:27:16 2018
  InstallationDate: Installed on 2018-03-15 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180315)
  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/1755970/+subscriptions

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

[Desktop-packages] [Bug 1755971] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_writer_default() from g_log_structured_array() from g_log_structured() from _gdk_x11_display_error_ev

[Daniel van Vugt]

Upstream:
https://gitlab.gnome.org/GNOME/mutter/issues/69

** Summary changed:

- 
/usr/bin/gnome-shell:5:_g_log_abort:g_log_writer_default:g_log_structured_array:g_log_structured:_gdk_x11_display_error_event
+ gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_writer_default() from g_log_structured_array() from g_log_structured() 
from _gdk_x11_display_error_event()

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

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

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_writer_default() from g_log_structured_array() from
  g_log_structured() from _gdk_x11_display_error_event()

Status in gnome-shell package in Ubuntu:
  Confirmed

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

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

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

[Desktop-packages] [Bug 1755970] [NEW] No home directory created for new user and account won't delete

[Arin Lares]

Public bug reported:

I'm using Xubuntu 18.04, the iso uploaded at 2:19 UTC, 15/3/2018(as of
posting, the latest release), running in Virtualbox 5.28 host on a newly
installed Xubuntu 18.04 system using the Beta 1 ISO.

I was running through the QA testing for a new install, and got to the
point where I need to create an account, log out, and log into the new
account.  It went well the first time, the old and the new user accounts
worked.  I logged back into the original account (created at install),
deleted the other account, started Firefox (to have an app running for
the session to be saved), created the account with the same name, logged
out of my first account, and logged into the newly created account.

The account wouldn't log in.  Checking /home, there should be two home
folders, /home/arin (the home folder for the account created by the
installer), and /home/knock, the account I had created, deleted, and
created again.  /home/knock did not exist this second time.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-system-tools 3.0.0-6ubuntu1
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: Wed Mar 14 20:27:16 2018
InstallationDate: Installed on 2018-03-15 (0 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180315)
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 bionic xubuntu-exp

** Tags added: xubuntu-exp

** Description changed:

  I'm using Xubuntu 18.04, the iso uploaded at 2:19 UTC, 15/3/2018(as of
- posting, the latest release).
+ posting, the latest release), running in Virtualbox 5.28 host on a newly
+ installed Xubuntu 18.04 system using the Beta 1 ISO.
  
  I was running through the QA testing for a new install, and got to the
  point where I need to create an account, log out, and log into the new
  account.  It went well the first time, the old and the new user accounts
  worked.  I logged back into the original account (created at install),
  deleted the other account, started Firefox (to have an app running for
  the session to be saved), created the account with the same name, logged
  out of my first account, and logged into the newly created account.
  
  The account wouldn't log in.  Checking /home, there should be two home
  folders, /home/arin (the home folder for the account created by the
  installer), and /home/knock, the account I had created, deleted, and
  created again.  /home/knock did not exist this second time.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-system-tools 3.0.0-6ubuntu1
  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: Wed Mar 14 20:27:16 2018
  InstallationDate: Installed on 2018-03-15 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180315)
  SourcePackage: gnome-system-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  No home directory created for new user and account won't delete

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

Bug description:
  I'm using Xubuntu 18.04, the iso uploaded at 2:19 UTC, 15/3/2018(as of
  posting, the latest release), running in Virtualbox 5.28 host on a
  newly installed Xubuntu 18.04 system using the Beta 1 ISO.

  I was running through the QA testing for a new install, and got to the
  point where I need to create an account, log out, and log into the new
  account.  It went well the first time, the old and the new user
  accounts worked.  I logged back into the original account (created at
  install), deleted the other account, started Firefox (to have an app
  running for the session to be saved), created the account with the
  same name, logged out of my first account, and logged into the newly
  created account.

  The account wouldn't log in.  Checking /home, there should be two home
  folders, /home/arin (the home folder for the account created by the
  installer), and /home/knock, the account I had created, deleted, and
  created again.  /home/knock did not exist this second time.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-system-tools 3.0.0-6ubuntu1
  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: Wed Mar 14 20:27:16 2018
  InstallationDate: Installed on 2018-03-15 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS 

[Desktop-packages] [Bug 1755971] [NEW] gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_writer_default() from g_log_structured_array() from g_log_structured() from _gdk_x11_display_error_

[errors.ubuntu.com bug bridge]

Public bug reported:

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

** Affects: gnome-shell (Ubuntu)
 Importance: Medium
 Status: Confirmed


** Tags: artful bionic

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_writer_default() from g_log_structured_array() from
  g_log_structured() from _gdk_x11_display_error_event()

Status in gnome-shell package in Ubuntu:
  Confirmed

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

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

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

[Desktop-packages] [Bug 1755144] Re: No audio on vlc or videos sound or video files

[Daniel van Vugt]

Thanks.

It looks like your issues might be caused by these unsupported package
versions you have installed:

ii  libavcodec-extra  7:3.3.3-2~ubuntu16.04.1~ppa1  
all  FFmpeg library with extra codecs 
(metapackage)
ii  libavcodec-extra57:amd64  7:3.3.3-2~ubuntu16.04.1~ppa1  
amd64FFmpeg library with additional 
de/encoders for audio/video codecs
ii  libavdevice57:amd64   7:3.2.6-1~backport1.1~xenial  
amd64FFmpeg library for handling input 
and output devices - runtime files
ii  libavfilter6:amd647:3.2.6-1~backport1.1~xenial  
amd64FFmpeg library containing media 
filters - runtime files
ii  libavformat57:amd64   7:3.2.6-1~backport1.1~xenial  
amd64FFmpeg library with (de)muxers for 
multimedia containers - runtime files
ii  libavresample3:amd64  7:3.3.3-2~ubuntu16.04.1~ppa1  
amd64FFmpeg compatibility library for 
resampling - runtime files
ii  libavutil55:amd64 7:3.3.3-2~ubuntu16.04.1~ppa1  
amd64FFmpeg library with functions for 
simplifying programming - runtime files

Your system appears to be mixing and matching the standard ffmpeg
packages from Ubuntu 16.04 (version 7:2.8.11-0ubuntu0.16.04.1) and
nonstandard ones from PPAs.

Please purge all PPAs from your system and retest:

  1. sudo apt install ppa-purge
  2. sudo ppa-purge    (on all the PPAs you are using)
  3. Retest and provide new output from 'dpkg -l | grep libav > libav.txt'

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

Title:
  No audio on vlc or videos sound or video files

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Up until a few weeks ago there was no problem with playing sound from mp3 
files. I have a pair of usb speakers. Audio plays Ok on them for video clips 
using Chrome (e.g. from BBC website). Using vlc 2.2.2 (from Ubuntu repos), 
neither a CD nor DVD (video is Ok) nor mp3 file plays audio. mp3 files play Ok 
using Rhythmbox. I've also tried vlc 3.0 with no success.
  Interestingly, the standard Videos app (Totem?) also doesn't play sound on 
these speakers either of an mp4 file (downloaded from YouTube, though it plays 
Ok on YouTube website using Chrome) or a DVD. Clemenetine plays mp3 files Ok. I 
first reported this as bug 1752267 as I thought that the problem was with vlc. 
On that bug, it was suggested that the problem is with Pulseaudio.
  Just now, I've tried to play sound through my monitor's built in speakers 
connected by hdmi (though the monitor displays Ok) with no success even though 
the built-in speakers play sound using pavucontrol when testing is invoked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  john   2410 F pulseaudio
   /dev/snd/controlC0:  john   2410 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 12 11:06:46 2018
  InstallationDate: Installed on 2016-12-08 (458 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-404
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:

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

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

[Desktop-packages] [Bug 1755473] Re: Some strings of Ubuntu Dock settings are not translated anymore on Ubuntu 18.04

[Jeremy Bicha]

** Changed in: gnome-control-center (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Some strings of Ubuntu Dock settings are not translated anymore on
  Ubuntu 18.04

Status in Ubuntu Translations:
  New
Status in gnome-control-center package in Ubuntu:
  Fix Committed

Bug description:
  Another translation issue. :-( It looks like that some recent update
  of Ubuntu 18.04 broke the translation of the "Dock", "Ubuntu Dock
  Settings","Dock;Launcher;" and "Ubuntu Dock" strings. They are fully
  translated on Launchpad in my (Czech) language, but the translation is
  not applied anymore.

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

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

[Desktop-packages] [Bug 1755758] Re: gnome-control-center FTBFS with gnome-bluetooth 3.28

[Jeremy Bicha]

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

** Changed in: gnome-bluetooth (Ubuntu)
   Status: New => Fix Committed

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

Title:
  gnome-control-center FTBFS with gnome-bluetooth 3.28

Status in GNOME Bluetooth:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Fix Committed
Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 18.04
  meson 0.45.0

  gnome-control-center 3.28.0 fails to build from source with gnome-
  bluetooth 3.28.0. The build succeeds with gnome-bluetooth 3.27.90.

  Build log excerpt
  =
  Native dependency libnm found: YES 1.10.4
  Native dependency libnma found: YES 1.8.10
  Native dependency mm-glib found: YES 1.6.8
  Native dependency NetworkManager found: YES 1.10.4

  meson.build:212:2: ERROR: Could not generate cargs for gnome-
  bluetooth-1.0:

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

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

[Desktop-packages] [Bug 1755900] Re: sql cookie errors from gnome-shell, or its users

[Daniel van Vugt]

I can't see any sql messages in my log on 18.04. And I can't see any sql
use in the source code of either gnome-shell or mutter.

Are you using any non-standard extensions with gnome-shell?

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

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

Title:
  sql cookie errors from gnome-shell, or its users

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  it seems like gnome-shell; or something that calls into gnome-shell;
  have trouble with sqlite:

  journalctl -b -e | grep -e gnome-shell -e org.gnome.Shell.desktop |
  grep sqlite

  has a lot of:

  org.gnome.Shell.desktop[24475]:
  [16281:32625:0314/201004.637228:ERROR:connection.cc(1945)] Cookie
  sqlite error 1, errno 0: cannot start a transaction within a
  transaction, sql: BEGIN TRANSACTION

  
  and similar. My current boot has 66 of them, with only 10h of uptime.

  I do suspend and resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 14 20:11:22 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' b"['r']"
   b'org.gnome.shell' b'favorite-apps' b"['hexchat.desktop', 
'chrome-bebigdkelppomhhjaaianniiifjbgocn-Default.desktop', 
'chrome-clhhggbfdinjmjhajaheehoeibfljjno-Default.desktop', 
'google-chrome.desktop', 'firefox.desktop', 'yubioath.desktop', 
'org.gnome.Terminal.desktop', 'org.gnome.Nautilus.desktop', 
'virt-manager.desktop', 'pgadmin3.desktop', 'android-studio.desktop', 
'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2012-01-12 (2253 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318)
  ProcEnviron:
   LANG=en_US.UTF-8
   TERM=xterm-256color
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-01-11 (62 days ago)

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

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

[Desktop-packages] [Bug 1755938] Re: gnome-shell crashed with SIGABRT in g_assertion_message()

[Daniel van Vugt]

Please do this:

1. Apply the workaround from bug 994921.
2. Reproduce the crash.
3. Look in /var/crash for new files, and if found run:
   ubuntu-bug /var/crash/YOURFILE.crash.
4. When the new bug is created, let us know here what that bug ID is.

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

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

Title:
  gnome-shell crashed with SIGABRT in g_assertion_message()

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.18.5-0ubuntu0.3
Candidate: 3.18.5-0ubuntu0.3
Version table:
   *** 3.18.5-0ubuntu0.3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   3.18.4-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  Happened for no reason that I can see. Syslog output of the crash is
  here - https://paste.ubuntu.com/p/JJzsS7T6mQ/

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

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

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

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1691701
   gnome-shell crashed with SIGTRAP in XSync() from meta_pre_paint_func() from 
_clutter_run_repaint_functions() from master_clock_update_stages() from 
clutter_clock_dispatch()

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Crashed seemingly randomly just after performing a search. Using
  Ubuntu GNOME 16.04 Beta

  uname -a output:

  Linux steve-ThinkPad-SL510 4.4.0-14-generic #30-Ubuntu SMP Tue Mar 15
  13:04:17 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Mar 21 18:49:25 2016
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2015-12-05 (107 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/libmutter.so.0
  Title: gnome-shell crashed with signal 5 in _XReply()
  UpgradeStatus: Upgraded to xenial on 2016-03-12 (9 days ago)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1691701] Re: gnome-shell crashed with SIGTRAP in XSync() from meta_pre_paint_func() from _clutter_run_repaint_functions() from master_clock_update_stages() from clutter_clock_d

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-shell crashed with SIGTRAP in XSync() from meta_pre_paint_func()
  from _clutter_run_repaint_functions() from
  master_clock_update_stages() from clutter_clock_dispatch()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.24.1-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/e65ecf01c68dcdeebf7e1112c96ad6dda77f2ed0 
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 you can request it at 
http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1691701] Re: gnome-shell crashed with SIGTRAP in XSync() from meta_pre_paint_func() from _clutter_run_repaint_functions() from master_clock_update_stages() from clutter_clock_d

[Daniel van Vugt]

See also bug 1755779.

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

Title:
  gnome-shell crashed with SIGTRAP in XSync() from meta_pre_paint_func()
  from _clutter_run_repaint_functions() from
  master_clock_update_stages() from clutter_clock_dispatch()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.24.1-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/e65ecf01c68dcdeebf7e1112c96ad6dda77f2ed0 
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 you can request it at 
http://forms.canonical.com/reports/.

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

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

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

[Daniel van Vugt]

Looks like bug 1691701. Only the stack trace changed a little in 18.04
so we have this new bug.

** Information type changed from Private to Public

** Summary changed:

- gnome-shell crashed with signal 5
+ gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_writer_default() from g_log_structured_array() from ... XSync() from 
meta_pre_paint_func() from _clutter_run_repaint_functions()

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_writer_default() from g_log_structured_array() from ... XSync()
  from meta_pre_paint_func() from _clutter_run_repaint_functions()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  don't know why, maybe related to printer

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 14 10:02:43 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'thunderbird.desktop', 'libreoffice-calc.desktop', 
'org.gnome.Nautilus.desktop', 'rhythmbox.desktop', 
'libreoffice-writer.desktop', 'yelp.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-02-12 (29 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
  Title: gnome-shell 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-shell/+bug/1755779/+subscriptions

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

[Desktop-packages] [Bug 1755450] Re: nautilus crashed with SIGSEGV in malloc_consolidate()

[Seth Arnold]

I wonder if this is related:

mars 13 10:33:52 hostname gnome-software[2180]: Creating pipes for
GWakeup: Too many open files

Thanks

** Information type changed from Private Security to Public

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

Title:
  nautilus crashed with SIGSEGV in malloc_consolidate()

Status in nautilus package in Ubuntu:
  New

Bug description:
  Opening file with double click in nautilus

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.2-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 13 11:37:41 2018
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2018-01-08 (63 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7fae50f40b10 :   cmp
%rax,0x28(%r13)
   PC (0x7fae50f40b10) ok
   source "%rax" ok
   destination "0x28(%r13)" (0xf9bd) not located in a known VMA 
region (needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   malloc_consolidate (av=av@entry=0x7fae5129bc40 ) at malloc.c:4456
   _int_free (have_lock=0, p=, av=0x7fae5129bc40 ) 
at malloc.c:4362
   __GI___libc_free (mem=0x55611461a330) at malloc.c:3124
   tcache_thread_shutdown () at malloc.c:2969
   arena_thread_freeres () at arena.c:950
  Title: nautilus crashed with SIGSEGV in malloc_consolidate()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()

[Daniel van Vugt]

The crash occurs on this line of code:

  g_warning ("Failed to set CRTC mode %s: %m",
crtc->current_mode->name);

As crtc is not NULL it must be current_mode or name that has an invalid
value.

** Tags added: wayland wayland-session

** Description changed:

+ https://gitlab.gnome.org/GNOME/mutter/issues/70
+ 
+ ---
+ 
  The crash was reported after booting and logging in to an X.Org session.
  
  $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  
  $ apt-cache policy gnome-shell
  gnome-shell:
-   Instalovaná verze: 3.27.92-0ubuntu1
-   Kandidát:  3.27.92-0ubuntu1
-   Tabulka verzí:
-  *** 3.27.92-0ubuntu1 500
- 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Instalovaná verze: 3.27.92-0ubuntu1
+   Kandidát:  3.27.92-0ubuntu1
+   Tabulka verzí:
+  *** 3.27.92-0ubuntu1 500
+ 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Mar 11 11:08:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
-  
+ 
  InstallationDate: Installed on 2017-12-19 (81 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
-  LANGUAGE=cs_CZ
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=cs_CZ.UTF-8
-  SHELL=/bin/false
+  LANGUAGE=cs_CZ
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=cs_CZ.UTF-8
+  SHELL=/bin/false
  SegvAnalysis:
-  Segfault happened at: 0x7f3fee5d2f17 : 
mov0x20(%rax),%rcx
-  PC (0x7f3fee5d2f17) ok
-  source "0x20(%rax)" (0x0020) not located in a known VMA region (needed 
readable region)!
-  destination "%rcx" ok
+  Segfault happened at: 0x7f3fee5d2f17 : 
mov0x20(%rax),%rcx
+  PC (0x7f3fee5d2f17) ok
+  source "0x20(%rax)" (0x0020) not located in a known VMA region (needed 
readable region)!
+  destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
-  meta_gpu_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
-  meta_renderer_native_finish_frame () at 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
-  () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
-  () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
-  () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
+  meta_gpu_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
+  meta_renderer_native_finish_frame () at 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
+  () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
+  () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
+  () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
  Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode()
  UpgradeStatus: Upgraded to bionic on 2018-03-05 (5 days ago)
  UserGroups:

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

Title:
  gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode()
  from meta_renderer_native_finish_frame()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/70

  ---

  The crash was reported after booting and logging in to an X.Org
  session.

  $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  $ apt-cache policy gnome-shell
  gnome-shell:
    Instalovaná verze: 3.27.92-0ubuntu1
    Kandidát:  3.27.92-0ubuntu1
    Tabulka verzí:
   *** 3.27.92-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Mar 11 11:08:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2017-12-19 (81 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=cs_CZ
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened 

[Desktop-packages] [Bug 1755562] Re: package libwinpr-sspi0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should rei

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libwinpr-sspi0.1:amd64
  1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in freerdp package in Ubuntu:
  New

Bug description:
  kk

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libwinpr-sspi0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2
  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: Tue Mar 13 22:34:51 2018
  DuplicateSignature:
   package:libwinpr-sspi0.1:amd64:1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package libwinpr-sspi0.1:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-03-12 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: freerdp
  Title: package libwinpr-sspi0.1:amd64 
1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Bug Watch Updater]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()

[Daniel van Vugt]

Upstream bug report:
https://gitlab.gnome.org/GNOME/mutter/issues/70

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

Title:
  gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode()
  from meta_renderer_native_finish_frame()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/70

  ---

  The crash was reported after booting and logging in to an X.Org
  session.

  $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  $ apt-cache policy gnome-shell
  gnome-shell:
    Instalovaná verze: 3.27.92-0ubuntu1
    Kandidát:  3.27.92-0ubuntu1
    Tabulka verzí:
   *** 3.27.92-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Mar 11 11:08:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2017-12-19 (81 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=cs_CZ
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f3fee5d2f17 : 
mov0x20(%rax),%rcx
   PC (0x7f3fee5d2f17) ok
   source "0x20(%rax)" (0x0020) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_gpu_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   meta_renderer_native_finish_frame () at 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
  Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode()
  UpgradeStatus: Upgraded to bionic on 2018-03-05 (5 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1755562] Re: package libwinpr-sspi0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should rei

[Seth Arnold]

** Information type changed from Private Security to Public

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

Title:
  package libwinpr-sspi0.1:amd64
  1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in freerdp package in Ubuntu:
  New

Bug description:
  kk

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libwinpr-sspi0.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2
  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: Tue Mar 13 22:34:51 2018
  DuplicateSignature:
   package:libwinpr-sspi0.1:amd64:1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package libwinpr-sspi0.1:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-03-12 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: freerdp
  Title: package libwinpr-sspi0.1:amd64 
1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1.2 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1696305] Re: High CPU usage in gnome-shell just redrawing the screen (Firefox is running)

[Daniel van Vugt]

This bug is about the Firefox case only now.

If you have any other problems then please open a new bug.

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

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

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

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

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

Title:
  High CPU usage in gnome-shell just redrawing the screen (Firefox is
  running)

Status in firefox package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  Even when doing nothing at all, gnome-shell uses around 70% CPU.

  ```
  inxi -t cm
  Processes: CPU: % used - top 5 active
 1: cpu: 68.6% command: gnome-shell pid: 1399
 2: cpu: 50.4% command: Xwayland pid: 1405
 3: cpu: 19.7% command: firefox pid: 3684
 4: cpu: 2.4% command: gnome-shell pid: 1859
 5: cpu: 1.5% command: gnome-tweak-tool (started by: python) pid: 
13603
 Memory: MB / % used - Used/Total: 2350.1/11897.0MB - top 5 active
 1: mem: 1033.63MB (8.6%) command: firefox pid: 3684
 2: mem: 317.59MB (2.6%) command: gnome-shell pid: 1859
 3: mem: 267.55MB (2.2%) command: gnome-software pid: 2058
 4: mem: 111.25MB (0.9%) command: Xorg pid: 1506
 5: mem: 90.90MB (0.7%) command: nautilus-desktop pid: 2055
  ```

  It's also strange that Xwayland is active as I did choose the "normal" gnome 
session upon signin.
  ```
  echo $XDG_SESSION_TYPE
  x11
  ```

  While searching I found a recent problem with AMD GPUs, but I'm using an 
Intel GPU
  ```
  glxinfo 
  name of display: :0
  display: :0  screen: 0
  direct rendering: Yes
  server glx vendor string: SGI
  server glx version string: 1.4
  server glx extensions:
  GLX_ARB_create_context, GLX_ARB_create_context_profile, 
  GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
  GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, 
  GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
  GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, 
  GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_texture_from_pixmap, 
  GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, 
  GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, 
  GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, 
  GLX_SGI_make_current_read, GLX_SGI_swap_control
  client glx vendor string: Mesa Project and SGI
  client glx version string: 1.4
  client glx extensions:
  GLX_ARB_create_context, GLX_ARB_create_context_profile, 
  GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
  GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, 
  GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, 
  GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, 
  GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, 
  GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
  GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
  GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
  GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
  GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
  GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
  GLX_SGI_swap_control, GLX_SGI_video_sync
  GLX version: 1.4
  GLX extensions:
  GLX_ARB_create_context, GLX_ARB_create_context_profile, 
  GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
  GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, 
  GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, 
  GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, 
  GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, 
  GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
  GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
  GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
  GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
  GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
  GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
  GLX_SGI_swap_control, GLX_SGI_video_sync
  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: Intel Open Source Technology Center (0x8086)
  Device: Mesa DRI Intel(R) Haswell Mobile  (0xa16)
  Version: 17.1.0
  Accelerated: yes
  Video memory: 1536MB
  Unified memory: yes
  Preferred profile: core (0x1)
  Max core profile version: 4.5
  Max compat profile version: 3.0
  

[Desktop-packages] [Bug 1753528] Re: gvfsd-mtp assert failure: corrupted double-linked list

[Seth Arnold]

** Information type changed from Private Security to Public

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

Title:
  gvfsd-mtp assert failure: corrupted double-linked list

Status in gvfs package in Ubuntu:
  New

Bug description:
  I don't know correctly

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gvfs-backends 1.35.91-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AssertionMessage: corrupted double-linked list
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  5 21:25:32 2018
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2018-02-26 (6 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.22 
/org/gtk/gvfs/exec_spaw/14
  ProcEnviron:
   LANG=en_IN
   LANGUAGE=en_IN:en
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: gvfs
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7efbfdc7eb9a 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7efbfdc7ccba "corrupted double-linked 
list") at malloc.c:5350
   _int_malloc (av=av@entry=0x7efbe420, bytes=bytes@entry=6) at 
malloc.c:3926
   __GI___libc_malloc (bytes=6) at malloc.c:3065
   g_malloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gvfsd-mtp assert failure: corrupted double-linked list
  UpgradeStatus: Upgraded to bionic on 2018-02-27 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

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

[Seth Arnold]

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

** Information type changed from Public Security to Public

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

Title:
  gnome-software crashed with signal 5

Status in gnome-software package in Ubuntu:
  New

Bug description:
  não sei informar onde ou como foi o erro.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  7 09:18:54 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-02-23 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180221)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.27.92-0ubuntu1
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-software
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_new () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   snapd_client_find_section_sync () at 
/usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   () at /usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_snap.so
  Title: gnome-software crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1754160] Re: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

[Seth Arnold]

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

** Information type changed from Public Security to Public

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

Title:
  deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

Status in deja-dup package in Ubuntu:
  New

Bug description:
  .

  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: ubuntu:GNOME
  Date: Wed Mar  7 17:33:46 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2018-03-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307)
  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: 0x7f6d6db94588:movl   $0x0,(%rax)
   PC (0x7f6d6db94588) 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=0x7f6d6ddfc02c, 
init_routine=0x7f6d64c51490 <__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 lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1727653] Re: error: can't start new thread

[Miles]

I was able to get the open files changed to 65535 using the above link.
Today after I started my computer I got the same error I've been getting
about not being able to create a new thread.

~$ ulimit -a
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 31429
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files  (-n) 65535
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) 31429
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited

Error I see when the backup runs automatically.

Traceback (innermost last):
  File "/usr/bin/duplicity", line 1555, in 
with_tempdir(main)
  File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
  File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
  File "/usr/bin/duplicity", line 1472, in do_backup
restore(col_stats)
  File "/usr/bin/duplicity", line 728, in restore
restore_get_patched_rop_iter(col_stats)):
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 558, in 
Write_ROPaths
for ropath in rop_iter:
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 521, in 
integrate_patch_iters
for patch_seq in collated:
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
setrorps(overflow, elems)
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
elems[i] = iter_list[i].next()
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
for path in path_iter:
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
tarinfo_list = [tar_iter.next()]
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
self.set_tarfile()
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
self.current_fp = self.fileobj_iter.next()
  File "/usr/bin/duplicity", line 765, in get_fileobj_iter
manifest.volume_info_dict[vol_num])
  File "/usr/bin/duplicity", line 808, in restore_get_enc_fileobj
fileobj = tdp.filtered_open_with_delete("rb")
  File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 120, in 
filtered_open_with_delete
fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
  File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 779, in 
filtered_open
return gpg.GPGFile(False, self, gpg_profile)
  File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 224, in 
__init__
'logger': self.logger_fp})
  File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 374, 
in run
create_fhs, attach_fhs)
  File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 420, 
in _attach_fork_exec
process.thread.start()
  File "/usr/lib/python2.7/threading.py", line 736, in start
_start_new_thread(self.__bootstrap, ())
 error: can't start new thread

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

Title:
  error: can't start new thread

Status in Duplicity:
  In Progress
Status in deja-dup package in Ubuntu:
  Triaged
Status in duplicity package in Ubuntu:
  In Progress

Bug description:
  $ uname -a
  Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  duplicity gets started daily via deja-dup automatically.

  Every now and then (approx. every third time) I get the following
  error:

  --

  Failed with an unknown error.

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File 

[Desktop-packages] [Bug 1753279] Re: deja-dup-monitor crashed with SIGSEGV

[Seth Arnold]

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

** Information type changed from Public Security to Public

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

Title:
  deja-dup-monitor crashed with SIGSEGV

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  ubuntu bionic beaver .
  I get this error but don't know why because I don't use deja-dup.
  I've got this a multiple times after logging in to my system

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  Uname: Linux 4.15.7-041507-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Mar  4 22:58:40 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  SegvAnalysis:
   Segfault happened at: 0x7fcdf71eb588:movl   $0x0,(%rax)
   PC (0x7fcdf71eb588) 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:
   () at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7fcdf745302c, 
init_routine=0x7fcdee2a8490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () at 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1755949] Re: process-cpp FTBFS in bionic

[Steve Langasek]

Removing packages from bionic:
process-cpp 3.0.1-0ubuntu5 in bionic
libprocess-cpp-dev 3.0.1-0ubuntu5 in bionic amd64
libprocess-cpp-dev 3.0.1-0ubuntu5 in bionic arm64
libprocess-cpp-dev 3.0.1-0ubuntu5 in bionic armhf
libprocess-cpp-dev 3.0.1-0ubuntu5 in bionic i386
libprocess-cpp-dev 3.0.1-0ubuntu5 in bionic ppc64el
libprocess-cpp-dev 3.0.1-0ubuntu5 in bionic s390x
libprocess-cpp-doc 3.0.1-0ubuntu5 in bionic amd64
libprocess-cpp-doc 3.0.1-0ubuntu5 in bionic arm64
libprocess-cpp-doc 3.0.1-0ubuntu5 in bionic armhf
libprocess-cpp-doc 3.0.1-0ubuntu5 in bionic i386
libprocess-cpp-doc 3.0.1-0ubuntu5 in bionic ppc64el
libprocess-cpp-doc 3.0.1-0ubuntu5 in bionic s390x
libprocess-cpp3 3.0.1-0ubuntu5 in bionic amd64
libprocess-cpp3 3.0.1-0ubuntu5 in bionic arm64
libprocess-cpp3 3.0.1-0ubuntu5 in bionic armhf
libprocess-cpp3 3.0.1-0ubuntu5 in bionic i386
libprocess-cpp3 3.0.1-0ubuntu5 in bionic ppc64el
libprocess-cpp3 3.0.1-0ubuntu5 in bionic s390x
Comment: Obsoleted product, FTBFS; LP: #1747128
1 package successfully removed.
Removing packages from bionic-proposed:
process-cpp 3.0.1-0ubuntu6 in bionic
Comment: Obsoleted product, FTBFS; LP: #1747128
1 package successfully removed.


** Changed in: process-cpp (Ubuntu)
   Status: New => Fix Released

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

Title:
  process-cpp FTBFS in bionic

Status in dbus-cpp package in Ubuntu:
  Fix Released
Status in process-cpp package in Ubuntu:
  Fix Released

Bug description:
  process-cpp fails to build with an inscrutable error from cmake about
  failing to find pthreads:

  Determining if the function pthread_create exists in the pthreads failed with 
the following output:
  Change Dir: /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp

  Run Build Command:"/usr/bin/make" "cmTC_b3690/fast"
  make[1]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
  /usr/bin/make -f CMakeFiles/cmTC_b3690.dir/build.make 
CMakeFiles/cmTC_b3690.dir/build
  make[2]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
  Building C object CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o
  /usr/bin/cc   -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create   -o 
CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o   -c 
/usr/share/cmake-3.9/Modules/CheckFunctionExists.c
  Linking C executable cmTC_b3690
  /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_b3690.dir/link.txt 
--verbose=1
  /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create  
-Wl,-Bsymbolic-functions -Wl,-z,relro  -rdynamic 
CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o  -o cmTC_b3690 -lpthreads 

  https://launchpad.net/ubuntu/+source/process-
  cpp/3.0.1-0ubuntu6/+build/13627287/+files/buildlog_ubuntu-bionic-amd64
  .process-cpp_3.0.1-0ubuntu6_BUILDING.txt.gz

  pthreads are certainly supported.  They're spelled '-pthread'.  I have
  no idea why cmake is failing to find them, you'd think this is a
  pretty basic thing; and other cmake-using software doesn't seem to
  have this problem.

  Poking around in the CMakeFiles, it appears to be some sort of adverse
  interaction with gmock.  But I don't know why this is or how to fix
  it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1755949/+subscriptions

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

[Desktop-packages] [Bug 1752819] Re: jackd crashed with SIGABRT in std::terminate()

[Seth Arnold]

** Information type changed from Private Security to Public

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

Title:
  jackd crashed with SIGABRT in std::terminate()

Status in jackd2 package in Ubuntu:
  Invalid

Bug description:
  Hi,
  as I first installed UBUNTU BIONIC with some problems on drivers etc. such as 
print samsung recognised but not working,Asus xonar not stilli recognised,and 
AMD video Radeon H4670 not recognised.
  Then I reinstalled UBUNT 17 lts with the same problems.
  So what's still wrong? What should I remove or install?

  Thank You all for your attention.

  BST RGDS

  Angelo

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: jackd2 1.9.12~dfsg-2
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  2 10:01:44 2018
  ExecutablePath: /usr/bin/jackd
  InstallationDate: Installed on 2018-02-14 (15 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180206)
  JournalErrors:
   -- Logs begin at Wed 2018-02-14 14:45:05 CET, end at Fri 2018-03-02 10:04:45 
CET. --
   mar 02 09:53:48 username-desktop kernel: radeon :01:00.0: Invalid PCI 
ROM header signature: expecting 0xaa55, got 0x
   mar 02 09:54:09 username-desktop pulseaudio[1067]: [autospawn] core-util.c: 
Home directory not accessible: Permesso negato
   mar 02 09:54:09 username-desktop pulseaudio[1067]: [pulseaudio] main.c: 
Failed to acquire autospawn lock
   mar 02 09:54:44 username-desktop pulseaudio[1376]: [pulseaudio] 
bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: 
Failed to activate service 'org.bluez': timed out 
(service_start_timeout=25000ms)
  ProcCmdline: /usr/bin/jackd -T -ndefault -dalsa -dhw:0 -r44100 -p1024 -n2
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: jackd2
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libjackserver.so.0
  Title: jackd crashed with SIGABRT in std::terminate()
  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/jackd2/+bug/1752819/+subscriptions

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

[Desktop-packages] [Bug 1755949] Re: process-cpp FTBFS in bionic

[Steve Langasek]

Removing packages from bionic:
dbus-cpp 5.0.0+18.04.20171031-1 in bionic
dbus-cpp-bin 5.0.0+18.04.20171031-1 in bionic amd64
dbus-cpp-bin 5.0.0+18.04.20171031-1 in bionic arm64
dbus-cpp-bin 5.0.0+18.04.20171031-1 in bionic armhf
dbus-cpp-bin 5.0.0+18.04.20171031-1 in bionic i386
dbus-cpp-bin 5.0.0+18.04.20171031-1 in bionic ppc64el
dbus-cpp-bin 5.0.0+18.04.20171031-1 in bionic s390x
dbus-cpp-dev-examples 5.0.0+18.04.20171031-1 in bionic amd64
dbus-cpp-dev-examples 5.0.0+18.04.20171031-1 in bionic arm64
dbus-cpp-dev-examples 5.0.0+18.04.20171031-1 in bionic armhf
dbus-cpp-dev-examples 5.0.0+18.04.20171031-1 in bionic i386
dbus-cpp-dev-examples 5.0.0+18.04.20171031-1 in bionic ppc64el
dbus-cpp-dev-examples 5.0.0+18.04.20171031-1 in bionic s390x
libdbus-cpp-dev 5.0.0+18.04.20171031-1 in bionic amd64
libdbus-cpp-dev 5.0.0+18.04.20171031-1 in bionic arm64
libdbus-cpp-dev 5.0.0+18.04.20171031-1 in bionic armhf
libdbus-cpp-dev 5.0.0+18.04.20171031-1 in bionic i386
libdbus-cpp-dev 5.0.0+18.04.20171031-1 in bionic ppc64el
libdbus-cpp-dev 5.0.0+18.04.20171031-1 in bionic s390x
libdbus-cpp5 5.0.0+18.04.20171031-1 in bionic amd64
libdbus-cpp5 5.0.0+18.04.20171031-1 in bionic arm64
libdbus-cpp5 5.0.0+18.04.20171031-1 in bionic armhf
libdbus-cpp5 5.0.0+18.04.20171031-1 in bionic i386
libdbus-cpp5 5.0.0+18.04.20171031-1 in bionic ppc64el
libdbus-cpp5 5.0.0+18.04.20171031-1 in bionic s390x
Comment: Obsoleted product, build-depends on process-cpp which is broken; LP: 
#1747128
1 package successfully removed.


** Changed in: dbus-cpp (Ubuntu)
   Status: New => Fix Released

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

Title:
  process-cpp FTBFS in bionic

Status in dbus-cpp package in Ubuntu:
  Fix Released
Status in process-cpp package in Ubuntu:
  Fix Released

Bug description:
  process-cpp fails to build with an inscrutable error from cmake about
  failing to find pthreads:

  Determining if the function pthread_create exists in the pthreads failed with 
the following output:
  Change Dir: /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp

  Run Build Command:"/usr/bin/make" "cmTC_b3690/fast"
  make[1]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
  /usr/bin/make -f CMakeFiles/cmTC_b3690.dir/build.make 
CMakeFiles/cmTC_b3690.dir/build
  make[2]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
  Building C object CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o
  /usr/bin/cc   -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create   -o 
CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o   -c 
/usr/share/cmake-3.9/Modules/CheckFunctionExists.c
  Linking C executable cmTC_b3690
  /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_b3690.dir/link.txt 
--verbose=1
  /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create  
-Wl,-Bsymbolic-functions -Wl,-z,relro  -rdynamic 
CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o  -o cmTC_b3690 -lpthreads 

  https://launchpad.net/ubuntu/+source/process-
  cpp/3.0.1-0ubuntu6/+build/13627287/+files/buildlog_ubuntu-bionic-amd64
  .process-cpp_3.0.1-0ubuntu6_BUILDING.txt.gz

  pthreads are certainly supported.  They're spelled '-pthread'.  I have
  no idea why cmake is failing to find them, you'd think this is a
  pretty basic thing; and other cmake-using software doesn't seem to
  have this problem.

  Poking around in the CMakeFiles, it appears to be some sort of adverse
  interaction with gmock.  But I don't know why this is or how to fix
  it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1755949/+subscriptions

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

[Desktop-packages] [Bug 1752417] Re: network-manager doesn't offer IKE VPN connections

[Seth Arnold]

Hello Apicultor,

You can install network-manager-strongswan and the associated StrongSwan
suite of utilities if you want to use IKEv2 VPNs with Network Manager.
LT2P requires 17.10 or the upcoming 18.04 LTS for the network-manager-
l2tp package: https://launchpad.net/ubuntu/+source/network-manager-l2tp

Thanks

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

Title:
  network-manager doesn't offer IKE VPN connections

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  network-manager lists only PPTP as an available VPN client connection
  type (and also offers to import a file). I'd expect L2TP-over-IPSec
  and IKEv1/IKEv2 options as well.

  In fact, most major desktop OSes have removed PPTP altogether because
  it's insecure, and Ubuntu should probably do so in 18.04 as well, at
  least from the GUI!

  $ apt list network-manager
  Llistant… Fet
  network-manager/bionic,now 1.10.4-1ubuntu2 amd64 [instal·lat]

  $ uname -a
  Linux machinename 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

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

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

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

[Desktop-packages] [Bug 1754651] Re: gnome-control-center windows remains open after using the launch-panel/online-accounts/add "API"

[Ubuntu Foundations Team Bug Bot]

The attachment "gcc.debdiff" seems to be a debdiff.  The ubuntu-sponsors
team has been subscribed to the bug report so that they can review and
hopefully sponsor the debdiff.  If the attachment isn't a patch, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  gnome-control-center windows remains open after using the launch-panel
  /online-accounts/add "API"

Status in gnome-control-center package in Ubuntu:
  In Progress

Bug description:
  To reproduce:

  1) open gnome-calendar
  2) go to calendar-settings
  3) activate a row in order to add an account
  4) close the new-account dialog

  Expected result:
  - The gnome-control-center main window is closed

  Actual result:
  - The gnome-control-center main window remains open

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

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

[Desktop-packages] [Bug 1752417] Re: network-manager doesn't offer IKE VPN connections

[Seth Arnold]

** Information type changed from Private Security to Public Security

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

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

Title:
  network-manager doesn't offer IKE VPN connections

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  network-manager lists only PPTP as an available VPN client connection
  type (and also offers to import a file). I'd expect L2TP-over-IPSec
  and IKEv1/IKEv2 options as well.

  In fact, most major desktop OSes have removed PPTP altogether because
  it's insecure, and Ubuntu should probably do so in 18.04 as well, at
  least from the GUI!

  $ apt list network-manager
  Llistant… Fet
  network-manager/bionic,now 1.10.4-1ubuntu2 amd64 [instal·lat]

  $ uname -a
  Linux machinename 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

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

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

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

[Desktop-packages] [Bug 1755949] Re: process-cpp FTBFS in bionic

[Steve Langasek]

** No longer affects: mediascanner2 (Ubuntu)

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

Title:
  process-cpp FTBFS in bionic

Status in dbus-cpp package in Ubuntu:
  New
Status in process-cpp package in Ubuntu:
  New

Bug description:
  process-cpp fails to build with an inscrutable error from cmake about
  failing to find pthreads:

  Determining if the function pthread_create exists in the pthreads failed with 
the following output:
  Change Dir: /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp

  Run Build Command:"/usr/bin/make" "cmTC_b3690/fast"
  make[1]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
  /usr/bin/make -f CMakeFiles/cmTC_b3690.dir/build.make 
CMakeFiles/cmTC_b3690.dir/build
  make[2]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
  Building C object CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o
  /usr/bin/cc   -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create   -o 
CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o   -c 
/usr/share/cmake-3.9/Modules/CheckFunctionExists.c
  Linking C executable cmTC_b3690
  /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_b3690.dir/link.txt 
--verbose=1
  /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create  
-Wl,-Bsymbolic-functions -Wl,-z,relro  -rdynamic 
CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o  -o cmTC_b3690 -lpthreads 

  https://launchpad.net/ubuntu/+source/process-
  cpp/3.0.1-0ubuntu6/+build/13627287/+files/buildlog_ubuntu-bionic-amd64
  .process-cpp_3.0.1-0ubuntu6_BUILDING.txt.gz

  pthreads are certainly supported.  They're spelled '-pthread'.  I have
  no idea why cmake is failing to find them, you'd think this is a
  pretty basic thing; and other cmake-using software doesn't seem to
  have this problem.

  Poking around in the CMakeFiles, it appears to be some sort of adverse
  interaction with gmock.  But I don't know why this is or how to fix
  it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1755949/+subscriptions

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

[Desktop-packages] [Bug 1742612] Re: Xorg crashed with SIGABRT in glamor_make_current()

[Launchpad Bug Tracker]

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

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

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

Title:
  Xorg crashed with SIGABRT in glamor_make_current()

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  X crashes when logging into a KDE or GNOME Shell session; the SDDM
  greeter doesn't tickle the relevant codepath. Similarly, starting X
  and running xterm against works fine.

  It seems that glamor_priv is being unset somewhere?

  This is entirely reproducible, and didn't occur in 17.10.

  This system is somewhat weird, in that it's got both a Radeon and an
  NVIDIA card active in it, with displays connected to both.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0+bcachefs.git20180105.67e9882d-1-generic 
4.13.13
  Uname: Linux 4.13.0+bcachefs.git20180105.67e9882d-1-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Wed Jan 10 17:23:11 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn XT [Radeon HD 7870 GHz 
Edition] [1002:6818] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Pitcairn XT [Radeon HD 7870 GHz 
Edition] [1458:2554]
   NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GM107 [GeForce GTX 750 Ti] [1043:84bb]
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/lib/xorg/Xorg -nolisten tcp -auth 
/var/run/sddm/{d1b73357-b856-41a6-8073-0a4d2de13cc3} -background none -noreset 
-displayfd 17 vt7
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
  ProcKernelCmdLine: 
BOOT_IMAGE=/vmlinuz-4.13.0+bcachefs.git20180105.67e9882d-1-generic root= ro 
quiet splash vt.handoff=7 break=mount
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   glamor_make_current (glamor_priv=0x0) at 
../../../../glamor/glamor_utils.h:726
   glamor_block_handler (screen=0x55f93f2b9140) at 
../../../../glamor/glamor.c:258
   radeon_cs_flush_indirect (pScrn=0x55f93f2bcb90) at ../../src/radeon_kms.c:108
   redisplay_dirty (dirty=0x55f93f3a3570, region=0x55f93f873220) at 
../../src/radeon_kms.c:585
   radeon_dirty_update (scrn=0x55f93f2bc1f0) at ../../src/radeon_kms.c:884
  Title: Xorg crashed with SIGABRT in glamor_make_current()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/05/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1904
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170 PRO GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1904:bd07/05/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  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 N/A
  version.libdrm2: libdrm2 2.4.89-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1755949] [NEW] process-cpp FTBFS in bionic

[Steve Langasek]

Public bug reported:

process-cpp fails to build with an inscrutable error from cmake about
failing to find pthreads:

Determining if the function pthread_create exists in the pthreads failed with 
the following output:
Change Dir: /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTC_b3690/fast"
make[1]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_b3690.dir/build.make 
CMakeFiles/cmTC_b3690.dir/build
make[2]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o
/usr/bin/cc   -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create   -o 
CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o   -c 
/usr/share/cmake-3.9/Modules/CheckFunctionExists.c
Linking C executable cmTC_b3690
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_b3690.dir/link.txt 
--verbose=1
/usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create  
-Wl,-Bsymbolic-functions -Wl,-z,relro  -rdynamic 
CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o  -o cmTC_b3690 -lpthreads 

https://launchpad.net/ubuntu/+source/process-
cpp/3.0.1-0ubuntu6/+build/13627287/+files/buildlog_ubuntu-bionic-amd64
.process-cpp_3.0.1-0ubuntu6_BUILDING.txt.gz

pthreads are certainly supported.  They're spelled '-pthread'.  I have
no idea why cmake is failing to find them, you'd think this is a pretty
basic thing; and other cmake-using software doesn't seem to have this
problem.

Poking around in the CMakeFiles, it appears to be some sort of adverse
interaction with gmock.  But I don't know why this is or how to fix it.

** Affects: dbus-cpp (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: process-cpp (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: dbus-cpp (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  process-cpp FTBFS in bionic

Status in dbus-cpp package in Ubuntu:
  New
Status in process-cpp package in Ubuntu:
  New

Bug description:
  process-cpp fails to build with an inscrutable error from cmake about
  failing to find pthreads:

  Determining if the function pthread_create exists in the pthreads failed with 
the following output:
  Change Dir: /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp

  Run Build Command:"/usr/bin/make" "cmTC_b3690/fast"
  make[1]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
  /usr/bin/make -f CMakeFiles/cmTC_b3690.dir/build.make 
CMakeFiles/cmTC_b3690.dir/build
  make[2]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
  Building C object CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o
  /usr/bin/cc   -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create   -o 
CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o   -c 
/usr/share/cmake-3.9/Modules/CheckFunctionExists.c
  Linking C executable cmTC_b3690
  /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_b3690.dir/link.txt 
--verbose=1
  /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create  
-Wl,-Bsymbolic-functions -Wl,-z,relro  -rdynamic 
CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o  -o cmTC_b3690 -lpthreads 

  https://launchpad.net/ubuntu/+source/process-
  cpp/3.0.1-0ubuntu6/+build/13627287/+files/buildlog_ubuntu-bionic-amd64
  .process-cpp_3.0.1-0ubuntu6_BUILDING.txt.gz

  pthreads are certainly supported.  They're spelled '-pthread'.  I have
  no idea why cmake is failing to find them, you'd think this is a
  pretty basic thing; and other cmake-using software doesn't seem to
  have this problem.

  Poking around in the CMakeFiles, it appears to be some sort of adverse
  interaction with gmock.  But I don't know why this is or how to fix
  it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1755949/+subscriptions

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

[Desktop-packages] [Bug 1617564] Re: [master] package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which

[Seth Arnold]

Is there any chance someone from the desktop team could add a Conflicts:
line (or whichever line is most appropriate) to account-plugin-facebook
in account-plugins before 18.04 LTS is released, so we could avoid
another five years of this bug? :)

Please? :)

Thanks

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

Title:
  [master] package kaccounts-providers (not installed) failed to
  install/upgrade: trying to overwrite '/etc/signon-ui/webkit-
  options.d/www.facebook.com.conf', which is also in package account-
  plugin-facebook 0.12+16.04.20160126-0ubuntu1

Status in One Hundred Papercuts:
  Confirmed
Status in account-plugins package in Ubuntu:
  Confirmed
Status in kaccounts-providers package in Ubuntu:
  Confirmed

Bug description:
  showing this error when installing kde environment in ubuntu 16.04. it
  say kaccounts  niot installed. so i think it may cause some security
  issue

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: kaccounts-providers (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Aug 27 18:11:18 2016
  DuplicateSignature:
   package:kaccounts-providers:(not installed)
   Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb
 (--unpack):
    trying to overwrite '/usr/share/accounts/services/google-im.service', which 
is also in package account-plugin-google 0.12+16.04.20160126-0ubuntu1
  ErrorMessage: trying to overwrite 
'/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in 
package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1
  InstallationDate: Installed on 2016-08-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: kaccounts-providers
  Title: package kaccounts-providers (not installed) failed to install/upgrade: 
trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', 
which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1752940] Re: Major security vulnerability in 2.92 please upgrade PPA to 2.93

[Seth Arnold]

Hello, this was fixed in https://usn.ubuntu.com/3533-1/ .

If you have problems with specific trackers blocking this version it'd
be best to open a new bug with details, so that a Stable Release Update
could be prepared: https://wiki.ubuntu.com/StableReleaseUpdates

Thanks

** Information type changed from Private Security to Public Security

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

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

Title:
  Major security vulnerability in 2.92 please upgrade PPA to 2.93

Status in transmission package in Ubuntu:
  Fix Released

Bug description:
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5702

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

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

[Desktop-packages] [Bug 1755934] Re: gnome-calendar crashed with SIGSEGV in gcal_manager_get_default_source()

[Apport retracing service]

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

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 #1725005, 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/1755934/+attachment/5079872/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-calendar crashed with SIGSEGV in
  gcal_manager_get_default_source()

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  After I tried to create a calendar event the app froze for ~10 secs
  and then crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-calendar 3.27.90-1build1
  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
  CrashCounter: 1
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Wed Mar 14 23:36:02 2018
  ExecutablePath: /usr/bin/gnome-calendar
  InstallationDate: Installed on 2017-09-08 (187 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x556578d2faa6 :   
cmp(%rdx),%rax
   PC (0x556578d2faa6) ok
   source "(%rdx)" (0x13c7568261) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-calendar
  StacktraceTop:
   gcal_manager_get_default_source ()
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-calendar crashed with SIGSEGV in 
gcal_manager_get_default_source()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo

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

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

[Desktop-packages] [Bug 1755938] [NEW] gnome-shell crashed with SIGABRT in g_assertion_message()

[chris pollock]

Public bug reported:

lsb_release -rd
Description:Ubuntu 16.04.4 LTS
Release:16.04

apt-cache policy gnome-shell
gnome-shell:
  Installed: 3.18.5-0ubuntu0.3
  Candidate: 3.18.5-0ubuntu0.3
  Version table:
 *** 3.18.5-0ubuntu0.3 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
100 /var/lib/dpkg/status
 3.18.4-0ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

Happened for no reason that I can see. Syslog output of the crash is
here - https://paste.ubuntu.com/p/JJzsS7T6mQ/

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

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

Title:
  gnome-shell crashed with SIGABRT in g_assertion_message()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.18.5-0ubuntu0.3
Candidate: 3.18.5-0ubuntu0.3
Version table:
   *** 3.18.5-0ubuntu0.3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   3.18.4-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  Happened for no reason that I can see. Syslog output of the crash is
  here - https://paste.ubuntu.com/p/JJzsS7T6mQ/

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

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

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

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Loggig first defect... I did sudo apt-get autoclean, next sudo apt-get 
autocelan, next sudo apt-get autoremove and finally  restart my laptop.
  After booting I got error message - hope it's in the logs...

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  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: GNOME-Greeter:GNOME
  Date: Wed Mar 14 22:25:18 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2016-01-19 (784 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.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-14 (0 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1754651] Re: gnome-control-center windows remains open after using the launch-panel/online-accounts/add "API"

[Andrea Azzarone]

Please find attached a possible fix. Please notice that I'm not
forwarding this upstream as I would prefer to have a cleaner solution
upstream. Possibly we might need to extend gnome-online-accounts api to
improve the client-side add-account dialog.

** Patch added: "gcc.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1754651/+attachment/5079854/+files/gcc.debdiff

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

Title:
  gnome-control-center windows remains open after using the launch-panel
  /online-accounts/add "API"

Status in gnome-control-center package in Ubuntu:
  In Progress

Bug description:
  To reproduce:

  1) open gnome-calendar
  2) go to calendar-settings
  3) activate a row in order to add an account
  4) close the new-account dialog

  Expected result:
  - The gnome-control-center main window is closed

  Actual result:
  - The gnome-control-center main window remains open

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

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

[Desktop-packages] [Bug 1755928] [NEW] [snap] build artifacts in snap and in LD_LIBRARY_PATH

[Olivier Tilloy]

Public bug reported:

The snap includes build artifacts under $SNAP/build that shouldn't be
there:

$ ls 
/snap/libreoffice/current/build/libreoffice-6.0/parts/libreoffice/build/workdir/UnpackedTarball/*/src/.libs/
/snap/libreoffice/current/build/libreoffice-6.0/parts/libreoffice/build/workdir/UnpackedTarball/gpgmepp/src/.libs/:
libgpgme.so.11

/snap/libreoffice/current/build/libreoffice-6.0/parts/libreoffice/build/workdir/UnpackedTarball/libassuan/src/.libs/:
libassuan.so.0

Those shared libs are also found under $SNAP/lib/libreoffice/program/.

The command-*.wrapper scripts add those paths to the LD_LIBRARY_PATH.

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu Bionic Beaver (development branch)"

DESKTOP_SESSION=ubuntu
GTK_MODULES=gail:atk-bridge
HOME=/home/osomon/snap/libreoffice/56
LANG=fr_FR.UTF-8
LC_MONETARY=fr_FR.UTF-8
LC_NAME=fr_FR.UTF-8
LC_NUMERIC=fr_FR.UTF-8
LC_TIME=fr_FR.UTF-8
LD_LIBRARY_PATH=/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl32:/var/lib/snapd/void:/snap/libreoffice/56/build/libreoffice-6.0/parts/libreoffice/build/workdir/UnpackedTarball/gpgmepp/src/.libs:/snap/libreoffice/56/build/libreoffice-6.0/parts/libreoffice/build/workdir/UnpackedTarball/libassuan/src/.libs:/snap/libreoffice/56/lib/x86_64-linux-gnu:/snap/libreoffice/56/usr/lib:/snap/libreoffice/56/usr/lib/man-db:/snap/libreoffice/56/usr/lib/x86_64-linux-gnu:/snap/libreoffice/56/usr/lib/x86_64-linux-gnu/mesa:/snap/libreoffice/56/usr/lib/x86_64-linux-gnu/mesa-egl:/snap/libreoffice/56/usr/lib/x86_64-linux-gnu/pulseaudio:/snap/libreoffice/56/usr/lib/x86_64-linux-gnu/mesa-egl:/snap/libreoffice/56/usr/lib/x86_64-linux-gnu/mesa::/snap/libreoffice/56/lib:/snap/libreoffice/56/usr/lib:/snap/libreoffice/56/lib/x86_64-linux-gnu:/snap/libreoffice/56/usr/lib/x86_64-linux-gnu
PATH=/snap/libreoffice/56/usr/sbin:/snap/libreoffice/56/usr/bin:/snap/libreoffice/56/sbin:/snap/libreoffice/56/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
SNAP=/snap/libreoffice/56
SNAP_ARCH=amd64
SNAP_COMMON=/var/snap/libreoffice/common
SNAP_DATA=/var/snap/libreoffice/56
SNAP_LIBRARY_PATH=/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl32:/var/lib/snapd/void
SNAP_NAME=libreoffice
SNAP_REEXEC=
SNAP_REVISION=56
SNAP_USER_COMMON=/home/osomon/snap/libreoffice/common
SNAP_USER_DATA=/home/osomon/snap/libreoffice/56
SNAP_VERSION=6.0.2.1
TEMPDIR=/tmp
TMPDIR=/run/user/1000/snap.libreoffice
XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg
XDG_CURRENT_DESKTOP=ubuntu:GNOME
XDG_DATA_DIRS=/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop
XDG_RUNTIME_DIR=/run/user/1000/snap.libreoffice
XDG_SESSION_DESKTOP=ubuntu
XDG_SESSION_TYPE=x11

** Affects: libreoffice (Ubuntu)
 Importance: Low
 Status: Triaged


** Tags: snap

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

** Changed in: libreoffice (Ubuntu)
   Importance: Undecided => Low

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

Title:
  [snap] build artifacts in snap and in LD_LIBRARY_PATH

Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  The snap includes build artifacts under $SNAP/build that shouldn't be
  there:

  $ ls 
/snap/libreoffice/current/build/libreoffice-6.0/parts/libreoffice/build/workdir/UnpackedTarball/*/src/.libs/
  
/snap/libreoffice/current/build/libreoffice-6.0/parts/libreoffice/build/workdir/UnpackedTarball/gpgmepp/src/.libs/:
  libgpgme.so.11

  
/snap/libreoffice/current/build/libreoffice-6.0/parts/libreoffice/build/workdir/UnpackedTarball/libassuan/src/.libs/:
  libassuan.so.0

  Those shared libs are also found under $SNAP/lib/libreoffice/program/.

  The command-*.wrapper scripts add those paths to the LD_LIBRARY_PATH.

  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu Bionic Beaver (development branch)"

  DESKTOP_SESSION=ubuntu
  GTK_MODULES=gail:atk-bridge
  HOME=/home/osomon/snap/libreoffice/56
  LANG=fr_FR.UTF-8
  LC_MONETARY=fr_FR.UTF-8
  LC_NAME=fr_FR.UTF-8
  LC_NUMERIC=fr_FR.UTF-8
  LC_TIME=fr_FR.UTF-8
  

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

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  backup had just finished, after i installed windows TTF

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  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: GNOME-Greeter:GNOME
  Date: Wed Mar 14 15:56:27 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-12 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  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/1755921/+subscriptions

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

[Desktop-packages] [Bug 714908] Re: gnome-keyring reads unsafe SSH keys

[Bug Watch Updater]

** Changed in: gnome-keyring
   Status: Confirmed => Fix Released

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

Title:
  gnome-keyring reads unsafe SSH keys

Status in GNOME Keyring:
  Fix Released
Status in gnome-keyring package in Ubuntu:
  Invalid
Status in gnome-keyring source package in Natty:
  Invalid

Bug description:
  Binary package hint: gnome-keyring

  OpenSSH enforces that one's keys must be mode 0700 so that unsafe
  permissions do not go unnoticed. gnome-keyring should perform this
  check as well. It looks like pkcs11/ssh-store/gkm-ssh-private-key.c
  gkm_ssh_private_key_parse() is the place to do it, or possibly pkcs11
  /ssh-store/gkm-ssh-module.c file_load() since it checks some aspects
  of the files already.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-keyring 2.92.92.is.2.32.1-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.37-12.26-generic 2.6.37
  Uname: Linux 2.6.37-12-generic x86_64
  Architecture: amd64
  Date: Mon Feb  7 15:23:20 2011
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   LC_MESSAGES=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-keyring

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

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

[Desktop-packages] [Bug 1730451] Re: MemoryError while verifying backup

[Launchpad Bug Tracker]

This bug was fixed in the package duplicity - 0.7.17-0ubuntu1

---
duplicity (0.7.17-0ubuntu1) bionic; urgency=medium

  * New upstream bug-fix release
- Reverts a new feature that required too much memory, causing
  OOM crashes (LP: #1730451)

 -- Michael Terry   Tue, 13 Mar 2018 11:12:30 -0400

** Changed in: duplicity (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  MemoryError while verifying backup

Status in Duplicity:
  Fix Released
Status in duplicity package in Ubuntu:
  Fix Released

Bug description:
  While trying to verify a backup (launched from deja-dup), I receive
  the following error.  My system currently shows 11G of RAM available
  plus 23G of swap.  Possibly related to #1720159?

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 763, in get_fileobj_iter
  manifest = backup_set.get_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, 
in get_manifest
  return self.get_local_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224, 
in get_local_manifest
  return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 214, in 
from_string
  for match in vi_iterator:
  MemoryError

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  6 10:50:12 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-03 (1190 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: duplicity
  UpgradeStatus: Upgraded to artful on 2017-09-29 (37 days ago)

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

-- 
Mailing list: https://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 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

[Lars Nyqvist]

Firefox 59 fails as earlier .

Mozilla Crash Reporter:

Add-ons: 
activity-stream%40mozilla.org:2018.02.17.0026-173e2795,aushelper%40mozilla.org:2.0,firefox%40getpocket.com:1.0.5,followonsearch%40mozilla.com:0.9.6,formautofill%40mozilla.org:1.0,onboarding%40mozilla.org:1.0,screenshots%40mozilla.org:25.0.0,shield-recipe-client%40mozilla.org:80,webcompat%40mozilla.org:1.1,%7B972ce4c6-7e08-4474-a285-3208198ce6fd%7D:59.0,langpack-fi%40firefox.mozilla.org:59.0,langpack-en-GB%40firefox.mozilla.org:59.0,langpack-en-ZA%40firefox.mozilla.org:59.0
BuildID: 20180313132558
CrashTime: 1521057567
DOMIPCEnabled: 1
EMCheckCompatibility: true
Email:
FramePoisonBase: 004041121792
FramePoisonSize: 4096
InstallTime: 1521056803
Notes: Ubuntu 17.10FP(D00-L1000-W-T000) OpenGL: VMware, Inc.
-- llvmpipe (LLVM 5.0, 128 bits) -- 3.0 Mesa 17.2.8 --
texture_from_pixmap
WR? WR- OMTP? OMTP-
ProductID: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
ProductName: Firefox
ReleaseChannel: release
SafeMode: 0
SecondsSinceLastCrash: 754
StartupCrash: 0
StartupTime: 1521057071
TelemetryEnvironment:
{"build":{"applicationId":"{ec8030f7-c20a-464f-9b0e-13a3a9e97384}","applicationName":"Firefox","architecture":"arm","buildId":"20180313132558","version":"59.0","vendor":"Mozilla","platformVersion":"59.0","xpcomAbi":"arm-eabi-gcc3","hotfixVersion":null,"updaterAvailable":false},"partner":{"distributionId":null,"distributionVersion":null,"partnerId":null,"distributor":null,"distributorChannel":null,"partnerNames":[]},"system":{"memoryMB":2014,"virtualMaxMB":null,"cpu":{"count":4,"cores":null,"vendor":null,"family":null,"model":null,"stepping":null,"l2cacheKB":null,"l3cacheKB":null,"speedMHz":1608,"extensions":["hasEDSP","hasARMv6","hasARMv7","hasNEON"]},"os":{"name":"Linux","version":"4.13.5","locale":"fi-FI"},"hdd":{"profile":{"model":null,"revision":null},"binary":{"model":null,"revision":null},"system":{"model":null,"revision":null}},"gfx":{"D2DEnabled":null,"DWriteEnabled":null,"ContentBackend":"Cairo","adapters":[{"description":"VMware,
Inc. -- llvmpipe (LLVM 5.0, 128 bits)","vendorID":"VMware,
Inc.","deviceID":"llvmpipe (LLVM 5.0, 128
bits)","subsysID":null,"RAM":null,"driver":null,"driverVersion":"3.0
Mesa 
17.2.8","driverDate":null,"GPUActive":true}],"monitors":[],"features":{"compositor":"none","gpuProcess":{"status":"unused"}}},"appleModelId":null},"settings":{"blocklistEnabled":true,"e10sEnabled":true,"e10sMultiProcesses":4,"telemetryEnabled":false,"locale":"en-US","update":{"channel":"release","enabled":false,"autoDownload":true},"userPrefs":{"browser.search.widget.inNavBar":false,"browser.startup.homepage":"","general.config.filename":""},"sandbox":{"effectiveContentProcessLevel":null},"addonCompatibilityCheckEnabled":true,"isDefaultBrowser":null},"profile":{}}
Theme: classic/1.0
ThreadIdNameMapping: 12238:"Gecko_IOThread",12240:"Timer",12241:"Link
Monitor",12242:"Socket Thread",12243:"JS
Watchdog",12252:"BGReadURLs",12253:"Hang Monitor",12262:"Cache2
I/O",12263:"Cookie",12266:"DOM Worker",12267:"IPDL
Background",12271:"LoadRoots",12273:"GMPThread",12274:"SoftwareVsyncThread",12275:"Compositor",12276:"VRListener",12277:"ImgDecoder
#1",12278:"ImgDecoder #2",12279:"ImgDecoder
#3",12280:"ImageIO",12285:"DataStorage",12286:"DataStorage",12287:"SysProxySetting",12289:"ProxyResolution",12290:"DataStorage",12291:"URL
Classifier",12293:"Classifier Update",12296:"HTML5
Parser",12297:"StreamTrans
#4",12300:"ImageBridgeChild",12301:"ProcessHangMon",
Throttleable: 1
UptimeTS: 618.2765232
Vendor: Mozilla
Version: 59.0
useragent_locale: en-US

This report also contains technical information about the state of the
application when it crashed.

Debug :

$ firefox -g
GNU gdb (Ubuntu 8.0.1-0ubuntu1) 8.0.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabihf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/firefox/firefox...Reading symbols from
/usr/lib/debug/.build-id/bd/a0a6829cde3953f321d5d0e1ef0e32cb8b82a1.debug...done.
done.
(gdb) run
Starting program: /usr/lib/firefox/firefox
Cannot parse expression `.L1200 4@r4'.
warning: Probes-based dynamic linker interface failed.
Reverting to original interface.

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Can't read data for section '.debug_info' in file

[Desktop-packages] [Bug 1755913] [NEW] [snap] testing libreoffice.filebug

[Olivier Tilloy]

Public bug reported:

this is a simple test

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu Bionic Beaver (development branch)"

DESKTOP_SESSION=ubuntu
GTK_MODULES=gail:atk-bridge
HOME=/home/osomon/snap/libreoffice/x1
LANG=fr_FR.UTF-8
LC_MONETARY=fr_FR.UTF-8
LC_NAME=fr_FR.UTF-8
LC_NUMERIC=fr_FR.UTF-8
LC_TIME=fr_FR.UTF-8
LD_LIBRARY_PATH=/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl32:/var/lib/snapd/void:/snap/libreoffice/x1/build/libreoffice-6.0/parts/libreoffice/build/workdir/UnpackedTarball/gpgmepp/src/.libs:/snap/libreoffice/x1/build/libreoffice-6.0/parts/libreoffice/build/workdir/UnpackedTarball/libassuan/src/.libs:/snap/libreoffice/x1/lib/x86_64-linux-gnu:/snap/libreoffice/x1/usr/lib:/snap/libreoffice/x1/usr/lib/man-db:/snap/libreoffice/x1/usr/lib/x86_64-linux-gnu:/snap/libreoffice/x1/usr/lib/x86_64-linux-gnu/mesa:/snap/libreoffice/x1/usr/lib/x86_64-linux-gnu/mesa-egl:/snap/libreoffice/x1/usr/lib/x86_64-linux-gnu/pulseaudio:/snap/libreoffice/x1/usr/lib/x86_64-linux-gnu/mesa-egl:/snap/libreoffice/x1/usr/lib/x86_64-linux-gnu/mesa::/snap/libreoffice/x1/lib:/snap/libreoffice/x1/usr/lib:/snap/libreoffice/x1/lib/x86_64-linux-gnu:/snap/libreoffice/x1/usr/lib/x86_64-linux-gnu
PATH=/snap/libreoffice/x1/usr/sbin:/snap/libreoffice/x1/usr/bin:/snap/libreoffice/x1/sbin:/snap/libreoffice/x1/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
SNAP=/snap/libreoffice/x1
SNAP_ARCH=amd64
SNAP_COMMON=/var/snap/libreoffice/common
SNAP_DATA=/var/snap/libreoffice/x1
SNAP_LIBRARY_PATH=/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl32:/var/lib/snapd/void
SNAP_NAME=libreoffice
SNAP_REEXEC=
SNAP_REVISION=x1
SNAP_USER_COMMON=/home/osomon/snap/libreoffice/common
SNAP_USER_DATA=/home/osomon/snap/libreoffice/x1
SNAP_VERSION=6.0.2.1
TEMPDIR=/tmp
TMPDIR=/run/user/1000/snap.libreoffice
XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg
XDG_CURRENT_DESKTOP=ubuntu:GNOME
XDG_DATA_DIRS=/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop
XDG_RUNTIME_DIR=/run/user/1000/snap.libreoffice
XDG_SESSION_DESKTOP=ubuntu
XDG_SESSION_TYPE=x11

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


** Tags: snap

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

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

Title:
  [snap] testing libreoffice.filebug

Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  this is a simple test

  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu Bionic Beaver (development branch)"

  DESKTOP_SESSION=ubuntu
  GTK_MODULES=gail:atk-bridge
  HOME=/home/osomon/snap/libreoffice/x1
  LANG=fr_FR.UTF-8
  LC_MONETARY=fr_FR.UTF-8
  LC_NAME=fr_FR.UTF-8
  LC_NUMERIC=fr_FR.UTF-8
  LC_TIME=fr_FR.UTF-8
  
LD_LIBRARY_PATH=/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl32:/var/lib/snapd/void:/snap/libreoffice/x1/build/libreoffice-6.0/parts/libreoffice/build/workdir/UnpackedTarball/gpgmepp/src/.libs:/snap/libreoffice/x1/build/libreoffice-6.0/parts/libreoffice/build/workdir/UnpackedTarball/libassuan/src/.libs:/snap/libreoffice/x1/lib/x86_64-linux-gnu:/snap/libreoffice/x1/usr/lib:/snap/libreoffice/x1/usr/lib/man-db:/snap/libreoffice/x1/usr/lib/x86_64-linux-gnu:/snap/libreoffice/x1/usr/lib/x86_64-linux-gnu/mesa:/snap/libreoffice/x1/usr/lib/x86_64-linux-gnu/mesa-egl:/snap/libreoffice/x1/usr/lib/x86_64-linux-gnu/pulseaudio:/snap/libreoffice/x1/usr/lib/x86_64-linux-gnu/mesa-egl:/snap/libreoffice/x1/usr/lib/x86_64-linux-gnu/mesa::/snap/libreoffice/x1/lib:/snap/libreoffice/x1/usr/lib:/snap/libreoffice/x1/lib/x86_64-linux-gnu:/snap/libreoffice/x1/usr/lib/x86_64-linux-gnu
  
PATH=/snap/libreoffice/x1/usr/sbin:/snap/libreoffice/x1/usr/bin:/snap/libreoffice/x1/sbin:/snap/libreoffice/x1/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  SNAP=/snap/libreoffice/x1
  SNAP_ARCH=amd64
  SNAP_COMMON=/var/snap/libreoffice/common
  SNAP_DATA=/var/snap/libreoffice/x1
  
SNAP_LIBRARY_PATH=/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl32:/var/lib/snapd/void
  SNAP_NAME=libreoffice
  SNAP_REEXEC=
  SNAP_REVISION=x1
  SNAP_USER_COMMON=/home/osomon/snap/libreoffice/common
  SNAP_USER_DATA=/home/osomon/snap/libreoffice/x1
  SNAP_VERSION=6.0.2.1
  TEMPDIR=/tmp
  TMPDIR=/run/user/1000/snap.libreoffice
  XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg
  XDG_CURRENT_DESKTOP=ubuntu:GNOME
  
XDG_DATA_DIRS=/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop
  XDG_RUNTIME_DIR=/run/user/1000/snap.libreoffice
  XDG_SESSION_DESKTOP=ubuntu
  XDG_SESSION_TYPE=x11

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1750289] Re: gnome-disks crashed with SIGSEGV in udisks_partition_table_get_type_()

[Rui Madeira]

Also ran into this, formatting a new sata drive with ext4

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

Title:
  gnome-disks crashed with SIGSEGV in udisks_partition_table_get_type_()

Status in gnome-disk-utility package in Ubuntu:
  Confirmed

Bug description:
  When trying to format usb2 stick

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-disk-utility 3.27.90-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-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 18 23:40:52 2018
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2018-02-08 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208)
  JournalErrors:
   -- Logs begin at Thu 2018-02-08 20:55:29 CET, end at Sun 2018-02-18 23:41:14 
CET. --
   feb 18 10:57:37 hostname avahi-daemon[1187]: chroot.c: open() failed: No 
such file or directory
   feb 18 10:57:37 hostname NetworkManager[1202]: 
((src/devices/nm-device.c:1452)): assertion '' failed
   feb 18 10:58:02 hostname gdm-password][3049]: pam_env(gdm-password:session): 
Expandable variables must be wrapped in {} <@valencia:en> - ignoring
   feb 18 10:58:03 hostname pulseaudio[3253]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
  ProcCmdline: /usr/bin/gnome-disks --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7fedd31179f9 :   
mov(%rbx),%rdi
   PC (0x7fedd31179f9) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-disk-utility
  StacktraceTop:
   udisks_partition_table_get_type_ () at 
/usr/lib/x86_64-linux-gnu/libudisks2.so.0
   finish_cb ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-disks crashed with SIGSEGV in udisks_partition_table_get_type_()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev pulse pulse-access sambashare 
sudo video

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

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

[Desktop-packages] [Bug 1745666] Re: gsd-housekeeping leaks file descriptors

[ROnaldve]

on Bionic gnome too, for me it says:

gsd-housekeepin[983]: Failed to enumerate children of 
/tmp/systemd-private-babe9614aa12489a9f2fc7347580de0b-rtkit-daemon.service-Dq1Pd4:
 Error opening directory 
'/tmp/systemd-private-babe9614aa12489a9f2fc7347580de0b-rtkit-daemon.service-Dq1Pd4':
 Permission denied
Mar 14 21:02:06 nx7400 gsd-housekeepin[983]: Failed to enumerate children of 
/tmp/systemd-private-babe9614aa12489a9f2fc7347580de0b-colord.service-7OoC3b: 
Error opening directory 
'/tmp/systemd-private-babe9614aa12489a9f2fc7347580de0b-colord.service-7OoC3b': 
Permission denied
Mar 14 21:02:06 nx7400 gsd-housekeepin[983]: Failed to enumerate children of 
/var/tmp/systemd-private-babe9614aa12489a9f2fc7347580de0b-colord.service-Ydr791:
 Error opening directory 
'/var/tmp/systemd-private-babe9614aa12489a9f2fc7347580de0b-colord.service-Ydr791':
 Permission denied
Mar 14 21:02:06 nx7400 gsd-housekeepin[983]: Failed to enumerate children of 
/tmp/systemd-private-babe9614aa12489a9f2fc7347580de0b-systemd-resolved.service-R5QQbf:
 Error opening directory 
'/tmp/systemd-private-babe9614aa12489a9f2fc7347580de0b-systemd-resolved.service-R5QQbf':
 Permission denied
Mar 14 21:02:06 nx7400 gsd-housekeepin[983]: Failed to enumerate children of 
/var/tmp/systemd-private-babe9614aa12489a9f2fc7347580de0b-ntp.service-Sms3zf: 
Error opening directory 
'/var/tmp/systemd-private-babe9614aa12489a9f2fc7347580de0b-ntp.service-Sms3zf': 
Permission denied
Mar 14 21:02:06 nx7400 gsd-housekeepin[983]: Failed to enumerate children of 
/tmp/systemd-private-babe9614aa12489a9f2fc7347580de0b-ntp.service-FS65FP: Error 
opening directory 
'/tmp/systemd-private-babe9614aa12489a9f2fc7347580de0b-ntp.service-FS65FP': 
Permission denied
Mar 14 21:02:06 nx7400 gsd-housekeepin[983]: Failed to enumerate children of 
/var/tmp/systemd-private-babe9614aa12489a9f2fc7347580de0b-rtkit-daemon.service-8OSzh6:
 Error opening directory 
'/var/tmp/systemd-private-babe9614aa12489a9f2fc7347580de0b-rtkit-daemon.service-8OSzh6':
 Permission denied
Mar 14 21:02:06 nx7400 gsd-housekeepin[983]: Failed to enumerate children of 
/var/tmp/systemd-private-babe9614aa12489a9f2fc7347580de0b-systemd-resolved.service-qSrjak:
 Error opening directory 
'/var/tmp/systemd-private-babe9614aa12489a9f2fc7347580de0b-systemd-resolved.service-qSrjak':
 Permission denied
... and goes on and on..

I eased access to tmp and /var/tmp dir's to rwxrwxr.. (not recursive) for the 
both, maybe it helps.
..earlier in the day this made my laptop reboot.

hope it helps.

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

Title:
  gsd-housekeeping leaks file descriptors

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

Bug description:
  Apparently a process called gsd-housekeeping is periodically invoked
  on my Ubuntu 17.10 system. It traverses my /var/tmp for some reason.
  Looks like it is leaking file descriptors while doing so.

  My syslogs are full of error messages like the following:

  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_raw_storage_iter.h: Error 
opening directory 
'/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_raw_storage_iter.h': Too many 
open files
  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/basic_string.h: Error opening 
directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/basic_string.h': Too 
many open files
  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/quoted_string.h: Error opening 
directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/quoted_string.h': Too 
many open files
  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/postypes.h: Error opening 
directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/postypes.h': Too many 
open files
  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_iterator.h: Error opening 
directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_iterator.h': Too 
many open files
  Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of 
/var/tmp/chmaa-backup/usr/include/c++/5/bits/move.h: Error opening directory 
'/var/tmp/chmaa-backup/usr/include/c++/5/bits/move.h': Too many open files

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt policy gnome-settings-daemon
  gnome-settings-daemon:
Installed: 3.26.2-0ubuntu0.1
Candidate: 3.26.2-0ubuntu0.1
Version table:
   *** 3.26.2-0ubuntu0.1 500
  500 http://se.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.26.1-0ubuntu5 500
   

[Desktop-packages] [Bug 1755900] [NEW] sql cookie errors from gnome-shell, or its users

[Dimitri John Ledkov]

Public bug reported:

it seems like gnome-shell; or something that calls into gnome-shell;
have trouble with sqlite:

journalctl -b -e | grep -e gnome-shell -e org.gnome.Shell.desktop | grep
sqlite

has a lot of:

org.gnome.Shell.desktop[24475]:
[16281:32625:0314/201004.637228:ERROR:connection.cc(1945)] Cookie sqlite
error 1, errno 0: cannot start a transaction within a transaction, sql:
BEGIN TRANSACTION


and similar. My current boot has 66 of them, with only 10h of uptime.

I do suspend and resume.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.27.92-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 14 20:11:22 2018
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'command-history' b"['r']"
 b'org.gnome.shell' b'favorite-apps' b"['hexchat.desktop', 
'chrome-bebigdkelppomhhjaaianniiifjbgocn-Default.desktop', 
'chrome-clhhggbfdinjmjhajaheehoeibfljjno-Default.desktop', 
'google-chrome.desktop', 'firefox.desktop', 'yubioath.desktop', 
'org.gnome.Terminal.desktop', 'org.gnome.Nautilus.desktop', 
'virt-manager.desktop', 'pgadmin3.desktop', 'android-studio.desktop', 
'gnome-control-center.desktop']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2012-01-12 (2253 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318)
ProcEnviron:
 LANG=en_US.UTF-8
 TERM=xterm-256color
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to bionic on 2018-01-11 (62 days ago)

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


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

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

Title:
  sql cookie errors from gnome-shell, or its users

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  it seems like gnome-shell; or something that calls into gnome-shell;
  have trouble with sqlite:

  journalctl -b -e | grep -e gnome-shell -e org.gnome.Shell.desktop |
  grep sqlite

  has a lot of:

  org.gnome.Shell.desktop[24475]:
  [16281:32625:0314/201004.637228:ERROR:connection.cc(1945)] Cookie
  sqlite error 1, errno 0: cannot start a transaction within a
  transaction, sql: BEGIN TRANSACTION

  
  and similar. My current boot has 66 of them, with only 10h of uptime.

  I do suspend and resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 14 20:11:22 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' b"['r']"
   b'org.gnome.shell' b'favorite-apps' b"['hexchat.desktop', 
'chrome-bebigdkelppomhhjaaianniiifjbgocn-Default.desktop', 
'chrome-clhhggbfdinjmjhajaheehoeibfljjno-Default.desktop', 
'google-chrome.desktop', 'firefox.desktop', 'yubioath.desktop', 
'org.gnome.Terminal.desktop', 'org.gnome.Nautilus.desktop', 
'virt-manager.desktop', 'pgadmin3.desktop', 'android-studio.desktop', 
'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2012-01-12 (2253 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318)
  ProcEnviron:
   LANG=en_US.UTF-8
   TERM=xterm-256color
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-01-11 (62 days ago)

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

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

[Desktop-packages] [Bug 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program

[Julian Alarcon]

Maybe this is related to this bug:
https://bugzilla.gnome.org/show_bug.cgi?id=776570

I found a workaround, here:
https://unix.stackexchange.com/questions/68/gnome-3-22-disable-
altshift-keyboard-layout-switching

Setting this works:
dconf write /org/gnome/desktop/input-sources/xkb-options "['grp_led:scroll']"

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

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

Title:
  Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes
  shortcuts with ctrl+shift, etc not working in any program

Status in GNOME Settings Daemon:
  Fix Released
Status in GNOME Shell:
  Won't Fix
Status in Unity:
  Confirmed
Status in X.Org X server:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Triaged
Status in gnome-settings-daemon package in ALT Linux:
  Unknown
Status in gnome-settings-daemon package in Debian:
  New
Status in gnome-settings-daemon package in Fedora:
  In Progress
Status in gnome-settings-daemon package in openSUSE:
  Confirmed

Bug description:
  Tried only with ctrl+shift, maybe behaves the same for other modifier
  key combinations when used as shortcut for switching layouts.

  - Set ctrl+shift as shortcut for switching keyboard layouts
  - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work 
(actually Terminal window loses focus when ctrl+shift is pressed, and layout is 
switched)

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.8.5-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Mon Oct 28 16:40:02 2013
  InstallationDate: Installed on 2013-10-23 (5 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1754864] Re: Flatpak runtime extensions are not installed when using GNOME Software on Ubuntu

[AsciiWolf]

So, I have just tested this on the latest Fedora Rawhide and experienced
the same issue as on Ubuntu 18.04 so it looks like that this is really
an upstream issue.

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

Title:
  Flatpak runtime extensions are not installed when using GNOME Software
  on Ubuntu

Status in gnome-software package in Ubuntu:
  New

Bug description:
  When installing a Flatpak application that depends on some runtimes
  and they depend on some additional runtime extensions using GNOME
  Software on Ubuntu 18.04, the runtime extensions are not installed.
  They are installed if you run "flatpak update" from Terminal after the
  installation. This issue should be already fixed in GNOME Software
  upstream so I believe that this is a downstream Ubuntu issue. Please,
  fix this.

  Steps to Reproduce:
  1. Use the latest, fully updated Ubuntu 18.04 image.
  2. Install "flatpak" and "gnome-software-plugin-flatpak" packages.
  3. Restart the system.
  4. Download and add the Flathub repo file: 
https://dl.flathub.org/repo/flathub.flatpakrepo
  5. Search and install the "GNOME Web" Flatpak package using GNOME Software.
  6. Run the installed "Web" application.

  Actual results:
  GNOME Web is started with the default (Adwaita) theme (and without the 
correct locale if you use non-English system).

  Expected results:
  GNOME Web is started with the correct (Ubuntu) theme (and with the correct 
locale if you use non-English system).

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

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

[Desktop-packages] [Bug 1755885] Re: Night Light won't turn on after start on display #1

[Joe_Bishop]

Reload and the workaround didn't work this time. And mirroring screen
worked.

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

Title:
  Night Light won't turn on after start on display #1

Status in xorg package in Ubuntu:
  New

Bug description:
  I have two displays and have Night Light mode enabled with Sunset to
  Sunrise setting (tried to change it into Manual, but this didn't make
  any difference).

  It was perfectly OK some time before, but now only display #2 is
  started with the Night Light mode switched on.

  I can work around it: go to the Display Settings, try to switch into
  non-native mode for Display #1 and it switched into it with Night
  Light enabled. Then choose not to keep settings and it returns into
  native resolution with Night Light on.

  Not all changes help to switch the mode on though. For instance,
  mirroring screen doesn't switch it on.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.42  Sat Mar  3 04:10:22 
PST 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Mar 14 21:31:45 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.15.0-10-generic, x86_64: installed
   nvidia, 390.42, 4.15.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e5]
  InstallationDate: Installed on 2018-02-05 (37 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=68661197-00b4-4652-9c8f-2ef606012d2d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/17/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-K/USB 3.1
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  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.:bvr0702:bd03/17/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-K/USB3.1:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1754564] Re: nautilus crash on double clicking on a file

[cubells]

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

I can confirm that bug is solved with mutter patch.

$ apt-cache policy mutter
mutter:
  Instal·lat: 3.28.0-1
  Candidat:   3.28.0-1
  Taula de versió:
 *** 3.28.0-1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

Thank you very much!!!

** This bug has been marked a duplicate of bug 1754169
   [Bionic] [wayland] many gnome applications exit or crash when a file is 
opened from within

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

Title:
  nautilus crash on double clicking on a file

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  On double click on a file like as test.txt, nautilus is closed
  suddenly and file is not open.

  
  $ G_DEBUG="all" NAUTILUS_DEBUG="All" nautilus
  Gdk-Message: 06:47:01.176: Error 71 (Error de protocol) dispatching to 
Wayland display.


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

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

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

[Desktop-packages] [Bug 299158] Re: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place

[Horst Schirmeier]

** Also affects: fonts-hack (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream
  Vera Mono: Combining diacritics out of place

Status in fonts-dejavu package in Ubuntu:
  Confirmed
Status in fonts-droid package in Ubuntu:
  Won't Fix
Status in fonts-hack package in Ubuntu:
  New
Status in fonts-liberation package in Ubuntu:
  Confirmed
Status in fonts-noto package in Ubuntu:
  New
Status in fonts-tlwg package in Ubuntu:
  New
Status in msttcorefonts package in Ubuntu:
  Won't Fix
Status in oxygen-fonts package in Ubuntu:
  New
Status in ttf-bitstream-vera package in Ubuntu:
  New

Bug description:
  In the Liberation Mono font, combining diacritical marks are drawn
  over the following character rather than the preceding.

  According to the Unicode standard since at least version 3.0, chapter
  3.6, verse D56, combining characters apply to the preceding base
  character. However, this font renders them on the following base
  character.

  Version info:
  Ubuntu Intrepid
  ttf-liberation 1.04~beta2-2

  To reproduce:
  1. Open gedit.
  2. Type the following three code points: U+0061 U+0301 U+0065 (Latin small 
letter a, Combining acute accent, Latin small letter e).
  3. Via Edit|Preferences|Font & Colors|Font, select the Liberation Mono font.

  Expected:
  * Two grapheme clusters are displayed: Latin small letter a with acute 
accent, Latin small letter e.

  Observed:
  * The grapheme clusters displayed are: Latin small letter a, Latin small 
letter e with acute accent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/299158/+subscriptions

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

[Desktop-packages] [Bug 1755887] [NEW] Duplicate Login keyring created on every login, results in multiple keyring unlock requests on each login

[Nathaniel W. Turner]

Public bug reported:

Steps:

1. Log in to gnome session.
2. Authentication required for login keyring dialog appears.
3. Enter correct password.
4. Go back to step 2 (repeats N times).
5. Do whatever (or nothing).
6. Log out.

Every time I log in (step 1), the value of N increases.
I also see in the "Passwords and Keys" application, that there are multiple 
"Passwords" keyrings with the exact same name, "Login" (see screenshot). The 
number of duplicate keyrings increases with each login.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-session 3.27.91-0ubuntu4
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: GNOME
Date: Wed Mar 14 14:48:40 2018
EcryptfsInUse: Yes
SourcePackage: gnome-session
UpgradeStatus: Upgraded to bionic on 2018-03-06 (7 days ago)

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


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

** Attachment added: "Screenshot from 2018-03-14 14-56-43.png"
   
https://bugs.launchpad.net/bugs/1755887/+attachment/5079684/+files/Screenshot%20from%202018-03-14%2014-56-43.png

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

Title:
  Duplicate Login keyring created on every login, results in multiple
  keyring unlock requests on each login

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Steps:

  1. Log in to gnome session.
  2. Authentication required for login keyring dialog appears.
  3. Enter correct password.
  4. Go back to step 2 (repeats N times).
  5. Do whatever (or nothing).
  6. Log out.

  Every time I log in (step 1), the value of N increases.
  I also see in the "Passwords and Keys" application, that there are multiple 
"Passwords" keyrings with the exact same name, "Login" (see screenshot). The 
number of duplicate keyrings increases with each login.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.27.91-0ubuntu4
  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: GNOME
  Date: Wed Mar 14 14:48:40 2018
  EcryptfsInUse: Yes
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (7 days ago)

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

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

[Desktop-packages] [Bug 1750289] Re: gnome-disks crashed with SIGSEGV in udisks_partition_table_get_type_()

[Xosé]

This happens for me also but with FAT, reformatting an existing
partition

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

Title:
  gnome-disks crashed with SIGSEGV in udisks_partition_table_get_type_()

Status in gnome-disk-utility package in Ubuntu:
  Confirmed

Bug description:
  When trying to format usb2 stick

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-disk-utility 3.27.90-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-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 18 23:40:52 2018
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2018-02-08 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208)
  JournalErrors:
   -- Logs begin at Thu 2018-02-08 20:55:29 CET, end at Sun 2018-02-18 23:41:14 
CET. --
   feb 18 10:57:37 hostname avahi-daemon[1187]: chroot.c: open() failed: No 
such file or directory
   feb 18 10:57:37 hostname NetworkManager[1202]: 
((src/devices/nm-device.c:1452)): assertion '' failed
   feb 18 10:58:02 hostname gdm-password][3049]: pam_env(gdm-password:session): 
Expandable variables must be wrapped in {} <@valencia:en> - ignoring
   feb 18 10:58:03 hostname pulseaudio[3253]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
  ProcCmdline: /usr/bin/gnome-disks --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7fedd31179f9 :   
mov(%rbx),%rdi
   PC (0x7fedd31179f9) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-disk-utility
  StacktraceTop:
   udisks_partition_table_get_type_ () at 
/usr/lib/x86_64-linux-gnu/libudisks2.so.0
   finish_cb ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-disks crashed with SIGSEGV in udisks_partition_table_get_type_()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev pulse pulse-access sambashare 
sudo video

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

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

[Desktop-packages] [Bug 1755885] [NEW] Night Light won't turn on after start on display #1

[Joe_Bishop]

Public bug reported:

I have two displays and have Night Light mode enabled with Sunset to
Sunrise setting (tried to change it into Manual, but this didn't make
any difference).

It was perfectly OK some time before, but now only display #2 is started
with the Night Light mode switched on.

I can work around it: go to the Display Settings, try to switch into
non-native mode for Display #1 and it switched into it with Night Light
enabled. Then choose not to keep settings and it returns into native
resolution with Night Light on.

Not all changes help to switch the mode on though. For instance,
mirroring screen doesn't switch it on.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.42  Sat Mar  3 04:10:22 
PST 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Wed Mar 14 21:31:45 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.15.0-10-generic, x86_64: installed
 nvidia, 390.42, 4.15.0-10-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e5]
InstallationDate: Installed on 2018-02-05 (37 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=68661197-00b4-4652-9c8f-2ef606012d2d ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/17/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0702
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-K/USB 3.1
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
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.:bvr0702:bd03/17/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-K/USB3.1:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.90-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic has-workaround regression reproducible ubuntu

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

Title:
  Night Light won't turn on after start on display #1

Status in xorg package in Ubuntu:
  New

Bug description:
  I have two displays and have Night Light mode enabled with Sunset to
  Sunrise setting (tried to change it into Manual, but this didn't make
  any difference).

  It was perfectly OK some time before, but now only display #2 is
  started with the Night Light mode switched on.

  I can work around it: go to the Display Settings, try to switch into
  non-native mode for Display #1 and it switched into it with Night
  Light enabled. Then choose not to keep settings and it returns into
  native resolution with Night Light on.

  Not all changes help to switch the mode on though. For instance,
  

[Desktop-packages] [Bug 1755880] Re: package doc-base 0.10.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 3

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package doc-base 0.10.7 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 3

Status in doc-base package in Ubuntu:
  New

Bug description:
  $ update-manager
  /usr/bin/update-manager:28: PyGIWarning: Gtk was imported without specifying 
a version first. Use gi.require_version('Gtk', '3.0') before import to ensure 
that the right version gets loaded.
from gi.repository import Gtk
  /usr/lib/python3/dist-packages/UpdateManager/UnitySupport.py:29: PyGIWarning: 
Dbusmenu was imported without specifying a version first. Use 
gi.require_version('Dbusmenu', '0.4') before import to ensure that the right 
version gets loaded.
from gi.repository import Dbusmenu, Unity
  /usr/lib/python3/dist-packages/UpdateManager/UnitySupport.py:29: PyGIWarning: 
Unity was imported without specifying a version first. Use 
gi.require_version('Unity', '7.0') before import to ensure that the right 
version gets loaded.
from gi.repository import Dbusmenu, Unity
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  Use of uninitialized value $template in exists at 
/usr/share/perl5/Debconf/Template.pm line 86, <> line 7.
  Use of uninitialized value $item in exists at 
/usr/share/perl5/Debconf/DbDriver/Cache.pm line 40, <> line 7.
  Use of uninitialized value $item in exists at 
/usr/share/perl5/Debconf/DbDriver/Cache.pm line 40, <> line 7.
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  Use of uninitialized value $template in exists at 
/usr/share/perl5/Debconf/Template.pm line 86, <> line 7.
  Use of uninitialized value $item in exists at 
/usr/share/perl5/Debconf/DbDriver/Cache.pm line 40, <> line 7.
  Use of uninitialized value $item in exists at 
/usr/share/perl5/Debconf/DbDriver/Cache.pm line 40, <> line 7.
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  Use of uninitialized value $template in exists at 
/usr/share/perl5/Debconf/Template.pm line 86, <> line 7.
  Use of uninitialized value $item in exists at 
/usr/share/perl5/Debconf/DbDriver/Cache.pm line 40, <> line 7.
  Use of uninitialized value $item in exists at 
/usr/share/perl5/Debconf/DbDriver/Cache.pm line 40, <> line 7.
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  Use of uninitialized value $template in exists at 
/usr/share/perl5/Debconf/Template.pm line 86, <> line 3.
  Use of uninitialized value $item in exists at 
/usr/share/perl5/Debconf/DbDriver/Cache.pm line 40, <> line 3.
  Use of uninitialized value $item in exists at 
/usr/share/perl5/Debconf/DbDriver/Cache.pm line 40, <> line 3.
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  billy@billy-P35-DS3P:~$ ^C
  billy@billy-P35-DS3P:~$ 
  billy@billy-P35-DS3P:~$

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: doc-base 0.10.7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Wed Mar 14 17:19:35 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 3
  InstallationDate: Installed on 2015-12-19 (815 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: doc-base
  Title: package doc-base 0.10.7 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 3
  UpgradeStatus: Upgraded to xenial on 2016-10-07 (522 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/doc-base/+bug/1755880/+subscriptions

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

[Desktop-packages] [Bug 1752091] Re: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed

[Willem Hobers]

Same problem here: Xubuntu 18.04, daily.

Mar 14 18:52:27 Xubuntu-18-04 gvfsd-metadata[1628]: g_udev_device_has_property: 
assertion 'G_UDEV_IS_DEVICE (device)' failed
Mar 14 18:52:27 Xubuntu-18-04 gvfsd-metadata[1628]: message repeated 7 times: [ 
g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed]

In this case it's on a working install of 18.04.

Is there more information I can provide to help?

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

Title:
  gvfsd-metadata[1703]: g_udev_device_has_property: assertion
  'G_UDEV_IS_DEVICE (device)' failed

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  I have no idea about the package to blame: gvfs/udev/kernel ?

  This is now logged:
  gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE 
(device)' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs 1.35.91-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Feb 27 14:21:10 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1755880] [NEW] package doc-base 0.10.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 3

[Billy91]

Public bug reported:

$ update-manager
/usr/bin/update-manager:28: PyGIWarning: Gtk was imported without specifying a 
version first. Use gi.require_version('Gtk', '3.0') before import to ensure 
that the right version gets loaded.
  from gi.repository import Gtk
/usr/lib/python3/dist-packages/UpdateManager/UnitySupport.py:29: PyGIWarning: 
Dbusmenu was imported without specifying a version first. Use 
gi.require_version('Dbusmenu', '0.4') before import to ensure that the right 
version gets loaded.
  from gi.repository import Dbusmenu, Unity
/usr/lib/python3/dist-packages/UpdateManager/UnitySupport.py:29: PyGIWarning: 
Unity was imported without specifying a version first. Use 
gi.require_version('Unity', '7.0') before import to ensure that the right 
version gets loaded.
  from gi.repository import Dbusmenu, Unity
debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
Use of uninitialized value $template in exists at 
/usr/share/perl5/Debconf/Template.pm line 86, <> line 7.
Use of uninitialized value $item in exists at 
/usr/share/perl5/Debconf/DbDriver/Cache.pm line 40, <> line 7.
Use of uninitialized value $item in exists at 
/usr/share/perl5/Debconf/DbDriver/Cache.pm line 40, <> line 7.
debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
Use of uninitialized value $template in exists at 
/usr/share/perl5/Debconf/Template.pm line 86, <> line 7.
Use of uninitialized value $item in exists at 
/usr/share/perl5/Debconf/DbDriver/Cache.pm line 40, <> line 7.
Use of uninitialized value $item in exists at 
/usr/share/perl5/Debconf/DbDriver/Cache.pm line 40, <> line 7.
debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
Use of uninitialized value $template in exists at 
/usr/share/perl5/Debconf/Template.pm line 86, <> line 7.
Use of uninitialized value $item in exists at 
/usr/share/perl5/Debconf/DbDriver/Cache.pm line 40, <> line 7.
Use of uninitialized value $item in exists at 
/usr/share/perl5/Debconf/DbDriver/Cache.pm line 40, <> line 7.
debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
Use of uninitialized value $template in exists at 
/usr/share/perl5/Debconf/Template.pm line 86, <> line 3.
Use of uninitialized value $item in exists at 
/usr/share/perl5/Debconf/DbDriver/Cache.pm line 40, <> line 3.
Use of uninitialized value $item in exists at 
/usr/share/perl5/Debconf/DbDriver/Cache.pm line 40, <> line 3.
debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
billy@billy-P35-DS3P:~$ ^C
billy@billy-P35-DS3P:~$ 
billy@billy-P35-DS3P:~$

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: doc-base 0.10.7
ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
Uname: Linux 4.4.0-112-generic i686
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
Date: Wed Mar 14 17:19:35 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 3
InstallationDate: Installed on 2015-12-19 (815 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.25
SourcePackage: doc-base
Title: package doc-base 0.10.7 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 3
UpgradeStatus: Upgraded to xenial on 2016-10-07 (522 days ago)

** Affects: doc-base (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package doc-base 0.10.7 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 3

Status in doc-base package in Ubuntu:
  New

Bug description:
  $ update-manager
  /usr/bin/update-manager:28: PyGIWarning: Gtk was imported without specifying 
a version first. Use gi.require_version('Gtk', '3.0') before import to ensure 
that the right version gets loaded.
from gi.repository import Gtk
  /usr/lib/python3/dist-packages/UpdateManager/UnitySupport.py:29: PyGIWarning: 
Dbusmenu was imported without specifying a version first. Use 
gi.require_version('Dbusmenu', '0.4') before import 

[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

[Kev Bowring]

Don't appear to be able to find the appropriate log in Ubuntu - however
grepping journalctl there for blue* gives me:

journalctl |grep blue*
Mar 14 17:51:27 ubuntu NetworkManager[985]:   [1521049887.5999] Loaded 
device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
Mar 14 17:51:33 ubuntu dbus-daemon[949]: [system] Activating via systemd: 
service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.36' 
(uid=999 pid=1532 comm="/usr/bin/pulseaudio --start --log-target=syslog " 
label="unconfined")
Mar 14 17:51:58 ubuntu dbus-daemon[949]: [system] Failed to activate service 
'org.bluez': timed out (service_start_timeout=25000ms)
Mar 14 17:51:58 ubuntu pulseaudio[1532]: [pulseaudio] bluez5-util.c: 
GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive 
a reply. Possible causes include: the remote application did not send a reply, 
the message bus security policy blocked the reply, the reply timeout expired, 
or the network connection was broken.

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

  Possibly 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 1721499] Re: Repeating prompt: "Automatically unlock this keyring whenever I'm logged in" when starting Chromium after boot

[Olivier Tilloy]

Excellent, closing the bug then. Thanks!

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

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

Title:
  Repeating prompt: "Automatically unlock this keyring whenever I'm
  logged in" when starting Chromium after boot

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  After each boot, I keep getting the prompt to unlock my keyring
  although I have selected to automatically unlock this keyring when I
  open Chromium or Chrome.

  I am attaching a screenshot.

  Tested on Ubuntu 17.10 GNOME.

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

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

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

[AsciiWolf]

I was able to reproduce this issue on the latest Fedora Rawhide under
Wayland so this is an upstream issue.

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

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

Status in Cheese:
  Unknown
Status in cheese package in Ubuntu:
  Triaged

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1750514] Re: cupsd (11) ippCopyAttribute → copy_attrs → copy_printer_attrs → get_printer_attrs → cupsdProcessIPPRequest

[Till Kamppeter]

Fix will conme with the upcoming CUPS 2.2.7 bug fix release which we
will upload to Bionic.

** Changed in: cups (Ubuntu Bionic)
   Status: Confirmed => Triaged

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

Title:
  cupsd (11) ippCopyAttribute → copy_attrs → copy_printer_attrs →
  get_printer_attrs → cupsdProcessIPPRequest

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Triaged
Status in cups source package in Bionic:
  Triaged

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

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

-- 
Mailing list: https://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 1721499] Re: Repeating prompt: "Automatically unlock this keyring whenever I'm logged in" when starting Chromium after boot

[Robert Orzanna]

Nope, we are all good.

Thanks for your follow-up! :-)

On Wed, Mar 14, 2018 at 5:46 PM, Olivier Tilloy <
olivier.til...@canonical.com> wrote:

> Sorry for the lack of feedback. Is this still happening with the latest
> chromium update?
>
> ** Changed in: chromium-browser (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1721499
>
> Title:
>   Repeating prompt: "Automatically unlock this keyring whenever I'm
>   logged in" when starting Chromium after boot
>
> Status in chromium-browser package in Ubuntu:
>   Incomplete
>
> Bug description:
>   After each boot, I keep getting the prompt to unlock my keyring
>   although I have selected to automatically unlock this keyring when I
>   open Chromium or Chrome.
>
>   I am attaching a screenshot.
>
>   Tested on Ubuntu 17.10 GNOME.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1721499/+
> subscriptions
>

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

Title:
  Repeating prompt: "Automatically unlock this keyring whenever I'm
  logged in" when starting Chromium after boot

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  After each boot, I keep getting the prompt to unlock my keyring
  although I have selected to automatically unlock this keyring when I
  open Chromium or Chrome.

  I am attaching a screenshot.

  Tested on Ubuntu 17.10 GNOME.

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

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

[Desktop-packages] [Bug 1755202] Re: Clone Mac Address Function On Default Wifi Setting Does Not Work (Ubuntu 17.10)

[John Doe]

** Description changed:

  I am Just Using Ubuntu 17.10.
  
  My Uname -a Result -> Linux user 4.13.0-36-generic #40-Ubuntu SMP Fri
  Feb 16 20:07:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux.
  
  Before Using Ubuntu 17.10, I was on fedora 26. I notice that there is
  also (MAC Address Randomization issue). I can fixed it and can use
  default mac address spoofing function from wifi setting -> Network
  Profile Setting (*) -> Identity -> Cloned Address -> And Add mac address
  to spoof for particular network.
  
  This Default mac address spoof function is very useful for me.
  
  Clearly, I doesn't mean (MAC Address Randomization issue)
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513
  
  Now I have a trouble with this feature (default mac spoffing). I can
  connect Wifi-s with great signal easily without using cloned address
  function.
  
  But when I added spoof address to setting, the wifi-s cannot be
  connected. I tried two wifi-s from near me which can connect on fedora
  26. One is open type network and the other is WPA Enterprise network.
  
  If this function doesn't work for anyone, this must be a bug.
  If it is a bug, hope it will fix it next release.
  
  Please, Don't Hesitate to ask more information. I really want to help to
  fix bug.
  
+ Hardware Info
+ Lenovo Z470 - Core i5 Second Gen
+ I used external wifi adapter - Card King http://a.co/gMrHzZQ  (RT3072 Chipset)
+ 
+ 
  #info
  lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  
  network-manager:
    Installed: 1.8.4-1ubuntu3
    Candidate: 1.8.4-1ubuntu3
    Version table:
   *** 1.8.4-1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status
  
- 
- journalctl log is pasted here.
- https://pastebin.com/Ki3R48pw
+ Update Journalctl with network-manager log
+ First I Connect my wifi named "blizzart" without using spoof address. 
Connected and works fine.
+ After 2 minutes later, I disconnected.
+ And then add spoof address and try to connect again.
+ But It is still trying to connect. You can see in the log.
+ https://pastebin.com/vmFMefih

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

Title:
  Clone Mac Address Function On Default Wifi Setting Does Not Work
  (Ubuntu 17.10)

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I am Just Using Ubuntu 17.10.

  My Uname -a Result -> Linux user 4.13.0-36-generic #40-Ubuntu SMP Fri
  Feb 16 20:07:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux.

  Before Using Ubuntu 17.10, I was on fedora 26. I notice that there is
  also (MAC Address Randomization issue). I can fixed it and can use
  default mac address spoofing function from wifi setting -> Network
  Profile Setting (*) -> Identity -> Cloned Address -> And Add mac
  address to spoof for particular network.

  This Default mac address spoof function is very useful for me.

  Clearly, I doesn't mean (MAC Address Randomization issue)
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513

  Now I have a trouble with this feature (default mac spoffing). I can
  connect Wifi-s with great signal easily without using cloned address
  function.

  But when I added spoof address to setting, the wifi-s cannot be
  connected. I tried two wifi-s from near me which can connect on fedora
  26. One is open type network and the other is WPA Enterprise network.

  If this function doesn't work for anyone, this must be a bug.
  If it is a bug, hope it will fix it next release.

  Please, Don't Hesitate to ask more information. I really want to help
  to fix bug.

  Hardware Info
  Lenovo Z470 - Core i5 Second Gen
  I used external wifi adapter - Card King http://a.co/gMrHzZQ  (RT3072 Chipset)

  
  #info
  lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  network-manager:
    Installed: 1.8.4-1ubuntu3
    Candidate: 1.8.4-1ubuntu3
    Version table:
   *** 1.8.4-1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  Update Journalctl with network-manager log
  First I Connect my wifi named "blizzart" without using spoof address. 
Connected and works fine.
  After 2 minutes later, I disconnected.
  And then add spoof address and try to connect again.
  But It is still trying to connect. You can see in the log.
  https://pastebin.com/vmFMefih

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

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

[Desktop-packages] [Bug 1721499] Re: Repeating prompt: "Automatically unlock this keyring whenever I'm logged in" when starting Chromium after boot

[Olivier Tilloy]

Sorry for the lack of feedback. Is this still happening with the latest
chromium update?

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

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

Title:
  Repeating prompt: "Automatically unlock this keyring whenever I'm
  logged in" when starting Chromium after boot

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  After each boot, I keep getting the prompt to unlock my keyring
  although I have selected to automatically unlock this keyring when I
  open Chromium or Chrome.

  I am attaching a screenshot.

  Tested on Ubuntu 17.10 GNOME.

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

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

[Desktop-packages] [Bug 1722101] Re: package cups-daemon 2.1.3-4ubuntu0.3 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su conf

[Launchpad Bug Tracker]

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

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

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

Title:
  package cups-daemon 2.1.3-4ubuntu0.3 failed to install/upgrade: El
  paquete está en un estado grave de inconsistencia - debe reinstalarlo
  antes de intentar su configuración.

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Since some weeks ago, I got problems with "cups-daemon" updating, my
  system say: the file is has not found and I don't know what to do.
  Please help me.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4ubuntu0.3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  CupsErrorLog:
   
  Date: Thu Oct  5 18:09:33 2017
  DpkgHistoryLog:
   Start-Date: 2017-10-05  18:09:02
   Commandline: apt-get -f install
   Requested-By: alex (1000)
   Upgrade: libcups2:i386 (2.1.3-4, 2.1.3-4ubuntu0.3), cups-bsd:i386 (2.1.3-4, 
2.1.3-4ubuntu0.3), cups:i386 (2.1.3-4, 2.1.3-4ubuntu0.3), cups-client:i386 
(2.1.3-4, 2.1.3-4ubuntu0.3)
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2016-11-01 (341 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Hewlett-Packard Compaq Presario C700 Notebook PC
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=ee27e26c-dc63-4754-a015-5bbfe542d39d ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=ee27e26c-dc63-4754-a015-5bbfe542d39d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4ubuntu0.3 failed to install/upgrade: El 
paquete está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/25/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.34
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 30D9
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 83.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.34:bd09/25/2008:svnHewlett-Packard:pnCompaqPresarioC700NotebookPC:pvrF.34:rvnHewlett-Packard:rn30D9:rvr83.21:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: Compaq Presario C700 Notebook PC
  dmi.product.version: F.34
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1715255] Re: libreoffice has uninstalled, will not launch or open documents.

[Olivier Tilloy]

Sorry for the lack of feedback. Is this issue still affecting you?

If so, try re-installing libreoffice through the software center, or via
this command line:

sudo apt install libreoffice

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

Title:
  libreoffice has uninstalled, will not launch or open documents.

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  I am using Ubuntu 17.04 and libreoffice has uninstalled making it so I
  cannot make written documents.  I am recently having trouble with
  loading new software in ubuntu 17.04 through the command line and
  through the ubuntu app store.

  ProblemType: Bug
  DistroRelease: Kali 2017.1
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Tue Sep  5 18:46:58 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-03-23 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  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/1715255/+subscriptions

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

[Desktop-packages] [Bug 1755866] [NEW] [snap] test bug report

[Olivier Tilloy]

Public bug reported:

nothing happened

DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
DESKTOP_SESSION=ubuntu
GDMSESSION=ubuntu
GNOME_DESKTOP_SESSION_ID=this-is-deprecated
GNOME_SHELL_SESSION_MODE=ubuntu
LANG=fr_FR.UTF-8
LC_ADDRESS=fr_FR.UTF-8
LC_IDENTIFICATION=fr_FR.UTF-8
LC_MEASUREMENT=fr_FR.UTF-8
LC_MONETARY=fr_FR.UTF-8
LC_NAME=fr_FR.UTF-8
LC_NUMERIC=fr_FR.UTF-8
LC_PAPER=fr_FR.UTF-8
LC_TELEPHONE=fr_FR.UTF-8
LC_TIME=fr_FR.UTF-8
PATH=/snap/libreoffice/x1/usr/sbin:/snap/libreoffice/x1/usr/bin:/snap/libreoffice/x1/sbin:/snap/libreoffice/x1/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
SESSION_MANAGER=local/bribon:@/tmp/.ICE-unix/7201,unix/bribon:/tmp/.ICE-unix/7201
SNAP=/snap/libreoffice/x1
SNAP_ARCH=amd64
SNAP_COMMON=/var/snap/libreoffice/common
SNAP_CONTEXT=X9N8v0hlqwgRNPPFJ5T4HgHj7M9V3kq6s4pp4Q9HPLxF
SNAP_COOKIE=X9N8v0hlqwgRNPPFJ5T4HgHj7M9V3kq6s4pp4Q9HPLxF
SNAP_DATA=/var/snap/libreoffice/x1
SNAP_LIBRARY_PATH=/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl32:/var/lib/snapd/void
SNAP_NAME=libreoffice
SNAP_REEXEC=
SNAP_REVISION=x1
SNAP_USER_COMMON=/home/osomon/snap/libreoffice/common
SNAP_USER_DATA=/home/osomon/snap/libreoffice/x1
SNAP_VERSION=6.0.2.1
TEMPDIR=/tmp
TMPDIR=/run/user/1000/snap.libreoffice
XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg
XDG_CURRENT_DESKTOP=ubuntu:GNOME
XDG_DATA_DIRS=/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop
XDG_MENU_PREFIX=gnome-
XDG_RUNTIME_DIR=/run/user/1000/snap.libreoffice
XDG_SEAT=seat0
XDG_SESSION_DESKTOP=ubuntu
XDG_SESSION_ID=2
XDG_SESSION_TYPE=x11
XDG_VTNR=2

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


** Tags: snap

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

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

Title:
  [snap] test bug report

Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  nothing happened

  DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
  DESKTOP_SESSION=ubuntu
  GDMSESSION=ubuntu
  GNOME_DESKTOP_SESSION_ID=this-is-deprecated
  GNOME_SHELL_SESSION_MODE=ubuntu
  LANG=fr_FR.UTF-8
  LC_ADDRESS=fr_FR.UTF-8
  LC_IDENTIFICATION=fr_FR.UTF-8
  LC_MEASUREMENT=fr_FR.UTF-8
  LC_MONETARY=fr_FR.UTF-8
  LC_NAME=fr_FR.UTF-8
  LC_NUMERIC=fr_FR.UTF-8
  LC_PAPER=fr_FR.UTF-8
  LC_TELEPHONE=fr_FR.UTF-8
  LC_TIME=fr_FR.UTF-8
  
PATH=/snap/libreoffice/x1/usr/sbin:/snap/libreoffice/x1/usr/bin:/snap/libreoffice/x1/sbin:/snap/libreoffice/x1/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  
SESSION_MANAGER=local/bribon:@/tmp/.ICE-unix/7201,unix/bribon:/tmp/.ICE-unix/7201
  SNAP=/snap/libreoffice/x1
  SNAP_ARCH=amd64
  SNAP_COMMON=/var/snap/libreoffice/common
  SNAP_CONTEXT=X9N8v0hlqwgRNPPFJ5T4HgHj7M9V3kq6s4pp4Q9HPLxF
  SNAP_COOKIE=X9N8v0hlqwgRNPPFJ5T4HgHj7M9V3kq6s4pp4Q9HPLxF
  SNAP_DATA=/var/snap/libreoffice/x1
  
SNAP_LIBRARY_PATH=/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl32:/var/lib/snapd/void
  SNAP_NAME=libreoffice
  SNAP_REEXEC=
  SNAP_REVISION=x1
  SNAP_USER_COMMON=/home/osomon/snap/libreoffice/common
  SNAP_USER_DATA=/home/osomon/snap/libreoffice/x1
  SNAP_VERSION=6.0.2.1
  TEMPDIR=/tmp
  TMPDIR=/run/user/1000/snap.libreoffice
  XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg
  XDG_CURRENT_DESKTOP=ubuntu:GNOME
  
XDG_DATA_DIRS=/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop
  XDG_MENU_PREFIX=gnome-
  XDG_RUNTIME_DIR=/run/user/1000/snap.libreoffice
  XDG_SEAT=seat0
  XDG_SESSION_DESKTOP=ubuntu
  XDG_SESSION_ID=2
  XDG_SESSION_TYPE=x11
  XDG_VTNR=2

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

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

[Desktop-packages] [Bug 1736452] Re: Password field changes height as you type in it

[AsciiWolf]

@vanvugt: It does not happen when using the default Adwaita theme.

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

Title:
  Password field changes height as you type in it

Status in fonts-ubuntu package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Login to Ubuntu 17.10, lock screen.
  On lock screen look at position of elements on screen
  Start typing password

  Expected behaviour

  Screen elements stay in the same place, with password appearing in the
  password field

  Actual behaviour

  Password field grows vertically, causing everything above it to shift
  up, and everything below to shift down.

  See screenshots of before/after, and comparison between the two
  images.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  5 14:47:08 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' b"['xkill', 'goxel']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'google-chrome.desktop', 
'chrome-hebeiaianhihkafkbopcfpkgloimgagb-Default.desktop', 'discord.desktop', 
'chrome-flidaonfhnkbealpaagddgffpppelhhb-Profile_1.desktop', 
'chrome-celnaknmndcdcjcagffhbhciignkeokb-Default.desktop', 
'chrome-dcdbodpaldbchkfinnjphocleggfceip-Default.desktop', 
'chrome-ddiddklncfgbfaaahngklemobghhjkim-Default.desktop', 
'chrome-fimghoffjcofmboofohmacdeabiimdeg-Profile_1.desktop', 
'irccloud-desktop_irccloud-desktop.desktop', 'telegramdesktop.desktop', 
'org.gnome.Terminal.desktop', 'code.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-08-02 (124 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Julian Andres Klode]

It generally always shows edge for me for uninstalled snaps, and the
right version for installed ones.

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

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

Status in gnome-software package in Ubuntu:
  Confirmed

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

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

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

  It should be the version from stable.

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

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

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

[Desktop-packages] [Bug 1738971] Re: libreoffice application error

[Olivier Tilloy]

Sorry for the lack of feedback. Are you still seeing this issue with the
latest libreoffice update (version 1:5.4.5-0ubuntu0.17.10.5) ?

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

Title:
  libreoffice application error

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  >libreoffice 
  /usr/lib/libreoffice/program/javaldx: error while loading shared libraries: 
  libreglo.so: cannot open shared object file: No such file or directory
  Warning: failed to read path from javaldx
  /usr/lib/libreoffice/program/soffice.bin: error while loading shared 
libraries: libreglo.so: cannot open shared object file: No such file or 
directory

  >locate libreglo.so
  /usr/lib/libreoffice/program/libreglo.so

  >cd /usr/lib/libreoffice/program/

  >libreoffice 
  Application Error

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice 1:5.4.2-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Dec 19 11:22:37 2017
  InstallationDate: Installed on 2009-11-30 (2940 days ago)
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-08-31 (109 days ago)

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

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

[Desktop-packages] [Bug 1755820] Re: Screen dims when disabled

[Gunnar Hjalmarsson]

Thanks for your report. It sounds like an issue with the behavior rather
than the documentation, though.

** Package changed: ubuntu-docs (Ubuntu) => gnome-control-center
(Ubuntu)

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

Title:
  Screen dims when disabled

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

Bug description:
  Screen dims even though it is disabled in power settings, though it is only 
when it is on battery power.
  I do not want it to dim the screen while i am reading something, therefore 
disabled it.

  Ubuntu release: 17.10

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

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

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

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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 with signal 5 in g_log_default_handler()

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  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: GNOME-Greeter:GNOME
  Date: Wed Mar 14 07:44:54 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-20 (144 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=el_GR.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/1755860/+subscriptions

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

[Desktop-packages] [Bug 1755859] [NEW] idk

[Stanislav]

Public bug reported:

idk

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-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 Mar 14 19:19:35 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-36-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:1840]
 Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (rev ff) (prog-if ff)
InstallationDate: Installed on 2018-03-09 (4 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
ProcEnviron:
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/07/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.27
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 1840
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 56.32
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.27:bd09/07/2016:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr07921020561610100:rvnHewlett-Packard:rn1840:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
dmi.product.name: HP Pavilion g6 Notebook PC
dmi.product.version: 07921020561610100
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91+git1803091830.5236de~oibaf~x
version.libgl1-mesa-dri: libgl1-mesa-dri 18.1~git1803121343.e76cf1~oibaf~x
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.1~git1803121343.e76cf1~oibaf~x
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

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


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

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

Title:
  idk

Status in xorg package in Ubuntu:
  New

Bug description:
  idk

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-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 Mar 14 19:19:35 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-36-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:1840]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2018-03-09 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.27
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1840
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Desktop-packages] [Bug 1755820] [NEW] Screen dims when disabled

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Screen dims even though it is disabled in power settings, though it is only 
when it is on battery power.
I do not want it to dim the screen while i am reading something, therefore 
disabled it.

Ubuntu release: 17.10

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

-- 
Screen dims when disabled
https://bugs.launchpad.net/bugs/1755820
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-control-center 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 1752145] Re: system freeze after full screen video viewing with Xorg on ultrawide monitor

[Krister]

I'm able to interact with the system normally using the ctrl-alt-F3
terminal, although none of the methods listed in
https://askubuntu.com/questions/455301/how-to-restart-gnome-shell-after-
it-became-unresponsive-freeze/496999 properly restart gnome-shell.  It
seems to be related to graphics.

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

Title:
  system freeze after full screen video viewing with Xorg on ultrawide
  monitor

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

Bug description:
  1. open a video (either youtube or totem)
  2. put it in full screen.
  3. wait

  Eventually (within minutes) the system will freeze in one of 2 ways.

  1. There will be only blackness with no response ( even
  unresponsive).

  2. There will be snow that shifts with keyboard and mouse interaction
  (see photo).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 27 19:08:13 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['workspace-g...@mathematical.coffee.gmail.com', 
'alt-tab-worksp...@kwalo.net', 'system-moni...@paradoxxx.zero.gmail.com', 
'user-th...@gnome-shell-extensions.gcampax.github.com', 
'ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']"
   b'org.gnome.shell' b'enable-hot-corners' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['googleinbox.desktop', 
'googlecalendar.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 11'"
  InstallationDate: Installed on 2018-01-05 (53 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2018-01-05 (53 days ago)

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

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

[Desktop-packages] [Bug 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode()
  from meta_renderer_native_finish_frame()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The crash was reported after booting and logging in to an X.Org
  session.

  $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  $ apt-cache policy gnome-shell
  gnome-shell:
Instalovaná verze: 3.27.92-0ubuntu1
Kandidát:  3.27.92-0ubuntu1
Tabulka verzí:
   *** 3.27.92-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Mar 11 11:08:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-12-19 (81 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=cs_CZ
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f3fee5d2f17 : 
mov0x20(%rax),%rcx
   PC (0x7f3fee5d2f17) ok
   source "0x20(%rax)" (0x0020) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_gpu_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   meta_renderer_native_finish_frame () at 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
  Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode()
  UpgradeStatus: Upgraded to bionic on 2018-03-05 (5 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1755848] [NEW] [snap] this is a test

[Olivier Tilloy]

Public bug reported:

this is
not a test

foo bar

DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
DESKTOP_SESSION=ubuntu
GDMSESSION=ubuntu
GNOME_DESKTOP_SESSION_ID=this-is-deprecated
GNOME_SHELL_SESSION_MODE=ubuntu
LANG=fr_FR.UTF-8
LC_ADDRESS=fr_FR.UTF-8
LC_IDENTIFICATION=fr_FR.UTF-8
LC_MEASUREMENT=fr_FR.UTF-8
LC_MONETARY=fr_FR.UTF-8
LC_NAME=fr_FR.UTF-8
LC_NUMERIC=fr_FR.UTF-8
LC_PAPER=fr_FR.UTF-8
LC_TELEPHONE=fr_FR.UTF-8
LC_TIME=fr_FR.UTF-8
PATH=/home/osomon/.cargo/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
SESSION_MANAGER=local/bribon:@/tmp/.ICE-unix/7201,unix/bribon:/tmp/.ICE-unix/7201
XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg
XDG_CURRENT_DESKTOP=ubuntu:GNOME
XDG_DATA_DIRS=/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop
XDG_MENU_PREFIX=gnome-
XDG_RUNTIME_DIR=/run/user/1000
XDG_SEAT=seat0
XDG_SESSION_DESKTOP=ubuntu
XDG_SESSION_ID=2
XDG_SESSION_TYPE=x11
XDG_VTNR=2

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


** Tags: snap

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

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

Title:
  [snap] this is a test

Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  this is
  not a test

  foo bar

  DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
  DESKTOP_SESSION=ubuntu
  GDMSESSION=ubuntu
  GNOME_DESKTOP_SESSION_ID=this-is-deprecated
  GNOME_SHELL_SESSION_MODE=ubuntu
  LANG=fr_FR.UTF-8
  LC_ADDRESS=fr_FR.UTF-8
  LC_IDENTIFICATION=fr_FR.UTF-8
  LC_MEASUREMENT=fr_FR.UTF-8
  LC_MONETARY=fr_FR.UTF-8
  LC_NAME=fr_FR.UTF-8
  LC_NUMERIC=fr_FR.UTF-8
  LC_PAPER=fr_FR.UTF-8
  LC_TELEPHONE=fr_FR.UTF-8
  LC_TIME=fr_FR.UTF-8
  
PATH=/home/osomon/.cargo/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
  
SESSION_MANAGER=local/bribon:@/tmp/.ICE-unix/7201,unix/bribon:/tmp/.ICE-unix/7201
  XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg
  XDG_CURRENT_DESKTOP=ubuntu:GNOME
  
XDG_DATA_DIRS=/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop
  XDG_MENU_PREFIX=gnome-
  XDG_RUNTIME_DIR=/run/user/1000
  XDG_SEAT=seat0
  XDG_SESSION_DESKTOP=ubuntu
  XDG_SESSION_ID=2
  XDG_SESSION_TYPE=x11
  XDG_VTNR=2

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

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

[Desktop-packages] [Bug 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed

[Stephen M]

Every time I turn around, I have a no failure related to gnome-keyring.
After having Chromium running for a few minutes it hangs again for a
minute or so with the same error message:

Gkr-Message: secret service operation failed: Did not receive a reply.
Possible causes include: the remote application did not send a reply,
the message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken.

Keyring may end up making Chromium unusable.

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

Title:
  gnome-keyring not unlocked on xenial when dbus-user-session is
  installed

Status in chromium-browser package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Triaged
Status in flatpak package in Ubuntu:
  Fix Released

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed

[Stephen M]

After killing and restarting the keyring which fixed Network Manager,
then Chromium developed a slow start problem caused by gnome-keyring.

smm@laptop ~
$ chromium-browser --enable-logging=stderr
ATTENTION: default value of option force_s3tc_enable overridden by environment.
Gkr-Message: secret service operation failed: Did not receive a reply. Possible 
causes include: the remote application did not send a reply, the message bus 
security policy blocked the reply, the reply timeout expired, or the network 
connection was broken.
[7981:7981:0314/102437.107901:WARNING:password_store_factory.cc(241)] Using 
basic (unencrypted) store for password storage. See 
https://chromium.googlesource.com/chromium/src/+/master/docs/linux_password_storage.md
 for more information about password storage options.

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

Title:
  gnome-keyring not unlocked on xenial when dbus-user-session is
  installed

Status in chromium-browser package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Triaged
Status in flatpak package in Ubuntu:
  Fix Released

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1754401] Re: mounting /proc with hidepid causes: Fatal server error: (EE) xf86OpenConsole: Cannot open virtual console 1 (Permission denied)

[Bug Watch Updater]

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

** Changed in: xorg-server
   Importance: Unknown => Medium

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

Title:
  mounting /proc with hidepid causes: Fatal server error: (EE)
  xf86OpenConsole: Cannot open virtual console 1 (Permission denied)

Status in X.Org X server:
  Confirmed
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  I don't what changed but today, my Artful laptop refuses to start a
  graphical session. The last update seems entirely unrelated:

  # /var/log/apt/history.log
  Start-Date: 2018-03-06  15:50:35
  Commandline: apt-get dist-upgrade
  Requested-By: simon (1000)
  Upgrade: libpq5:amd64 (9.6.7-0ubuntu0.17.10, 9.6.8-0ubuntu0.17.10)
  End-Date: 2018-03-06  15:50:39

  I tried linux-image-4.13.0-32-generic and linux-
  image-4.13.0-36-generic to no avail. I removed the "quiet splash" args
  from /etc/default/grub but it didn't help. Using "nomodeset" makes the
  graphical session almost work but the brightness of the screen is so
  low that I cannot use it and can't make it brighter either.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.26.1-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Thu Mar  8 11:08:35 2018
  InstallationDate: Installed on 2017-10-21 (137 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1754401] Re: mounting /proc with hidepid causes: Fatal server error: (EE) xf86OpenConsole: Cannot open virtual console 1 (Permission denied)

[Simon Déziel]

I added a link to the upstream bug, thanks for the guidance Daniel.

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

** Also affects: xorg-server via
   https://bugs.freedesktop.org/show_bug.cgi?id=105508
   Importance: Unknown
   Status: Unknown

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

Title:
  mounting /proc with hidepid causes: Fatal server error: (EE)
  xf86OpenConsole: Cannot open virtual console 1 (Permission denied)

Status in X.Org X server:
  Confirmed
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  I don't what changed but today, my Artful laptop refuses to start a
  graphical session. The last update seems entirely unrelated:

  # /var/log/apt/history.log
  Start-Date: 2018-03-06  15:50:35
  Commandline: apt-get dist-upgrade
  Requested-By: simon (1000)
  Upgrade: libpq5:amd64 (9.6.7-0ubuntu0.17.10, 9.6.8-0ubuntu0.17.10)
  End-Date: 2018-03-06  15:50:39

  I tried linux-image-4.13.0-32-generic and linux-
  image-4.13.0-36-generic to no avail. I removed the "quiet splash" args
  from /etc/default/grub but it didn't help. Using "nomodeset" makes the
  graphical session almost work but the brightness of the screen is so
  low that I cannot use it and can't make it brighter either.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.26.1-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Thu Mar  8 11:08:35 2018
  InstallationDate: Installed on 2017-10-21 (137 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1755830] Re: gnome-control-center crashed with SIGSEGV in gtk_tree_store_insert_with_values()

[Apport retracing service]

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

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 #1755098, 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/1755830/+attachment/5079421/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

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

Title:
  gnome-control-center crashed with SIGSEGV in
  gtk_tree_store_insert_with_values()

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

Bug description:
  Hello

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.27.92-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic i686
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 14 15:45:02 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-01-06 (66 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release i386 
(20171017.1)
  ProcCmdline: gnome-control-center network
  SegvAnalysis:
   Segfault happened at: 0xb768b182 : 
mov0xc(%edi),%ebp
   PC (0xb768b182) ok
   source "0xc(%edi)" (0x000c) not located in a known VMA region (needed 
readable region)!
   destination "%ebp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   gtk_tree_store_insert_with_values () from 
/usr/lib/i386-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgnome-bluetooth.so.13
   ?? () from /usr/lib/i386-linux-gnu/libgnome-bluetooth.so.13
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in 
gtk_tree_store_insert_with_values()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1617630] Re: Mousepad show the warning Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus -*

[Damian Yerrick]

I even encountered this bug when I tried to report it.

$ ubuntu-bug at-spi2-core

** (apport-gtk:): WARNING **: Couldn't connect to accessibility bus:
Failed to connect to socket /tmp/dbus-##: Connection refused

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

Title:
  Mousepad show the warning Couldn't connect to accessibility bus:
  Failed to connect to socket /tmp/dbus -*

Status in at-spi2-core package in Ubuntu:
  Confirmed

Bug description:
  When I start mousepad in a terminal, I have this warning :

  ** (mousepad:25021): WARNING **: Couldn't connect to accessibility
  bus: Failed to connect to socket /tmp/dbus-5pX3Lo3SAH: Connexion
  refusée

  When I start it with GKSU, the warning is not displayed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1617630/+subscriptions

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

[Desktop-packages] [Bug 1193236] Re: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*

[Damian Yerrick]

Comment #20 appears to recommend filing a deliberate duplicate:

> Please open your own report if you are affected.

One such duplicate is Bug #1617630.

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

Title:
   Couldn't connect to accessibility bus: Failed to connect to socket
  /tmp/dbus-*

Status in at-spi:
  Invalid
Status in at-spi2-core package in Ubuntu:
  Invalid
Status in gnome-session package in Ubuntu:
  Invalid
Status in at-spi2-core package in Debian:
  Invalid

Bug description:
  Since a few days, xsession-errors is fullfilled by that kind of
  errors:

  ** (nautilus:22621): WARNING **: Couldn't connect to accessibility
  bus: Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection
  refused

  ** (gedit:22640): WARNING **: Couldn't connect to accessibility bus:
  Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection refused

  Similar errors are reported all over the net, but Debian have tried to fix it 
already:
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702517

  But some other devs seems to blame an atk-bridge:
  https://groups.google.com/forum/#!topic/yad-common/nYP0RutlxNA

  And some others suggest a dbus/gdbus race; the good thing is that
  seems not disturbing that much the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libgdk-pixbuf2.0-0 2.28.1-1ubuntu2
  ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6
  Uname: Linux 3.9.0-6-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: i386
  Date: Fri Jun 21 08:35:40 2013
  MarkForUpload: True
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/at-spi/+bug/1193236/+subscriptions

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

[Desktop-packages] [Bug 1617630] Re: Mousepad show the warning Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus -*

[Launchpad Bug Tracker]

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

** Changed in: at-spi2-core (Ubuntu)
   Status: New => Confirmed

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

Title:
  Mousepad show the warning Couldn't connect to accessibility bus:
  Failed to connect to socket /tmp/dbus -*

Status in at-spi2-core package in Ubuntu:
  Confirmed

Bug description:
  When I start mousepad in a terminal, I have this warning :

  ** (mousepad:25021): WARNING **: Couldn't connect to accessibility
  bus: Failed to connect to socket /tmp/dbus-5pX3Lo3SAH: Connexion
  refusée

  When I start it with GKSU, the warning is not displayed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1617630/+subscriptions

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

[Desktop-packages] [Bug 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed

[Stephen M]

Running "chromium-browser --enable-logging=stderr" results in:

$ chromium-browser --enable-logging=stderr
ATTENTION: default value of option force_s3tc_enable overridden by environment.

I'm also running the gnome-keyring-daemon in the foreground and see this
message:

** (gnome-keyring-daemon:31165): WARNING **: asked to register item
/org/freedesktop/secrets/collection/login/12, but it's already
registered

** Message: The Secret Service was already initialized

Chromium starts up quickly, but network manager can't access the keyring
and hangs for a minute or two before it gives up when I try to connect
to a VPN.  Then it prompts me for the passwords, as it was unable to
retrieve them from gnome-keyring.

Killing and restarting the daemon fixes the problem.  Every night I
suspend my laptop when I go home and find the deamon is hung again the
next morning.

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

Title:
  gnome-keyring not unlocked on xenial when dbus-user-session is
  installed

Status in chromium-browser package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Triaged
Status in flatpak package in Ubuntu:
  Fix Released

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1752145] Re: system freeze after full screen video viewing with Xorg on ultrawide monitor

[Timo Aaltonen]

it's likely a kernel bug if the whole system freezes, so maybe try
newer/older kernels:

http://kernel.ubuntu.com/~kernel-ppa/mainline/

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

Title:
  system freeze after full screen video viewing with Xorg on ultrawide
  monitor

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

Bug description:
  1. open a video (either youtube or totem)
  2. put it in full screen.
  3. wait

  Eventually (within minutes) the system will freeze in one of 2 ways.

  1. There will be only blackness with no response ( even
  unresponsive).

  2. There will be snow that shifts with keyboard and mouse interaction
  (see photo).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 27 19:08:13 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['workspace-g...@mathematical.coffee.gmail.com', 
'alt-tab-worksp...@kwalo.net', 'system-moni...@paradoxxx.zero.gmail.com', 
'user-th...@gnome-shell-extensions.gcampax.github.com', 
'ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']"
   b'org.gnome.shell' b'enable-hot-corners' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['googleinbox.desktop', 
'googlecalendar.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 11'"
  InstallationDate: Installed on 2018-01-05 (53 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2018-01-05 (53 days ago)

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

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

[Desktop-packages] [Bug 1753146] Re: Characters Snap doesn't have color emoji

[Ken VanDine]

** Changed in: gnome-platform-snap
   Status: Fix Committed => Fix Released

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

Title:
  Characters Snap doesn't have color emoji

Status in gnome-platform-snap:
  Fix Released
Status in gnome-characters package in Ubuntu:
  Fix Released
Status in gnome-characters source package in Bionic:
  Fix Released

Bug description:
  The GNOME Characters snap doesn't have color emoji. This is a regression 
compared to the .deb.
  This week, the snap replaced the .deb in the default install.

  Maybe you need to build this snap using bionic's cairo?

  
  $ snap info gnome-characters
  name:  gnome-characters
  summary:   A character map application
  publisher: canonical
  license:   unknown
  description: |
Characters is a simple utility application to find and
insert unusual characters.
  snap-id: qJcS3UjpF9AMJKWAiKwA5EWbm0y6Uduw
  commands:
- gnome-characters
  tracking:stable
  installed:   3.26.2 (50) 12MB -
  refreshed:   2018-01-30 17:02:22 -0500 EST
  channels:   
stable:3.26.2(50) 12MB -
candidate: 3.26.2(50) 12MB -
beta:  ↑   
edge:  v3.26.2+git15.c29237e (58) 13MB -

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-platform-snap/+bug/1753146/+subscriptions

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

[Desktop-packages] [Bug 1753146] Re: Characters Snap doesn't have color emoji

[Ken VanDine]

** Changed in: gnome-platform-snap
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

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

Title:
  Characters Snap doesn't have color emoji

Status in gnome-platform-snap:
  Fix Committed
Status in gnome-characters package in Ubuntu:
  Fix Released
Status in gnome-characters source package in Bionic:
  Fix Released

Bug description:
  The GNOME Characters snap doesn't have color emoji. This is a regression 
compared to the .deb.
  This week, the snap replaced the .deb in the default install.

  Maybe you need to build this snap using bionic's cairo?

  
  $ snap info gnome-characters
  name:  gnome-characters
  summary:   A character map application
  publisher: canonical
  license:   unknown
  description: |
Characters is a simple utility application to find and
insert unusual characters.
  snap-id: qJcS3UjpF9AMJKWAiKwA5EWbm0y6Uduw
  commands:
- gnome-characters
  tracking:stable
  installed:   3.26.2 (50) 12MB -
  refreshed:   2018-01-30 17:02:22 -0500 EST
  channels:   
stable:3.26.2(50) 12MB -
candidate: 3.26.2(50) 12MB -
beta:  ↑   
edge:  v3.26.2+git15.c29237e (58) 13MB -

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-platform-snap/+bug/1753146/+subscriptions

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

[Desktop-packages] [Bug 1755675] Re: Ubuntu 17.10 OpenVPN DNS Leaks

[Brian Murray]

** Package changed: ubuntu => network-manager (Ubuntu)

** Tags added: artful

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

Title:
  Ubuntu 17.10 OpenVPN DNS Leaks

Status in network-manager package in Ubuntu:
  New

Bug description:
  On Ubuntu 17.10 x64 I have noticed that when using the NetworkManager
  and OpenVPN, that DNS leaks from the Router or ISP, instead of only
  being tunneled from the VPN...

  I have spent hours playing with this, it's beyond absurd, the amount
  of time and effort needed to try and resolve something that should be
  working out the box!

  This is not LFS, or Slackware, in fact Slackware is simpler and easier
  to make this work in less then 5 mins!

  Seriously this has been an ongoing issue for ages/years in Ubuntu, and
  the end-users typically for Ubuntu are inexperienced users, again, the
  only thing end-users should have to do is install the correct OpenVPN
  packages, configure OpenVPN in the NetworkManager and it works, but it
  doesn't!

  While Canonical works on trying to resolve this, can someone PLEASE
  tell me a simple way in which to prevent DNS leaks while using OpenVPN
  through the NetworkManager?

  THANKS

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

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

[Desktop-packages] [Bug 1755675] [NEW] Ubuntu 17.10 OpenVPN DNS Leaks

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

On Ubuntu 17.10 x64 I have noticed that when using the NetworkManager
and OpenVPN, that DNS leaks from the Router or ISP, instead of only
being tunneled from the VPN...

I have spent hours playing with this, it's beyond absurd, the amount of
time and effort needed to try and resolve something that should be
working out the box!

This is not LFS, or Slackware, in fact Slackware is simpler and easier
to make this work in less then 5 mins!

Seriously this has been an ongoing issue for ages/years in Ubuntu, and
the end-users typically for Ubuntu are inexperienced users, again, the
only thing end-users should have to do is install the correct OpenVPN
packages, configure OpenVPN in the NetworkManager and it works, but it
doesn't!

While Canonical works on trying to resolve this, can someone PLEASE tell
me a simple way in which to prevent DNS leaks while using OpenVPN
through the NetworkManager?

THANKS

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


** Tags: bot-comment
-- 
Ubuntu 17.10 OpenVPN DNS Leaks
https://bugs.launchpad.net/bugs/1755675
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to network-manager 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 1696250] Re: Please hide Start Center and Math

[Bug Watch Updater]

** Changed in: libreoffice (Debian)
   Status: New => Fix Committed

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

Title:
  Please hide Start Center and Math

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice package in Debian:
  Fix Committed

Bug description:
  From GNOME Shell, open the Applications Overview and click the Show
  Applications button to see the list of apps. Currently, LibreOffice
  takes up a whole row on my computer (6 icons) which seems excessive
  with GNOME Shell's current design.

  I suggest that we do like Fedora and hide the LibreOffice Start Center
  and LibreOffice Math.

  Instead of opening a Start Center, it makes more sense for a user to
  just open the app they want directly.

  I don't think users want to create a mathematical formula just to
  create one, but to insert into a document so it makes more sense to
  start Math from within the other app.

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

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

[Desktop-packages] [Bug 1755758] Re: gnome-control-center FTBFS with gnome-bluetooth 3.28

[Jeremy Bicha]

** Description changed:

  Ubuntu 18.04
  meson 0.45.0
  
  gnome-control-center 3.28.0 fails to build from source with gnome-
  bluetooth 3.28.0. The build succeeds with gnome-bluetooth 3.27.90.
- 
  
  Build log excerpt
  =
  Native dependency libnm found: YES 1.10.4
  Native dependency libnma found: YES 1.8.10
  Native dependency mm-glib found: YES 1.6.8
  Native dependency NetworkManager found: YES 1.10.4
  
  meson.build:212:2: ERROR: Could not generate cargs for gnome-
  bluetooth-1.0:
- 
- Other info
- ==
- I am settings block-proposed so that we can at least compile 
gnome-control-center if we disable -proposed.

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

Title:
  gnome-control-center FTBFS with gnome-bluetooth 3.28

Status in GNOME Bluetooth:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04
  meson 0.45.0

  gnome-control-center 3.28.0 fails to build from source with gnome-
  bluetooth 3.28.0. The build succeeds with gnome-bluetooth 3.27.90.

  Build log excerpt
  =
  Native dependency libnm found: YES 1.10.4
  Native dependency libnma found: YES 1.8.10
  Native dependency mm-glib found: YES 1.6.8
  Native dependency NetworkManager found: YES 1.10.4

  meson.build:212:2: ERROR: Could not generate cargs for gnome-
  bluetooth-1.0:

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

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

[Jeremy Bicha]

Stephen, there is a link in the sidebar of
https://launchpad.net/bugs/1751460 to mute bug mail for this bug. Or you
can edit your subscription there to stop receiving comments for this
bug.

-- 
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:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed
Status in deja-dup source package in Bionic:
  Confirmed
Status in webkit2gtk source package in Bionic:
  Confirmed

Bug description:
  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 1753146] Re: Characters Snap doesn't have color emoji

[Ken VanDine]

I've fixed this in gnome-3-26-1604 in the edge channel.  After a round
of testing of apps I'll resolve this.

** Also affects: gnome-platform-snap
   Importance: Undecided
   Status: New

** Changed in: gnome-platform-snap
   Status: New => Fix Committed

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

Title:
  Characters Snap doesn't have color emoji

Status in gnome-platform-snap:
  Fix Committed
Status in gnome-characters package in Ubuntu:
  Fix Released
Status in gnome-characters source package in Bionic:
  Fix Released

Bug description:
  The GNOME Characters snap doesn't have color emoji. This is a regression 
compared to the .deb.
  This week, the snap replaced the .deb in the default install.

  Maybe you need to build this snap using bionic's cairo?

  
  $ snap info gnome-characters
  name:  gnome-characters
  summary:   A character map application
  publisher: canonical
  license:   unknown
  description: |
Characters is a simple utility application to find and
insert unusual characters.
  snap-id: qJcS3UjpF9AMJKWAiKwA5EWbm0y6Uduw
  commands:
- gnome-characters
  tracking:stable
  installed:   3.26.2 (50) 12MB -
  refreshed:   2018-01-30 17:02:22 -0500 EST
  channels:   
stable:3.26.2(50) 12MB -
candidate: 3.26.2(50) 12MB -
beta:  ↑   
edge:  v3.26.2+git15.c29237e (58) 13MB -

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-platform-snap/+bug/1753146/+subscriptions

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

[Desktop-packages] [Bug 1753146] Re: Characters Snap doesn't have color emoji

[Jeremy Bicha]

This is fixed in the edge channel for the gnome-3-26-1604 snap and will
be promoted to stable soon.

It required backporting cairo, freetype, and fontconfig from bionic.

Thanks!

** Changed in: gnome-characters (Ubuntu Bionic)
   Status: Confirmed => Fix Released

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

Title:
  Characters Snap doesn't have color emoji

Status in gnome-platform-snap:
  Fix Committed
Status in gnome-characters package in Ubuntu:
  Fix Released
Status in gnome-characters source package in Bionic:
  Fix Released

Bug description:
  The GNOME Characters snap doesn't have color emoji. This is a regression 
compared to the .deb.
  This week, the snap replaced the .deb in the default install.

  Maybe you need to build this snap using bionic's cairo?

  
  $ snap info gnome-characters
  name:  gnome-characters
  summary:   A character map application
  publisher: canonical
  license:   unknown
  description: |
Characters is a simple utility application to find and
insert unusual characters.
  snap-id: qJcS3UjpF9AMJKWAiKwA5EWbm0y6Uduw
  commands:
- gnome-characters
  tracking:stable
  installed:   3.26.2 (50) 12MB -
  refreshed:   2018-01-30 17:02:22 -0500 EST
  channels:   
stable:3.26.2(50) 12MB -
candidate: 3.26.2(50) 12MB -
beta:  ↑   
edge:  v3.26.2+git15.c29237e (58) 13MB -

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-platform-snap/+bug/1753146/+subscriptions

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

[Desktop-packages] [Bug 299158] Re: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place

[Horst Schirmeier]

Correction: "Hack Bold" renders correctly, "Hack Regular" doesn't.

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

Title:
  DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream
  Vera Mono: Combining diacritics out of place

Status in fonts-dejavu package in Ubuntu:
  Confirmed
Status in fonts-droid package in Ubuntu:
  Won't Fix
Status in fonts-liberation package in Ubuntu:
  Confirmed
Status in fonts-noto package in Ubuntu:
  New
Status in fonts-tlwg package in Ubuntu:
  New
Status in msttcorefonts package in Ubuntu:
  Won't Fix
Status in oxygen-fonts package in Ubuntu:
  New
Status in ttf-bitstream-vera package in Ubuntu:
  New

Bug description:
  In the Liberation Mono font, combining diacritical marks are drawn
  over the following character rather than the preceding.

  According to the Unicode standard since at least version 3.0, chapter
  3.6, verse D56, combining characters apply to the preceding base
  character. However, this font renders them on the following base
  character.

  Version info:
  Ubuntu Intrepid
  ttf-liberation 1.04~beta2-2

  To reproduce:
  1. Open gedit.
  2. Type the following three code points: U+0061 U+0301 U+0065 (Latin small 
letter a, Combining acute accent, Latin small letter e).
  3. Via Edit|Preferences|Font & Colors|Font, select the Liberation Mono font.

  Expected:
  * Two grapheme clusters are displayed: Latin small letter a with acute 
accent, Latin small letter e.

  Observed:
  * The grapheme clusters displayed are: Latin small letter a, Latin small 
letter e with acute accent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/299158/+subscriptions

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