date:20180406

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

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 #1712961, 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/1761928/+attachment/5105041/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1761928

Title:
  gnome-control-center crashed with SIGSEGV in
  __GI_strtoul_l_internal()

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

Bug description:
  Trying to open the control settings via the wifi/battery/audio menu in
  the top right.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Apr  7 07:22:06 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-01-23 (73 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x7f7a8628ed60 <__GI___strtoul_l+32>:  movsbq 
(%rdi),%rax
   PC (0x7f7a8628ed60) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   __GI_strtoul_l_internal (loc=0x7f7a86633960 <_nl_C_locobj>, group=0, 
base=10, endptr=0x7fff33640dd8, nptr=0x0) at ../stdlib/strtol_l.c:292
   __GI___strtoul_l (nptr=0x0, endptr=0x7fff33640dd8, base=10, 
loc=0x7f7a86633960 <_nl_C_locobj>) at ../stdlib/strtol_l.c:547
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: gnome-control-center crashed with SIGSEGV in 
__GI_strtoul_l_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo

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

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

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

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

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

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

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

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

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

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

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

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Moved mouse and came out of blank screen mode and gnome-shell crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr  6 18:37:56 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-04-04 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

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

2018-04-06 Thread Tim Lunn

** Description changed:

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

** Patch added: "updated debdiff against debian experimental"
   
https://bugs.launchpad.net/ubuntu/+source/libzip/+bug/1674057/+attachment/5105030/+files/libzip_1.5.0-r3.debdiff

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

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

Title:
  [FFe] upgrade libzip to version 1.5.0

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

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

  Other

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

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

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

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

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

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

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

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

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

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I just switched on my computer and logged on. I crash report window
  opened so I am here.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr  6 20:43:17 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-02 (186 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: 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/1761924/+subscriptions

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

[Desktop-packages] [Bug 1756547] Re: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d

This bug was fixed in the package gnome-shell - 3.28.0-0ubuntu4

---
gnome-shell (3.28.0-0ubuntu4) bionic; urgency=medium

  * debian/rules:
- Drop javascript comments in gnome-shell.pot so the currently used
  version of gettext in LP gets more permissive wrt cases where
  the number of %d modifiers in a translation differs from what's
  in msgid (LP: #1756547).

 -- Gunnar Hjalmarsson   Fri, 06 Apr 2018 15:58:00
+0200

** Changed in: gnome-shell (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  LP refuses to import plural strings where e.g. msgstr[0] entries in PO
  file miss %d

Status in Launchpad itself:
  New
Status in Ubuntu Translations:
  In Progress
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  Some strings of GNOME Shell are untranslated in the Czech translation
  on Ubuntu 18.04 although they are translated upstream and when I try
  to manually translate them on launchpad, I get this error: "number of
  format specifications in 'msgid_plural' and 'msgstr[0]' does not
  match".

  The bad strings are:
  %d minute ago
  %d minutes ago

  %d hour ago
  %d hours ago

  %d week ago
  %d weeks ago

  %d month ago
  %d months ago

  %d year ago
  %d years ago

  They seem to be correct, but they are not accepted for some reason.

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

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

[Desktop-packages] [Bug 1761898] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 [modified: lib/udev/hwdb.d/20-sane.hwdb lib/udev/rules.d/60-libsane1.rules] failed to install/upgrade: trying to o

2018-04-06 Thread dino99

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

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

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

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

Status in sane-backends package in Ubuntu:
  New

Bug description:
  problem related to wine install.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1 [modified: 
lib/udev/hwdb.d/20-sane.hwdb lib/udev/rules.d/60-libsane1.rules]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sat Apr  7 01:14:28 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1 [modified: 
lib/udev/hwdb.d/20-sane.hwdb lib/udev/rules.d/60-libsane1.rules]
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-QUNzTZ/163-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2017-10-15 (173 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 [modified: 
lib/udev/hwdb.d/20-sane.hwdb lib/udev/rules.d/60-libsane1.rules] failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: Upgraded to artful on 2017-10-22 (166 days ago)

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

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

[Desktop-packages] [Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

2018-04-06 Thread James Donald

@herrtimson are you expecting revert-128661.patch to fix the strd r2,
r3, [r1] startup segfault on xenial/trusty, the Skia assembly illegal
instruction, or both?

The discussion in bug 1434526 indicates this patch is necessary on
Firefox 60 to resolve an armhf build failure on the latest trunk, but
that regression appears to be newer than both of the crash symptoms at
hand here.

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

Status in Mozilla Firefox:
  Expired
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Firefox always crashes when launched after the 55.0.1 update on an
  Orange Pi PC Plus (a single-board computer similar to a Raspberry Pi),
  even in safe mode.

  I did a fresh install of Armbian (a Ubuntu Xenial 16.04 re-spin for
  ARM single-board computer) on a similar board (Orange Pi Plus 2e),
  installed Firefox and experienced the same problem--it won't load
  without crashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 55.0.1+build2-0ubuntu0.16.04.2
  Uname: Linux 3.4.113-sun8i armv7l
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: armhf
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jim1138 F pulseaudio
   /dev/snd/controlC0:  jim1138 F pulseaudio
  BuildID: 20170814194718
  Card0.Amixer.info:
   Card hw:0 'audiocodec'/'audiocodec'
 Mixer name : ''
 Components : ''
 Controls  : 12
 Simple ctrls  : 12
  Card1.Amixer.info:
   Card hw:1 'sndhdmi'/'sndhdmi'
 Mixer name : ''
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'hdmi audio format Function',0
 Capabilities: enum
 Items: 'null' 'pcm' 'AC3' 'MPEG1' 'MP3' 'MPEG2' 'AAC' 'DTS' 'ATRAC' 
'ONE_BIT_AUDIO' 'DOLBY_DIGITAL_PLUS' 'DTS_HD' 'MAT' 'WMAPRO'
 Item0: 'pcm'
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Thu Aug 17 05:37:00 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.10.1 dev eth0 
   default via 192.168.10.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.10.0/24 dev eth0  proto kernel  scope link  src 192.168.10.107 
   192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.108  
metric 600
  Locales: extensions.sqlite corrupt or missing
  PciMultimedia:
   
  PciNetwork:
   
  Profiles: Profile0 (Default) - LastVersion=55.0.1/20170814194718
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1761913] Re: gnome-software crashed with SIGABRT in g_assertion_message_error → ensure_surface_for_gicon → gtk_icon_helper_load_surface → gtk_icon_helper_ensure_surface → gtk_i

2018-04-06 Thread Jean-Baptiste Lallement

** Summary changed:

- gnome-software crashed with SIGABRT in g_assertion_message()
+ gnome-software crashed with SIGABRT in g_assertion_message_error → 
ensure_surface_for_gicon → gtk_icon_helper_load_surface → 
gtk_icon_helper_ensure_surface → gtk_icon_helper_ensure_surface → 
_gtk_icon_helper_get_size → gtk_image_get_content_size

** Information type changed from Private to Public

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

Title:
  gnome-software crashed with SIGABRT in g_assertion_message_error →
  ensure_surface_for_gicon → gtk_icon_helper_load_surface →
  gtk_icon_helper_ensure_surface → gtk_icon_helper_ensure_surface →
  _gtk_icon_helper_get_size → gtk_image_get_content_size

Status in gnome-software package in Ubuntu:
  New

Bug description:
  testing ubuntu 18.04, this error popped up while NOT using gnome-
  software...

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  7 11:52:45 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-04-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu7
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-software
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_error () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: gnome-software crashed with SIGABRT in g_assertion_message()
  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/1761913/+subscriptions

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

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

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

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

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

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

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

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

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

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

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I plugged in my third display.

  ```
  #!/bin/bash
  echo "setting frame buffer" &&
  xrandr --fb 12800x2880 &&
  echo "setting laptop monitor" &&
  xrandr --output eDP-1-1 --mode 3840x2160 --rate 60 --pos 0x0 --primary &&
  echo "setting 27 inch monitor" &&
  xrandr --output DP-0.2 --mode 2560x1440 --scale-from 5120x2880 --panning 
5120x2880+3840+0 --pos 3840x0 &&
  echo "setting the samsung monitor" &&
  xrandr --output DP-0.1 --mode 1920x1080 --scale-from 3840x2160 --panning 
3840x2160+8960+0 --pos 8960x0 &&
  echo "setting global scaling to 2x" &&
  gsettings set org.gnome.desktop.interface scaling-factor 2
  cat <~/.config/monitors.xml
  

  
3840
0
2

  
DP-0.2
ACI
ASUS PB278
F1LMTF085150
  
  
2560
1440
59.950550079345703
  

  
  
0
0
2
yes

  
eDP-1-1
MEI
0x96a2
0x
  
  
3840
2160
60.000240325927734
  

  
  
6400
0
2

  
DP-0.1
SAM
SMBX2231
0x5a32504e
  
  
1920
1080
60
  

  

  
  EOF
  ```

  is my display configuration. Three screens. Third is problematic in
  Linux.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr  6 18:41:52 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-28 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325)
  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/1761910/+subscriptions

-- 
Mailing list:

[Desktop-packages] [Bug 1761911] [NEW] Have to manually "sudo ifconfig eth0 up" and "sudo dhclient eth0" after every reboot

2018-04-06 Thread Walter Dietrich

Public bug reported:

I did an upgrade with "sudo apt-get dist-upgrade", and it removed 
network-manager and network-manager-gnome. I could not connect to my LAN afer 
that. I was able to find instructions for downgrading the libnl packages at
https://askubuntu.com/questions/727127/last-upgrade-crashes-network-manager-no-internet-connection-no-applet

I am able to get online again by running the following commands
sudo ifconfig eth0 up
sudo dhclient eth0
(Fortunately, I have a Ethernet I can plug in to.) I have to do this every time 
I reboot. This is inconvenient as a usually use Desktop Sharing with another 
computer as the client. I use an SSH tunnel for security. This means that every 
time I reboot, I have to physically access the computer's console to enter the 
ifconfig and dhclient commands to get the computer back on the network. I tried 
to reinstall network-manager and network-manager-gnome, but the command results 
said there were dependencies that prevented the installation. The fixes in the 
web page referenced above do not help, so I'm reporting this as a bug.

Thanks for your assistance.

$ sudo lsb_release -rd
[sudo] password for wally: 
Description:Ubuntu 14.04.1 LTS
Release:14.04
$


$ apt-cache policy network-manager
network-manager:
  Installed: (none)
  Candidate: 0.9.8.8-0ubuntu7.1
  Version table:
 0.9.8.8-0ubuntu7.1 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
100 /var/lib/dpkg/status
 0.9.8.8-0ubuntu7 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
$

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: network-manager (not installed)
ProcVersionSignature: Ubuntu 3.13.0-144.193-generic 3.13.11-ckt39
Uname: Linux 3.13.0-144-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Apr  6 21:21:27 2018
InstallationDate: Installed on 2014-10-22 (1262 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

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

Title:
  Have to manually "sudo ifconfig eth0 up" and "sudo dhclient eth0"
  after every reboot

Status in network-manager package in Ubuntu:
  New

Bug description:
  I did an upgrade with "sudo apt-get dist-upgrade", and it removed 
network-manager and network-manager-gnome. I could not connect to my LAN afer 
that. I was able to find instructions for downgrading the libnl packages at
  
https://askubuntu.com/questions/727127/last-upgrade-crashes-network-manager-no-internet-connection-no-applet

  I am able to get online again by running the following commands
  sudo ifconfig eth0 up
  sudo dhclient eth0
  (Fortunately, I have a Ethernet I can plug in to.) I have to do this every 
time I reboot. This is inconvenient as a usually use Desktop Sharing with 
another computer as the client. I use an SSH tunnel for security. This means 
that every time I reboot, I have to physically access the computer's console to 
enter the ifconfig and dhclient commands to get the computer back on the 
network. I tried to reinstall network-manager and network-manager-gnome, but 
the command results said there were dependencies that prevented the 
installation. The fixes in the web page referenced above do not help, so I'm 
reporting this as a bug.

  Thanks for your assistance.

  $ sudo lsb_release -rd
  [sudo] password for wally: 
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  $

  
  $ apt-cache policy network-manager
  network-manager:
Installed: (none)
Candidate: 0.9.8.8-0ubuntu7.1
Version table:
   0.9.8.8-0ubuntu7.1 0
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.9.8.8-0ubuntu7 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  $

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-144.193-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-144-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  6 21:21:27 2018
  InstallationDate: Installed on 2014-10-22 (1262 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2018-04-06 Thread WalterNicholls

Confirmed, just setting up new Xubuntu virtual machine 17.10 - after all
updates.
Architecture: amd64
network-manager-openvpn and network-manager-openvpn-gnome both Version:
1.2.10-0ubuntu2

I originally started with a config downloaded from pfSense. As usual, openvpn
from command line is flawless.
After reboot was able to connect with NM getting

Seriously, while nearly 2 years old is nothing for an open-source bug,
this is one of a whole set of bugs in the Gnome openVPN plugin. I've
never had these troubles with KDE. The plugin could do with some love.

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

Title:
NetworkManager ignores pushed openvpn routes

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

Bug description:
Relevant information that may or may not have been included by ubuntu-
bug:

Ubuntu release 16.04
Package network-manager 1.2.0-0ubuntu0.16.04.2
Package network-manager-openvpn 1.1.93-1ubuntu1

NetworkManager ignores pushed openvpn routes when "Use this connection
only for resources on its network" is checked. This is a behavior
change since 14.04.

To repeat:

1) Use an OpenVpn server that pushes routes. I suggest using a server
that pushes several routes since this makes their absence obvious.
Set up a NetworkManager VPN of type OpenVpn to this server. Select
"Use this connection only for resources on its network" in the
"Routes" section of the IPV4 options.

2) Set up a raw OpenVpn connection to the same server.

3) Connect to the server using the raw OpenVpn connection. The pushed
routes are all there.

4) Connect to the server using NetworkManager. The only route added
is a n interface level route to the tunnel device network.

Using the same setup on 14.04, all pushed routes are added.

The missing routes are also "Resources on the VPN network", and should be
added in the absence of further direction. Ignoring pushed routes should be
controlled by the "Ignore automatically obtained routes" checkbox.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager-openvpn 1.1.93-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Fri Jul 15 23:12:55 2016
InstallationDate: Installed on 2016-05-04 (72 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: network-manager-openvpn
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1756547] Re: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d

2018-04-06 Thread Gunnar Hjalmarsson

@AsciiWolf: Do you have an idea which other packages besides gnome-shell
suffer from this kind of translation import problem?

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

Title:
  LP refuses to import plural strings where e.g. msgstr[0] entries in PO
  file miss %d

Status in Launchpad itself:
  New
Status in Ubuntu Translations:
  In Progress
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  Some strings of GNOME Shell are untranslated in the Czech translation
  on Ubuntu 18.04 although they are translated upstream and when I try
  to manually translate them on launchpad, I get this error: "number of
  format specifications in 'msgid_plural' and 'msgstr[0]' does not
  match".

  The bad strings are:
  %d minute ago
  %d minutes ago

  %d hour ago
  %d hours ago

  %d week ago
  %d weeks ago

  %d month ago
  %d months ago

  %d year ago
  %d years ago

  They seem to be correct, but they are not accepted for some reason.

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

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

[Desktop-packages] [Bug 1761897] Re: unity-settings-daemon crashed with signal 5 in g_main_context_dispatch()

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

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 #1727648, 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/1761897/+attachment/5104828/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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 unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1761897

Title:
  unity-settings-daemon crashed with signal 5 in
  g_main_context_dispatch()

Status in unity-settings-daemon package in Ubuntu:
  New

Bug description:
  18.04 w/DisplayLink D3100

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: unity-settings-daemon 15.04.1+18.04.20180216-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat Apr  7 02:13:18 2018
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2018-03-11 (26 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  Signal: 5
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/unity-settings-daemon-1.0/libxrandr.so
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: unity-settings-daemon crashed with signal 5 in 
g_main_context_dispatch()
  UpgradeStatus: Upgraded to bionic on 2018-03-11 (26 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1756547] Re: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d

2018-04-06 Thread Gunnar Hjalmarsson

The build of gnome-shell 3.28.0-0ubuntu4 was not sufficient to fix this.
The POT file without javascript comments was imported, but LP still
complained about the PO files for the affected languages.

The upstream PO files have those javascript comments too. As a test I
took the upstream Czech file, removed the javascript comments, and
uploaded manually. Imported without errors.

Next thought: Was the first failure about timing, i.e. did LP use the
info in the old template to validate the PO files? To test that I took
the upstream Serbian file and uploaded it manually without removing the
javascript comments. Imported without errors.

Conclusion: A no-change rebuild ought to be sufficient to fix it in
gnome-shell for the other affected languages.

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

Title:
  LP refuses to import plural strings where e.g. msgstr[0] entries in PO
  file miss %d

Status in Launchpad itself:
  New
Status in Ubuntu Translations:
  In Progress
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  Some strings of GNOME Shell are untranslated in the Czech translation
  on Ubuntu 18.04 although they are translated upstream and when I try
  to manually translate them on launchpad, I get this error: "number of
  format specifications in 'msgid_plural' and 'msgstr[0]' does not
  match".

  The bad strings are:
  %d minute ago
  %d minutes ago

  %d hour ago
  %d hours ago

  %d week ago
  %d weeks ago

  %d month ago
  %d months ago

  %d year ago
  %d years ago

  They seem to be correct, but they are not accepted for some reason.

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

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

[Desktop-packages] [Bug 1761898] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 [modified: lib/udev/hwdb.d/20-sane.hwdb lib/udev/rules.d/60-libsane1.rules] failed to install/upgrade: trying to o

** Tags removed: need-duplicate-check

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

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

Status in sane-backends package in Ubuntu:
  New

Bug description:
  problem related to wine install.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1 [modified: 
lib/udev/hwdb.d/20-sane.hwdb lib/udev/rules.d/60-libsane1.rules]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sat Apr  7 01:14:28 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1 [modified: 
lib/udev/hwdb.d/20-sane.hwdb lib/udev/rules.d/60-libsane1.rules]
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-QUNzTZ/163-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2017-10-15 (173 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 [modified: 
lib/udev/hwdb.d/20-sane.hwdb lib/udev/rules.d/60-libsane1.rules] failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: Upgraded to artful on 2017-10-22 (166 days ago)

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

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

[Desktop-packages] [Bug 1761898] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 [modified: lib/udev/hwdb.d/20-sane.hwdb lib/udev/rules.d/60-libsane1.rules] failed to install/upgrade: trying to

2018-04-06 Thread viacheslav

Public bug reported:

problem related to wine install.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1 [modified: 
lib/udev/hwdb.d/20-sane.hwdb lib/udev/rules.d/60-libsane1.rules]
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Sat Apr  7 01:14:28 2018
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental2ubuntu2.1 [modified: 
lib/udev/hwdb.d/20-sane.hwdb lib/udev/rules.d/60-libsane1.rules]
 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-QUNzTZ/163-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
  trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
InstallationDate: Installed on 2017-10-15 (173 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 [modified: 
lib/udev/hwdb.d/20-sane.hwdb lib/udev/rules.d/60-libsane1.rules] failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: Upgraded to artful on 2017-10-22 (166 days ago)

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


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

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

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

Status in sane-backends package in Ubuntu:
  New

Bug description:
  problem related to wine install.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1 [modified: 
lib/udev/hwdb.d/20-sane.hwdb lib/udev/rules.d/60-libsane1.rules]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sat Apr  7 01:14:28 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1 [modified: 
lib/udev/hwdb.d/20-sane.hwdb lib/udev/rules.d/60-libsane1.rules]
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-QUNzTZ/163-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2017-10-15 (173 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 [modified: 
lib/udev/hwdb.d/20-sane.hwdb lib/udev/rules.d/60-libsane1.rules] failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: Upgraded to artful on 2017-10-22 (166 days ago)

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

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

[Desktop-packages] [Bug 202300] Re: default colors provide bad contrast to default background

2018-04-06 Thread Artem

Can i ask Ubuntu team to add good Light terminal theme into new 18.04
LTS release? I mean professionally made theme. Because this Tango light
or Solarized light looks not really good. Some colors don't go together
and barely readable on light background.

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

Title:
  default colors provide bad contrast to default background

Status in GNOME Terminal:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Invalid

Bug description:
  The default colors of gnome-terminal are not optimally readable on a
  white background. They should be more saturated.

  The original submitter especially did not like the "light blue" color,
  which should be darker in his opinion.

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

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

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

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

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

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

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

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

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

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

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

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This error occurred for no apparent reason.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr  6 18:59:07 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-11-12 (145 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171109)
  ProcCmdline: /usr/bin/gnome-shell
  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/1761882/+subscriptions

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

[Desktop-packages] [Bug 1761585] Re: ibus_bus_init does an unconditional call to chmod on $HOME/.config/ibus/bus

2018-04-06 Thread Bug Watch Updater

** Changed in: ibus
   Status: Unknown => Fix Released

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

Title:
  ibus_bus_init does an unconditional call to chmod on
  $HOME/.config/ibus/bus

Status in ibus:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released

Bug description:
  This was spotted by jdstrand when running the chromium snap, which
  recently enabled ibus support (https://forum.snapcraft.io/t/cant-use-
  input-method-in-snap-apps/4712/12):

  audit[16919]: AVC apparmor="DENIED" operation="chmod"
  profile="snap.chromium.chromium" name="/home/osomon/.config/ibus/bus/"
  pid=16919 comm="chromium-browse" requested_mask="w" denied_mask="w"
  fsuid=1000 ouid=1000

  The code that calls chmod is in ibus_bus_init:

static void
ibus_bus_init (IBusBus *bus)
{
  gchar *path;
  […]
  path = g_path_get_dirname (ibus_get_socket_path ());
  g_mkdir_with_parents (path, 0700);
  g_chmod (path, 0700);
  […]
}

  This is rather harmless, but it could be avoided by checking first the
  file mode bits on that directory, and do the g_chmod call only if ≠
  0700.

  
  [Impact]

  Snaps that build on a xenial stack against libibus will trigger that apparmor 
denial, and even if actually harmless this will no doubt be reported as a 
problem by users who inspect the denials generated by their snaps.
  The patch (that is already upstream: 
https://github.com/ibus/ibus/commit/28d0c1d4bc47beb38995d84cc4bb1d539c08a070) 
fixes that by calling chmod conditionally, only if the file mode bits on the 
ibus socket path are ≠ 0700.

  
  [Test Case]

  Install the chromium snap from the stable channel (version
  65.0.3325.181, revision 274 as of this writing), and monitor the
  system journal for apparmor denials while launching it:

  journalctl -f | grep chmod

  Observe a denial similar to that one:

  audit[16919]: AVC apparmor="DENIED" operation="chmod"
  profile="snap.chromium.chromium" name="/home/osomon/.config/ibus/bus/"
  pid=16919 comm="chromium-browse" requested_mask="w" denied_mask="w"
  fsuid=1000 ouid=1000

  Now rebuild the chromium snap with the patched libibus (this can be
  done by downloading the .snap file, unpacking it with  unsquashfs,
  replacing the libibus files by unpacking the updated deb, then
  repacking the snap with `snapcraft pack`), install it and launch it
  while monitoring the system journal.

  Observe the denial on chmod is gone.

  
  [Regression Potential]

  This is a low-risk, self-contained change. It doesn't change the logic of 
ibus_bus_init.
  ibus input still working in apps (both debs and snaps) should be enough to 
prove that there are no regressions.


  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 5 21:55:30 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (642 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to bionic on 2018-01-29 (66 days ago)

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

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

[Desktop-packages] [Bug 1752197] Re: Videos won't resume after being paused

** Changed in: webkit2gtk (Ubuntu)
 Assignee: Leianna Heremaia (jahmaia) => (unassigned)

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

Title:
  Videos won't resume after being paused

Status in WebKit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Invalid
Status in webkit2gtk package in Ubuntu:
  Fix Released
Status in webkit2gtk source package in Artful:
  Confirmed

Bug description:
  On my Ubuntu 17.10 system, Epiphany Browser 3.26.1 has trouble playing
  YouTube videos. I can play a video from the start point without
  trouble, but if I pause the video the screen will freeze and stay that
  way after restarting the video, if I leave the page and go back later
  it will show a black screen. In both cases the soundtrack continues
  without problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: epiphany-browser 3.26.1-1ubuntu1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 27 17:27:50 2018
  InstallationDate: Installed on 2017-12-06 (83 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: epiphany-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/webkit-open-source/+bug/1752197/+subscriptions

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

[Desktop-packages] [Bug 1754872] Re: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Sett

2018-04-06 Thread Norbert

Still happens after installation of `xubuntu-desktop` from beta2
netboot.iso.

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

Title:
  gnome-control-center is unusable on xubuntu-desktop, but called from
  Gear (About this Computer, System Settings) icon, Text Entry Settings,
  clock (Time & Date Settings)

Status in gnome-control-center package in Ubuntu:
  New
Status in indicator-datetime package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  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 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

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

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

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

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

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

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

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

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

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  hz

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Wed Apr  4 18:45:46 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-02-06 (59 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180206)
  ProcCmdline: /usr/bin/gnome-shell
  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/1761864/+subscriptions

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

[Desktop-packages] [Bug 1761858] [NEW] libx11-6-dbgsym should be insection "debug" insead of section "libs"

2018-04-06 Thread Laurent Bonnaud

Public bug reported:

Hi,

the problem is that deborphan lists this package as removable, whereas I
want to keep it:

$ deborphan
[...]
libx11-6-dbgsym:amd64

It comes from the fact that libx11-6-dbgsym is in section "libs":

$ dpkg -s libx11-6-dbgsym
[...]
Section: libs

whereas it should be in section "devel".  All other *-dbgsym packages on
my system belong to this section.  For instance:

$ dpkg -s libqt5gui5-dbgsym
[...]
Section: debug

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libx11-6-dbgsym 2:1.6.4-3
Uname: Linux 4.15.15-041515-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: KDE
Date: Fri Apr  6 22:00:55 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0494]
MachineType: Dell Inc. Latitude E6520
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.15-041515-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro vsyscall=none 
security=apparmor intel_iommu=on enable_mtrr_cleanup mtrr_spare_reg_nr=1 
mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash vt.handoff=1
SourcePackage: libx11
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/14/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A19
dmi.board.name: 0NVF5K
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6520
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  libx11-6-dbgsym should be insection "debug" insead of section "libs"

Status in libx11 package in Ubuntu:
  New

Bug description:
  Hi,

  the problem is that deborphan lists this package as removable, whereas
  I want to keep it:

  $ deborphan
  [...]
  libx11-6-dbgsym:amd64

  It comes from the fact that libx11-6-dbgsym is in section "libs":

  $ dpkg -s libx11-6-dbgsym
  [...]
  Section: libs

  whereas it should be in section "devel".  All other *-dbgsym packages
  on my system belong to this section.  For instance:

  $ dpkg -s libqt5gui5-dbgsym
  [...]
  Section: debug

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libx11-6-dbgsym 2:1.6.4-3
  Uname: Linux 4.15.15-041515-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Fri Apr  6 22:00:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0494]
  MachineType: Dell Inc. Latitude E6520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.15-041515-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro vsyscall=none 
security=apparmor intel_iommu=on enable_mtrr_cleanup mtrr_spare_reg_nr=1 
mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash vt.handoff=1
  SourcePackage: libx11
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0NVF5K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

[Desktop-packages] [Bug 1752197] Re: Videos won't resume after being paused

2018-04-06 Thread Leianna Heremaia

I play a movie on youtube from the start without trouble, but it still
in slowness and not normal

** Changed in: webkit2gtk (Ubuntu)
 Assignee: (unassigned) => Leianna Heremaia (jahmaia)

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

Title:
  Videos won't resume after being paused

Status in WebKit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Invalid
Status in webkit2gtk package in Ubuntu:
  Fix Released
Status in webkit2gtk source package in Artful:
  Confirmed

Bug description:
  On my Ubuntu 17.10 system, Epiphany Browser 3.26.1 has trouble playing
  YouTube videos. I can play a video from the start point without
  trouble, but if I pause the video the screen will freeze and stay that
  way after restarting the video, if I leave the page and go back later
  it will show a black screen. In both cases the soundtrack continues
  without problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: epiphany-browser 3.26.1-1ubuntu1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 27 17:27:50 2018
  InstallationDate: Installed on 2017-12-06 (83 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: epiphany-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/webkit-open-source/+bug/1752197/+subscriptions

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

[Desktop-packages] [Bug 1761261] Re: nouveau/nvidia drivers do not work with display in Bionic on Asus GL703VD Laptop

2018-04-06 Thread Davide Villa

Same problem on my ASUS GL703VD.
I tried the 18.04 beta today starting a live session with the suggested boot 
option (modprobe.blacklist=nouveau).
I can work using an external monitor connected to the HDMI interface. The 
laptop display become black during the boot just after few seconds but I can 
see the boot progress on the external monitor.

The system works fine with Ubuntu 17.10 with the old kernel
4.13.0-38-generic.

I tried the new kernel 4.16 with ubuntu 17.10 from the mainline
repository but the problem is the same: black laptop screen during boot,
external HDMI monitor working.

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

Title:
  nouveau/nvidia drivers do not work with display in Bionic on Asus
  GL703VD Laptop

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Tried to install Bionic Desktop on my Asus GL703VD ROG Laptop with
  NVIDIA GTX 1050M Video Card (with i915 Intel graphics card when not
  using 3D) and the installer does not display. I have tried
  nouveau.modeset=0 and nomodeset boot options to no avail. I was able
  to finally install Bionic by hooking up the laptop to a projector, but
  after a reboot, the laptop display still did not work and I had to set
  the account to autologin otherwise I could not login to the laptop. I
  then install openssh-server so that I could ssh into the laptop and I
  installed the nvidia-390 drivers from ppa:graphics-drivers/ppa which
  installed, but still no local display.

  In Artful, I could install with the nouveau.modeset=0 and then
  installing the proprietary NVIDIA drivers and everything (except
  touchpad, LP: 1738263) worked.

  lspci shows the graphics card and NVIDIA card, and lsmod does show
  that before NVIDIA drivers install, it is using nouveau, asus_wmi, and
  i915 for graphcis, and once NVIDIA drivers are install, lsmod only
  shows i915 and asus_wmi for graphics while nvidia is used for gpu and
  3D, but still no display on the laptop.

  lsmod_prenvidia.txt shows the nouveau driver and the /proc/cmdline
  lsmod_nvidia.txt shows nvidia drivers installed and the /proc/cmdline
  lspci.txt shows the detected hardware
  lshw.txt shows the hardware in the laptop.

  Please let me know if you need any other information.

  Thanks,
  Luke

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

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

[Desktop-packages] [Bug 1761261] Re: nouveau/nvidia drivers do not work with display in Bionic on Asus GL703VD Laptop

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

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

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

Title:
  nouveau/nvidia drivers do not work with display in Bionic on Asus
  GL703VD Laptop

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Tried to install Bionic Desktop on my Asus GL703VD ROG Laptop with
  NVIDIA GTX 1050M Video Card (with i915 Intel graphics card when not
  using 3D) and the installer does not display. I have tried
  nouveau.modeset=0 and nomodeset boot options to no avail. I was able
  to finally install Bionic by hooking up the laptop to a projector, but
  after a reboot, the laptop display still did not work and I had to set
  the account to autologin otherwise I could not login to the laptop. I
  then install openssh-server so that I could ssh into the laptop and I
  installed the nvidia-390 drivers from ppa:graphics-drivers/ppa which
  installed, but still no local display.

  In Artful, I could install with the nouveau.modeset=0 and then
  installing the proprietary NVIDIA drivers and everything (except
  touchpad, LP: 1738263) worked.

  lspci shows the graphics card and NVIDIA card, and lsmod does show
  that before NVIDIA drivers install, it is using nouveau, asus_wmi, and
  i915 for graphcis, and once NVIDIA drivers are install, lsmod only
  shows i915 and asus_wmi for graphics while nvidia is used for gpu and
  3D, but still no display on the laptop.

  lsmod_prenvidia.txt shows the nouveau driver and the /proc/cmdline
  lsmod_nvidia.txt shows nvidia drivers installed and the /proc/cmdline
  lspci.txt shows the detected hardware
  lshw.txt shows the hardware in the laptop.

  Please let me know if you need any other information.

  Thanks,
  Luke

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

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

[Desktop-packages] [Bug 1761261] Re: nouveau/nvidia drivers do not work with display in Bionic on Asus GL703VD Laptop

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

** Changed in: xserver-xorg-video-nouveau (Ubuntu)
   Status: New => Confirmed

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

Title:
  nouveau/nvidia drivers do not work with display in Bionic on Asus
  GL703VD Laptop

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Tried to install Bionic Desktop on my Asus GL703VD ROG Laptop with
  NVIDIA GTX 1050M Video Card (with i915 Intel graphics card when not
  using 3D) and the installer does not display. I have tried
  nouveau.modeset=0 and nomodeset boot options to no avail. I was able
  to finally install Bionic by hooking up the laptop to a projector, but
  after a reboot, the laptop display still did not work and I had to set
  the account to autologin otherwise I could not login to the laptop. I
  then install openssh-server so that I could ssh into the laptop and I
  installed the nvidia-390 drivers from ppa:graphics-drivers/ppa which
  installed, but still no local display.

  In Artful, I could install with the nouveau.modeset=0 and then
  installing the proprietary NVIDIA drivers and everything (except
  touchpad, LP: 1738263) worked.

  lspci shows the graphics card and NVIDIA card, and lsmod does show
  that before NVIDIA drivers install, it is using nouveau, asus_wmi, and
  i915 for graphcis, and once NVIDIA drivers are install, lsmod only
  shows i915 and asus_wmi for graphics while nvidia is used for gpu and
  3D, but still no display on the laptop.

  lsmod_prenvidia.txt shows the nouveau driver and the /proc/cmdline
  lsmod_nvidia.txt shows nvidia drivers installed and the /proc/cmdline
  lspci.txt shows the detected hardware
  lshw.txt shows the hardware in the laptop.

  Please let me know if you need any other information.

  Thanks,
  Luke

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

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

[Desktop-packages] [Bug 1752197] Re: Videos won't resume after being paused

This bug was fixed in the package webkit2gtk - 2.20.0-2ubuntu1

---
webkit2gtk (2.20.0-2ubuntu1) bionic; urgency=medium

  * Enable gstreamer-gl on Ubuntu
- Resuming paused videos will work correctly now (LP: #1752197)

 -- Jeremy Bicha   Wed, 04 Apr 2018 08:08:55 -0400

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

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

Title:
  Videos won't resume after being paused

Status in WebKit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Invalid
Status in webkit2gtk package in Ubuntu:
  Fix Released
Status in webkit2gtk source package in Artful:
  Confirmed

Bug description:
  On my Ubuntu 17.10 system, Epiphany Browser 3.26.1 has trouble playing
  YouTube videos. I can play a video from the start point without
  trouble, but if I pause the video the screen will freeze and stay that
  way after restarting the video, if I leave the page and go back later
  it will show a black screen. In both cases the soundtrack continues
  without problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: epiphany-browser 3.26.1-1ubuntu1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 27 17:27:50 2018
  InstallationDate: Installed on 2017-12-06 (83 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: epiphany-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/webkit-open-source/+bug/1752197/+subscriptions

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

[Desktop-packages] [Bug 1761849] [NEW] Radiance title bar is a lot bigger in fullscreen than Ambiance

2018-04-06 Thread Hito

Public bug reported:

Ubuntu 18.04 Beta 1
Radiance title bar is relay huge, see screenshots below;

Ambiance:
https://i.imgur.com/Q31yqx9.png

Radiance:
https://i.imgur.com/SYL0U7y.png

** Affects: ubuntu-themes (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Radiance title bar is a lot bigger in fullscreen than Ambiance

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 Beta 1
  Radiance title bar is relay huge, see screenshots below;

  Ambiance:
  https://i.imgur.com/Q31yqx9.png

  Radiance:
  https://i.imgur.com/SYL0U7y.png

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

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

[Desktop-packages] [Bug 1761844] Re: Thunderbird: emojis is displayed in the email list

2018-04-06 Thread Diego Germán Gonzalez

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

Title:
  Thunderbird: emojis is displayed in the email list

Status in thunderbird package in Ubuntu:
  New

Bug description:
  The list of emails received from Thunderbird shows emojis. This does not 
happen with all accounts.
  It appears to be with the last email address added.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:52.6.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   diego  1607 F...m pulseaudio
   /dev/snd/controlC0:  diego  1607 F pulseaudio
   /dev/snd/controlC1:  diego  1607 F pulseaudio
  BuildID: 20180131200234
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  6 15:58:17 2018
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-04-05 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  IpRoute:
   default via 181.31.1.1 dev enp2s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp2s0 scope link metric 1000 
   181.31.1.0/24 dev enp2s0 proto kernel scope link src 181.31.1.84 metric 100
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=52.6.0/20180131200234 (In use)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: GA-78LMT-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd08/14/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1761844] [NEW] Thunderbird: emojis is displayed in the email list

2018-04-06 Thread Diego Germán Gonzalez

Public bug reported:

The list of emails received from Thunderbird shows emojis. This does not happen 
with all accounts.
It appears to be with the last email address added.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: thunderbird 1:52.6.0+build1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   diego  1607 F...m pulseaudio
 /dev/snd/controlC0:  diego  1607 F pulseaudio
 /dev/snd/controlC1:  diego  1607 F pulseaudio
BuildID: 20180131200234
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  6 15:58:17 2018
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2018-04-05 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
IpRoute:
 default via 181.31.1.1 dev enp2s0 proto dhcp metric 100 
 169.254.0.0/16 dev enp2s0 scope link metric 1000 
 181.31.1.0/24 dev enp2s0 proto kernel scope link src 181.31.1.84 metric 100
IwConfig:
 lono wireless extensions.
 
 enp2s0no wireless extensions.
Locales: extensions.sqlite corrupt or missing
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=52.6.0/20180131200234 (In use)
RfKill:
 
RunningIncompatibleAddons: False
SourcePackage: thunderbird
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/14/2012
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F4
dmi.board.name: GA-78LMT-S2
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd08/14/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-78LMT-S2
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug bionic

** Attachment added: "Untitled.png"
   
https://bugs.launchpad.net/bugs/1761844/+attachment/5104553/+files/Untitled.png

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

Title:
  Thunderbird: emojis is displayed in the email list

Status in thunderbird package in Ubuntu:
  New

Bug description:
  The list of emails received from Thunderbird shows emojis. This does not 
happen with all accounts.
  It appears to be with the last email address added.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:52.6.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   diego  1607 F...m pulseaudio
   /dev/snd/controlC0:  diego  1607 F pulseaudio
   /dev/snd/controlC1:  diego  1607 F pulseaudio
  BuildID: 20180131200234
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  6 15:58:17 2018
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-04-05 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  IpRoute:
   default via 181.31.1.1 dev enp2s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp2s0 scope link metric 1000 
   181.31.1.0/24 dev enp2s0 proto kernel scope link src 181.31.1.84 metric 100
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=52.6.0/20180131200234 (In use)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: GA-78LMT-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version:

[Desktop-packages] [Bug 1749940] Re: package network-manager-gnome 1.2.6-0ubuntu0.16.04.4 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar

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

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

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

Title:
  package network-manager-gnome 1.2.6-0ubuntu0.16.04.4 failed to
  install/upgrade: O pacote está num mau estado de inconsistência; deve
  reinstala-lo antes de tentar configura-lo.

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

Bug description:
  please , i don't understand the bug , help ! alguns arquivos no
  terminal estao informando que o pacote está corrompido e eu nao sei o
  que fazer

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: network-manager-gnome 1.2.6-0ubuntu0.16.04.4
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Feb 15 06:05:37 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  ErrorMessage: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-11-29 (78 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IpRoute:
   default via 192.168.0.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.0.111  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: network-manager-applet
  Title: package network-manager-gnome 1.2.6-0ubuntu0.16.04.4 failed to 
install/upgrade: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   wlp3s0  wifi  connected/org/freedesktop/NetworkManager/Devices/2  
SAM NET Tayrone 1  b4738f86-8f8b-4d7e-a051-3b82b8c5262e  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp2s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/0  -- 
----
 
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

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

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

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

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

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

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

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

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

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

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I was just using terminal.  Just started using Linux, sorry if this
  should have been a dup, I wasnt sure

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr  6 13:38:11 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-04-05 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180401)
  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/1761833/+subscriptions

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

[Desktop-packages] [Bug 1761834] [NEW] Right-click doesn't work

2018-04-06 Thread Eric Stith

Public bug reported:

I decided to try out the beta for 18.04 from 17.10.  Upon upgrading, I
discovered that right-clicking no longer works on my trackpad, and
right-clicks are handled as left-clicks would be.  Two-finger right
click does not work either.  If I plug in a mouse with a physical right
button, right clicking does work.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Fri Apr  6 11:26:00 2018
DistUpgraded: 2018-04-06 11:14:08,949 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.14.15-041415-generic, x86_64: installed
 bbswitch, 0.8, 4.15.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 530 [1028:06e4]
   Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4]
InstallationDate: Installed on 2017-05-04 (337 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: Dell Inc. XPS 15 9550
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic 
root=UUID=62d6bfc3-82e2-4ca2-9255-8dae5ad9b117 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-04-06 (0 days ago)
dmi.bios.date: 08/21/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.0
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd08/21/2017:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic 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/1761834

Title:
  Right-click doesn't work

Status in xorg package in Ubuntu:
  New

Bug description:
  I decided to try out the beta for 18.04 from 17.10.  Upon upgrading, I
  discovered that right-clicking no longer works on my trackpad, and
  right-clicks are handled as left-clicks would be.  Two-finger right
  click does not work either.  If I plug in a mouse with a physical
  right button, right clicking does work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr  6 11:26:00 2018
  DistUpgraded: 2018-04-06 11:14:08,949 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.14.15-041415-generic, x86_64: installed
   bbswitch, 0.8, 4.15.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 530 [1028:06e4]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4]
  InstallationDate: Installed on 2017-05-04 (337 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic 
root=UUID=62d6bfc3-82e2-4ca2-9255-8dae5ad9b117 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-04-06 (0 days ago)
  dmi.bios.date: 08/21/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.

[Desktop-packages] [Bug 1568576] Re: Thinkpad T460 & Ultra Dock - No audio output on dock plug

2018-04-06 Thread Stephan

Same here with L470
(uname -a: 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux )

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

Title:
  Thinkpad T460 & Ultra Dock - No audio output on dock plug

Status in ALSA driver:
  New
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Thinkpad T460, Ultra dock, 2 channel speakers connected to dock.
  4.4.0-18 Kernel / 16.04.

  When the laptop is docked & speakers are connected to the dock audio
  connector, I get no audio outpout from the dock audio connector.

  Looks like the same issue as reported in:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1385680

  However the pin quirks appear to be different for the T*60 series of
  laptops.

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

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

[Desktop-packages] [Bug 1756547] Re: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d

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

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

Title:
  LP refuses to import plural strings where e.g. msgstr[0] entries in PO
  file miss %d

Status in Launchpad itself:
  New
Status in Ubuntu Translations:
  In Progress
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  Some strings of GNOME Shell are untranslated in the Czech translation
  on Ubuntu 18.04 although they are translated upstream and when I try
  to manually translate them on launchpad, I get this error: "number of
  format specifications in 'msgid_plural' and 'msgstr[0]' does not
  match".

  The bad strings are:
  %d minute ago
  %d minutes ago

  %d hour ago
  %d hours ago

  %d week ago
  %d weeks ago

  %d month ago
  %d months ago

  %d year ago
  %d years ago

  They seem to be correct, but they are not accepted for some reason.

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

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

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

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

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

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

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

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

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

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

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

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  start ubuntu

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Apr  5 22:25:06 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-04-01 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180401)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.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/1761818/+subscriptions

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

[Desktop-packages] [Bug 1761816] This bug is a duplicate

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

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

** This bug has been marked a duplicate of bug 1751460
   [regression] deja-dup-monitor crashed with SIGSEGV in 
Gigacage::::operator()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Error appeared out of the blue, was trying to run Sofware Update via
  Ubuntu Software app

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-2fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  6 10:26:04 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2018-03-01 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f380a9c90a8:movl   $0x0,(%rax)
   PC (0x7f380a9c90a8) 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=0x7f380ac3002c, 
init_routine=0x7f3801a6e590 <__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/1761816/+subscriptions

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

[Desktop-packages] [Bug 572045] Re: should be marked undumpable to avoid PTRACE attach

2018-04-06 Thread 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/572045

Title:
  should be marked undumpable to avoid PTRACE attach

Status in GNOME Keyring:
  Fix Released
Status in GnuPG2:
  Fix Released
Status in gnome-keyring package in Ubuntu:
  Triaged
Status in gnupg2 package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gnome-keyring

  Programs that keep sensitive information in memory should avoid
  dumping core or being PTRACEable.  Things like ssh-agent already
  accomplish this by calling:

  prctl(PR_SET_DUMPABLE, 0);

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-keyring 2.92.92.is.2.30.0-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic x86_64
  Architecture: amd64
  Date: Thu Apr 29 22:19:39 2010
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-keyring

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

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

[Desktop-packages] [Bug 465689] Re: Ubuntu Clock Won't Show Year

I was ultimately able to achieve my exactly desired format using a GNOME
extension made by Daniel Khodabakhsh. Thank you Daniel!

I found that here:
https://github.com/Daniel-Khodabakhsh/datetime-format

Screenshot:
http://neartalk.com/ss/2018-04-06_003_1919x1079.png

Format:
%A | %m-%d-%G | %I:%M %p

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

Title:
  Ubuntu Clock Won't Show Year

Status in GNOME Panel:
  In Progress
Status in Indicator Date and Time:
  Fix Released
Status in gnome-panel package in Ubuntu:
  Triaged
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  indicator-datetime, Ubuntu 12.10

  The Ubuntu menu bar clock offers no setting to "show year".

  Yes, I know what year it is, but I have very good reason for wanting
  it shown. For years, I've been collecting screen-shots, when I'm doing
  something I think is pretty cool. When I use to use windows, these
  screen shots (over the years) have always showed the current year.

  However, since April of 2007 (The date I started using Ubuntu
  exclusively), my screen shots have not included the year, because the
  Gnome clock doesn't provide this capability.

  : "'Year' should be both
  insensitive and unchecked whenever 'Date and month' is unchecked..."

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

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

[Desktop-packages] [Bug 1761593] Re: Uninstall left nouveau blacklisted

2018-04-06 Thread Kev Bowring

Rechecked this (multiple times)

Using the GUI at Software & Updates>Additional Drivers appears to now
not remove conf files and hence user is left with 640x480px (assume
because of the blacklist file left in /etc/modprobe.d)

If one installs via apt and then purges - the nvidia conf file is
removed and a normal at reboot results.

The same behaviour is seen if installed via Software & Updates and then
removed with apt purge.

Pretty positive this was not previously the case when using the GUI to
install nvidia driver.

Only have 1 card to test against - so possibly only affects nvidia-340.

Notes from testing and some pastebin of terminal logs attached.

** Attachment added: "nvidia_testing"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1761593/+attachment/5104355/+files/nvidia_testing

** Package changed: nvidia-graphics-drivers-340 (Ubuntu) => software-
properties (Ubuntu)

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

Title:
  Uninstall left nouveau blacklisted

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Following a successful install and subsequent use of nvidia-340 -
  uninstallation of nvidia via Additional Drivers led to a reboot to a
  desktop at 640x480 px.

  Investigation found an nvidia created file left on the system
  blacklisting nouveau, deleted file and rebooted to normal desktop.

  Didn't think about ubuntu-reporting this - can try and replicate and
  apport-collect if it's of any use.

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

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

[Desktop-packages] [Bug 1707451] Re: udisksd crashed with SIGSEGV in g_mutex_lock()

This bug was fixed in the package udisks2 - 2.7.6-2ubuntu6

---
udisks2 (2.7.6-2ubuntu6) bionic; urgency=medium

  * debian/patches/remove_sigint_source.patch:
- backport a segfault fix from an upstream PR, thanks andyrock!
  (lp: #1707451)

 -- Sebastien Bacher   Wed, 04 Apr 2018 09:39:45
+0200

** Changed in: udisks2 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  udisksd crashed with SIGSEGV in g_mutex_lock()

Status in udisks:
  New
Status in glib package in Ubuntu:
  Confirmed
Status in udisks2 package in Ubuntu:
  Fix Released

Bug description:
  Showed up after login

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: udisks2 2.6.5-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sun Jul 30 00:35:31 2017
  ExecutablePath: /usr/lib/udisks2/udisksd
  InstallationDate: Installed on 2017-06-22 (37 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170622)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcCmdline: /usr/lib/udisks2/udisksd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic.efi.signed 
root=UUID=44b31662-d2ab-443b-9546-86d022d8de0d ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f4900fb5c65 :   lock xadd 
%eax,(%rdi)
   PC (0x7f4900fb5c65) ok
   source "%eax" ok
   destination "(%rdi)" (0x3a9d80e262617474) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: udisks2
  StacktraceTop:
   g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   main ()
  Title: udisksd crashed with SIGSEGV in g_mutex_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/12/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.40
  dmi.board.name: Z87 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd04/12/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 1756378] Re: Udisks2 flacky test (regression from 2.7)

This bug was fixed in the package udisks2 - 2.7.6-2ubuntu6

---
udisks2 (2.7.6-2ubuntu6) bionic; urgency=medium

  * debian/patches/remove_sigint_source.patch:
- backport a segfault fix from an upstream PR, thanks andyrock!
  (lp: #1707451)

 -- Sebastien Bacher   Wed, 04 Apr 2018 09:39:45
+0200

** Changed in: udisks2 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Udisks2 flacky test (regression from 2.7)

Status in udisks2 package in Ubuntu:
  Fix Released
Status in udisks2 source package in Bionic:
  Fix Released

Bug description:
  One of the udisks2 tests has become flacky in the 2.7 update

  ERROR: test_ext4 (__main__.FS)
  fs: ext4
  --
  Traceback (most recent call last):
File "src/tests/integration-test", line 680, in test_ext4
  self._do_fs_check('ext4')
File "src/tests/integration-test", line 841, in _do_fs_check
  self._do_udisks_check(fs_type)
File "src/tests/integration-test", line 1045, in _do_udisks_check
  cd_fs.call_mount_sync(ro_options, None)
  AttributeError: 'NoneType' object has no attribute 'call_mount_sync'

  That needs to be resolved

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

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

[Desktop-packages] [Bug 465689] Re: Ubuntu Clock Won't Show Year

Lonnie, please use a separate gnome-shell bug for that issue.

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

Title:
  Ubuntu Clock Won't Show Year

Status in GNOME Panel:
  In Progress
Status in Indicator Date and Time:
  Fix Released
Status in gnome-panel package in Ubuntu:
  Triaged
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  indicator-datetime, Ubuntu 12.10

  The Ubuntu menu bar clock offers no setting to "show year".

  Yes, I know what year it is, but I have very good reason for wanting
  it shown. For years, I've been collecting screen-shots, when I'm doing
  something I think is pretty cool. When I use to use windows, these
  screen shots (over the years) have always showed the current year.

  However, since April of 2007 (The date I started using Ubuntu
  exclusively), my screen shots have not included the year, because the
  Gnome clock doesn't provide this capability.

  : "'Year' should be both
  insensitive and unchecked whenever 'Date and month' is unchecked..."

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

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

[Desktop-packages] [Bug 1737053] Re: [MIR] brotli

2018-04-06 Thread Matthias Klose

patch merged into the bionic package

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

Title:
  [MIR] brotli

Status in brotli package in Ubuntu:
  Incomplete

Bug description:
  Availability
  
  Built for all supported architectures. In sync with Debian.

  Rationale
  =
  brotli is a file compression format and library developed and maintained by 
Google. brotli is required by the WOFF 2.0 format for compressed web fonts. 
brotli and woff2 are libraries that are technically already in main because 
they are bundled in Firefox and webkit2gtk.

  The next major stable release of webkit2gtk, 2.20, will be released in March. 
It drops those 2 bundled libraries. I think our options are basically
  1) Bundle those libraries anyway, or
  2) Approve this MIR, or
  3) Drop support for the WOFF2 format in webkit2gtk

  Security
  
  brotli is a security-sensitive library.

  There was one security bug fixed recently for xenial (LP: #1737364)

  https://security-tracker.debian.org/tracker/source-package/brotli
  https://launchpad.net/ubuntu/+source/brotli/+cve

  Quality assurance
  =
  - Ubuntu Desktop Bugs is subscribed.
  - dh_auto_test runs upstream build tests. Test failure would fail the build.
  - New autopkgtests pass on all arches:
  http://autopkgtest.ubuntu.com/packages/b/brotli
  https://ci.debian.net/packages/b/brotli/

  https://bugs.launchpad.net/ubuntu/+source/brotli
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=brotli
  https://github.com/google/brotli/issues

  Dependencies
  
  No universe binary dependencies

  Standards compliance
  
  4.1.1, debhelper compat 10, dh7 simple rules

  Maintenance
  ===
  Actively maintained:
  https://github.com/google/brotli

  Not team maintained in Debian.
  https://tracker.debian.org/pkg/brotli

  Other Info
  ==
  webkit2gtk is managed similar to Firefox and Chromium. So far, new releases 
are pushed to Ubuntu 16.04 LTS and newer as security updates, but the Ubuntu 
Security Team does not guarantee security support for webkit2gtk.

  The woff2 MIR is LP: #1742743

  We are going to need to backport brotli and woff2 into main as
  security updates for 16.04 LTS and 17.10. The new version of brotli
  adds new binary packages (in particular, the C library needed by woff2
  and webkit2gtk).

  brotli has no reverse dependencies in 16.04 and 17.10. (fonttools is a
  reverse-dependency in 18.04.)

  brotli has a bizarre build system.

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

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

[Desktop-packages] [Bug 465689] Re: Ubuntu Clock Won't Show Year

Will I ever be able to convenience people that "show year" is actually a
useful feature when taking screenshots over time?

Now, that I've upgraded to Ubuntu 18.04 and GNOME 3.28, it looks like
I'll have to start this 2009 battle all over again. It will not allow me
to format the clock the way I want it to display.

In Unity, I could at least achieved my desired clock format with a
command:

gsettings set com.canonical.indicator.datetime time-format "'custom'" ;
gsettings set com.canonical.indicator.datetime custom-time-format "'%A |
%m-%d-%Y | %l:%M%p'"

In GNOME 3.28 on Ubuntu 18.04, I've yet to figure out a way to achieved
my desired format. The GUI doesn't offer "show year" and I've yet to
discover a command (like the one above) that achieves the exact custom
format I desire.

** Tags added: bionic

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

Title:
  Ubuntu Clock Won't Show Year

Status in GNOME Panel:
  In Progress
Status in Indicator Date and Time:
  Fix Released
Status in gnome-panel package in Ubuntu:
  Triaged
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  indicator-datetime, Ubuntu 12.10

  The Ubuntu menu bar clock offers no setting to "show year".

  Yes, I know what year it is, but I have very good reason for wanting
  it shown. For years, I've been collecting screen-shots, when I'm doing
  something I think is pretty cool. When I use to use windows, these
  screen shots (over the years) have always showed the current year.

  However, since April of 2007 (The date I started using Ubuntu
  exclusively), my screen shots have not included the year, because the
  Gnome clock doesn't provide this capability.

  : "'Year' should be both
  insensitive and unchecked whenever 'Date and month' is unchecked..."

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

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

[Desktop-packages] [Bug 1749546] Re: Booting a live session is slow - fontconfig regenerates its font cache

This bug was fixed in the package fontconfig - 2.12.6-0ubuntu2

---
fontconfig (2.12.6-0ubuntu2) bionic; urgency=medium

  * Upload proposed patch from upstream bug #103652. If the fontconfig cache
was built on a system that has nanosecond timestamps and then later
transplanted to one that doesn't - for example by mksquashfs as part of a
live CD build - we consider the cache invalid and rebuild it during the
boot process. Depending on the fonts involved, this can take a significant
amount of time and potentially cause knock-on timeouts. The approach in
this patch is to ignore the nanosecond portion of the cache's value if we
get 0 when stat()ing the referenced directory, meaning it is considered
fresh if the rest of the timestamp matches. (LP: #1749546)

 -- Iain Lane   Thu, 05 Apr 2018 17:13:52
+0100

** Changed in: fontconfig (Ubuntu Bionic)
   Status: In Progress => Fix Released

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

Title:
  Booting a live session is slow - fontconfig regenerates its font cache

Status in Fontconfig:
  Confirmed
Status in fontconfig package in Ubuntu:
  Fix Released
Status in fontconfig source package in Bionic:
  Fix Released

Bug description:
  On Bionic Ubuntu Desktop booting to a live session is slow. It takes
  roughly 2 min on my test machine to boot from the "Try or Install
  Ubuntu" boot menu to a usable session.

  It also takes 1 minute to logout and 17s to log in again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: casper 1.388
  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
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 16:43:19 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: casper
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1740741] Re: * Hide imagemagick's Display app from the Ubuntu GNOME session as well

** Package changed: ubuntu-settings (Ubuntu) => imagemagick (Ubuntu)

** Changed in: imagemagick (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
* Hide imagemagick's Display app from the Ubuntu GNOME session as
  well

Status in imagemagick package in Ubuntu:
  Fix Committed

Bug description:
  Imagemagick's Display app was hidden from the default Ubuntu session
  for Artful (LP: #1717951), but was still visible if you chose the
  GNOME session instead.

  I propose to apply the same fix (for the same reasons given in Bug
  1717951) to the GNOME session in Bionic.

  Link to bug 1717951: https://bugs.launchpad.net/ubuntu/+source/ubuntu-
  settings/+bug/1717951

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

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

[Desktop-packages] [Bug 1740743] Re: Hide Imagemagick's Display app from GNOME software

** Package changed: gnome-software (Ubuntu) => imagemagick (Ubuntu)

** Changed in: imagemagick (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  Hide Imagemagick's Display app from GNOME software

Status in imagemagick package in Ubuntu:
  Fix Committed

Bug description:
  In bug #1717951 Imagemagick was already removed from being displayed
  in GNOME-Shell.

  It is still listed in GNOME-Software which causes some (potential)
  usability issues:

  Users can still test the "imagemagick" app from within Ubuntu Software
  and decide to remove it from there. Because that app looks dated, ugly
  and out of place in a modern desktop environment. Removing Imagemagick
  has the bad side-effect of removing printing support while user won't
  even realize that Imagemagick was printing related at all.

  Thus I propose to remove the app from being listed as installed in
  Ubuntu Software at all. Or to be moved to the "System Apps" section to
  prevent users from removing it manually (and unvoluntarily CUPS with
  it).

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

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

[Desktop-packages] [Bug 1761593] Re: Uninstall left nouveau blacklisted

2018-04-06 Thread Kev Bowring

apport-collect failed to collect new information for this bug as nvidia
is no longer installed.

test@test-MBB-44608:~$ ls /etc/modprobe.d/
alsa-base.conf   blacklist-framebuffer.conf   dkms.conf
blacklist-ath_pci.conf   blacklist-modem.conf iwlwifi.conf
blacklist.conf   blacklist-oss.conf   nvidia-340.conf
blacklist-firewire.conf  blacklist-rare-network.conf
test@test-MBB-44608:~$ cat /etc/modprobe.d/nvidia-340.conf 
# This file was installed by nvidia-340
# Do not edit this file manually

blacklist nouveau
blacklist lbm-nouveau
alias nouveau off
alias lbm-nouveau off

sudo apt autoremove did:
The following packages will be REMOVED
  dkms lib32gcc1 libc6-i386 libcuda1-340 libxnvctrl0 nvidia-settings
  pkg-config screen-resolution-extra

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

Title:
  Uninstall left nouveau blacklisted

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

Bug description:
  Following a successful install and subsequent use of nvidia-340 -
  uninstallation of nvidia via Additional Drivers led to a reboot to a
  desktop at 640x480 px.

  Investigation found an nvidia created file left on the system
  blacklisting nouveau, deleted file and rebooted to normal desktop.

  Didn't think about ubuntu-reporting this - can try and replicate and
  apport-collect if it's of any use.

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

-- 
Mailing list: https://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 1761747] Re: 18.04 beta 2 ubuntu-software doesn't show firefox as installed

2018-04-06 Thread Anthony Jackson

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

This is not a duplicate bug. Please re-read report. This is about the
minimal install not listing Firefox *as* installed when it clearly is.




‐‐‐ Original Message ‐‐‐

On April 6, 2018 2:31 PM, Jeremy Bicha  wrote:

> 
> 
> *** This bug is a duplicate of bug 1682455 ***
> 
> https://bugs.launchpad.net/bugs/1682455
> 
> ** This bug has been marked a duplicate of bug 1682455
> 
> thunderbird not available in GNOME Software
> 
> 
> 
> 
> You received this bug notification because you are subscribed to the bug
> 
> report.
> 
> https://bugs.launchpad.net/bugs/1761747
> 
> Title:
> 
> 18.04 beta 2 ubuntu-software doesn't show firefox as installed
> 
> Status in gnome-software package in Ubuntu:
> 
> New
> 
> Bug description:
> 
> $ lsb_release -rd
> 
> Description: Ubuntu Bionic Beaver (development branch)
> 
> Release: 18.04
> 
> om/ubuntu bionic/main i386 Packages
> 
> 100 /var/lib/dpkg/status
> 
> ubuntu-software:
> 
> Installed: 3.28.0-0ubuntu7
> 
> Candidate: 3.28.0-0ubuntu7
> 
> Version table:
> 
> *** 3.28.0-0ubuntu7 500
> 
> 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
> 
> 500 http://gb.archive.ubuntu.c500 http://gb.archive.ubuntu.c...
> 
> Ubuntu Software does not see Firefox as installed (testing on minimal
> 
> installation option). The package is not shown in the list of
> 
> installed software and the Install button for Firefox snap package is
> 
> available. Installing this leaves both versions on the system, while
> 
> expected for an experienced user this is not intuitive for a new
> 
> Ubuntu user.
> 
> ProblemType: Bug
> 
> DistroRelease: Ubuntu 18.04
> 
> Package: ubuntu-software 3.28.0-0ubuntu7
> 
> ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
> 
> Uname: Linux 4.15.0-13-generic x86_64
> 
> ApportVersion: 2.20.9-0ubuntu2
> 
> Architecture: amd64
> 
> CurrentDesktop: ubuntu:GNOME
> 
> Date: Fri Apr 6 14:11:43 2018
> 
> InstallationDate: Installed on 2018-04-06 (0 days ago)
> 
> InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
> 
> InstalledPlugins:
> 
> gnome-software-plugin-flatpak N/A
> 
> gnome-software-plugin-limba N/A
> 
> gnome-software-plugin-snap 3.28.0-0ubuntu7
> 
> PackageArchitecture: all
> 
> 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/1761747/+subscriptions

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

Title:
  18.04 beta 2 ubuntu-software doesn't show firefox as installed

Status in gnome-software package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  om/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status

  
  ubuntu-software:
Installed: 3.28.0-0ubuntu7
Candidate: 3.28.0-0ubuntu7
Version table:
   *** 3.28.0-0ubuntu7 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://gb.archive.ubuntu.c500 http://gb.archive.ubuntu.c...

  Ubuntu Software does not see Firefox as installed (testing on minimal
  installation option). The package is not shown in the list of
  installed software and the Install button for Firefox snap package is
  available. Installing this leaves both versions on the system, while
  expected for an experienced  user this is not intuitive for a new
  Ubuntu user.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-software 3.28.0-0ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  6 14:11:43 2018
  InstallationDate: Installed on 2018-04-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu7
  PackageArchitecture: all
  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/1761747/+subscriptions

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

[Desktop-packages] [Bug 1761792] Re: Xwayland crashed with SIGABRT in OsAbort()

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

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 #1745799, 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/1761792/+attachment/5104273/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1745799
   Xwayland crashed with SIGABRT in OsAbort()

** Tags removed: need-amd64-retrace

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

Title:
  Xwayland crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  System froze when I unlocked the greeter.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr  6 17:45:23 2018
  DistUpgraded: 2018-03-24 15:02:43,050 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Juniper XT [Radeon HD 
5770] [174b:1482]
  InstallationDate: Installed on 2014-07-15 (1361 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  MachineType: Gigabyte Technology Co., Ltd. GA-890GPA-UD3H
  ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -accessx -core 
-listen 4 -listen 5 -displayfd 6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=0889d734-ea91-4bdb-9d16-2a0a923ad3d1 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
  Title: Xwayland crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (13 days ago)
  UserGroups:
   
  dmi.bios.date: 07/23/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FD
  dmi.board.name: GA-890GPA-UD3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd07/23/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-890GPA-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-890GPA-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-890GPA-UD3H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Jun 20 10:32:21 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1
  xserver.video_driver: radeon

To manage notifications about this

[Desktop-packages] [Bug 1761789] Re: soffice.bin crashed with SIGSEGV in JNI_CreateJavaVM()

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

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 #1726145, 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/1761789/+attachment/5104253/+files/CoreDump.gz

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

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

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

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

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

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

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

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

Title:
  soffice.bin crashed with SIGSEGV in JNI_CreateJavaVM()

Status in libreoffice package in Ubuntu:
  New

Bug description:
  ibreoffice crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-core 1:6.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic i686
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: MATE
  Date: Fri Apr  6 18:42:25 2018
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2018-01-14 (82 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --writer --splash-pipe=5
  SegvAnalysis:
   Segfault happened at: 0xa84ccc15:movb   $0x0,(%eax)
   PC (0xa84ccc15) ok
   source "$0x0" ok
   destination "(%eax)" (0xbf716fe0) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
   ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
   ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
   ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
   JNI_CreateJavaVM () from 
/usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
  Title: soffice.bin crashed with SIGSEGV in JNI_CreateJavaVM()
  UpgradeStatus: Upgraded to bionic on 2018-04-06 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

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

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

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

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

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

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

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

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

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

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  it had have happen many times,olso i did install hand brake but it
  does not work at all.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr  6 06:13:47 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-04-03 (3 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  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/1761794/+subscriptions

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

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

2018-04-06 Thread Jean-Baptiste Lallement

Public bug reported:

System froze when I unlocked the greeter.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: xwayland 2:1.19.6-1ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CrashCounter: 1
CurrentDesktop: GNOME-Greeter:GNOME
Date: Fri Apr  6 17:45:23 2018
DistUpgraded: 2018-03-24 15:02:43,050 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xwayland
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] 
(prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Juniper XT [Radeon HD 
5770] [174b:1482]
InstallationDate: Installed on 2014-07-15 (1361 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
MachineType: Gigabyte Technology Co., Ltd. GA-890GPA-UD3H
ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -accessx -core 
-listen 4 -listen 5 -displayfd 6
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=0889d734-ea91-4bdb-9d16-2a0a923ad3d1 ro quiet splash vt.handoff=1
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 OsAbort ()
 ?? ()
 FatalError ()
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
Title: Xwayland crashed with SIGABRT in OsAbort()
UpgradeStatus: Upgraded to bionic on 2018-03-24 (13 days ago)
UserGroups:
 
dmi.bios.date: 07/23/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: FD
dmi.board.name: GA-890GPA-UD3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd07/23/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-890GPA-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-890GPA-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-890GPA-UD3H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Tue Jun 20 10:32:21 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1
xserver.video_driver: radeon

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


** Tags: amd64 apport-crash bionic need-amd64-retrace ubuntu

** Information type changed from Private to Public

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

Title:
  Xwayland crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  System froze when I unlocked the greeter.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr  6 17:45:23 2018
  DistUpgraded: 2018-03-24 15:02:43,050 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Juniper XT [Radeon HD 
5770] [174b:1482]
  InstallationDate: Installed on 2014-07-15 (1361 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  MachineType: Gigabyte Technology Co., Ltd. GA-890GPA-UD3H
  ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -accessx -core 
-listen 4 -listen 5 -displayfd 6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=0889d734-ea91-4bdb-9d16-2a0a923ad3d1 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
  Title:

[Desktop-packages] [Bug 1729181] Re: directory and file icons are same in "Files" app

2018-04-06 Thread Malachi de AElfweald

I am seeing the same thing in Ubuntu 18.04 w/ the Classic Gnome login.
I do not see it with the Ubuntu login.

malachid@odin:~$ env | grep -i session
GNOME_SHELL_SESSION_MODE=classic
XDG_SESSION_ID=3
DESKTOP_SESSION=gnome-classic
XDG_SESSION_TYPE=x11
XDG_SESSION_DESKTOP=gnome-classic
GDMSESSION=gnome-classic
GNOME_DESKTOP_SESSION_ID=this-is-deprecated
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
SESSION_MANAGER=local/odin:@/tmp/.ICE-unix/2232,unix/odin:/tmp/.ICE-unix/2232

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

Title:
  directory and file icons are same in "Files" app

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  while browsing File Manager with nautilus, it does not show different
  icons for files and directory. Please see attached screenshot.

  using Ubuntu Desktop 17.10 with wayland
  GNOME nautilus 3.26.0

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

-- 
Mailing list: https://launchpad.net/~desktop-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: [ffe] Out of the box, Ubuntu Bionic offers only insecure VPN option

2018-04-06 Thread Sebastien Bacher

Ubuntu Desktop and Ubuntu Security teams are in agreement that it would
be worth adding to the default installation, that's a new feature though
so needs ubuntu-release to ack the addition, turning the bug to a ffe
and subscribing them for review

** Summary changed:

- Out of the box, Ubuntu Bionic offers only insecure VPN option
+ [ffe] Out of the box, Ubuntu Bionic offers only insecure VPN option

** Summary changed:

- [ffe] Out of the box, Ubuntu Bionic offers only insecure VPN option
+ [ffe] including network-manager-openvpn-gnome in the default installation

-- 
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:
  [ffe] including network-manager-openvpn-gnome in the default
  installation

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager-openvpn package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

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 1761593] Re: Uninstall left nouveau blacklisted

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

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

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

Title:
  Uninstall left nouveau blacklisted

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

Bug description:
  Following a successful install and subsequent use of nvidia-340 -
  uninstallation of nvidia via Additional Drivers led to a reboot to a
  desktop at 640x480 px.

  Investigation found an nvidia created file left on the system
  blacklisting nouveau, deleted file and rebooted to normal desktop.

  Didn't think about ubuntu-reporting this - can try and replicate and
  apport-collect if it's of any use.

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

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

[Desktop-packages] [Bug 1761593] Re: Uninstall left nouveau blacklisted

2018-04-06 Thread Vitor Luis

I've had exactly the same problem described above. Installed Nvidia drivers via
via Additional Drivers and all was working fine.
After that I decided to remove the Nvidia drivers and rebooted the laptop. My
screen resolution was set as 640x480, without any possibility of changing it.
Asking for help, on #ubuntu+1 @ Freenode, someone told me to check
/etc/modprobe.d for a nvidia conf file. I've done that and it was there.
Deleting the file and rebooting the laptop solved the issue.

Exterminador

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

Title:
Uninstall left nouveau blacklisted

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

Bug description:
Following a successful install and subsequent use of nvidia-340 -
uninstallation of nvidia via Additional Drivers led to a reboot to a
desktop at 640x480 px.

Investigation found an nvidia created file left on the system
blacklisting nouveau, deleted file and rebooted to normal desktop.

Didn't think about ubuntu-reporting this - can try and replicate and
apport-collect if it's of any use.

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

[Desktop-packages] [Bug 1758314] Re: Open new windows in the middle of the screen

This bug was fixed in the package ubuntu-settings - 18.04.2

---
ubuntu-settings (18.04.2) bionic; urgency=medium

  [ Didier Roche ]
  * Open new windows in the middle of the screen as requested by the community
for the communitheme session. (LP: #1758314)

  [ Jeremy Bicha ]
  * Add override for gnome-initial-setup.desktop for the Ubuntu sessions with
'Welcome to Ubuntu' title and Ubuntu icon
  * Allow the new .desktop to be translated
  * Depend on gnome-control-center-data since that's where the icon is
currently installed
  * Drop the imagemagick .desktop overrides. Let's fix the issue in
imagemagick directly.

 -- Jeremy Bicha   Fri, 06 Apr 2018 08:24:28 -0400

** Changed in: ubuntu-settings (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Open new windows in the middle of the screen

Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  When opening a new new window in gnome-shell it comes up in the top
  left corner. This is not desireable since it creates a lot of "black"
  there in dark themes and it has some pixels of a bright background
  theme shining through due to window headerbar being rounded.

  Gnome solved the "pixels shining through thing" upstream by having
  that corner rounded in a gnome-session. But this is not feasible in
  the Ubuntu session because the Ubuntu dock is there and the corner
  cannot be rounded.

  Having new windows come up in the middle of the screen would be more
  pleasing visually: It doesn't look crammed (dark headerbar + dark top
  bar) by default and the background pixels shine only "through" if you
  choose to drag the window to that corner.

  On the Ubuntu Community HUB Carlos Lobrano suggested to toggle a
  switch in Mutter to change the default position for new windows. It's
  center-new-windows under /org/gnome/mutter

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

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

[Desktop-packages] [Bug 1761593] Re: Uninstall left nouveau blacklisted

2018-04-06 Thread Kev Bowring

someone turned up in #ubuntu+1 - they had nvidia-340.conf left after
uninstallation

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

Title:
  Uninstall left nouveau blacklisted

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

Bug description:
  Following a successful install and subsequent use of nvidia-340 -
  uninstallation of nvidia via Additional Drivers led to a reboot to a
  desktop at 640x480 px.

  Investigation found an nvidia created file left on the system
  blacklisting nouveau, deleted file and rebooted to normal desktop.

  Didn't think about ubuntu-reporting this - can try and replicate and
  apport-collect if it's of any use.

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

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

[Desktop-packages] [Bug 1761662] Re: The title of the application in the application window appears incorrect.

2018-04-06 Thread Chris

Distributor ID: Ubuntu
Description:Ubuntu 16.04.4 LTS
Release:16.04
Codename:   xenial

Desktop: Unity

Language U.S. English

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

Title:
  The title of the application in the application window appears
  incorrect.

Status in gnome-calculator package in Ubuntu:
  Incomplete

Bug description:
  The main application window shows the name of the application as
  "Calculat or" instead of "Calculator" (Two words broken in an unusual
  place rather than all one word).

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

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

[Desktop-packages] [Bug 1761773] [NEW] Touch Screen stop working on 18.04 beta1

2018-04-06 Thread Raul Dias

Public bug reported:

The touch screen on a HP TouchSmart works fine on other releases.
On the beta of 18.04 it stopped to work.

Bus 005 Device 002: ID 1926:0003 NextWindow 1900 HID Touchscreen

On 16.04 it is recognized as TOUCHSCREEN by X.org.  
On 18.04 beta 1, it is recognized as mouse.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  6 11:39:07 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Pegatron G98M [GeForce 9300M GS] [1b0a:9010]
InstallationDate: Installed on 2018-04-05 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
MachineType: HP-Pavilion FQ429AA-AC4 IQ510br
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=0c40330f-866b-42e4-a61d-3ca0daf9ee6f ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/10/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.06
dmi.board.name: EVE
dmi.board.vendor: PEGATRON CORPORATION.
dmi.board.version: 1.04
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.06:bd07/10/2008:svnHP-Pavilion:pnFQ429AA-AC4IQ510br:pvr:rvnPEGATRONCORPORATION.:rnEVE:rvr1.04:cvnHewlett-Packard:ct3:cvrChassisVersion:
dmi.product.family: 103C_53316J
dmi.product.name: FQ429AA-AC4 IQ510br
dmi.sys.vendor: HP-Pavilion
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic 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/1761773

Title:
  Touch Screen stop working on 18.04 beta1

Status in xorg package in Ubuntu:
  New

Bug description:
  The touch screen on a HP TouchSmart works fine on other releases.
  On the beta of 18.04 it stopped to work.

  Bus 005 Device 002: ID 1926:0003 NextWindow 1900 HID Touchscreen

  On 16.04 it is recognized as TOUCHSCREEN by X.org.  
  On 18.04 beta 1, it is recognized as mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  6 11:39:07 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Pegatron G98M [GeForce 9300M GS] [1b0a:9010]
  InstallationDate: Installed on 2018-04-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  MachineType: HP-Pavilion FQ429AA-AC4 IQ510br
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=0c40330f-866b-42e4-a61d-3ca0daf9ee6f ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.06
  dmi.board.name: EVE
  dmi.board.vendor: PEGATRON CORPORATION.
  dmi.board.version: 1.04
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.06:bd07/10/2008:svnHP-Pavilion:pnFQ429AA-AC4IQ510br:pvr:rvnPEGATRONCORPORATION.:rnEVE:rvr1.04:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.family: 103C_53316J
  dmi.product.name: FQ429AA-AC4 IQ510br
  dmi.sys.vendor: HP-Pavilion
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri:

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

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

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 #1761466, 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/1761769/+attachment/5104131/+files/CoreDump.gz

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

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

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

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

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

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

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

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

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

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  Seemed to happen after I closed calendar.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-calendar 3.28.0-1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  6 09:50:00 2018
  ExecutablePath: /usr/bin/gnome-calendar
  InstallationDate: Installed on 2017-07-18 (262 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
  ProcEnviron:
   SHELL=/usr/bin/zsh
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x56105c00af11 :
mov0x18(%rdi),%rdi
   PC (0x56105c00af11) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-calendar
  StacktraceTop:
   gcal_manager_is_client_writable ()
   ()
   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_is_client_writable()
  UpgradeStatus: Upgraded to bionic on 2018-04-05 (0 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1761773] Re: Touch Screen stop working on 18.04 beta1

2018-04-06 Thread Raul Dias

** Attachment added: "X.org logs from 16.04 (Install Media Try Ubuntu option) 
where it works"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761773/+attachment/5104182/+files/Xorg.0.log

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

Title:
  Touch Screen stop working on 18.04 beta1

Status in xorg package in Ubuntu:
  New

Bug description:
  The touch screen on a HP TouchSmart works fine on other releases.
  On the beta of 18.04 it stopped to work.

  Bus 005 Device 002: ID 1926:0003 NextWindow 1900 HID Touchscreen

  On 16.04 it is recognized as TOUCHSCREEN by X.org.  
  On 18.04 beta 1, it is recognized as mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  6 11:39:07 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Pegatron G98M [GeForce 9300M GS] [1b0a:9010]
  InstallationDate: Installed on 2018-04-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  MachineType: HP-Pavilion FQ429AA-AC4 IQ510br
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=0c40330f-866b-42e4-a61d-3ca0daf9ee6f ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.06
  dmi.board.name: EVE
  dmi.board.vendor: PEGATRON CORPORATION.
  dmi.board.version: 1.04
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.06:bd07/10/2008:svnHP-Pavilion:pnFQ429AA-AC4IQ510br:pvr:rvnPEGATRONCORPORATION.:rnEVE:rvr1.04:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.family: 103C_53316J
  dmi.product.name: FQ429AA-AC4 IQ510br
  dmi.sys.vendor: HP-Pavilion
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

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

2018-04-06 Thread Tim Lunn

I have been liasing with upstream to sort of the few remaining issues,
they have been super responsive, and for the the most part those are
fixed upstream, I will update the packaging with upstream fixes once I
get back into range of a power point! in the next day or three.

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

Title:
  [FFe] upgrade libzip to version 1.5.0

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

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

  Other Changes:
  - A bunch of bug fixes
  - A number of new features like bzip2 (this optional and could be disabled 
for 18.04), improved AES encryption support, some of the new features are other 
platforms only
  - Breaks API (only 1 symbol was removed though), soname bump, so will require 
a mini transition, all the 24 reverse-depends that I count are in universe. 
Some are seeded in flavours (see below)
  - Build system switched to Cmake in latest release
  - Ark will build with libzip support where it didnt before

  Testing:
  It has a fairly comprehensive test suite, all tests are now passing.

  I have run a test rebuild for all the rdepends in ppa:darkxst/libzip.
  All built successfully, except for 2 packages, cbmc and plume-creater
  that had unrelated fallout due to gcc7 and other packaging changes.

  Other Notes:
  - There are a bunch of presumably private symbols leaked into the debian 
symbols file. Not ideal, but probably not the only package in the archive like 
that.
  - Have forwarded upstream a couple of patches and will follow symbols later
  - I will also push for the update into Debian

  Build Logs:
  
https://launchpadlibrarian.net/363222435/buildlog_ubuntu-bionic-amd64.libzip_1.5.0-0ubuntu1~bionic3_BUILDING.txt.gz

  Reverse-depends of libzip4 that are seeded:
  ark (from ark) is seeded in:
    kubuntu: daily-live
    lubuntu-next: daily-live
  ideviceinstaller is seeded in:
    ubuntu-mate: daily-live
  libepub0 is seeded in:
    kubuntu: daily-live
    ubuntustudio: dvd
  libpstoedit0c2a is seeded in:
    kubuntu: supported
  okular-extra-backends is seeded in:
    kubuntu: daily-live

  Upstream Changelog
  ==
  1.5.0 [2018-03-11]
  ==

  * Use standard cryptographic library instead of custom AES implementation.
    This also simplifies the license.
  * Use `clang-format` to format the source code.
  * More Windows improvements.

  1.4.0 [2017-12-29]
  ==

  * Improve build with cmake
  * Retire autoconf/automake build system
  * Add `zip_source_buffer_fragment()`.
  * Add support to clone unchanged beginning of archive (instead of rewriting 
it).
    Supported for buffer sources and on Apple File System.
  * Add support for Microsoft Universal Windows Platform.

  1.3.2 [2017-11-20]
  ==
  * Fix bug introduced in last: zip_t was erroneously freed if zip_close() 
failed.

  1.3.1 [2017-11-19]
  ==

  * Install zipconf.h into ${PREFIX}/include
  * Add zip_libzip_version()
  * Fix AES tests on Linux

  1.3.0 [2017-09-02]
  ==

  * Support bzip2 compressed zip archives
  * Improve file progress callback code
  * Fix zip_fdopen()
  * CVE-2017-12858: Fix double free()
  * CVE-2017-14107: Improve EOCD64 parsing

  1.2.0 [2017-02-19]
  ==

  * Support for AES encryption (Winzip version), both encryption
    and decryption
  * Support legacy zip files with >64k entries
  * Fix seeking in zip_source_file if start > 0
  * Add zip_fseek() for seeking in uncompressed data
  * Add zip_ftell() for telling position in uncompressed data
  * Add zip_register_progress_callback() for UI updates during zip_close()

  1.1.3 [2016-05-28]
  ==

  * Fix build on Windows when using autoconf

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

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

[Desktop-packages] [Bug 1759590] Re: Chromium-Browser Won't Sustain My Profile

I tried deleting the config folder again, just now.

Then, launched chromium and created a bookmark and save the credentials
for a website login.

I closed chromium and then launched it again. It did remember the
bookmark I had added and the website credentials that I had saved during
the session.

However, after this I rebooted and logged back in.

Again, Chromium forgot everything! I had to start all over from scratch.

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

Title:
  Chromium-Browser Won't Sustain My Profile

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Each time I launch chromium-browser it forgets all previous sessions;
  it doesn't remember any saved passwords, history, bookmarks, or form
  data.

  It seem like it is creating a brand new profile each launch.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 65.0.3325.181-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 28 09:21:18 2018
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg'
   
'/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2018-02-09 (47 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Load-Avg-1min: 1.37
  Load-Processes-Running-Percent:   0.1%
  MachineType: Hewlett-Packard HP Pavilion dv8 Notebook PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=41d735c2-7b0b-4553-8de3-78761dcbc4f5 ro quiet splash vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to bionic on 2018-03-28 (0 days ago)
  dmi.bios.date: 05/31/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 7001
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 35.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.25:bd05/31/2010:svnHewlett-Packard:pnHPPaviliondv8NotebookPC:pvr04992224121000104:rvnHewlett-Packard:rn7001:rvr35.35:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv8 Notebook PC
  dmi.product.version: 04992224121000104
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.chromium-browser.customizations.00-example: [deleted]
  modified.conffile..etc.chromium-browser.default: [deleted]
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1761762] Re: Xorg crashed with SIGABRT in RRProviderAutoConfigGpuScreen()

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

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 #1724901, 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/1761762/+attachment/5104081/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1724901
   Xorg crashed with SIGABRT in RRProviderAutoConfigGpuScreen()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  Xorg crashed with SIGABRT in RRProviderAutoConfigGpuScreen()

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

Bug description:
  problems on nouveau and nvidia drivers with Kernel Linux 4.15.0-14 and
  4.15.0-15 .

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu3 [modified: 
usr/lib/xorg/modules/extensions/libglx.so]
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: 
'/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.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Apr  6 08:43:00 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.48: added
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0798]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798]
  InstallationDate: Installed on 2018-01-12 (84 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111)
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=0d9aae60-fff7-454c-8598-0f46d126827f ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: nvidia-graphics-drivers
  StacktraceTop:
   RRProviderAutoConfigGpuScreen ()
   InitOutput ()
   ?? ()
   __libc_start_main (main=0x56063f194b50, argc=12, argv=0x7ffe37dcc118, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffe37dcc108) at ../csu/libc-start.c:310
   _start ()
  Title: Xorg crashed with SIGABRT in RRProviderAutoConfigGpuScreen()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 08/17/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 0P84C9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd08/17/2017:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx

[Desktop-packages] [Bug 1682455] Re: thunderbird not available in GNOME Software

2018-04-06 Thread Will Cooke

** Tags added: rls-bb-incoming

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

Title:
  thunderbird not available in GNOME Software

Status in firefox package in Ubuntu:
  Triaged
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Ubuntu's firefox and thunderbird ship their app icons in
  /usr/share/pixmaps/

  Please move them to /usr/share/icons/hicolor/*/apps/ instead so that
  these apps can be shown as available for install in GNOME Software.

  References
  --
  http://appstream.ubuntu.com/bionic/main/issues/thunderbird.html
  http://appstream.ubuntu.com/bionic/main/issues/firefox.html
  
https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-icon

  Original Report
  ---
  I am filing this against Thunderbird, even though it also concerns another 
package (GNOME Software).

  Essentially, using a freshly installed Ubuntu GNOME 17.04, Thunderbird
  is not available in GNOME Software (the default software app for this
  flavour). You cannot find it via search or the packages browser.

  The only way to install it is via apt-get and even then it doesn't
  show in Software (see attached picture).

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

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

[Desktop-packages] [Bug 1759590] Re: Chromium-Browser Won't Sustain My Profile

Olivier, thanks for the suggestions, but so far nothing has worked.

I've gone to this extreme to completely remove Chromium:

sudo rm -rf /home/username/.config/chromium ; sudo rm -rf
/home/username/.cache/chromium ; sudo rm -rf /usr/lib/chromium-browser ;
sudo rm -rf /etc/chromium-browser ; sudo rm -rf /usr/share/app-
install/desktop/chromium* ; sudo rm -rf /usr/lib/x86_64-linux-gnu/oxide-
qt/chromium* ; sudo apt-get remove chromium-browser chit doesn't
remember any saved passwords, history, bookmarks, or form data.romium-
codecs-ffmpeg-extra

After reinstalling, it only remembers me for one session. After that I
have to log into every website like I'd never used Chromium before; it
doesn't remember any saved passwords, history, bookmarks, or form data.

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

Title:
  Chromium-Browser Won't Sustain My Profile

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Each time I launch chromium-browser it forgets all previous sessions;
  it doesn't remember any saved passwords, history, bookmarks, or form
  data.

  It seem like it is creating a brand new profile each launch.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 65.0.3325.181-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 28 09:21:18 2018
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg'
   
'/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2018-02-09 (47 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Load-Avg-1min: 1.37
  Load-Processes-Running-Percent:   0.1%
  MachineType: Hewlett-Packard HP Pavilion dv8 Notebook PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=41d735c2-7b0b-4553-8de3-78761dcbc4f5 ro quiet splash vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to bionic on 2018-03-28 (0 days ago)
  dmi.bios.date: 05/31/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 7001
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 35.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.25:bd05/31/2010:svnHewlett-Packard:pnHPPaviliondv8NotebookPC:pvr04992224121000104:rvnHewlett-Packard:rn7001:rvr35.35:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv8 Notebook PC
  dmi.product.version: 04992224121000104
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.chromium-browser.customizations.00-example: [deleted]
  modified.conffile..etc.chromium-browser.default: [deleted]
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1761663] Re: Attached encrypted USB drive gets stuck in password prompt

2018-04-06 Thread Cerin

I use my laptop for development for systems that are standardized on
16.04, so I don't have the option to upgrade at the moment.

Also, I don't think this problem has been in 16.04 for very long. I've
attached encrypted drives dozens of times over the last couple years,
and have never had this problem. It's only after the last batch of
package updates in the last month that now it locks me out.

Do you know what package is responsible for the password prompt shown
upon mounting encrypted USB hard drives?

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

Title:
  Attached encrypted USB drive gets stuck in password prompt

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I used the standard tools in Ubuntu 16 to format and encrypt a large
  USB hard drive for storing secure backups to. I then used that drive
  with the standard "Backups" tool to capture periodic backups.

  My hard drive recently died, forcing me to re-install Ubuntu 16. The
  re-install went well, but when I tried to attach the drive to restore
  my personal files, a modal appeared, prompting me to enter my
  password.

  So I did. And then it prompted me again. I thought I'd mistyped my
  password, so I re-entered it, making sure my caplocks or numlock key
  weren't on, but again, it prompted me. After each prompt, the full-
  screen modal darkened the background until after a dozen attempts, my
  background was almost completely black. I suspect what's going on is
  something's trying to access the encrypted disk while I'm typing in
  the password, and each access is triggering another prompt,
  effectively locking me out of the system because it's impossible for
  me to enter a nearly infinite series of prompts.

  This bug is a huge problem for two reasons:

  1. it locks you out of your computer
  2. it prevents you from accessing secure storage and restoring your system

  I managed to partially workaround #1 by switching to a terminal and
  running `export DISPLAY=:0; gnome-shell --replace`. That caused Gnome
  to reload, which minimized the modal program, allowing me to kill it
  in the app thumbnail view.

  However, that's a huge hassle, and I'm still unable to access any data
  on encrypted USB drives, even when I enter the password correctly.
  Please advise.

  I don't know exactly what component to file this bug under, so I chose
  "gnome-shell". Please re-tag it if this is incorrect.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.5-0ubuntu0.3
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Apr  6 00:26:33 2018
  DisplayManager: lightdm
  InstallationDate: Installed on 2018-03-23 (13 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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: Out of the box, Ubuntu Bionic offers only insecure VPN option

2018-04-06 Thread Robie Basak

Thank you for filing this bug. I agree that it's worth asking the
desktop team to consider the default set of VPN plugins available by
default from time to time.

> In fact, most major desktop OSes have removed PPTP altogether because
it's insecure...

I'm commenting because I'd like to point out that I don't think this is
a reasonable justification. Ubuntu is *user focused*. Users don't
usually have the option of choosing their VPN technology since the
server end is normally configured by someone else. Ideally I think
Ubuntu should make sure that the majority of users can connect most
easily to the VPN they already have. We should keep Ubuntu useful to the
majority of Ubuntu users by default. This should be our primary
motivator for any decision.

A secondary effect is that those in control of choosing VPN technologies
might be influenced by the availability of clients in Ubuntu as default.
It might be reasonable for us to change what we ship by default based on
this effect, but it should only be secondary to the primary cause of
shipping something useful to users.

Inconveniencing users by removing the availability of a component by
default because we think they should be using something different is not
something I think is appropriate for the Ubuntu project. I don't think
it's appropriate for us to be hostile to our users in this manner.
Ubuntu has traditionally done the exact opposite - for example by taking
the pragmatic stance in making available non-free codecs and drivers
instead of deliberately making it difficult for users who have already
made non-free hardware and codec choices such as some other
distributions.

If PPTP support is removed by default for policy (rather than technical
or maintenance) reasons, I think it be done on the basis that Ubuntu VPN
users don't need and won't miss PPTP support and not just because we
think that the users are doing it wrong.

I have no objection to bringing in other plugins for default (eg.
openvpn sounds like a great idea) but of course that is subject to a
team being prepared to commit the time to maintain that.

(I'm just an unconnected Ubuntu developer and have no say in any final
decision)

-- 
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:
  Out of the box, Ubuntu Bionic offers only insecure VPN option

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager-openvpn package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

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 1759590] Re: Chromium-Browser Won't Sustain My Profile

I wish I could edit my last comment; it is some how corrupted. Here it
is again (hopefully as intended)

I've gone to this extreme to completely remove Chromium:

sudo rm -rf /home/username/.config/chromium ; sudo rm -rf
/home/username/.cache/chromium ; sudo rm -rf /usr/lib/chromium-browser ;
sudo rm -rf /etc/chromium-browser ; sudo rm -rf /usr/share/app-
install/desktop/chromium* ; sudo rm -rf /usr/lib/x86_64-linux-gnu/oxide-
qt/chromium* ; sudo apt-get remove chromium-browser chromium-codecs-
ffmpeg-extra

After reinstalling, it only remembers me for one session. After that I
have to log into every website like I'd never used Chromium before; it
doesn't remember any saved passwords, history, bookmarks, or form data.

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

Title:
  Chromium-Browser Won't Sustain My Profile

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Each time I launch chromium-browser it forgets all previous sessions;
  it doesn't remember any saved passwords, history, bookmarks, or form
  data.

  It seem like it is creating a brand new profile each launch.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 65.0.3325.181-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 28 09:21:18 2018
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg'
   
'/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2018-02-09 (47 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Load-Avg-1min: 1.37
  Load-Processes-Running-Percent:   0.1%
  MachineType: Hewlett-Packard HP Pavilion dv8 Notebook PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=41d735c2-7b0b-4553-8de3-78761dcbc4f5 ro quiet splash vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to bionic on 2018-03-28 (0 days ago)
  dmi.bios.date: 05/31/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 7001
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 35.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.25:bd05/31/2010:svnHewlett-Packard:pnHPPaviliondv8NotebookPC:pvr04992224121000104:rvnHewlett-Packard:rn7001:rvr35.35:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv8 Notebook PC
  dmi.product.version: 04992224121000104
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.chromium-browser.customizations.00-example: [deleted]
  modified.conffile..etc.chromium-browser.default: [deleted]
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 124406] Re: Keyboard keys get stuck and repeat

I'm sorry for flooding this thread, but I have more experience to share.

After another reboot in "clocksource=jiffies" mode, I saw that 1 OS
second passes in real 0.5 seconds. But the rest of the system was pretty
stable. Keyboard auto-repeat was twice as fast, but did not get
triggered inadvertently.

I did another reboot in "clocksource=jiffies" mode and opened the online clock 
application. Initially the clock speed seemed normal. After 20-30 seconds it 
became twice as fast.
Then from the console, I started an application with an infinite loop therein. 
That made the clock seconds turn very very fast. Probably CPU speed has 
influence here.

Good news is that when I changed the boot option to "clocksource=tsc", I
got stable results even after a few reboots. Seconds seem to pass as
fast as they should be.

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

Title:
  Keyboard keys get stuck and repeat

Status in GNU Emacs:
  Invalid
Status in Linux:
  Confirmed
Status in X.Org X server:
  In Progress
Status in linux package in Ubuntu:
  Won't Fix
Status in xorg-server package in Ubuntu:
  Won't Fix
Status in linux source package in Jaunty:
  Won't Fix
Status in xorg-server source package in Jaunty:
  Invalid
Status in Gentoo Linux:
  New

Bug description:
  Keyboard keys such as the arrows, Alt-F4, PageUp/PageDown, etc. often
  get 'stuck' and continue being 'clicked' even after they are
  physically released. For example when clicking Alt-F4, sometimes it
  gets stuck so all the windows are closed instead of just one.

  My configuration is Feisty + Xgl + Compiz Fusion. My previous
  configuration was Edgy + Xgl + Beryl, where this didn't happen. Others
  have reported the same problem without using either Xgl or Compiz.

  The keyboard itself isn't the problem. When dual-booting to Windows,
  everything works fine. Also, the problem happens with two different
  keyboards (internal laptop, external USB).

  My best guess is that the problem occurs at time of high system load.
  Somehow during these times the key-release signal gets lost and the
  key-press is repeated indefinitely. This happens more often with
  Compiz configurations because Compiz tends to increase system load. It
  also happens more often with power-hungry apps like Firefox and
  Acrobat Reader for similar reasons.

  PS: When the keys would repeat all input devices would be locked up.
  ie. mouse won't move, clicks don't do anything, keyboard presses don't
  register. Then when it becomes unstuck, the mouse moves around and
  everything. Hope this helps.

  See also this forum thread for other people with the same problem:
  http://ubuntuforums.org/showthread.php?t=432057

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

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

[Desktop-packages] [Bug 1755456] Re: [ffe] Optional recording/sending of installer details to help improving Ubuntu

This bug was fixed in the package gnome-initial-setup - 3.28.0-2ubuntu1

---
gnome-initial-setup (3.28.0-2ubuntu1) bionic; urgency=medium

  * debian/patches/0001-Add-Ubuntu-mode-with-special-pages.patch:
  * debian/ubuntu-changes.png:
- Show Ubuntu welcome pages (LP: #1755456)
  * debian/control:
- Build-Depends on libsnapd-glib-dev, libsoupd2.4-dev,
  libsysmetrics-dev
- Enable langpack usage

 -- Robert Ancell   Fri, 06 Apr 2018
09:52:39 +1200

** Changed in: gnome-initial-setup (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  [ffe] Optional recording/sending of installer details to help
  improving Ubuntu

Status in gnome-initial-setup package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged

Bug description:
  The topic has been discussed on the ubuntu-devel@ list, see
  https://lists.ubuntu.com/archives/ubuntu-
  devel/2018-February/040139.html

  The feature has different parts
  - the installer is going to record some informations about the installation 
details & options selected
  - the session is going to have a command line/GUI part that let user 
review those informations
  - the desktop settings should have a control to change the option later on

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

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

[Desktop-packages] [Bug 1735929] Re: security problems with incorrect permissions for ubuntu 17.10

2018-04-06 Thread Sebastien Bacher

Change attached to the upstream bug

** Changed in: gnome-session (Ubuntu Bionic)
   Status: Triaged => In Progress

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

Title:
  security problems with incorrect permissions for ubuntu 17.10

Status in dconf:
  Confirmed
Status in gnome-session:
  Confirmed
Status in d-conf package in Ubuntu:
  Fix Released
Status in dconf package in Ubuntu:
  Triaged
Status in gnome-session package in Ubuntu:
  In Progress
Status in session-migration package in Ubuntu:
  Fix Released
Status in d-conf source package in Bionic:
  Fix Released
Status in dconf source package in Bionic:
  Triaged
Status in gnome-session source package in Bionic:
  In Progress
Status in session-migration source package in Bionic:
  Fix Released

Bug description:
  The release of Ubuntu you are using (lsb_release -rd):
  Description:  Ubuntu 17.10
  Release:  17.10

  This is a fresh installation of Ubuntu 17.10 from the mini.iso.
  I select only default options + [Ubuntu Desktop] installation.

  What you expected to happen:
  My home folder contains the following folders with correct and safe 
permissions after the first login:
  drwx-- 11 user user 4096 Dec  2 17:40 .config
  drwx--  3 user user 4096 Dec  2 17:39 .local

  What happened instead:
  I received these folders after the first login:
  drwxr-xr-x 11 user user 4096 Dec  2 17:40 .config
  drwxr-xr-x  3 user user 4096 Dec  2 17:39 .local
  It is not safe. Any user can access to my .config folders and read for 
example my mail databases

  I'm trying to create a new user...:
  sudo useradd -m user2
  sudo passwd user2
  ... and login then.
  It has the same problem:
  drwxr-xr-x 10 user2 user2 4096 Dec  2 19:44 .config
  drwxr-xr-x  3 user2 user2 4096 Dec  2 19:44 .local

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

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

[Desktop-packages] [Bug 1756547] Re: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d

2018-04-06 Thread Gunnar Hjalmarsson

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

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  LP refuses to import plural strings where e.g. msgstr[0] entries in PO
  file miss %d

Status in Launchpad itself:
  New
Status in Ubuntu Translations:
  In Progress
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  Some strings of GNOME Shell are untranslated in the Czech translation
  on Ubuntu 18.04 although they are translated upstream and when I try
  to manually translate them on launchpad, I get this error: "number of
  format specifications in 'msgid_plural' and 'msgstr[0]' does not
  match".

  The bad strings are:
  %d minute ago
  %d minutes ago

  %d hour ago
  %d hours ago

  %d week ago
  %d weeks ago

  %d month ago
  %d months ago

  %d year ago
  %d years ago

  They seem to be correct, but they are not accepted for some reason.

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

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

[Desktop-packages] [Bug 1756547] Re: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d

** Branch linked: lp:~gunnarhj/gnome-shell/gettext-workaround

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

Title:
  LP refuses to import plural strings where e.g. msgstr[0] entries in PO
  file miss %d

Status in Launchpad itself:
  New
Status in Ubuntu Translations:
  In Progress
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  Some strings of GNOME Shell are untranslated in the Czech translation
  on Ubuntu 18.04 although they are translated upstream and when I try
  to manually translate them on launchpad, I get this error: "number of
  format specifications in 'msgid_plural' and 'msgstr[0]' does not
  match".

  The bad strings are:
  %d minute ago
  %d minutes ago

  %d hour ago
  %d hours ago

  %d week ago
  %d weeks ago

  %d month ago
  %d months ago

  %d year ago
  %d years ago

  They seem to be correct, but they are not accepted for some reason.

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

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

[Desktop-packages] [Bug 1756720] Re: nm-applet stop showing vpn status

2018-04-06 Thread gpothier

I think I have the same issue. The VPN switches always appear in the Off
state, although the VPN is active. I think this might be part of a wider
issue, because there are several problems with the network applet:

- In the menu, the wired connections has no name or icon, there is just
a blank line with an arrow to expand it (see attached picture). Once
expanded, the wired connection options (profiles, turn off, configure)
are there.

- The connection icon does not appear in the top bar (see attached
picture)

- There is no WiFi connections line, although WiFi is up and running:

gpothier@tadzim3:~$ nmcli d
DEVICE  TYPE  STATE  CONNECTION 
eth3ethernet  connected  auto   
wlan0   wifi  connected  kyg
virbr0  bridgeconnected  virbr0 
lo  loopback  unmanaged  -- 
virbr0-nic  tun   unmanaged  -- 

- Restarting network manager causes the applet to completely misbehave.
For instance, after restarting NM, attempting to connect to a VPN
through the applet actually tries to connect to some random remembered
WiFi network. It is necessary to restart Gnome Shell for the applet to
resync with NM.



** Attachment added: "Screenshot from 2018-04-06 10-48-13.png"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1756720/+attachment/5104055/+files/Screenshot%20from%202018-04-06%2010-48-13.png

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

Title:
  nm-applet stop showing vpn status

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

Bug description:
  nm-applet status for vpn is not showing the vpn status (i.e. vpn is
  always off).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager-gnome 1.8.10-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 18 19:35:40 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-02-27 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180227)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.10.4   connected  started  full  enabled enabled  
disabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1761585] Re: ibus_bus_init does an unconditional call to chmod on $HOME/.config/ibus/bus

2018-04-06 Thread Olivier Tilloy

** Patch added: "xenial SRU debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1761585/+attachment/5104078/+files/lp1761585.debdiff

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

Title:
  ibus_bus_init does an unconditional call to chmod on
  $HOME/.config/ibus/bus

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  Fix Released

Bug description:
  This was spotted by jdstrand when running the chromium snap, which
  recently enabled ibus support (https://forum.snapcraft.io/t/cant-use-
  input-method-in-snap-apps/4712/12):

  audit[16919]: AVC apparmor="DENIED" operation="chmod"
  profile="snap.chromium.chromium" name="/home/osomon/.config/ibus/bus/"
  pid=16919 comm="chromium-browse" requested_mask="w" denied_mask="w"
  fsuid=1000 ouid=1000

  The code that calls chmod is in ibus_bus_init:

static void
ibus_bus_init (IBusBus *bus)
{
  gchar *path;
  […]
  path = g_path_get_dirname (ibus_get_socket_path ());
  g_mkdir_with_parents (path, 0700);
  g_chmod (path, 0700);
  […]
}

  This is rather harmless, but it could be avoided by checking first the
  file mode bits on that directory, and do the g_chmod call only if ≠
  0700.

  
  [Impact]

  Snaps that build on a xenial stack against libibus will trigger that apparmor 
denial, and even if actually harmless this will no doubt be reported as a 
problem by users who inspect the denials generated by their snaps.
  The patch (that is already upstream: 
https://github.com/ibus/ibus/commit/28d0c1d4bc47beb38995d84cc4bb1d539c08a070) 
fixes that by calling chmod conditionally, only if the file mode bits on the 
ibus socket path are ≠ 0700.

  
  [Test Case]

  Install the chromium snap from the stable channel (version
  65.0.3325.181, revision 274 as of this writing), and monitor the
  system journal for apparmor denials while launching it:

  journalctl -f | grep chmod

  Observe a denial similar to that one:

  audit[16919]: AVC apparmor="DENIED" operation="chmod"
  profile="snap.chromium.chromium" name="/home/osomon/.config/ibus/bus/"
  pid=16919 comm="chromium-browse" requested_mask="w" denied_mask="w"
  fsuid=1000 ouid=1000

  Now rebuild the chromium snap with the patched libibus (this can be
  done by downloading the .snap file, unpacking it with  unsquashfs,
  replacing the libibus files by unpacking the updated deb, then
  repacking the snap with `snapcraft pack`), install it and launch it
  while monitoring the system journal.

  Observe the denial on chmod is gone.

  
  [Regression Potential]

  This is a low-risk, self-contained change. It doesn't change the logic of 
ibus_bus_init.
  ibus input still working in apps (both debs and snaps) should be enough to 
prove that there are no regressions.


  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 5 21:55:30 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (642 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to bionic on 2018-01-29 (66 days ago)

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

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

[Desktop-packages] [Bug 1756720] Re: nm-applet stop showing vpn status

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

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

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

Title:
  nm-applet stop showing vpn status

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

Bug description:
  nm-applet status for vpn is not showing the vpn status (i.e. vpn is
  always off).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager-gnome 1.8.10-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 18 19:35:40 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-02-27 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180227)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.10.4   connected  started  full  enabled enabled  
disabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1761585] Re: ibus_bus_init does an unconditional call to chmod on $HOME/.config/ibus/bus

2018-04-06 Thread Olivier Tilloy

** Description changed:

  This was spotted by jdstrand when running the chromium snap, which
  recently enabled ibus support (https://forum.snapcraft.io/t/cant-use-
  input-method-in-snap-apps/4712/12):
  
  audit[16919]: AVC apparmor="DENIED" operation="chmod"
  profile="snap.chromium.chromium" name="/home/osomon/.config/ibus/bus/"
  pid=16919 comm="chromium-browse" requested_mask="w" denied_mask="w"
  fsuid=1000 ouid=1000
  
  The code that calls chmod is in ibus_bus_init:
  
static void
ibus_bus_init (IBusBus *bus)
{
  gchar *path;
  […]
  path = g_path_get_dirname (ibus_get_socket_path ());
  g_mkdir_with_parents (path, 0700);
  g_chmod (path, 0700);
  […]
}
  
- This could be avoided by checking first the file mode bits on that
- directory, and do the g_chmod call only if ≠ 0700.
+ This is rather harmless, but it could be avoided by checking first the
+ file mode bits on that directory, and do the g_chmod call only if ≠
+ 0700.
+ 
+ 
+ [Impact]
+ 
+ Snaps that build on a xenial stack against libibus will trigger that apparmor 
denial, and even if actually harmless this will no doubt be reported as a 
problem by users who inspect the denials generated by their snaps.
+ The patch (that is already upstream: 
https://github.com/ibus/ibus/commit/28d0c1d4bc47beb38995d84cc4bb1d539c08a070) 
fixes that by calling chmod conditionally, only if the file mode bits on the 
ibus socket path are ≠ 0700.
+ 
+ 
+ [Test Case]
+ 
+ Install the chromium snap from the stable channel (version
+ 65.0.3325.181, revision 274 as of this writing), and monitor the system
+ journal for apparmor denials while launching it:
+ 
+ journalctl -f | grep chmod
+ 
+ Observe a denial similar to that one:
+ 
+ audit[16919]: AVC apparmor="DENIED" operation="chmod"
+ profile="snap.chromium.chromium" name="/home/osomon/.config/ibus/bus/"
+ pid=16919 comm="chromium-browse" requested_mask="w" denied_mask="w"
+ fsuid=1000 ouid=1000
+ 
+ Now rebuild the chromium snap with the patched libibus (this can be done
+ by downloading the .snap file, unpacking it with  unsquashfs, replacing
+ the libibus files by unpacking the updated deb, then repacking the snap
+ with `snapcraft pack`), install it and launch it while monitoring the
+ system journal.
+ 
+ Observe the denial on chmod is gone.
+ 
+ 
+ [Regression Potential]
+ 
+ This is a low-risk, self-contained change. It doesn't change the logic of 
ibus_bus_init.
+ ibus input still working in apps (both debs and snaps) should be enough to 
prove that there are no regressions.
+ 
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
- Date: Thu Apr  5 21:55:30 2018
+ Date: Thu Apr 5 21:55:30 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (642 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to bionic on 2018-01-29 (66 days ago)

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

Title:
  ibus_bus_init does an unconditional call to chmod on
  $HOME/.config/ibus/bus

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  Fix Released

Bug description:
  This was spotted by jdstrand when running the chromium snap, which
  recently enabled ibus support (https://forum.snapcraft.io/t/cant-use-
  input-method-in-snap-apps/4712/12):

  audit[16919]: AVC apparmor="DENIED" operation="chmod"
  profile="snap.chromium.chromium" name="/home/osomon/.config/ibus/bus/"
  pid=16919 comm="chromium-browse" requested_mask="w" denied_mask="w"
  fsuid=1000 ouid=1000

  The code that calls chmod is in ibus_bus_init:

static void
ibus_bus_init (IBusBus *bus)
{
  gchar *path;
  […]
  path = g_path_get_dirname (ibus_get_socket_path ());
  g_mkdir_with_parents (path, 0700);
  g_chmod (path, 0700);
  […]
}

  This is rather harmless, but it could be avoided by checking first the
  file mode bits on that directory, and do the g_chmod call only if ≠
  0700.

  
  [Impact]

  Snaps that build on a xenial stack against libibus will trigger that apparmor 
denial, and even if actually harmless this will no doubt be reported as a 
problem by users who inspect the denials generated by their snaps.
  The patch (that is already upstream: 
https://github.com/ibus/ibus/commit/28d0c1d4bc47beb38995d84cc4bb1d539c08a070) 
fixes that by calling chmod conditionally, only if the file mode bits on the 
ibus socket path are ≠ 0700.

  
  [Test Case]

  Install the chromium snap from the stable channel (version
  65.0.3325.181, revision 274 as of this

[Desktop-packages] [Bug 1759538] Re: [ffe] Install bolt by default for thunderbolt devices support

This bug was fixed in the package gnome-shell - 3.28.0-0ubuntu3

---
gnome-shell (3.28.0-0ubuntu3) bionic; urgency=medium

  * Recommend bolt for Thunderbolt 3 support (LP: #1759538)

 -- Jeremy Bicha   Wed, 04 Apr 2018 10:04:50 -0400

** Changed in: gnome-shell (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [ffe] Install bolt by default for thunderbolt devices support

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  Bolt is a new component that is handling the authentification of
  thunderbolt-3 devices. Without a way to authentificate the devices
  those can't be used so it's sort of an important hardware enablement
  type of feature.

  The MIR for bolt has been approved as bug #1752056, including a
  security review.

  GNOME 3.28 (which is what we have in bionic) already include the UI
  side for the user prompting, the request is just to install the
  service by default so things work out of the box.

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

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

[Desktop-packages] [Bug 1761747] Re: 18.04 beta 2 ubuntu-software doesn't show firefox as installed

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

** This bug has been marked a duplicate of bug 1682455
   thunderbird not available in GNOME Software

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

Title:
  18.04 beta 2 ubuntu-software doesn't show firefox as installed

Status in gnome-software package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  om/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status

  
  ubuntu-software:
Installed: 3.28.0-0ubuntu7
Candidate: 3.28.0-0ubuntu7
Version table:
   *** 3.28.0-0ubuntu7 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://gb.archive.ubuntu.c500 http://gb.archive.ubuntu.c...

  Ubuntu Software does not see Firefox as installed (testing on minimal
  installation option). The package is not shown in the list of
  installed software and the Install button for Firefox snap package is
  available. Installing this leaves both versions on the system, while
  expected for an experienced  user this is not intuitive for a new
  Ubuntu user.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-software 3.28.0-0ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  6 14:11:43 2018
  InstallationDate: Installed on 2018-04-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu7
  PackageArchitecture: all
  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/1761747/+subscriptions

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

[Desktop-packages] [Bug 1730035] Re: Needs to depend on Python3

This bug was fixed in the package xorg - 1:7.7+19ubuntu6

---
xorg (1:7.7+19ubuntu6) bionic; urgency=medium

  * control: Add python3-apport to xserver-xorg depends due to the apport hook.
(LP: #1730035)
  * control: Depend on x11proto-dev instead of the old packages.

 -- Timo Aaltonen   Thu, 05 Apr 2018 15:47:54 +0300

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

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

Title:
  Needs to depend on Python3

Status in xorg package in Ubuntu:
  Fix Released
Status in xorg source package in Artful:
  New

Bug description:
  [Impact]

  source_xorg.py apport hook does not work if python3 is not installed.

  [Test case]

  install on a clean system, check that apport-bug xorg does the right
  thing.

  [Regression potential]

  Minimal, just adds the correct dependencies that were missing.

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

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

[Desktop-packages] [Bug 1761747] [NEW] 18.04 beta 2 ubuntu-software doesn't show firefox as installed

2018-04-06 Thread Anthony Jackson

Public bug reported:

$ lsb_release -rd
Description:Ubuntu Bionic Beaver (development branch)
Release:18.04
om/ubuntu bionic/main i386 Packages
100 /var/lib/dpkg/status


ubuntu-software:
  Installed: 3.28.0-0ubuntu7
  Candidate: 3.28.0-0ubuntu7
  Version table:
 *** 3.28.0-0ubuntu7 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://gb.archive.ubuntu.c500 http://gb.archive.ubuntu.c...

Ubuntu Software does not see Firefox as installed (testing on minimal
installation option). The package is not shown in the list of installed
software and the Install button for Firefox snap package is available.
Installing this leaves both versions on the system, while expected for
an experienced  user this is not intuitive for a new Ubuntu user.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-software 3.28.0-0ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  6 14:11:43 2018
InstallationDate: Installed on 2018-04-06 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.28.0-0ubuntu7
PackageArchitecture: all
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  18.04 beta 2 ubuntu-software doesn't show firefox as installed

Status in gnome-software package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  om/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status

  
  ubuntu-software:
Installed: 3.28.0-0ubuntu7
Candidate: 3.28.0-0ubuntu7
Version table:
   *** 3.28.0-0ubuntu7 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://gb.archive.ubuntu.c500 http://gb.archive.ubuntu.c...

  Ubuntu Software does not see Firefox as installed (testing on minimal
  installation option). The package is not shown in the list of
  installed software and the Install button for Firefox snap package is
  available. Installing this leaves both versions on the system, while
  expected for an experienced  user this is not intuitive for a new
  Ubuntu user.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-software 3.28.0-0ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  6 14:11:43 2018
  InstallationDate: Installed on 2018-04-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu7
  PackageArchitecture: all
  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/1761747/+subscriptions

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

[Desktop-packages] [Bug 1734034] Re: Cannot Use the Character U07AE on any Editor

2018-04-06 Thread Affan Juafar

To @vanvugt, i was able to print the unicode in a window i coded on X11,
since X11 use libinput, i do not think its an issue with libinput.

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

Title:
  Cannot Use the Character U07AE on any Editor

Status in gnome-shell package in Ubuntu:
  New
Status in libinput package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  When using 'Dhivehi' as a keyboard input source, unicode character
  U07AE does not work when typing on LibreOffice or Gedit.

  The character is o on the keyboard. When this key is pressed nothing
  happens.

  All the other keys (characters) work fine except for the one that
  should be given by pressing o. Even Shift+o Works. I also tried
  exchanging the mapping of the unicode to another key. Even with that,
  the unicode character did not work.

  I have tried changing xkbd/symbol mapping to a different key. But that
  didn't help.

  With xev tool, the Unicode symbol is detected in the Terminal. But it
  does not work when tried elsewhere.

  I can insert the character by typing the Unicode, like Ctrl+Shift+
  U07AE. But to do this, I have to change language to English.

  This issue came up on Ubuntu 17.10; in 16.04 it works as it should.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  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
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 23 10:56:19 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2017-11-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=210cd2fd-b33b-4626-8740-2831bfcb4900 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  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/gnome-shell/+bug/1734034/+subscriptions

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

[Desktop-packages] [Bug 124406] Re: Keyboard keys get stuck and repeat

WWweeel,IIIii
booottteeedd   aaaggaaiiin
ih clocksource=jiffies,,,   aaanndd
ttthhhee ise   ggot
uuuccc worrss  ttiiis
tiiee


ssooo clocksource=jiffiesddooes oot
smmmtob  a
ddeffiiiiitttvvve
sooutttiiooo

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

Title:
  Keyboard keys get stuck and repeat

Status in GNU Emacs:
  Invalid
Status in Linux:
  Confirmed
Status in X.Org X server:
  In Progress
Status in linux package in Ubuntu:
  Won't Fix
Status in xorg-server package in Ubuntu:
  Won't Fix
Status in linux source package in Jaunty:
  Won't Fix
Status in xorg-server source package in Jaunty:
  Invalid
Status in Gentoo Linux:
  New

Bug description:
  Keyboard keys such as the arrows, Alt-F4, PageUp/PageDown, etc. often
  get 'stuck' and continue being 'clicked' even after they are
  physically released. For example when clicking Alt-F4, sometimes it
  gets stuck so all the windows are closed instead of just one.

  My configuration is Feisty + Xgl + Compiz Fusion. My previous
  configuration was Edgy + Xgl + Beryl, where this didn't happen. Others
  have reported the same problem without using either Xgl or Compiz.

  The keyboard itself isn't the problem. When dual-booting to Windows,
  everything works fine. Also, the problem happens with two different
  keyboards (internal laptop, external USB).

  My best guess is that the problem occurs at time of high system load.
  Somehow during these times the key-release signal gets lost and the
  key-press is repeated indefinitely. This happens more often with
  Compiz configurations because Compiz tends to increase system load. It
  also happens more often with power-hungry apps like Firefox and
  Acrobat Reader for similar reasons.

  PS: When the keys would repeat all input devices would be locked up.
  ie. mouse won't move, clicks don't do anything, keyboard presses don't
  register. Then when it becomes unstuck, the mouse moves around and
  everything. Hope this helps.

  See also this forum thread for other people with the same problem:
  http://ubuntuforums.org/showthread.php?t=432057

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

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

[Desktop-packages] [Bug 1761743] [NEW] Xorg crash, session logout after screen turned off

2018-04-06 Thread dreasty

Public bug reported:

Session logout after screen turned off and also logout during work

May be related to Bug 1721428

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  6 15:52:02 2018
DistUpgraded: 2018-04-02 12:05:40,293 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 v4l2loopback, 0.10.0, 4.13.0-37-generic, x86_64: installed
 v4l2loopback, 0.10.0, 4.15.0-13-generic, x86_64: installed
 virtualbox, 5.2.8, 4.13.0-37-generic, x86_64: installed
 virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 510 [8086:1902] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 510 
[1462:7996]
InstallationDate: Installed on 2017-03-02 (400 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1a2c:2124 China Resource Semico Co., Ltd 
 Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: MSI MS-7996
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=fa8af88c-68e6-4582-872e-a2c53edcbf97 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to bionic on 2018-04-02 (4 days ago)
dmi.bios.date: 07/27/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.80
dmi.board.asset.tag: Default string
dmi.board.name: H110M PRO-VD (MS-7996)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd07/27/2016:svnMSI:pnMS-7996:pvr1.0:rvnMSI:rnH110MPRO-VD(MS-7996):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.family: Default string
dmi.product.name: MS-7996
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


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

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

Title:
  Xorg crash, session logout after screen turned off

Status in xorg package in Ubuntu:
  New

Bug description:
  Session logout after screen turned off and also logout during work

  May be related to Bug 1721428

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  6 15:52:02 2018
  DistUpgraded: 2018-04-02 12:05:40,293 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback, 0.10.0, 4.13.0-37-generic, x86_64: installed
   v4l2loopback, 0.10.0, 4.15.0-13-generic, x86_64: installed
   virtualbox, 5.2.8, 4.13.0-37-generic, x86_64: installed
   virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 510 [8086:1902] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 510 
[1462:7996]
  InstallationDate: Installed on 2017-03-02 (400 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1a2c:2124 China Resource Semico Co., Ltd 
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID

[Desktop-packages] [Bug 1761745] [NEW] privacy URL is available in /etc/os-release

2018-04-06 Thread Iain Lane

Public bug reported:

This one is quite minor, but there is a canonical location for the
privacy policy URL

PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies
/privacy-policy"

which I think ought to be used.

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

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

Title:
  privacy URL is available in /etc/os-release

Status in gnome-initial-setup package in Ubuntu:
  New

Bug description:
  This one is quite minor, but there is a canonical location for the
  privacy policy URL

  PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies
  /privacy-policy"

  which I think ought to be used.

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

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

[Desktop-packages] [Bug 1761741] [NEW] Simple-scan snap throws relocation error

2018-04-06 Thread LukeWH

Public bug reported:

OS: Solus 3.999
Snap version: 3.26.0
Expected: Application to launch
What happened: The following error
/snap/simple-scan/13/usr/bin/simple-scan: relocation error: /usr/lib/libc.so.6: 
symbol __tunable_get_val, version GLIBC_PRIVATE not defined in file 
ld-linux-x86-64.so.2 with link time reference

** Affects: simple-scan (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Simple-scan snap throws relocation error

Status in simple-scan package in Ubuntu:
  New

Bug description:
  OS: Solus 3.999
  Snap version: 3.26.0
  Expected: Application to launch
  What happened: The following error
  /snap/simple-scan/13/usr/bin/simple-scan: relocation error: 
/usr/lib/libc.so.6: symbol __tunable_get_val, version GLIBC_PRIVATE not defined 
in file ld-linux-x86-64.so.2 with link time reference

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

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

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

2018-04-06 Thread Ahmet Aksoy

https://gist.github.com/Parduk/54ab53a12ec063ae6c3bc945f326130b

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

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

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

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

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

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

[Desktop-packages] [Bug 1760308] Re: Unicode input not working on Bionic with CTRL-SHIFT-U

This bug was fixed in the package ibus - 1.5.17-3ubuntu3

---
ibus (1.5.17-3ubuntu3) bionic; urgency=medium

  * debian/patches/ubuntu-conditional-chmod.patch: backport an upstream commit
to make a call to chmod conditional, to avoid apparmor denials for confined
apps (e.g. snaps) that use libibus (LP: #1761585)

ibus (1.5.17-3ubuntu2) bionic; urgency=medium

  * debian/patches/ubuntu-unicode-keybinding.patch:
- use a change proposed/rejected upstream to restore ctrl-shift-u,
  upstream consider it superseeded by the emoji selector but that has
  no keybinding in our ibus version and is not an exact replacement
  (lp: #1760308)

 -- Olivier Tilloy   Fri, 06 Apr 2018
11:04:22 +0200

** Changed in: ibus (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Unicode input not working on Bionic with CTRL-SHIFT-U

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  Fix Released
Status in ibus source package in Bionic:
  Fix Released

Bug description:
  I need to enter Unicode with Unicode escape codes and the Ubuntu
  prescribed way is to use CTRL-SHIFT-U and then enter some numbers to
  input.  This doesn't do anything in the Ubuntu Bionic beta.

  Potentially related the ALT-TAB window switching is delayed in
  recognizing the occurrence of the keys being pressed such that I have
  to hold ALT-TAB instead of quickly hitting both simultaneously.

  This is from a system that was upgraded from a previous Ubuntu version
  without any issues.

  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  The "Affects" package may not be accurate as I don't know what the
  cause application is for this.

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

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

[Desktop-packages] [Bug 1752056] Re: [MIR] bolt

2018-04-06 Thread Matthias Klose

Override component to main
bolt 0.2-0ubuntu1 in bionic: universe/admin -> main
bolt 0.2-0ubuntu1 in bionic amd64: universe/admin/optional/100% -> main
bolt 0.2-0ubuntu1 in bionic arm64: universe/admin/optional/100% -> main
bolt 0.2-0ubuntu1 in bionic armhf: universe/admin/optional/100% -> main
bolt 0.2-0ubuntu1 in bionic i386: universe/admin/optional/100% -> main
bolt 0.2-0ubuntu1 in bionic ppc64el: universe/admin/optional/100% -> main
bolt 0.2-0ubuntu1 in bionic s390x: universe/admin/optional/100% -> main
7 publications overridden.


** Changed in: bolt (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [MIR] bolt

Status in bolt package in Ubuntu:
  Fix Released

Bug description:
  * Availability

  Builds on all supported architectures in Ubuntu.
  Not in Debian yet.

  * Rationale

  Required to authorize thunderbolt 3 devices

  * Security

  The project is recent and has no known security issue, it should
  probably get a security team review though since it's a system service
  dealing with a security feature

  * Quality assurance

  - the desktop-packages team is going to be subscribed once the package is 
NEWed
  - the package is using current packaging standards
  - tests are enabled in the package build and successful

  * Dependendies

  They are already in main (glib, polkit, libudev)

  * Standards compliance

  Using current standard and dh packaging

  * Maintainance

  Upstream is active and the desktop team is going to look after the
  package in ubuntu

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

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

[Desktop-packages] [Bug 1761585] Re: ibus_bus_init does an unconditional call to chmod on $HOME/.config/ibus/bus

This bug was fixed in the package ibus - 1.5.17-3ubuntu3

---
ibus (1.5.17-3ubuntu3) bionic; urgency=medium

  * debian/patches/ubuntu-conditional-chmod.patch: backport an upstream commit
to make a call to chmod conditional, to avoid apparmor denials for confined
apps (e.g. snaps) that use libibus (LP: #1761585)

ibus (1.5.17-3ubuntu2) bionic; urgency=medium

  * debian/patches/ubuntu-unicode-keybinding.patch:
- use a change proposed/rejected upstream to restore ctrl-shift-u,
  upstream consider it superseeded by the emoji selector but that has
  no keybinding in our ibus version and is not an exact replacement
  (lp: #1760308)

 -- Olivier Tilloy   Fri, 06 Apr 2018
11:04:22 +0200

** Changed in: ibus (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  ibus_bus_init does an unconditional call to chmod on
  $HOME/.config/ibus/bus

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  Fix Released

Bug description:
  This was spotted by jdstrand when running the chromium snap, which
  recently enabled ibus support (https://forum.snapcraft.io/t/cant-use-
  input-method-in-snap-apps/4712/12):

  audit[16919]: AVC apparmor="DENIED" operation="chmod"
  profile="snap.chromium.chromium" name="/home/osomon/.config/ibus/bus/"
  pid=16919 comm="chromium-browse" requested_mask="w" denied_mask="w"
  fsuid=1000 ouid=1000

  The code that calls chmod is in ibus_bus_init:

static void
ibus_bus_init (IBusBus *bus)
{
  gchar *path;
  […]
  path = g_path_get_dirname (ibus_get_socket_path ());
  g_mkdir_with_parents (path, 0700);
  g_chmod (path, 0700);
  […]
}

  This could be avoided by checking first the file mode bits on that
  directory, and do the g_chmod call only if ≠ 0700.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  5 21:55:30 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (642 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to bionic on 2018-01-29 (66 days ago)

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

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

[Desktop-packages] [Bug 1761742] [NEW] Hangs for a few seconds when entering the last page when the metrics server is unavailable

2018-04-06 Thread Iain Lane

Public bug reported:

This server doesn't work at the minute.

When advancing to the last page of the wizard, the following message is
displayed:

** (gnome-initial-setup:803): WARNING **: 13:44:36.643: Failed to send
decline: data were not delivered successfully to metrics server:
couldn't send post http request: Post
https://metrics.ubuntu.com/ubuntu/desktop/18.04: dial tcp
92.242.132.16:443: i/o timeout

and there is a delay of a few seconds displaying the page.

I suppose the calls to sysmetrics to send the report/decline should be
done asynchronously. It's probably not a big problem if a few people
manage to quit before the submission is finished, but if it is then
there would need to be a way for the quit button to wait for all save
calls to finish their async work.

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

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

Title:
  Hangs for a few seconds when entering the last page when the metrics
  server is unavailable

Status in gnome-initial-setup package in Ubuntu:
  New

Bug description:
  This server doesn't work at the minute.

  When advancing to the last page of the wizard, the following message
  is displayed:

  ** (gnome-initial-setup:803): WARNING **: 13:44:36.643: Failed to send
  decline: data were not delivered successfully to metrics server:
  couldn't send post http request: Post
  https://metrics.ubuntu.com/ubuntu/desktop/18.04: dial tcp
  92.242.132.16:443: i/o timeout

  and there is a delay of a few seconds displaying the page.

  I suppose the calls to sysmetrics to send the report/decline should be
  done asynchronously. It's probably not a big problem if a few people
  manage to quit before the submission is finished, but if it is then
  there would need to be a way for the quit button to wait for all save
  calls to finish their async work.

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

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

[Desktop-packages] [Bug 1761739] [NEW] Submits a message to a remote server even when "No, don't send any info" is selected

2018-04-06 Thread Iain Lane

Public bug reported:

I tried out the new Ubuntu mode of gnome-initial setup. I went through
the steps, and picked "No, don't send any info". Then on the last page
the application froze for several seconds (a separate bug), and I saw
this message in the console.

** (gnome-initial-setup:30381): WARNING **: 12:52:10.585: Failed to send
decline: data were not delivered successfully to metrics server:
couldn't send post http request: Post
https://metrics.ubuntu.com/ubuntu/desktop/18.04: dial tcp
92.242.132.16:443: i/o timeout

We tried to send to a remote server even though I picked an option that
I intended to not report to you.

I think either we should not send this 'decline' message (this is my
preferred option), or we should make it reasonably clear that picking
"No" is going to ping home.

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


** Tags: rls-bb-incoming

** Tags added: rls-bb-incoming

** Description changed:

  I tried out the new Ubuntu mode of gnome-initial setup. I went through
  the steps, and picked "No, don't send any info". Then on the last page
  the application froze for several seconds (a separate bug), and I saw
  this message in the console.
  
  ** (gnome-initial-setup:30381): WARNING **: 12:52:10.585: Failed to send
  decline: data were not delivered successfully to metrics server:
  couldn't send post http request: Post
  https://metrics.ubuntu.com/ubuntu/desktop/18.04: dial tcp
  92.242.132.16:443: i/o timeout
  
  We tried to send to a remote server even though I picked an option that
  I intended to not report to you.
  
- I think either we should not send this 'decline' message, or we should
- make it reasonably clear that picking "No" is going to ping home.
+ I think either we should not send this 'decline' message (this is my
+ preferred option), or we should make it reasonably clear that picking
+ "No" is going to ping home.

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

Title:
  Submits a message to a remote server even when "No, don't send any
  info" is selected

Status in gnome-initial-setup package in Ubuntu:
  New

Bug description:
  I tried out the new Ubuntu mode of gnome-initial setup. I went through
  the steps, and picked "No, don't send any info". Then on the last page
  the application froze for several seconds (a separate bug), and I saw
  this message in the console.

  ** (gnome-initial-setup:30381): WARNING **: 12:52:10.585: Failed to
  send decline: data were not delivered successfully to metrics server:
  couldn't send post http request: Post
  https://metrics.ubuntu.com/ubuntu/desktop/18.04: dial tcp
  92.242.132.16:443: i/o timeout

  We tried to send to a remote server even though I picked an option
  that I intended to not report to you.

  I think either we should not send this 'decline' message (this is my
  preferred option), or we should make it reasonably clear that picking
  "No" is going to ping home.

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

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

[Desktop-packages] [Bug 124406] Re: Keyboard keys get stuck and repeat

I'm not sure whether it gives any information, but here is some output
from journalctl, where the bug happens (no "clocksource=jiffies" boot
option is used):

$ journalctl -k | grep clocksource

clocksource: refined-jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 7645519600211568 ns
clocksource: jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 
764504178510 ns
clocksource: Switched to clocksource refined-jiffies
clocksource: tsc: mask: 0x max_cycles: 0x2879c5f06f2, 
max_idle_ns: 440795220049 ns
clocksource: Switched to clocksource tsc
clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as 
unstable because the skew is too large:
clocksource:   'refined-jiffies' wd_now: fffedcd0 wd_last: 
fffedc58 mask: 
clocksource:   'tsc' cs_now: 13ccf176fe cs_last: 13299ba17d 
mask: 
kernel: tsc: Marking TSC unstable due to clocksource watchdog
kernel: clocksource: Switched to clocksource refined-jiffies

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

Title:
  Keyboard keys get stuck and repeat

Status in GNU Emacs:
  Invalid
Status in Linux:
  Confirmed
Status in X.Org X server:
  In Progress
Status in linux package in Ubuntu:
  Won't Fix
Status in xorg-server package in Ubuntu:
  Won't Fix
Status in linux source package in Jaunty:
  Won't Fix
Status in xorg-server source package in Jaunty:
  Invalid
Status in Gentoo Linux:
  New

Bug description:
  Keyboard keys such as the arrows, Alt-F4, PageUp/PageDown, etc. often
  get 'stuck' and continue being 'clicked' even after they are
  physically released. For example when clicking Alt-F4, sometimes it
  gets stuck so all the windows are closed instead of just one.

  My configuration is Feisty + Xgl + Compiz Fusion. My previous
  configuration was Edgy + Xgl + Beryl, where this didn't happen. Others
  have reported the same problem without using either Xgl or Compiz.

  The keyboard itself isn't the problem. When dual-booting to Windows,
  everything works fine. Also, the problem happens with two different
  keyboards (internal laptop, external USB).

  My best guess is that the problem occurs at time of high system load.
  Somehow during these times the key-release signal gets lost and the
  key-press is repeated indefinitely. This happens more often with
  Compiz configurations because Compiz tends to increase system load. It
  also happens more often with power-hungry apps like Firefox and
  Acrobat Reader for similar reasons.

  PS: When the keys would repeat all input devices would be locked up.
  ie. mouse won't move, clicks don't do anything, keyboard presses don't
  register. Then when it becomes unstuck, the mouse moves around and
  everything. Hope this helps.

  See also this forum thread for other people with the same problem:
  http://ubuntuforums.org/showthread.php?t=432057

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

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

[Desktop-packages] [Bug 124406] Re: Keyboard keys get stuck and repeat