[Desktop-packages] [Bug 2053110] Re: openjdk-8 402 fails to install in focal, jammy, mantic on i386

[Thorsten Glaser]

Hi Vladimir, rmadison says it’s fixed now and it’s available for i386
again, so I undid the workaround addition.

I’ve just uploaded 8u412, but I’ve re-enabled tests for Debian. Due to
your situation with the i386 packages, you’ll have to regenerate
d/control on noble to get the i386 exclusion (I hope I got the syntax,
with both architecture and profile specification, right).

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

Title:
  openjdk-8 402 fails to install in focal, jammy, mantic on i386

Status in java-atk-wrapper package in Ubuntu:
  Confirmed
Status in openjdk-8 package in Ubuntu:
  Fix Released
Status in openjdk-8 package in Debian:
  Fix Released

Bug description:
  openjdk-8 402 fails to install in focal, jammy, mantic on i386 due to
  dependency on java-atk-bridge.

  This dependency was introduced by dropping condition present in 392:
  --
    ifeq ($(derivative),Ubuntu)
  ifeq ($(DEB_HOST_ARCH),i386)
    ifeq (,$(filter $(distrel),precise trusty xenial bionic))
  with_bridge =
    endif
  endif
    endif
  --

  Note:
   java-atk-wrapper is present in noble on i386

  This is a regression introduced in 8u402-ga-2:

    * Restore M-A installability of focal/i386 package (LP#1916327)
  by adding xenial, bionic, focal, jammy to the list of releases
  built with the ATK bridge, but not enabling it by default;
  keep jessie on, stretch and sid and mantic/noble off the list:
  please report bugs for issues with the bridge, so sthibault
  can find, debug, fix them

  See LP: #1916327

  The alternative is to publish atk-wrapper for i386 in mantic, jammy
  and focal.

  Options:
   a) rollback the fix in Ubuntu
   b) publish atk-wrapper

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/2053110/+subscriptions


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

[Desktop-packages] [Bug 2053110] Re: openjdk-8 402 fails to install in focal, jammy, mantic on i386

[Thorsten Glaser]

(FWIW, last time I looked, it _did_ exist in noble)

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

Title:
  openjdk-8 402 fails to install in focal, jammy, mantic on i386

Status in java-atk-wrapper package in Ubuntu:
  Confirmed
Status in openjdk-8 package in Ubuntu:
  Fix Released
Status in openjdk-8 package in Debian:
  Fix Released

Bug description:
  openjdk-8 402 fails to install in focal, jammy, mantic on i386 due to
  dependency on java-atk-bridge.

  This dependency was introduced by dropping condition present in 392:
  --
    ifeq ($(derivative),Ubuntu)
  ifeq ($(DEB_HOST_ARCH),i386)
    ifeq (,$(filter $(distrel),precise trusty xenial bionic))
  with_bridge =
    endif
  endif
    endif
  --

  Note:
   java-atk-wrapper is present in noble on i386

  This is a regression introduced in 8u402-ga-2:

    * Restore M-A installability of focal/i386 package (LP#1916327)
  by adding xenial, bionic, focal, jammy to the list of releases
  built with the ATK bridge, but not enabling it by default;
  keep jessie on, stretch and sid and mantic/noble off the list:
  please report bugs for issues with the bridge, so sthibault
  can find, debug, fix them

  See LP: #1916327

  The alternative is to publish atk-wrapper for i386 in mantic, jammy
  and focal.

  Options:
   a) rollback the fix in Ubuntu
   b) publish atk-wrapper

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/2053110/+subscriptions


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

[Desktop-packages] [Bug 2053110] Re: openjdk-8 402 fails to install in focal, jammy, mantic on i386

[Thorsten Glaser]

oh ffs, it’s missing (again?) in noble, too?

I’ll add noble to the workaround for 8u412-ga-1, which I’m working on
r/n.

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

Title:
  openjdk-8 402 fails to install in focal, jammy, mantic on i386

Status in java-atk-wrapper package in Ubuntu:
  Confirmed
Status in openjdk-8 package in Ubuntu:
  Fix Released
Status in openjdk-8 package in Debian:
  Fix Released

Bug description:
  openjdk-8 402 fails to install in focal, jammy, mantic on i386 due to
  dependency on java-atk-bridge.

  This dependency was introduced by dropping condition present in 392:
  --
    ifeq ($(derivative),Ubuntu)
  ifeq ($(DEB_HOST_ARCH),i386)
    ifeq (,$(filter $(distrel),precise trusty xenial bionic))
  with_bridge =
    endif
  endif
    endif
  --

  Note:
   java-atk-wrapper is present in noble on i386

  This is a regression introduced in 8u402-ga-2:

    * Restore M-A installability of focal/i386 package (LP#1916327)
  by adding xenial, bionic, focal, jammy to the list of releases
  built with the ATK bridge, but not enabling it by default;
  keep jessie on, stretch and sid and mantic/noble off the list:
  please report bugs for issues with the bridge, so sthibault
  can find, debug, fix them

  See LP: #1916327

  The alternative is to publish atk-wrapper for i386 in mantic, jammy
  and focal.

  Options:
   a) rollback the fix in Ubuntu
   b) publish atk-wrapper

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/2053110/+subscriptions


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

[Desktop-packages] [Bug 2020814] Re: xmllint does not recognize emdash (— )

[Thorsten Glaser]

Hmm. I normally use libxml2 via xmlstarlet which has a somewhat nicer UX
than xmllint.

My guess is that you didn’t give a DTD, so it could only check that all
present entities are syntactically valid, but not expand them.

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

Title:
  xmllint does not recognize emdash (—)

Status in libxml2 package in Ubuntu:
  Invalid

Bug description:
  I'm using Ubuntu 20.04.2 LTS, x85_64, fully patched. I'm using DocBook to 
build a PDF. One of the steps I use in my build script is to validate and 
format the XML using xmllint from libxml2-utils
  2.9.13+dfsg-1ubuntu0.3:

  echo "Validating book..."
  if ! xmllint --xinclude --noout --postvalid book.xml
  then
  echo "Validation failed. Exiting."
  exit 1
  fi
  echo "Complete."

  echo "Formatting source code..."
  for file in *.xml
  do
  if xmllint --format "${file}" --output "${file}.format"
  then
  mv "${file}.format" "${file}"
  fi
  done
  echo "Complete."

  When I added an emdash (—) the book failed to format:

  Validating book...
  Complete.
  Formatting source code...
  ch02.xml:58: parser error : Entity 'mdash' not defined
   injections are remediated using several methods. And two output devices 
—

 ^
  ch02.xml:58: parser error : Entity 'mdash' not defined
   methods. And two output devices — the printer and plaintext email 
—

 ^
  Complete.

  The text is:

  ... And two output devices — the printer and plaintext
  email — do not require...

  It seems like emdash should be recognized.

  -

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
  Codename:   jammy

  -

  $ xmllint --version
  xmllint: using libxml version 20913
 compiled with: Threads Tree Output Push Reader Patterns Writer SAXv1 FTP 
HTTP DTDValid HTML Legacy C14N Catalog XPath XPointer XInclude Iconv ICU 
ISO8859X Unicode Regexps Automata Schemas Schematron Modules Debug Zlib Lzma

  $ command -v xmllint
  /usr/bin/xmllint

  $ dpkg -S /usr/bin/xmllint
  libxml2-utils: /usr/bin/xmllint

  $ apt-cache show libxml2-utils
  Package: libxml2-utils
  Architecture: amd64
  Version: 2.9.13+dfsg-1ubuntu0.3
  Multi-Arch: foreign
  Priority: optional
  Section: text
  Source: libxml2
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian XML/SGML Group 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 202
  Depends: libc6 (>= 2.34), libxml2 (>= 2.9.0)
  Filename: 
pool/main/libx/libxml2/libxml2-utils_2.9.13+dfsg-1ubuntu0.3_amd64.deb
  Size: 40192
  MD5sum: 3ca7de07562010fcaabf255ea8fea9c4
  SHA1: 128a9cfaff49e85f2ab08578f389eecb21f17766
  SHA256: c279c07caf909545e2cedb7845b5ac652e0a70f9784e5faf799a1a01441b4649
  SHA512: 
51600d7206c9a5568fdaeee9adddbc48962fc094cc479f4bd42c0714b3725cd3200937f8c876a897db08fc50d891005d7dbabfb6ae12ad27ad6ed416f8b6a03d
  Homepage: http://xmlsoft.org
  ...

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


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

[Desktop-packages] [Bug 2020814] Re: xmllint does not recognize emdash (— )

[Thorsten Glaser]

Yeah well, those portability problems were back in the 1990s when people
used latin1 or whatever codepages.

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

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

Title:
  xmllint does not recognize emdash (—)

Status in libxml2 package in Ubuntu:
  Invalid

Bug description:
  I'm using Ubuntu 20.04.2 LTS, x85_64, fully patched. I'm using DocBook to 
build a PDF. One of the steps I use in my build script is to validate and 
format the XML using xmllint from libxml2-utils
  2.9.13+dfsg-1ubuntu0.3:

  echo "Validating book..."
  if ! xmllint --xinclude --noout --postvalid book.xml
  then
  echo "Validation failed. Exiting."
  exit 1
  fi
  echo "Complete."

  echo "Formatting source code..."
  for file in *.xml
  do
  if xmllint --format "${file}" --output "${file}.format"
  then
  mv "${file}.format" "${file}"
  fi
  done
  echo "Complete."

  When I added an emdash (—) the book failed to format:

  Validating book...
  Complete.
  Formatting source code...
  ch02.xml:58: parser error : Entity 'mdash' not defined
   injections are remediated using several methods. And two output devices 
—

 ^
  ch02.xml:58: parser error : Entity 'mdash' not defined
   methods. And two output devices — the printer and plaintext email 
—

 ^
  Complete.

  The text is:

  ... And two output devices — the printer and plaintext
  email — do not require...

  It seems like emdash should be recognized.

  -

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
  Codename:   jammy

  -

  $ xmllint --version
  xmllint: using libxml version 20913
 compiled with: Threads Tree Output Push Reader Patterns Writer SAXv1 FTP 
HTTP DTDValid HTML Legacy C14N Catalog XPath XPointer XInclude Iconv ICU 
ISO8859X Unicode Regexps Automata Schemas Schematron Modules Debug Zlib Lzma

  $ command -v xmllint
  /usr/bin/xmllint

  $ dpkg -S /usr/bin/xmllint
  libxml2-utils: /usr/bin/xmllint

  $ apt-cache show libxml2-utils
  Package: libxml2-utils
  Architecture: amd64
  Version: 2.9.13+dfsg-1ubuntu0.3
  Multi-Arch: foreign
  Priority: optional
  Section: text
  Source: libxml2
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian XML/SGML Group 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 202
  Depends: libc6 (>= 2.34), libxml2 (>= 2.9.0)
  Filename: 
pool/main/libx/libxml2/libxml2-utils_2.9.13+dfsg-1ubuntu0.3_amd64.deb
  Size: 40192
  MD5sum: 3ca7de07562010fcaabf255ea8fea9c4
  SHA1: 128a9cfaff49e85f2ab08578f389eecb21f17766
  SHA256: c279c07caf909545e2cedb7845b5ac652e0a70f9784e5faf799a1a01441b4649
  SHA512: 
51600d7206c9a5568fdaeee9adddbc48962fc094cc479f4bd42c0714b3725cd3200937f8c876a897db08fc50d891005d7dbabfb6ae12ad27ad6ed416f8b6a03d
  Homepage: http://xmlsoft.org
  ...

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


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

[Desktop-packages] [Bug 2020814] Re: xmllint does not recognize emdash (— )

[Thorsten Glaser]

I doubt this is a bug: nowhere do you pass the validator a DTD, and
entities are defined in the DTD.

It’s best practice nowadays to not use entities but just write the UTF-8
characters directly.

An em dash surrounded by hair spaces is: “ — ” (for your copy/paste
convenience)

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

Title:
  xmllint does not recognize emdash (—)

Status in libxml2 package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 20.04.2 LTS, x85_64, fully patched. I'm using DocBook to 
build a PDF. One of the steps I use in my build script is to validate and 
format the XML using xmllint from libxml2-utils
  2.9.13+dfsg-1ubuntu0.3:

  echo "Validating book..."
  if ! xmllint --xinclude --noout --postvalid book.xml
  then
  echo "Validation failed. Exiting."
  exit 1
  fi
  echo "Complete."

  echo "Formatting source code..."
  for file in *.xml
  do
  if xmllint --format "${file}" --output "${file}.format"
  then
  mv "${file}.format" "${file}"
  fi
  done
  echo "Complete."

  When I added an emdash (—) the book failed to format:

  Validating book...
  Complete.
  Formatting source code...
  ch02.xml:58: parser error : Entity 'mdash' not defined
   injections are remediated using several methods. And two output devices 
—

 ^
  ch02.xml:58: parser error : Entity 'mdash' not defined
   methods. And two output devices — the printer and plaintext email 
—

 ^
  Complete.

  The text is:

  ... And two output devices — the printer and plaintext
  email — do not require...

  It seems like emdash should be recognized.

  -

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
  Codename:   jammy

  -

  $ xmllint --version
  xmllint: using libxml version 20913
 compiled with: Threads Tree Output Push Reader Patterns Writer SAXv1 FTP 
HTTP DTDValid HTML Legacy C14N Catalog XPath XPointer XInclude Iconv ICU 
ISO8859X Unicode Regexps Automata Schemas Schematron Modules Debug Zlib Lzma

  $ command -v xmllint
  /usr/bin/xmllint

  $ dpkg -S /usr/bin/xmllint
  libxml2-utils: /usr/bin/xmllint

  $ apt-cache show libxml2-utils
  Package: libxml2-utils
  Architecture: amd64
  Version: 2.9.13+dfsg-1ubuntu0.3
  Multi-Arch: foreign
  Priority: optional
  Section: text
  Source: libxml2
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian XML/SGML Group 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 202
  Depends: libc6 (>= 2.34), libxml2 (>= 2.9.0)
  Filename: 
pool/main/libx/libxml2/libxml2-utils_2.9.13+dfsg-1ubuntu0.3_amd64.deb
  Size: 40192
  MD5sum: 3ca7de07562010fcaabf255ea8fea9c4
  SHA1: 128a9cfaff49e85f2ab08578f389eecb21f17766
  SHA256: c279c07caf909545e2cedb7845b5ac652e0a70f9784e5faf799a1a01441b4649
  SHA512: 
51600d7206c9a5568fdaeee9adddbc48962fc094cc479f4bd42c0714b3725cd3200937f8c876a897db08fc50d891005d7dbabfb6ae12ad27ad6ed416f8b6a03d
  Homepage: http://xmlsoft.org
  ...

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


-- 
Mailing list: https://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 1938442] Re: Wrong permissions on ~/.hplip/.gnupg

[Thorsten Alteholz]

Hi Till,

On Thu, 9 Dec 2021, Till Kamppeter wrote:

> Thorsten, could you also update the Debian package appropriately? And
> once one it, update to 3.21.10? Thanks.

I don't know why someone has a problem with the permissions of a directory 
containing public keys. At least the permissions of ~ should prevent 
world to access the directory. From my point of view the status of this 
bug in Hirsute and Fedora is the way to go ...

   Thorsten

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

Title:
  Wrong permissions on ~/.hplip/.gnupg

Status in hplip package in Ubuntu:
  New
Status in hplip source package in Bionic:
  New
Status in hplip source package in Focal:
  New
Status in hplip source package in Hirsute:
  Won't Fix
Status in hplip source package in Impish:
  New
Status in hplip source package in Jammy:
  New

Bug description:
  [Impact]
  * The directory ~/.hplip/.gnupg is readable by non-root users
  * This directory contains only public keys, but should still
have the permissions changed to 700 for privacy reasons

  [Test Case]
  * Install hplip and run `hp-plugin -i` 
  * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x
  * rm -rf ~/.hplip and install hplip from -proposed
  * run `hp-plugin -i` again
  * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx--

  [Regression Potential]
  * Because of file permissions becoming more restrictive,
it is possible that some other hplip binaries would
fail to read the .gnupg directory
  * To ensure this isn't the case, testing should be done
on different hplip use-cases to ensure they still
function properly

  [Original Description]
  Hi,

  we have a report in Fedora -
  https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey
  found out that ~/.hplip/.gnupg directory has permissions 755 instead
  of 700. Perms 700 prevent accessing the dir by other users, because
  the dir can contain private keys.

  However, .gnupg dir contains only a public key used in GPG
  verification of HP plugin, so the matter isn't that critical, but it
  is good to have it fixed.

  The patch is attached.

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


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

[Desktop-packages] [Bug 1729558] Re: [regression] In Java apps like Netbeans, dark menu bars don't look good for disabled elements

[Thorsten Glaser]

As far as I see, openjdk-8 (8u275-b01-1) contains this patch, so it was
backported upstream.

** Changed in: openjdk-8 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  [regression] In Java apps like Netbeans, dark menu bars don't look
  good for disabled elements

Status in Ubuntu theme:
  Invalid
Status in openjdk-8 package in Ubuntu:
  Fix Released
Status in openjdk-9 package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Invalid

Bug description:
  This fix, #961679, specifically Ambiance/gtk-2.0/gtkrc:346
  (http://bazaar.launchpad.net/~ubuntu-art-pkg/ubuntu-
  themes/trunk/revision/583), makes disabled elements in menus look
  terrible.

  Unfortunately I'm not aware of an easy way to get screenshots of open
  menus, so hopefully these attached phone pictures of Netbeans are
  enough to illustrate the issue.

  As you can see it is hard to tell the difference between what is
  disabled and what isn't, and the disabled items look fuzzy (easier to
  observe on monitor).

  I really don't see the issue with lighter menus, but if they must stay
  dark then the readability / contrast of disabled items needs to be
  fixed.

  Thanks

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

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

[Desktop-packages] [Bug 1750146] Re: Xbox (One) Wireless Controller won't connect

[Thorsten Schneider]

Can confirm this still happens with kernel 5.8.1. While the device is
listed correctly with its full name in bluetoothctl and can be trusted,
the final pairing will not work. syslog will constantly have a
"Refusing" message for the device and the connection:

Aug 12 15:47:25 htpc blueman-mechanism: Exiting
Aug 12 15:47:38 htpc systemd[1]: Starting Stop ureadahead data collection...
Aug 12 15:47:38 htpc systemd[1]: Started Stop ureadahead data collection.
Aug 12 15:47:51 htpc bluetoothd[962]: Refusing input device connect: No such 
file or directory (2)
Aug 12 15:47:51 htpc bluetoothd[962]: Refusing connection from 
C8:3F:26:44:17:2D: unknown device

For example an 8bitdo Arcade Stick can be paired and connected without
issues over bluetooth.

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

Title:
  Xbox (One) Wireless Controller won't connect

Status in gnome-control-center:
  Confirmed
Status in Linux:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  Xbox One Wireless Controllers (Model 1708) refuse to connect via bluetooth 
with Ubuntu 17.10 in the gnome-control-center.
  Placing the controller into pairing mode makes it visible on the Bluetooth 
Devices list and the device pairs, but does not make the full connection needed 
to pull the controller out of pairing mode.

  This renders my controller unusable with my Ubuntu PC unless I want to
  resort to using the wire (microUSB).

  Please fix. See the attached system information below.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-lowlatency 4.13.13
  Uname: Linux 4.13.0-32-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 17 09:26:14 2018
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1868660] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() from g_sign

[Thorsten]

i got this error when hovering with the mouse over the system tray as
described in the bug report however Iam using X11 and not wayland

i have the following crash files:
-rw-r- 1 root root  95M Mai 10 13:15 _usr_bin_gnome-shell.1000.crash
-rw-r--r-- 1 root root0 Mai 10 13:15 
_usr_bin_gnome-shell.1000.upload
-rw--- 1 root root   37 Mai 10 13:15 
_usr_bin_gnome-shell.1000.uploaded
-rw-r- 1 root root 2,4M Mai 10 13:15 
_usr_lib_x86_64-linux-gnu_libexec_kdeconnectd.1000.crash
-rw-r--r-- 1 root root0 Mai 10 13:15 
_usr_lib_x86_64-linux-gnu_libexec_kdeconnectd.1000.upload
-rw--- 1 root root   37 Mai 10 13:15 
_usr_lib_x86_64-linux-gnu_libexec_kdeconnectd.1000.uploaded

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

Title:
  gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style()
  from st_texture_cache_load_gicon() from st_icon_update() from
  _g_closure_invoke_va() from g_signal_emit_valist()

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

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

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

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

[Desktop-packages] [Bug 1830551] Re: rhythmbox loses daap connection everytime when dhcp lease expires

[Thorsten Hirsch]

Thanks, Sebastien. I reported the issue upstream since it's not specific
to Ubuntu (I could reproduce it on Arch Linux).

https://gitlab.gnome.org/GNOME/rhythmbox/issues/1711

** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/issues #1711
   https://gitlab.gnome.org/GNOME/rhythmbox/issues/1711

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

Title:
  rhythmbox loses daap connection everytime when dhcp lease expires

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  rhythmbox loses daap connection everytime the host (of rhythmbox) has
  to renew his dhcp lease. The daap server has a static IP.

  Here is the corresponding part of journalctl:

  Mai 26 22:06:05 myhostname systemd-networkd[4173]: enp5s0: DHCP lease lost
  Mai 26 22:06:05 myhostname avahi-daemon[736]: Withdrawing address record for 
192.168.0.11 on enp5s0.
  Mai 26 22:06:05 myhostname avahi-daemon[736]: Leaving mDNS multicast group on 
interface enp5s0.IPv4 with address 192.168.0.11.
  Mai 26 22:06:05 myhostname systemd-networkd[4173]: enp5s0: DHCPv4 address 
192.168.0.11/24 via 192.168.0.1
  Mai 26 22:06:05 myhostname avahi-daemon[736]: Interface enp5s0.IPv4 no longer 
relevant for mDNS.
  Mai 26 22:06:05 myhostname dbus-daemon[734]: [system] Activating via systemd: 
service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.335' (uid=193>
  Mai 26 22:06:05 myhostname avahi-daemon[736]: Joining mDNS multicast group on 
interface enp5s0.IPv4 with address 192.168.0.11.
  Mai 26 22:06:05 myhostname avahi-daemon[736]: New relevant interface 
enp5s0.IPv4 for mDNS.
  Mai 26 22:06:05 myhostname avahi-daemon[736]: Registering new address record 
for 192.168.0.11 on enp5s0.IPv4.
  Mai 26 22:06:05 myhostname systemd[1]: Starting Hostname Service...
  Mai 26 22:06:05 myhostname steam.desktop[1225]: JS method call 
Messaging.PostMessage with 4 arguments
  Mai 26 22:06:05 myhostname dbus-daemon[734]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
  Mai 26 22:06:05 myhostname systemd[1]: Started Hostname Service.
  Mai 26 22:06:05 myhostname audit[1]: SERVICE_START pid=1 uid=0 
auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=>
  Mai 26 22:06:05 myhostname kernel: audit: type=1130 
audit(1558901165.932:114): pid=1 uid=0 auid=4294967295 ses=4294967295 
msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd">
  Mai 26 22:06:06 myhostname rhythmbox[2127]: rb_playlist_source_mark_dirty: 
assertion 'RB_IS_PLAYLIST_SOURCE (source)' failed
  Mai 26 22:06:06 myhostname rhythmbox[2127]: rb_playlist_source_mark_dirty: 
assertion 'RB_IS_PLAYLIST_SOURCE (source)' failed
  Mai 26 22:06:06 myhostname rhythmbox[2127]: rb_playlist_source_mark_dirty: 
assertion 'RB_IS_PLAYLIST_SOURCE (source)' failed
  Mai 26 22:06:06 myhostname rhythmbox[2127]: rb_playlist_source_mark_dirty: 
assertion 'RB_IS_PLAYLIST_SOURCE (source)' failed
  Mai 26 22:06:06 myhostname rhythmbox[2127]: rb_playlist_source_mark_dirty: 
assertion 'RB_IS_PLAYLIST_SOURCE (source)' failed
  Mai 26 22:06:06 myhostname rhythmbox[2127]: rb_playlist_source_mark_dirty: 
assertion 'RB_IS_PLAYLIST_SOURCE (source)' failed

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

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

[Desktop-packages] [Bug 1800043] Re: nautilus cannot write on nfs file share base dir

[Thorsten]

Hi, I have exactly the same issue.
Since the OP didn't provide the gio infos upstream requested, I just wanted to 
jump in and provide those infos.

gio info /mnt/nfs/tfuehrerldap
Anzeigename: tfuehrerldap
Name bearbeiten: tfuehrerldap
Name: tfuehrerldap
Typ: directory
Größe:  4096
Adresse: file:///mnt/nfs/tfuehrerldap
Attribute:
  standard::type: 2
  standard::name: tfuehrerldap
  standard::display-name: tfuehrerldap
  standard::edit-name: tfuehrerldap
  standard::copy-name: tfuehrerldap
  standard::icon: folder
  standard::content-type: inode/directory
  standard::fast-content-type: inode/directory
  standard::size: 4096
  standard::allocated-size: 4096
  standard::symbolic-icon: folder-symbolic, folder
  etag::value: 1560855687:754488
  id::file: l68:88809598
  id::filesystem: l68
  access::can-read: TRUE
  access::can-write: FALSE
  access::can-execute: TRUE
  access::can-delete: FALSE
  access::can-trash: FALSE
  access::can-rename: FALSE
  time::modified: 1560855687
  time::modified-usec: 754488
  time::access: 1560855688
  time::access-usec: 767482
  time::changed: 1560855687
  time::changed-usec: 754488
  unix::device: 68
  unix::inode: 88809598
  unix::mode: 16877
  unix::nlink: 4
  unix::uid: 101
  unix::gid: 101
  unix::rdev: 0
  unix::block-size: 4096
  unix::blocks: 8
  unix::is-mountpoint: TRUE
  owner::user: tfuehrerldap
  owner::user-real: tfuehrerldap
  owner::group: users
  metadata::nautilus-list-view-sort-column: name
  metadata::nautilus-list-view-sort-reversed: false

gio info -f /mnt/nfs/tfuehrerldap
Attribute:
  filesystem::size: 3928343838720
  filesystem::free: 1362925715456
  filesystem::type: nfs
  filesystem::used: 2565296488448
  filesystem::remote: FALSE


cheers,
Thorsten

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

Title:
  nautilus cannot write on nfs file share base dir

Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  I installed Ubuntu 18.04LTS comming from 16.04LTS where I did not have this 
weird problem: If I mount a NFS share from a file server (i.e. Synology DS 418) 
Nautilus is not able to perform any write access to it (write, delete, make new 
directory,...). I can do all of this operations by using shell commands (touch, 
cp, mkdir...) in a terminal window. Also, nautilus can perform these actions if 
I start it with root privileges.
  Even stranger is the following: even though nautilus cannot write into the 
mounted shares it is able to write into its subfolders. This bug seems to 
affect others as well: 
https://askubuntu.com/questions/1000973/nautilus-cannot-write-into-1st-directory-of-a-nfs-share

  Ubuntu version: 18.04.1 LTS - amd64
  Nautilus version: 1:3.26.4-0~ubuntu18.04.1

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

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

[Desktop-packages] [Bug 1830551] Re: rhythmbox loses daap connection everytime when dhcp lease expires

[Thorsten Hirsch]

...because?

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

Title:
  rhythmbox loses daap connection everytime when dhcp lease expires

Status in rhythmbox package in Ubuntu:
  New
Status in rhythmbox-plugin-alternative-toolbar package in Ubuntu:
  Invalid

Bug description:
  rhythmbox loses daap connection everytime the host (of rhythmbox) has
  to renew his dhcp lease. The daap server has a static IP.

  Here is the corresponding part of journalctl:

  Mai 26 22:06:05 myhostname systemd-networkd[4173]: enp5s0: DHCP lease lost
  Mai 26 22:06:05 myhostname avahi-daemon[736]: Withdrawing address record for 
192.168.0.11 on enp5s0.
  Mai 26 22:06:05 myhostname avahi-daemon[736]: Leaving mDNS multicast group on 
interface enp5s0.IPv4 with address 192.168.0.11.
  Mai 26 22:06:05 myhostname systemd-networkd[4173]: enp5s0: DHCPv4 address 
192.168.0.11/24 via 192.168.0.1
  Mai 26 22:06:05 myhostname avahi-daemon[736]: Interface enp5s0.IPv4 no longer 
relevant for mDNS.
  Mai 26 22:06:05 myhostname dbus-daemon[734]: [system] Activating via systemd: 
service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.335' (uid=193>
  Mai 26 22:06:05 myhostname avahi-daemon[736]: Joining mDNS multicast group on 
interface enp5s0.IPv4 with address 192.168.0.11.
  Mai 26 22:06:05 myhostname avahi-daemon[736]: New relevant interface 
enp5s0.IPv4 for mDNS.
  Mai 26 22:06:05 myhostname avahi-daemon[736]: Registering new address record 
for 192.168.0.11 on enp5s0.IPv4.
  Mai 26 22:06:05 myhostname systemd[1]: Starting Hostname Service...
  Mai 26 22:06:05 myhostname steam.desktop[1225]: JS method call 
Messaging.PostMessage with 4 arguments
  Mai 26 22:06:05 myhostname dbus-daemon[734]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
  Mai 26 22:06:05 myhostname systemd[1]: Started Hostname Service.
  Mai 26 22:06:05 myhostname audit[1]: SERVICE_START pid=1 uid=0 
auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=>
  Mai 26 22:06:05 myhostname kernel: audit: type=1130 
audit(1558901165.932:114): pid=1 uid=0 auid=4294967295 ses=4294967295 
msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd">
  Mai 26 22:06:06 myhostname rhythmbox[2127]: rb_playlist_source_mark_dirty: 
assertion 'RB_IS_PLAYLIST_SOURCE (source)' failed
  Mai 26 22:06:06 myhostname rhythmbox[2127]: rb_playlist_source_mark_dirty: 
assertion 'RB_IS_PLAYLIST_SOURCE (source)' failed
  Mai 26 22:06:06 myhostname rhythmbox[2127]: rb_playlist_source_mark_dirty: 
assertion 'RB_IS_PLAYLIST_SOURCE (source)' failed
  Mai 26 22:06:06 myhostname rhythmbox[2127]: rb_playlist_source_mark_dirty: 
assertion 'RB_IS_PLAYLIST_SOURCE (source)' failed
  Mai 26 22:06:06 myhostname rhythmbox[2127]: rb_playlist_source_mark_dirty: 
assertion 'RB_IS_PLAYLIST_SOURCE (source)' failed
  Mai 26 22:06:06 myhostname rhythmbox[2127]: rb_playlist_source_mark_dirty: 
assertion 'RB_IS_PLAYLIST_SOURCE (source)' failed

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

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

[Desktop-packages] [Bug 1830551] [NEW] rhythmbox loses daap connection everytime when dhcp lease expires

[Thorsten Hirsch]

Public bug reported:

rhythmbox loses daap connection everytime the host (of rhythmbox) has to
renew his dhcp lease. The daap server has a static IP.

Here is the corresponding part of journalctl:

Mai 26 22:06:05 myhostname systemd-networkd[4173]: enp5s0: DHCP lease lost
Mai 26 22:06:05 myhostname avahi-daemon[736]: Withdrawing address record for 
192.168.0.11 on enp5s0.
Mai 26 22:06:05 myhostname avahi-daemon[736]: Leaving mDNS multicast group on 
interface enp5s0.IPv4 with address 192.168.0.11.
Mai 26 22:06:05 myhostname systemd-networkd[4173]: enp5s0: DHCPv4 address 
192.168.0.11/24 via 192.168.0.1
Mai 26 22:06:05 myhostname avahi-daemon[736]: Interface enp5s0.IPv4 no longer 
relevant for mDNS.
Mai 26 22:06:05 myhostname dbus-daemon[734]: [system] Activating via systemd: 
service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.335' (uid=193>
Mai 26 22:06:05 myhostname avahi-daemon[736]: Joining mDNS multicast group on 
interface enp5s0.IPv4 with address 192.168.0.11.
Mai 26 22:06:05 myhostname avahi-daemon[736]: New relevant interface 
enp5s0.IPv4 for mDNS.
Mai 26 22:06:05 myhostname avahi-daemon[736]: Registering new address record 
for 192.168.0.11 on enp5s0.IPv4.
Mai 26 22:06:05 myhostname systemd[1]: Starting Hostname Service...
Mai 26 22:06:05 myhostname steam.desktop[1225]: JS method call 
Messaging.PostMessage with 4 arguments
Mai 26 22:06:05 myhostname dbus-daemon[734]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
Mai 26 22:06:05 myhostname systemd[1]: Started Hostname Service.
Mai 26 22:06:05 myhostname audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=>
Mai 26 22:06:05 myhostname kernel: audit: type=1130 audit(1558901165.932:114): 
pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed 
comm="systemd" exe="/usr/lib/systemd/systemd">
Mai 26 22:06:06 myhostname rhythmbox[2127]: rb_playlist_source_mark_dirty: 
assertion 'RB_IS_PLAYLIST_SOURCE (source)' failed
Mai 26 22:06:06 myhostname rhythmbox[2127]: rb_playlist_source_mark_dirty: 
assertion 'RB_IS_PLAYLIST_SOURCE (source)' failed
Mai 26 22:06:06 myhostname rhythmbox[2127]: rb_playlist_source_mark_dirty: 
assertion 'RB_IS_PLAYLIST_SOURCE (source)' failed
Mai 26 22:06:06 myhostname rhythmbox[2127]: rb_playlist_source_mark_dirty: 
assertion 'RB_IS_PLAYLIST_SOURCE (source)' failed
Mai 26 22:06:06 myhostname rhythmbox[2127]: rb_playlist_source_mark_dirty: 
assertion 'RB_IS_PLAYLIST_SOURCE (source)' failed
Mai 26 22:06:06 myhostname rhythmbox[2127]: rb_playlist_source_mark_dirty: 
assertion 'RB_IS_PLAYLIST_SOURCE (source)' failed

** Affects: rhythmbox-plugin-alternative-toolbar (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  rhythmbox loses daap connection everytime when dhcp lease expires

Status in rhythmbox-plugin-alternative-toolbar package in Ubuntu:
  New

Bug description:
  rhythmbox loses daap connection everytime the host (of rhythmbox) has
  to renew his dhcp lease. The daap server has a static IP.

  Here is the corresponding part of journalctl:

  Mai 26 22:06:05 myhostname systemd-networkd[4173]: enp5s0: DHCP lease lost
  Mai 26 22:06:05 myhostname avahi-daemon[736]: Withdrawing address record for 
192.168.0.11 on enp5s0.
  Mai 26 22:06:05 myhostname avahi-daemon[736]: Leaving mDNS multicast group on 
interface enp5s0.IPv4 with address 192.168.0.11.
  Mai 26 22:06:05 myhostname systemd-networkd[4173]: enp5s0: DHCPv4 address 
192.168.0.11/24 via 192.168.0.1
  Mai 26 22:06:05 myhostname avahi-daemon[736]: Interface enp5s0.IPv4 no longer 
relevant for mDNS.
  Mai 26 22:06:05 myhostname dbus-daemon[734]: [system] Activating via systemd: 
service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.335' (uid=193>
  Mai 26 22:06:05 myhostname avahi-daemon[736]: Joining mDNS multicast group on 
interface enp5s0.IPv4 with address 192.168.0.11.
  Mai 26 22:06:05 myhostname avahi-daemon[736]: New relevant interface 
enp5s0.IPv4 for mDNS.
  Mai 26 22:06:05 myhostname avahi-daemon[736]: Registering new address record 
for 192.168.0.11 on enp5s0.IPv4.
  Mai 26 22:06:05 myhostname systemd[1]: Starting Hostname Service...
  Mai 26 22:06:05 myhostname steam.desktop[1225]: JS method call 
Messaging.PostMessage with 4 arguments
  Mai 26 22:06:05 myhostname dbus-daemon[734]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
  Mai 26 22:06:05 myhostname systemd[1]: Started Hostname Service.
  Mai 26 22:06:05 myhostname audit[1]: SERVICE_START pid=1 uid=0 
auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=

[Desktop-packages] [Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking

[Thorsten]

I also still have this issue with the default 18.04.1 version. However,
i installed a newer mesa version (which also upgrades a bunch of other
dependencies) using the padoka stable ppa and since then the issue is
gone.

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

Title:
  Screen contents revealed briefly on resume, before even unlocking

Status in GNOME Shell:
  In Progress
Status in Ubuntu GNOME:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Xenial:
  Fix Released
Status in gnome-shell package in Debian:
  Confirmed

Bug description:
  [Impact]

  When lock is enabled, the screen doesn't get blank/covered by
  lockscreen before suspending, thus on early resume the content might
  be shown.

  Video showing the bug: https://youtu.be/dDOgtK1MldI

  Reproduced on Ubuntu 2015.10, Ubuntu 2014.04

  [Test case]

  1. Work on highly secret files
  2. Close the lid of your laptop and go have a break
  3. Anyone who opens the lid of the laptop can see the secret files for a half 
second before the lock screen appears

  [Possible Regression]

  Content on screen isn't painted anymore and screen stays black.

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

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

[Desktop-packages] [Bug 1666264] Re: FFe: Update gnome-terminal to 3.24 and vte to 0.48

[Thorsten]

you probably have to apply the ubuntu tilix "pcre2-version-update" patch

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

Title:
  FFe: Update gnome-terminal to 3.24 and vte to 0.48

Status in gnome-terminal package in Ubuntu:
  Fix Released
Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  gnome-terminal and vte are still at their 3.20 (and 0.44) versions
  because they now hard-depend on pcre2, but the pcre2 MIR (LP:
  #163) has stalled because there is already one version of pcre in
  main and it would be a major task to convert all of main to use pcre2.

  So I reverted 3 commits for gnome-terminal and 5 for vte to make that
  MIR less urgent. I am concerned about the long-term maintainability of
  this approach - the vte patch is over 1600 lines.

  gnome-terminal 3.22 and vte 0.46 have been tested in the GNOME3
  Staging PPA for yakkety and zesty for months. I am not aware of any
  issues from that. This is slightly different since I haven't tested
  those versions without pcre2 until this weekend.

  The development cycle for gnome-terminal and vte has been fairly quiet
  so I believe it's safe to go ahead and update gnome-terminal to
  3.23.90 and vte to 0.47.90.

  https://git.gnome.org/browse/gnome-terminal/log
  https://git.gnome.org/browse/vte/log

  The packages are currently available for testing at

  
https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty

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

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

[Desktop-packages] [Bug 1757068] Re: Night light brakes when screen dims

[Thorsten Niehues]

I'm not sure if nightlight breaks after dim or after it turns off
completely. (since it cannot dim any more after having lowest possible
backlight already)

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

Title:
  Night light brakes when screen dims

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

Bug description:
  I'm using the night light function in Budgie which is set to a
  temperature of 4000 and the schedule is set from sunset to sunrise.
  When my display dims after X minutes of inactivity the night light
  function breaks which results in a much blue-er screen. When I move my
  mouse the dimming effect dissapears but and the temperature and
  brightness of my screen go back to the default value as if the night
  light function isn't on. Disabling and enabling the night light
  function fixes the issue until my screen dims again.

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

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

[Desktop-packages] [Bug 1676131] Re: Gnome Night Light doesn't work

[Thorsten Niehues]

For me nightlight is working perfectly after each reboot - but as soon as the 
display is turned off nightlight is off when the screen is powered on again.
As a workaround I turn the setting off and on again.

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

Title:
  Gnome Night Light doesn't work

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

Bug description:
  On the first boot of Ubuntu, the night light worked but after restart
  this option does nothing.

  I couldn't get any log from the terminal.


  Ubuntu Gnome 17.04 beta2
  gnome-control-center 1:3.24.0-0ubuntu1

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

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

[Desktop-packages] [Bug 1666264] Re: FFe: Update gnome-terminal to 3.24 and vte to 0.48

[Thorsten]

tilix seems to be warning-free with unpatched vte. Someone has posted
these warnings upstream: https://github.com/gnunn1/tilix/issues/1428 and
the response was "Please open a bug with Ubuntu, since they patch vte to
remove pcre2 regular expressions this issue is likely caused by that." a

** Bug watch added: github.com/gnunn1/tilix/issues #1428
   https://github.com/gnunn1/tilix/issues/1428

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

Title:
  FFe: Update gnome-terminal to 3.24 and vte to 0.48

Status in gnome-terminal package in Ubuntu:
  Fix Released
Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  gnome-terminal and vte are still at their 3.20 (and 0.44) versions
  because they now hard-depend on pcre2, but the pcre2 MIR (LP:
  #163) has stalled because there is already one version of pcre in
  main and it would be a major task to convert all of main to use pcre2.

  So I reverted 3 commits for gnome-terminal and 5 for vte to make that
  MIR less urgent. I am concerned about the long-term maintainability of
  this approach - the vte patch is over 1600 lines.

  gnome-terminal 3.22 and vte 0.46 have been tested in the GNOME3
  Staging PPA for yakkety and zesty for months. I am not aware of any
  issues from that. This is slightly different since I haven't tested
  those versions without pcre2 until this weekend.

  The development cycle for gnome-terminal and vte has been fairly quiet
  so I believe it's safe to go ahead and update gnome-terminal to
  3.23.90 and vte to 0.47.90.

  https://git.gnome.org/browse/gnome-terminal/log
  https://git.gnome.org/browse/vte/log

  The packages are currently available for testing at

  
https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty

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

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

[Desktop-packages] [Bug 1666264] Re: FFe: Update gnome-terminal to 3.24 and vte to 0.48

[Thorsten]

thanks a lot for the clarification, this is really helping me to
understand that! I am just a noob who wants to learn something and wants
to find the cause of a problem which annoys me. Thus, i invested some
time to dig into the problem :)

So the cause is that the MULTILINE flag is just that not set during
compilation?

tilix behavior is not broken and the hyperlink regex, which when added
causes the warning, is working. The only problem is that it is spamming
the logs with these warnings.

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

Title:
  FFe: Update gnome-terminal to 3.24 and vte to 0.48

Status in gnome-terminal package in Ubuntu:
  Fix Released
Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  gnome-terminal and vte are still at their 3.20 (and 0.44) versions
  because they now hard-depend on pcre2, but the pcre2 MIR (LP:
  #163) has stalled because there is already one version of pcre in
  main and it would be a major task to convert all of main to use pcre2.

  So I reverted 3 commits for gnome-terminal and 5 for vte to make that
  MIR less urgent. I am concerned about the long-term maintainability of
  this approach - the vte patch is over 1600 lines.

  gnome-terminal 3.22 and vte 0.46 have been tested in the GNOME3
  Staging PPA for yakkety and zesty for months. I am not aware of any
  issues from that. This is slightly different since I haven't tested
  those versions without pcre2 until this weekend.

  The development cycle for gnome-terminal and vte has been fairly quiet
  so I believe it's safe to go ahead and update gnome-terminal to
  3.23.90 and vte to 0.47.90.

  https://git.gnome.org/browse/gnome-terminal/log
  https://git.gnome.org/browse/vte/log

  The packages are currently available for testing at

  
https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty

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

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

[Desktop-packages] [Bug 1666264] Re: FFe: Update gnome-terminal to 3.24 and vte to 0.48

[Thorsten]

i should be more precise with the file name... the specific line is in
src/vtegtk.cc line 1906

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

Title:
  FFe: Update gnome-terminal to 3.24 and vte to 0.48

Status in gnome-terminal package in Ubuntu:
  Fix Released
Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  gnome-terminal and vte are still at their 3.20 (and 0.44) versions
  because they now hard-depend on pcre2, but the pcre2 MIR (LP:
  #163) has stalled because there is already one version of pcre in
  main and it would be a major task to convert all of main to use pcre2.

  So I reverted 3 commits for gnome-terminal and 5 for vte to make that
  MIR less urgent. I am concerned about the long-term maintainability of
  this approach - the vte patch is over 1600 lines.

  gnome-terminal 3.22 and vte 0.46 have been tested in the GNOME3
  Staging PPA for yakkety and zesty for months. I am not aware of any
  issues from that. This is slightly different since I haven't tested
  those versions without pcre2 until this weekend.

  The development cycle for gnome-terminal and vte has been fairly quiet
  so I believe it's safe to go ahead and update gnome-terminal to
  3.23.90 and vte to 0.47.90.

  https://git.gnome.org/browse/gnome-terminal/log
  https://git.gnome.org/browse/vte/log

  The packages are currently available for testing at

  
https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty

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

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

[Desktop-packages] [Bug 1666264] Re: FFe: Update gnome-terminal to 3.24 and vte to 0.48

[Thorsten]

Hi everyone,

I don't know which is the right place to post this, but the discussion
here seems to be the most appropriate for bringing this up.

I looked more into the tilix warnings. After all, the warnings seem to be 
caused by the vte lib and especially in the reverted parts.
Therefore, I downloaded the source with apt-get source libvte-2.91-0 and 
printed the arguments of line 1906 which triggers the warnings. 

#include  (at the top of the file)
printf("arguments: %d %d %d\n", g_regex_get_compile_flags(gregex),
G_REGEX_MULTILINE,
g_regex_get_compile_flags(gregex) & 
G_REGEX_MULTILINE);


So I started tilix and looked at the output:

arguments: 1 2 0

(tilix:5596): Vte-WARNING **: 10:32:57.957: (../../src/vtegtk.cc:1905):int 
vte_terminal_match_add_gregex(VteTerminal*, GRegex*, GRegexMatchFlags): runtime 
check failed: (g_regex_get_compile_flags(gregex) & G_REGEX_MULTILINE)
warning should be printed
arguments: 1 2 0

(tilix:5596): Vte-WARNING **: 10:32:57.957: (../../src/vtegtk.cc:1905):int 
vte_terminal_match_add_gregex(VteTerminal*, GRegex*, GRegexMatchFlags): runtime 
check failed: (g_regex_get_compile_flags(gregex) & G_REGEX_MULTILINE)
warning should be printed
arguments: 1 2 0

(tilix:5596): Vte-WARNING **: 10:32:57.957: (../../src/vtegtk.cc:1905):int 
vte_terminal_match_add_gregex(VteTerminal*, GRegex*, GRegexMatchFlags): runtime 
check failed: (g_regex_get_compile_flags(gregex) & G_REGEX_MULTILINE)
warning should be printed
arguments: 1 2 0

(tilix:5596): Vte-WARNING **: 10:32:57.957: (../../src/vtegtk.cc:1905):int 
vte_terminal_match_add_gregex(VteTerminal*, GRegex*, GRegexMatchFlags): runtime 
check failed: (g_regex_get_compile_flags(gregex) & G_REGEX_MULTILINE)
warning should be printed
arguments: 1 2 0

(tilix:5596): Vte-WARNING **: 10:32:57.957: (../../src/vtegtk.cc:1905):int 
vte_terminal_match_add_gregex(VteTerminal*, GRegex*, GRegexMatchFlags): runtime 
check failed: (g_regex_get_compile_flags(gregex) & G_REGEX_MULTILINE)
warning should be printed
arguments: 1 2 0

(tilix:5596): Vte-WARNING **: 10:32:57.957: (../../src/vtegtk.cc:1905):int 
vte_terminal_match_add_gregex(VteTerminal*, GRegex*, GRegexMatchFlags): runtime 
check failed: (g_regex_get_compile_flags(gregex) & G_REGEX_MULTILINE)
warning should be printed


As you can see both arguments itself are true. But why is a "bitwise and" used 
in g_warn_if_fail()? Since the first is 1 and the second 2, this causes 
0010 & 0001 ->  and the warning is triggered? 

So what I did and propose is to replace the "bitwise and" with a
"logical or". This causes that the warning is only triggered if one of
both arguments is false. -> The tilix warning is gone and everything
seems work for me!

This line is created by the ubuntu specific patch "revert-pcre2.patch"
and in this file in line 1065


Just for letting you know which part of tilix calls this function:
In the constructor in the file terminal.d the function applyPreferences() is 
called. There in the switch statement
the case SETTINGS_ALL_CUSTOM_HYPERLINK_KEY is calling loadRegex() which calls 
the vte function vte_terminal_match_add_gregex 6 times and triggers the 6 
warnings.

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

Title:
  FFe: Update gnome-terminal to 3.24 and vte to 0.48

Status in gnome-terminal package in Ubuntu:
  Fix Released
Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  gnome-terminal and vte are still at their 3.20 (and 0.44) versions
  because they now hard-depend on pcre2, but the pcre2 MIR (LP:
  #163) has stalled because there is already one version of pcre in
  main and it would be a major task to convert all of main to use pcre2.

  So I reverted 3 commits for gnome-terminal and 5 for vte to make that
  MIR less urgent. I am concerned about the long-term maintainability of
  this approach - the vte patch is over 1600 lines.

  gnome-terminal 3.22 and vte 0.46 have been tested in the GNOME3
  Staging PPA for yakkety and zesty for months. I am not aware of any
  issues from that. This is slightly different since I haven't tested
  those versions without pcre2 until this weekend.

  The development cycle for gnome-terminal and vte has been fairly quiet
  so I believe it's safe to go ahead and update gnome-terminal to
  3.23.90 and vte to 0.47.90.

  https://git.gnome.org/browse/gnome-terminal/log
  https://git.gnome.org/browse/vte/log

  The packages are currently available for testing at

  
https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty

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

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

[Desktop-packages] [Bug 1666264] Re: FFe: Update gnome-terminal to 3.24 and vte to 0.48

[Thorsten]

ari, i already have created a bug report for the tilix log messages:
https://bugs.launchpad.net/ubuntu/+source/tilix/+bug/1785885

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

Title:
  FFe: Update gnome-terminal to 3.24 and vte to 0.48

Status in gnome-terminal package in Ubuntu:
  Fix Released
Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  gnome-terminal and vte are still at their 3.20 (and 0.44) versions
  because they now hard-depend on pcre2, but the pcre2 MIR (LP:
  #163) has stalled because there is already one version of pcre in
  main and it would be a major task to convert all of main to use pcre2.

  So I reverted 3 commits for gnome-terminal and 5 for vte to make that
  MIR less urgent. I am concerned about the long-term maintainability of
  this approach - the vte patch is over 1600 lines.

  gnome-terminal 3.22 and vte 0.46 have been tested in the GNOME3
  Staging PPA for yakkety and zesty for months. I am not aware of any
  issues from that. This is slightly different since I haven't tested
  those versions without pcre2 until this weekend.

  The development cycle for gnome-terminal and vte has been fairly quiet
  so I believe it's safe to go ahead and update gnome-terminal to
  3.23.90 and vte to 0.47.90.

  https://git.gnome.org/browse/gnome-terminal/log
  https://git.gnome.org/browse/vte/log

  The packages are currently available for testing at

  
https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty

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

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

[Desktop-packages] [Bug 1731628] Re: Cannot add caldav calendar

[Thorsten]

still not possible in ubuntu 18.04 with calendar 3.28.2. I also tried a
posteo calendar.

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

Title:
  Cannot add caldav calendar

Status in gnome-calendar package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I try to add a caldav calendar

  calendars -> Add -> From Web ->
  https://posteo.de:8443/calendars/max.mustermann/default/

  and I hit enter but the "add" button in the right upper corner remains
  grayed out.

  Kind regards

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-calendar 3.26.2-1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 11 14:47:03 2017
  InstallationDate: Installed on 2017-11-11 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171109)
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1772638] Re: Segfault in libmutter-2.so after suspend/resume using wayland. Core files are always truncated and invalid while the default shell is zsh.

[Thorsten]

or handler 
doing an exit(), pid = 1725, errno = 11
  Mai 22 13:11:15 x1 org.gnome.SettingsDaemon.Power.desktop[1611]: 
xcb_connection_has_error() returned true
  Mai 22 13:11:15 x1 firefox.desktop[2050]: xcb_connection_has_error() returned 
true
  Mai 22 13:11:15 x1 pulseaudio[2430]: [pulseaudio] client-conf-x11.c: 
xcb_connection_has_error() returned true
  Mai 22 13:11:15 x1 polkitd(authority=local)[1059]: Unregistered 
Authentication Agent for unix-session:2 (system bus name :1.74, object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) 
(disconnected from bus)
  Mai 22 13:11:15 x1 rtkit-daemon[1171]: Successfully made thread 2434 of 
process 2434 (n/a) owned by '1000' high priority at nice level -11.
  Mai 22 13:11:15 x1 rtkit-daemon[1171]: Supervising 2 threads of 2 processes 
of 1 users.
  Mai 22 13:11:15 x1 pulseaudio[2434]: [pulseaudio] pid.c: Stale PID file, 
overwriting.
  Mai 22 13:11:15 x1 gdm-password][1430]: pam_unix(gdm-password:session): 
session closed for user thorsten
  Mai 22 13:11:15 x1 gsd-color[1217]: failed to connect to device: Failed to 
connect to missing device 
/org/freedesktop/ColorManager/devices/xrandr_AU_Optronics_thorsten_1000
  Mai 22 13:11:15 x1 pulseaudio[2434]: [pulseaudio] sink.c: Default and 
alternate sample rates are the same.
  ... followup crashes...

  
  Moreover, here is the apport.log: 
  ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: called for pid 1483, 
signal 11, core limit 0, dump mode 1
  ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
  ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: debug: session gdbus call: 
(true,)

  ERROR: apport (pid 2357) Tue May 22 13:11:15 2018: wrote report 
/var/crash/_usr_bin_gnome-shell.1000.crash
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: called for pid 1502, 
signal 6, core limit 18446744073709551615, dump mode 1
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: ignoring implausibly big 
core limit, treating as unlimited
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: executable: 
/usr/bin/Xwayland (command line "/usr/bin/Xwayland :0 -rootless -terminate 
-accessx -core -listen 4 -listen 5 -displayfd 6")
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: debug: session gdbus call: 
  ERROR: apport (pid 2429) Tue May 22 13:11:19 2018: wrote report 
/var/crash/_usr_bin_Xwayland.1000.crash
  ERROR: apport (pid 2429) Tue May 22 13:11:19 2018: writing core dump to 
/home/thorsten/core (limit: -1)
  ERROR: apport (pid 2429) Tue May 22 13:11:20 2018: writing core dump 
/home/thorsten/core of size 107855872

  Additionally, i have ~100MB "core" file in my home directory.

  I tried to report the created _usr_bin_gnome-shell.1000.crash file
  using the workaround from
  https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 and
  ubuntu-bug. However, i get the error: "The problem cannot be reported:
  Invalid core dump: BFD: warning /tmp/apport_core_ersfx7ym is
  truncated: expected core file size >= 846290944, found: 216288"

  reporting the corresponding _usr_bin_Xwayland.1000.crash file forwards
  me to https://bugs.launchpad.net/ubuntu/+source/xorg-
  server/+bug/1731911. But this only seems to indicate that Xwayland
  crashes since mutter has crashed.

  This error only occurs when using the wayland and not in the xorg
  session.

  I am running 4.16.10 mainline kernel due to some driver issues with my
  laptop (thinkpad x1 carbon gen6) but this also occurs when using the
  4.15 kernel and with and without loading the guc firmware.

  Thanks!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  PackageArchitecture: amd64
  Tags:  wayland-session bionic
  Uname: Linux 4.16.10-041610-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/apport/+bug/1772638/+subscriptions

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

[Desktop-packages] [Bug 1772638] Re: Segfault in libmutter-2.so after suspend/resume using wayland. Core files are always truncated and invalid while the default shell is zsh.

[Thorsten]

ication 'org.gnome.Shell.desktop' killed by signal 11
  Mai 22 13:11:15 x1 gnome-session-binary[1455]: WARNING: Application 
'org.gnome.Shell.desktop' killed by signal 11
  Mai 22 13:11:15 x1 gnome-session-binary[1455]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
  Mai 22 13:11:15 x1 kdeconnectd.desktop[1725]: ICE default IO error handler 
doing an exit(), pid = 1725, errno = 11
  Mai 22 13:11:15 x1 org.gnome.SettingsDaemon.Power.desktop[1611]: 
xcb_connection_has_error() returned true
  Mai 22 13:11:15 x1 firefox.desktop[2050]: xcb_connection_has_error() returned 
true
  Mai 22 13:11:15 x1 pulseaudio[2430]: [pulseaudio] client-conf-x11.c: 
xcb_connection_has_error() returned true
  Mai 22 13:11:15 x1 polkitd(authority=local)[1059]: Unregistered 
Authentication Agent for unix-session:2 (system bus name :1.74, object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) 
(disconnected from bus)
  Mai 22 13:11:15 x1 rtkit-daemon[1171]: Successfully made thread 2434 of 
process 2434 (n/a) owned by '1000' high priority at nice level -11.
  Mai 22 13:11:15 x1 rtkit-daemon[1171]: Supervising 2 threads of 2 processes 
of 1 users.
  Mai 22 13:11:15 x1 pulseaudio[2434]: [pulseaudio] pid.c: Stale PID file, 
overwriting.
  Mai 22 13:11:15 x1 gdm-password][1430]: pam_unix(gdm-password:session): 
session closed for user thorsten
  Mai 22 13:11:15 x1 gsd-color[1217]: failed to connect to device: Failed to 
connect to missing device 
/org/freedesktop/ColorManager/devices/xrandr_AU_Optronics_thorsten_1000
  Mai 22 13:11:15 x1 pulseaudio[2434]: [pulseaudio] sink.c: Default and 
alternate sample rates are the same.
  ... followup crashes...

  
  Moreover, here is the apport.log: 
  ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: called for pid 1483, 
signal 11, core limit 0, dump mode 1
  ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
  ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: debug: session gdbus call: 
(true,)

  ERROR: apport (pid 2357) Tue May 22 13:11:15 2018: wrote report 
/var/crash/_usr_bin_gnome-shell.1000.crash
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: called for pid 1502, 
signal 6, core limit 18446744073709551615, dump mode 1
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: ignoring implausibly big 
core limit, treating as unlimited
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: executable: 
/usr/bin/Xwayland (command line "/usr/bin/Xwayland :0 -rootless -terminate 
-accessx -core -listen 4 -listen 5 -displayfd 6")
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: debug: session gdbus call: 
  ERROR: apport (pid 2429) Tue May 22 13:11:19 2018: wrote report 
/var/crash/_usr_bin_Xwayland.1000.crash
  ERROR: apport (pid 2429) Tue May 22 13:11:19 2018: writing core dump to 
/home/thorsten/core (limit: -1)
  ERROR: apport (pid 2429) Tue May 22 13:11:20 2018: writing core dump 
/home/thorsten/core of size 107855872

  Additionally, i have ~100MB "core" file in my home directory.

  I tried to report the created _usr_bin_gnome-shell.1000.crash file
  using the workaround from
  https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 and
  ubuntu-bug. However, i get the error: "The problem cannot be reported:
  Invalid core dump: BFD: warning /tmp/apport_core_ersfx7ym is
  truncated: expected core file size >= 846290944, found: 216288"

  reporting the corresponding _usr_bin_Xwayland.1000.crash file forwards
  me to https://bugs.launchpad.net/ubuntu/+source/xorg-
  server/+bug/1731911. But this only seems to indicate that Xwayland
  crashes since mutter has crashed.

  This error only occurs when using the wayland and not in the xorg
  session.

  I am running 4.16.10 mainline kernel due to some driver issues with my
  laptop (thinkpad x1 carbon gen6) but this also occurs when using the
  4.15 kernel and with and without loading the guc firmware.

  Thanks!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  PackageArchitecture: amd64
  Tags:  wayland-session bionic
  Uname: Linux 4.16.10-041610-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/gnome-shell/+bug/1772638/+subscriptions

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

[Desktop-packages] [Bug 1772638] Re: segfault in libmutter-2.so after suspend/resume using wayland

[Thorsten]

p[1725]: ICE default IO error handler 
doing an exit(), pid = 1725, errno = 11
  Mai 22 13:11:15 x1 org.gnome.SettingsDaemon.Power.desktop[1611]: 
xcb_connection_has_error() returned true
  Mai 22 13:11:15 x1 firefox.desktop[2050]: xcb_connection_has_error() returned 
true
  Mai 22 13:11:15 x1 pulseaudio[2430]: [pulseaudio] client-conf-x11.c: 
xcb_connection_has_error() returned true
  Mai 22 13:11:15 x1 polkitd(authority=local)[1059]: Unregistered 
Authentication Agent for unix-session:2 (system bus name :1.74, object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) 
(disconnected from bus)
  Mai 22 13:11:15 x1 rtkit-daemon[1171]: Successfully made thread 2434 of 
process 2434 (n/a) owned by '1000' high priority at nice level -11.
  Mai 22 13:11:15 x1 rtkit-daemon[1171]: Supervising 2 threads of 2 processes 
of 1 users.
  Mai 22 13:11:15 x1 pulseaudio[2434]: [pulseaudio] pid.c: Stale PID file, 
overwriting.
  Mai 22 13:11:15 x1 gdm-password][1430]: pam_unix(gdm-password:session): 
session closed for user thorsten
  Mai 22 13:11:15 x1 gsd-color[1217]: failed to connect to device: Failed to 
connect to missing device 
/org/freedesktop/ColorManager/devices/xrandr_AU_Optronics_thorsten_1000
  Mai 22 13:11:15 x1 pulseaudio[2434]: [pulseaudio] sink.c: Default and 
alternate sample rates are the same.
  ... followup crashes...

  
  Moreover, here is the apport.log: 
  ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: called for pid 1483, 
signal 11, core limit 0, dump mode 1
  ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
  ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: debug: session gdbus call: 
(true,)

  ERROR: apport (pid 2357) Tue May 22 13:11:15 2018: wrote report 
/var/crash/_usr_bin_gnome-shell.1000.crash
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: called for pid 1502, 
signal 6, core limit 18446744073709551615, dump mode 1
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: ignoring implausibly big 
core limit, treating as unlimited
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: executable: 
/usr/bin/Xwayland (command line "/usr/bin/Xwayland :0 -rootless -terminate 
-accessx -core -listen 4 -listen 5 -displayfd 6")
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: debug: session gdbus call: 
  ERROR: apport (pid 2429) Tue May 22 13:11:19 2018: wrote report 
/var/crash/_usr_bin_Xwayland.1000.crash
  ERROR: apport (pid 2429) Tue May 22 13:11:19 2018: writing core dump to 
/home/thorsten/core (limit: -1)
  ERROR: apport (pid 2429) Tue May 22 13:11:20 2018: writing core dump 
/home/thorsten/core of size 107855872

  Additionally, i have ~100MB "core" file in my home directory.

  I tried to report the created _usr_bin_gnome-shell.1000.crash file
  using the workaround from
  https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 and
  ubuntu-bug. However, i get the error: "The problem cannot be reported:
  Invalid core dump: BFD: warning /tmp/apport_core_ersfx7ym is
  truncated: expected core file size >= 846290944, found: 216288"

  reporting the corresponding _usr_bin_Xwayland.1000.crash file forwards
  me to https://bugs.launchpad.net/ubuntu/+source/xorg-
  server/+bug/1731911. But this only seems to indicate that Xwayland
  crashes since mutter has crashed.

  This error only occurs when using the wayland and not in the xorg
  session.

  I am running 4.16.10 mainline kernel due to some driver issues with my
  laptop (thinkpad x1 carbon gen6) but this also occurs when using the
  4.15 kernel and with and without loading the guc firmware.

  Thanks!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  PackageArchitecture: amd64
  Tags:  wayland-session bionic
  Uname: Linux 4.16.10-041610-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/gnome-shell/+bug/1772638/+subscriptions

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

[Desktop-packages] [Bug 1772638] Re: segfault in libmutter-2.so after suspend/resume using wayland

[Thorsten]

Hi,

i switched my login shell back to bash (chsh -s /bin/bash) and i was not
able to reproduce the issue in ~30 resume/suspend cycles. This is still
no valid statistic but is it possible that zsh as login shell can
segfault mutter? Of course, I will report if it occurs!

ubuntu-bug still has the problem with the old crash file, probably since
it wrongly generated or?

Thanks and sry for this non-default setup.

Here is the additional system information:

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

cat /proc/sys/kernel/core_pipe_limit
0

should be enough space on /: df -h
Filesystem  Size  Used Avail Use% Mounted on
udev7,7G 0  7,7G   0% /dev
tmpfs   1,6G   10M  1,6G   1% /run
/dev/nvme0n1p6  246G   39G  195G  17% /
tmpfs   7,8G   41M  7,7G   1% /dev/shm
tmpfs   5,0M  4,0K  5,0M   1% /run/lock
tmpfs   7,8G 0  7,8G   0% /sys/fs/cgroup
/dev/loop0  3,8M  3,8M 0 100% /snap/gnome-system-monitor/39
/dev/loop3  140M  140M 0 100% /snap/gnome-3-26-1604/64
/dev/loop4  141M  141M 0 100% /snap/gnome-3-26-1604/59
/dev/loop2  3,4M  3,4M 0 100% /snap/gnome-system-monitor/36
/dev/loop1   21M   21M 0 100% /snap/gnome-logs/25
/dev/loop5  1,7M  1,7M 0 100% /snap/gnome-calculator/154
/dev/loop6   87M   87M 0 100% /snap/core/4486
/dev/loop7  2,4M  2,4M 0 100% /snap/gnome-calculator/167
/dev/loop8   87M   87M 0 100% /snap/core/4571
/dev/loop9   22M   22M 0 100% /snap/gnome-logs/31
/dev/loop11  13M   13M 0 100% /snap/gnome-characters/86
/dev/loop10  13M   13M 0 100% /snap/gnome-characters/69
/dev/loop12  87M   87M 0 100% /snap/core/4650
/dev/loop13 141M  141M 0 100% /snap/gnome-3-26-1604/62
/dev/nvme0n1p2   96M   29M   68M  30% /boot/efi
/dev/nvme0n1p7  473G  236G  238G  50% /media/thorsten/daten
tmpfs   1,6G   20K  1,6G   1% /run/user/119
tmpfs   1,6G  7,1M  1,6G   1% /run/user/1000

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

Title:
  segfault in libmutter-2.so after suspend/resume using wayland

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  i have the problem when running the gnome wayland session in ubuntu
  18.04 that in ~1 out of 5 resume/suspend cycles a segfault in
  libmutter-2.so occurs which then kills my current session. Here is my
  journctl from the crash:

  Mai 22 12:39:03 x1 systemd[1]: Reached target Sleep.
  Mai 22 12:39:03 x1 systemd[1]: Starting Suspend...
  Mai 22 12:39:03 x1 systemd-sleep[2349]: Suspending system...
  Mai 22 12:39:03 x1 kernel: PM: suspend entry (s2idle)
  Mai 22 12:39:03 x1 kernel: PM: Syncing filesystems ... done.
  Mai 22 12:39:03 x1 gnome-shell[1483]: Failed to set CRTC mode 2560x1440: 
Permission denied
  Mai 22 12:39:03 x1 wpa_supplicant[976]: nl80211: deinit ifname=wlp2s0 
disabled_11b_rates=0
  Mai 22 12:39:03 x1 kernel: gnome-shell[1483]: segfault at 20 ip 
7ff704b28b17 sp 7ffd6c1cd1b0 error 4 in 
libmutter-2.so.0.0.0[7ff704a3b000+156000]
  Mai 22 12:39:03 x1 kernel: [drm] Reducing the compressed framebuffer size. 
This may lead to less power savings than a non-reduced-size. Try to increase 
stolen memory size if available in BIOS.
  Mai 22 13:11:15 x1 kernel: Freezing user space processes ... (elapsed 0.001 
seconds) done.
  Mai 22 13:11:15 x1 kernel: OOM killer disabled.
  Mai 22 13:11:15 x1 kernel: Freezing remaining freezable tasks ... (elapsed 
0.001 seconds) done.
  Mai 22 13:11:15 x1 kernel: Suspending console(s) (use no_console_suspend to 
debug)
  Mai 22 13:11:15 x1 kernel: thinkpad_acpi: unknown possible thermal alarm or 
keyboard event received
  Mai 22 13:11:15 x1 kernel: thinkpad_acpi: unhandled HKEY event 0x6032
  Mai 22 13:11:15 x1 kernel: thinkpad_acpi: please report the conditions when 
this event happened to ibm-acpi-de...@lists.sourceforge.net
  Mai 22 13:11:15 x1 kernel: [drm] GuC: Loaded firmware 
i915/kbl_guc_ver9_39.bin (version 9.39)
  Mai 22 13:11:15 x1 kernel: i915 :00:02.0: GuC firmware

[Desktop-packages] [Bug 1772638] GsettingsChanges.txt

[Thorsten]

 polkitd(authority=local)[1059]: Unregistered 
Authentication Agent for unix-session:2 (system bus name :1.74, object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) 
(disconnected from bus)
  Mai 22 13:11:15 x1 rtkit-daemon[1171]: Successfully made thread 2434 of 
process 2434 (n/a) owned by '1000' high priority at nice level -11.
  Mai 22 13:11:15 x1 rtkit-daemon[1171]: Supervising 2 threads of 2 processes 
of 1 users.
  Mai 22 13:11:15 x1 pulseaudio[2434]: [pulseaudio] pid.c: Stale PID file, 
overwriting.
  Mai 22 13:11:15 x1 gdm-password][1430]: pam_unix(gdm-password:session): 
session closed for user thorsten
  Mai 22 13:11:15 x1 gsd-color[1217]: failed to connect to device: Failed to 
connect to missing device 
/org/freedesktop/ColorManager/devices/xrandr_AU_Optronics_thorsten_1000
  Mai 22 13:11:15 x1 pulseaudio[2434]: [pulseaudio] sink.c: Default and 
alternate sample rates are the same.
  ... followup crashes...

  
  Moreover, here is the apport.log: 
  ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: called for pid 1483, 
signal 11, core limit 0, dump mode 1
  ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
  ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: debug: session gdbus call: 
(true,)

  ERROR: apport (pid 2357) Tue May 22 13:11:15 2018: wrote report 
/var/crash/_usr_bin_gnome-shell.1000.crash
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: called for pid 1502, 
signal 6, core limit 18446744073709551615, dump mode 1
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: ignoring implausibly big 
core limit, treating as unlimited
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: executable: 
/usr/bin/Xwayland (command line "/usr/bin/Xwayland :0 -rootless -terminate 
-accessx -core -listen 4 -listen 5 -displayfd 6")
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: debug: session gdbus call: 
  ERROR: apport (pid 2429) Tue May 22 13:11:19 2018: wrote report 
/var/crash/_usr_bin_Xwayland.1000.crash
  ERROR: apport (pid 2429) Tue May 22 13:11:19 2018: writing core dump to 
/home/thorsten/core (limit: -1)
  ERROR: apport (pid 2429) Tue May 22 13:11:20 2018: writing core dump 
/home/thorsten/core of size 107855872

  Additionally, i have ~100MB "core" file in my home directory.

  I tried to report the created _usr_bin_gnome-shell.1000.crash file
  using the workaround from
  https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 and
  ubuntu-bug. However, i get the error: "The problem cannot be reported:
  Invalid core dump: BFD: warning /tmp/apport_core_ersfx7ym is
  truncated: expected core file size >= 846290944, found: 216288"

  reporting the corresponding _usr_bin_Xwayland.1000.crash file forwards
  me to https://bugs.launchpad.net/ubuntu/+source/xorg-
  server/+bug/1731911. But this only seems to indicate that Xwayland
  crashes since mutter has crashed.

  This error only occurs when using the wayland and not in the xorg
  session.

  I am running 4.16.10 mainline kernel due to some driver issues with my
  laptop (thinkpad x1 carbon gen6) but this also occurs when using the
  4.15 kernel and with and without loading the guc firmware.

  Thanks!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  PackageArchitecture: amd64
  Tags:  wayland-session bionic
  Uname: Linux 4.16.10-041610-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/gnome-shell/+bug/1772638/+subscriptions

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

[Desktop-packages] [Bug 1772638] Re: segfault in libmutter-2.so after suspend/resume using wayland

[Thorsten]

11:15 x1 kdeconnectd.desktop[1725]: ICE default IO error handler 
doing an exit(), pid = 1725, errno = 11
  Mai 22 13:11:15 x1 org.gnome.SettingsDaemon.Power.desktop[1611]: 
xcb_connection_has_error() returned true
  Mai 22 13:11:15 x1 firefox.desktop[2050]: xcb_connection_has_error() returned 
true
  Mai 22 13:11:15 x1 pulseaudio[2430]: [pulseaudio] client-conf-x11.c: 
xcb_connection_has_error() returned true
  Mai 22 13:11:15 x1 polkitd(authority=local)[1059]: Unregistered 
Authentication Agent for unix-session:2 (system bus name :1.74, object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) 
(disconnected from bus)
  Mai 22 13:11:15 x1 rtkit-daemon[1171]: Successfully made thread 2434 of 
process 2434 (n/a) owned by '1000' high priority at nice level -11.
  Mai 22 13:11:15 x1 rtkit-daemon[1171]: Supervising 2 threads of 2 processes 
of 1 users.
  Mai 22 13:11:15 x1 pulseaudio[2434]: [pulseaudio] pid.c: Stale PID file, 
overwriting.
  Mai 22 13:11:15 x1 gdm-password][1430]: pam_unix(gdm-password:session): 
session closed for user thorsten
  Mai 22 13:11:15 x1 gsd-color[1217]: failed to connect to device: Failed to 
connect to missing device 
/org/freedesktop/ColorManager/devices/xrandr_AU_Optronics_thorsten_1000
  Mai 22 13:11:15 x1 pulseaudio[2434]: [pulseaudio] sink.c: Default and 
alternate sample rates are the same.
  ... followup crashes...

  
  Moreover, here is the apport.log: 
  ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: called for pid 1483, 
signal 11, core limit 0, dump mode 1
  ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
  ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: debug: session gdbus call: 
(true,)

  ERROR: apport (pid 2357) Tue May 22 13:11:15 2018: wrote report 
/var/crash/_usr_bin_gnome-shell.1000.crash
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: called for pid 1502, 
signal 6, core limit 18446744073709551615, dump mode 1
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: ignoring implausibly big 
core limit, treating as unlimited
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: executable: 
/usr/bin/Xwayland (command line "/usr/bin/Xwayland :0 -rootless -terminate 
-accessx -core -listen 4 -listen 5 -displayfd 6")
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: debug: session gdbus call: 
  ERROR: apport (pid 2429) Tue May 22 13:11:19 2018: wrote report 
/var/crash/_usr_bin_Xwayland.1000.crash
  ERROR: apport (pid 2429) Tue May 22 13:11:19 2018: writing core dump to 
/home/thorsten/core (limit: -1)
  ERROR: apport (pid 2429) Tue May 22 13:11:20 2018: writing core dump 
/home/thorsten/core of size 107855872

  Additionally, i have ~100MB "core" file in my home directory.

  I tried to report the created _usr_bin_gnome-shell.1000.crash file
  using the workaround from
  https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 and
  ubuntu-bug. However, i get the error: "The problem cannot be reported:
  Invalid core dump: BFD: warning /tmp/apport_core_ersfx7ym is
  truncated: expected core file size >= 846290944, found: 216288"

  reporting the corresponding _usr_bin_Xwayland.1000.crash file forwards
  me to https://bugs.launchpad.net/ubuntu/+source/xorg-
  server/+bug/1731911. But this only seems to indicate that Xwayland
  crashes since mutter has crashed.

  This error only occurs when using the wayland and not in the xorg
  session.

  I am running 4.16.10 mainline kernel due to some driver issues with my
  laptop (thinkpad x1 carbon gen6) but this also occurs when using the
  4.15 kernel and with and without loading the guc firmware.

  Thanks!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  PackageArchitecture: amd64
  Tags:  wayland-session bionic
  Uname: Linux 4.16.10-041610-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/gnome-shell/+bug/1772638/+subscriptions

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

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

[Thorsten]

 polkitd(authority=local)[1059]: Unregistered 
Authentication Agent for unix-session:2 (system bus name :1.74, object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) 
(disconnected from bus)
  Mai 22 13:11:15 x1 rtkit-daemon[1171]: Successfully made thread 2434 of 
process 2434 (n/a) owned by '1000' high priority at nice level -11.
  Mai 22 13:11:15 x1 rtkit-daemon[1171]: Supervising 2 threads of 2 processes 
of 1 users.
  Mai 22 13:11:15 x1 pulseaudio[2434]: [pulseaudio] pid.c: Stale PID file, 
overwriting.
  Mai 22 13:11:15 x1 gdm-password][1430]: pam_unix(gdm-password:session): 
session closed for user thorsten
  Mai 22 13:11:15 x1 gsd-color[1217]: failed to connect to device: Failed to 
connect to missing device 
/org/freedesktop/ColorManager/devices/xrandr_AU_Optronics_thorsten_1000
  Mai 22 13:11:15 x1 pulseaudio[2434]: [pulseaudio] sink.c: Default and 
alternate sample rates are the same.
  ... followup crashes...

  
  Moreover, here is the apport.log: 
  ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: called for pid 1483, 
signal 11, core limit 0, dump mode 1
  ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
  ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: debug: session gdbus call: 
(true,)

  ERROR: apport (pid 2357) Tue May 22 13:11:15 2018: wrote report 
/var/crash/_usr_bin_gnome-shell.1000.crash
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: called for pid 1502, 
signal 6, core limit 18446744073709551615, dump mode 1
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: ignoring implausibly big 
core limit, treating as unlimited
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: executable: 
/usr/bin/Xwayland (command line "/usr/bin/Xwayland :0 -rootless -terminate 
-accessx -core -listen 4 -listen 5 -displayfd 6")
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: debug: session gdbus call: 
  ERROR: apport (pid 2429) Tue May 22 13:11:19 2018: wrote report 
/var/crash/_usr_bin_Xwayland.1000.crash
  ERROR: apport (pid 2429) Tue May 22 13:11:19 2018: writing core dump to 
/home/thorsten/core (limit: -1)
  ERROR: apport (pid 2429) Tue May 22 13:11:20 2018: writing core dump 
/home/thorsten/core of size 107855872

  Additionally, i have ~100MB "core" file in my home directory.

  I tried to report the created _usr_bin_gnome-shell.1000.crash file
  using the workaround from
  https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 and
  ubuntu-bug. However, i get the error: "The problem cannot be reported:
  Invalid core dump: BFD: warning /tmp/apport_core_ersfx7ym is
  truncated: expected core file size >= 846290944, found: 216288"

  reporting the corresponding _usr_bin_Xwayland.1000.crash file forwards
  me to https://bugs.launchpad.net/ubuntu/+source/xorg-
  server/+bug/1731911. But this only seems to indicate that Xwayland
  crashes since mutter has crashed.

  This error only occurs when using the wayland and not in the xorg
  session.

  I am running 4.16.10 mainline kernel due to some driver issues with my
  laptop (thinkpad x1 carbon gen6) but this also occurs when using the
  4.15 kernel and with and without loading the guc firmware.

  Thanks!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  PackageArchitecture: amd64
  Tags:  wayland-session bionic
  Uname: Linux 4.16.10-041610-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/gnome-shell/+bug/1772638/+subscriptions

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

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

[Thorsten]

ity=local)[1059]: Unregistered 
Authentication Agent for unix-session:2 (system bus name :1.74, object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) 
(disconnected from bus)
  Mai 22 13:11:15 x1 rtkit-daemon[1171]: Successfully made thread 2434 of 
process 2434 (n/a) owned by '1000' high priority at nice level -11.
  Mai 22 13:11:15 x1 rtkit-daemon[1171]: Supervising 2 threads of 2 processes 
of 1 users.
  Mai 22 13:11:15 x1 pulseaudio[2434]: [pulseaudio] pid.c: Stale PID file, 
overwriting.
  Mai 22 13:11:15 x1 gdm-password][1430]: pam_unix(gdm-password:session): 
session closed for user thorsten
  Mai 22 13:11:15 x1 gsd-color[1217]: failed to connect to device: Failed to 
connect to missing device 
/org/freedesktop/ColorManager/devices/xrandr_AU_Optronics_thorsten_1000
  Mai 22 13:11:15 x1 pulseaudio[2434]: [pulseaudio] sink.c: Default and 
alternate sample rates are the same.
  ... followup crashes...

  
  Moreover, here is the apport.log: 
  ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: called for pid 1483, 
signal 11, core limit 0, dump mode 1
  ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
  ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: debug: session gdbus call: 
(true,)

  ERROR: apport (pid 2357) Tue May 22 13:11:15 2018: wrote report 
/var/crash/_usr_bin_gnome-shell.1000.crash
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: called for pid 1502, 
signal 6, core limit 18446744073709551615, dump mode 1
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: ignoring implausibly big 
core limit, treating as unlimited
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: executable: 
/usr/bin/Xwayland (command line "/usr/bin/Xwayland :0 -rootless -terminate 
-accessx -core -listen 4 -listen 5 -displayfd 6")
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: debug: session gdbus call: 
  ERROR: apport (pid 2429) Tue May 22 13:11:19 2018: wrote report 
/var/crash/_usr_bin_Xwayland.1000.crash
  ERROR: apport (pid 2429) Tue May 22 13:11:19 2018: writing core dump to 
/home/thorsten/core (limit: -1)
  ERROR: apport (pid 2429) Tue May 22 13:11:20 2018: writing core dump 
/home/thorsten/core of size 107855872

  Additionally, i have ~100MB "core" file in my home directory.

  I tried to report the created _usr_bin_gnome-shell.1000.crash file
  using the workaround from
  https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 and
  ubuntu-bug. However, i get the error: "The problem cannot be reported:
  Invalid core dump: BFD: warning /tmp/apport_core_ersfx7ym is
  truncated: expected core file size >= 846290944, found: 216288"

  reporting the corresponding _usr_bin_Xwayland.1000.crash file forwards
  me to https://bugs.launchpad.net/ubuntu/+source/xorg-
  server/+bug/1731911. But this only seems to indicate that Xwayland
  crashes since mutter has crashed.

  This error only occurs when using the wayland and not in the xorg
  session.

  I am running 4.16.10 mainline kernel due to some driver issues with my
  laptop (thinkpad x1 carbon gen6) but this also occurs when using the
  4.15 kernel and with and without loading the guc firmware.

  Thanks!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  PackageArchitecture: amd64
  Tags:  wayland-session bionic
  Uname: Linux 4.16.10-041610-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/gnome-shell/+bug/1772638/+subscriptions

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

[Desktop-packages] [Bug 1772638] Re: segfault in libmutter-2.so after suspend/resume using wayland

[Thorsten]

 13:11:15 x1 rtkit-daemon[1171]: Supervising 2 threads of 2 processes 
of 1 users.
  Mai 22 13:11:15 x1 pulseaudio[2434]: [pulseaudio] pid.c: Stale PID file, 
overwriting.
  Mai 22 13:11:15 x1 gdm-password][1430]: pam_unix(gdm-password:session): 
session closed for user thorsten
  Mai 22 13:11:15 x1 gsd-color[1217]: failed to connect to device: Failed to 
connect to missing device 
/org/freedesktop/ColorManager/devices/xrandr_AU_Optronics_thorsten_1000
  Mai 22 13:11:15 x1 pulseaudio[2434]: [pulseaudio] sink.c: Default and 
alternate sample rates are the same.
  ... followup crashes...
  
  
  Moreover, here is the apport.log: 
  ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: called for pid 1483, 
signal 11, core limit 0, dump mode 1
  ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
  ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: debug: session gdbus call: 
(true,)
  
  ERROR: apport (pid 2357) Tue May 22 13:11:15 2018: wrote report 
/var/crash/_usr_bin_gnome-shell.1000.crash
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: called for pid 1502, 
signal 6, core limit 18446744073709551615, dump mode 1
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: ignoring implausibly big 
core limit, treating as unlimited
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: executable: 
/usr/bin/Xwayland (command line "/usr/bin/Xwayland :0 -rootless -terminate 
-accessx -core -listen 4 -listen 5 -displayfd 6")
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files
  
  ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: debug: session gdbus call: 
  ERROR: apport (pid 2429) Tue May 22 13:11:19 2018: wrote report 
/var/crash/_usr_bin_Xwayland.1000.crash
  ERROR: apport (pid 2429) Tue May 22 13:11:19 2018: writing core dump to 
/home/thorsten/core (limit: -1)
  ERROR: apport (pid 2429) Tue May 22 13:11:20 2018: writing core dump 
/home/thorsten/core of size 107855872
  
  Additionally, i have ~100MB "core" file in my home directory.
  
  I tried to report the created _usr_bin_gnome-shell.1000.crash file using
  the workaround from
  https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 and ubuntu-
  bug. However, i get the error: "The problem cannot be reported: Invalid
  core dump: BFD: warning /tmp/apport_core_ersfx7ym is truncated: expected
  core file size >= 846290944, found: 216288"
  
  reporting the corresponding _usr_bin_Xwayland.1000.crash file forwards
  me to https://bugs.launchpad.net/ubuntu/+source/xorg-
  server/+bug/1731911. But this only seems to indicate that Xwayland
  crashes since mutter has crashed.
  
  This error only occurs when using the wayland and not in the xorg
  session.
  
  I am running 4.16.10 mainline kernel due to some driver issues with my
  laptop (thinkpad x1 carbon gen6) but this also occurs when using the
  4.15 kernel and with and without loading the guc firmware.
  
  Thanks!
+ --- 
+ ApportVersion: 2.20.9-0ubuntu7
+ Architecture: amd64
+ CurrentDesktop: GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 18.04
+ Package: gnome-shell 3.28.1-0ubuntu2
+ PackageArchitecture: amd64
+ Tags:  wayland-session bionic
+ Uname: Linux 4.16.10-041610-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  segfault in libmutter-2.so after suspend/resume using wayland

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  i have the problem when running the gnome wayland session in ubuntu
  18.04 that in ~1 out of 5 resume/suspend cycles a segfault in
  libmutter-2.so occurs which then kills my current session. Here is my
  journctl from the crash:

  Mai 22 12:39:03 x1 systemd[1]: Reached target Sleep.
  Mai 22 12:39:03 x1 systemd[1]: Starting Suspend...
  Mai 22 12:39:03 x1 systemd-sleep[2349]: Suspending system...
  Mai 22 12:39:03 x1 kernel: PM: suspend entry (s2idle)
  Mai 22 12:39:03 x1 kernel: PM: Syncing filesystems ... done.
  Mai 22 12:39:03 x1 gnome-shell[1483]: Failed to set CRTC mode 2560x1440: 
Permission denied
  Mai 22 12:39:03 x1 wpa_supplicant[976]: nl80211: deinit ifname=wlp2s0 
disabled_11b_rates=0
  Mai 22 12:39:03 x1 kernel: gnome-shell[1483]: segfault at 20 ip 
7ff704b28b17 sp 7ffd6c1cd1b0 error 4 in 
libmutter-2.so.0.0.0[7ff704a3b000+156000]
  Mai 22 12:39:03 x1 kernel: [drm] Reducing the compressed framebuffer size. 
This may lead to

[Desktop-packages] [Bug 1772638] [NEW] segfault in libmutter-2.so after suspend/resume using wayland

[Thorsten]

-password][1430]: pam_unix(gdm-password:session): session 
closed for user thorsten
Mai 22 13:11:15 x1 gsd-color[1217]: failed to connect to device: Failed to 
connect to missing device 
/org/freedesktop/ColorManager/devices/xrandr_AU_Optronics_thorsten_1000
Mai 22 13:11:15 x1 pulseaudio[2434]: [pulseaudio] sink.c: Default and alternate 
sample rates are the same.
... followup crashes...


Moreover, here is the apport.log: 
ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: called for pid 1483, signal 
11, core limit 0, dump mode 1
ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
ERROR: apport (pid 2357) Tue May 22 12:39:03 2018: debug: session gdbus call: 
(true,)

ERROR: apport (pid 2357) Tue May 22 13:11:15 2018: wrote report 
/var/crash/_usr_bin_gnome-shell.1000.crash
ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: called for pid 1502, signal 
6, core limit 18446744073709551615, dump mode 1
ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: ignoring implausibly big 
core limit, treating as unlimited
ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: executable: 
/usr/bin/Xwayland (command line "/usr/bin/Xwayland :0 -rootless -terminate 
-accessx -core -listen 4 -listen 5 -displayfd 6")
ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 2429) Tue May 22 13:11:15 2018: debug: session gdbus call: 
ERROR: apport (pid 2429) Tue May 22 13:11:19 2018: wrote report 
/var/crash/_usr_bin_Xwayland.1000.crash
ERROR: apport (pid 2429) Tue May 22 13:11:19 2018: writing core dump to 
/home/thorsten/core (limit: -1)
ERROR: apport (pid 2429) Tue May 22 13:11:20 2018: writing core dump 
/home/thorsten/core of size 107855872

Additionally, i have ~100MB "core" file in my home directory.

I tried to report the created _usr_bin_gnome-shell.1000.crash file using
the workaround from
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 and ubuntu-
bug. However, i get the error: "The problem cannot be reported: Invalid
core dump: BFD: warning /tmp/apport_core_ersfx7ym is truncated: expected
core file size >= 846290944, found: 216288"

reporting the corresponding _usr_bin_Xwayland.1000.crash file forwards
me to https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1731911. But this only seems to indicate that Xwayland
crashes since mutter has crashed.

This error only occurs when using the wayland and not in the xorg
session.

I am running 4.16.10 mainline kernel due to some driver issues with my
laptop (thinkpad x1 carbon gen6) but this also occurs when using the
4.15 kernel and with and without loading the guc firmware.

Thanks!

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

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

Title:
  segfault in libmutter-2.so after suspend/resume using wayland

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hi,

  i have the problem when running the gnome wayland session in ubuntu
  18.04 that in ~1 out of 5 resume/suspend cycles a segfault in
  libmutter-2.so occurs which then kills my current session. Here is my
  journctl from the crash:

  Mai 22 12:39:03 x1 systemd[1]: Reached target Sleep.
  Mai 22 12:39:03 x1 systemd[1]: Starting Suspend...
  Mai 22 12:39:03 x1 systemd-sleep[2349]: Suspending system...
  Mai 22 12:39:03 x1 kernel: PM: suspend entry (s2idle)
  Mai 22 12:39:03 x1 kernel: PM: Syncing filesystems ... done.
  Mai 22 12:39:03 x1 gnome-shell[1483]: Failed to set CRTC mode 2560x1440: 
Permission denied
  Mai 22 12:39:03 x1 wpa_supplicant[976]: nl80211: deinit ifname=wlp2s0 
disabled_11b_rates=0
  Mai 22 12:39:03 x1 kernel: gnome-shell[1483]: segfault at 20 ip 
7ff704b28b17 sp 7ffd6c1cd1b0 error 4 in 
libmutter-2.so.0.0.0[7ff704a3b000+156000]
  Mai 22 12:39:03 x1 kernel: [drm] Reducing the compressed framebuffer size. 
This may lead to less power savings than a non-reduced-size. Try to increase 
stolen memory size if available in BIOS.
  Mai 22 13:11:15 x1 kernel: Freezing user space processes ... (elapsed 0.001 
seconds) done.
  Mai 22 13:11:15 x1 kernel: OOM killer disabled.
  Mai 22 13:11:15 x1 kernel: Freezing remaining freezable tasks ... (elapsed 
0.001 seconds) done.
  Mai 22 13:11:15 x1 kernel: Suspending console(s) (use no_console_suspend to 
debug)
  Mai 22 13:11:15 x1 kernel: thinkpad_acpi: unknown possible thermal alarm or 
keyboard event received
  Mai 22 13:11:15 x1 kernel: thinkpad_acpi: unhandled HKEY event 0x6032
  Mai 22 13:11:15 x1 kernel: thinkpad_acpi: please report the conditions when 
this event happened to ibm-acpi-de...@lists.sourceforge.net
  Mai 22 13:11:15 x1 kernel: [drm] GuC: L

[Desktop-packages] [Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking

[Thorsten]

for me this bug is only happening in 18.04 when using the X session and
does not occur when using wayland

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

Title:
  Screen contents revealed briefly on resume, before even unlocking

Status in GNOME Shell:
  In Progress
Status in Ubuntu GNOME:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Xenial:
  Fix Released
Status in gnome-shell package in Debian:
  Confirmed
Status in gnome-shell package in Fedora:
  In Progress

Bug description:
  [Impact]

  When lock is enabled, the screen doesn't get blank/covered by
  lockscreen before suspending, thus on early resume the content might
  be shown.

  Video showing the bug: https://youtu.be/dDOgtK1MldI

  Reproduced on Ubuntu 2015.10, Ubuntu 2014.04

  [Test case]

  1. Work on highly secret files
  2. Close the lid of your laptop and go have a break
  3. Anyone who opens the lid of the laptop can see the secret files for a half 
second before the lock screen appears

  [Possible Regression]

  Content on screen isn't painted anymore and screen stays black.

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

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

[Desktop-packages] [Bug 1730672] Re: Proxy settings not applied system-wide, are not used by Software Update or apt

[Thorsten Greeb]

Importance: Low? Are you sure?

In environments where Internet access is only possible via proxy

- Ubuntu Software: Not working
- Software Updater: Not working
- Automatic install of security updates: Not working
- Install Languages (Language Support): Not working
- ...

I find this quite critical!

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

Title:
  Proxy settings not applied system-wide, are not used by Software
  Update or apt

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

Bug description:
  The Network Proxy settings available under Settings/Network are not applied 
system wide. Unlike 16.x, there is no "apply system wide" setting. Setting a 
proxy here:
  - does not modify /etc/environment
  - does not set root's http_proxy, https_proxy, ftp_proxy environment 
variables 

  This means that apt and Software Updates do not receive the proxy
  settings, and package checks/updates/installs fail.

  
  workaround:

  sudo http_proxy='http://[username]:[password]@[webproxy]:[port]' apt
  update

  etc

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

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

[Desktop-packages] [Bug 1721614] Re: Firefox menus are misplaced

[Thorsten Munsch]

I found out that it doesn't work with my Nvidia GT430 and propritary
driver 384.90.

Bought an AMD RX550 last week, uninstalled the Nvidia driver, removed
the Nvidia, AMD card in, boot up 14.04 and the burger menu and
everything is working fine again in the browser.

I noticed then that the current amdgpu driver requires >16.04, switched
back to Nvidia card, installed 384.90 driver and voilá the menus are
behaving like written above again.

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

Title:
  Firefox menus are misplaced

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Sometimes Firefox places its menus at incorrect locations. See attached 
screenshot and video. This happens at least with the main (hamburger icon) 
menu, bookmark folders, and context menu. Moving the Firefox window temporarily 
solves the problem. It usually happens after resume from suspend, which in 
general in my case is accompanied by a display reconfiguration (unplug external 
monitor, suspend, resume, plug other external monitor).
  This looks very similar to this another bug 
(https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1641629) which I 
reported against Firefox 49 and that was resolved by installing Firefox 52. 
This time, it occurred in Firefox 55, and also now in Firefox 56. It started 
occurring sometime during the 17.10 cycle, which I have been using for a few 
months.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: firefox 56.0+build6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   gpothier   2684 F...m pulseaudio
   /dev/snd/controlC1:  gpothier   2684 F pulseaudio
   /dev/snd/controlC0:  gpothier   2684 F pulseaudio
  BuildID: 20171003222101
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Thu Oct  5 15:23:47 2017
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2015-01-23 (985 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MostRecentCrashID: bp-8649eb9a-09b9-49fc-8320-99cbf1171004
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=56.0/20171003222101 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-8649eb9a-09b9-49fc-8320-99cbf1171004
   bp-604f3b87-472e-4026-8588-3d2122160725
   bp-1cd058b7-bfd2-4105-a9b4-1852d2160703
   bp-b5b0d8b4-2b5b-40f5-b468-f5eec2160122
   bp-aba8367f-3da0-4f1c-9342-b377f2151224
  UpgradeStatus: Upgraded to artful on 2017-06-15 (112 days ago)
  dmi.bios.date: 03/30/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN43WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN43WW:bd03/30/2015:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1721614] Re: Firefox menus are misplaced

[Thorsten Munsch]

Starting with --safe-mode gets the burger menu working properly again.

In my profile I loaded the menu defaults via customization, doesn't
solve it.

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

Title:
  Firefox menus are misplaced

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Sometimes Firefox places its menus at incorrect locations. See attached 
screenshot and video. This happens at least with the main (hamburger icon) 
menu, bookmark folders, and context menu. Moving the Firefox window temporarily 
solves the problem. It usually happens after resume from suspend, which in 
general in my case is accompanied by a display reconfiguration (unplug external 
monitor, suspend, resume, plug other external monitor).
  This looks very similar to this another bug 
(https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1641629) which I 
reported against Firefox 49 and that was resolved by installing Firefox 52. 
This time, it occurred in Firefox 55, and also now in Firefox 56. It started 
occurring sometime during the 17.10 cycle, which I have been using for a few 
months.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: firefox 56.0+build6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   gpothier   2684 F...m pulseaudio
   /dev/snd/controlC1:  gpothier   2684 F pulseaudio
   /dev/snd/controlC0:  gpothier   2684 F pulseaudio
  BuildID: 20171003222101
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Thu Oct  5 15:23:47 2017
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2015-01-23 (985 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MostRecentCrashID: bp-8649eb9a-09b9-49fc-8320-99cbf1171004
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=56.0/20171003222101 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-8649eb9a-09b9-49fc-8320-99cbf1171004
   bp-604f3b87-472e-4026-8588-3d2122160725
   bp-1cd058b7-bfd2-4105-a9b4-1852d2160703
   bp-b5b0d8b4-2b5b-40f5-b468-f5eec2160122
   bp-aba8367f-3da0-4f1c-9342-b377f2151224
  UpgradeStatus: Upgraded to artful on 2017-06-15 (112 days ago)
  dmi.bios.date: 03/30/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN43WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN43WW:bd03/30/2015:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1721614] Re: Firefox menus are misplaced

[Thorsten Munsch]

But in 58.0a1 no button menu is drawn correct. Only the bookmark button
toggles the bookmarklist on the left of the window (uBlock, NoScript &
burger menu).

In 56 uBlock & NoScript buttons worked properly. Only the burger did
not.

In 58 no one, except the bookmark-toggle. In 56 the button is different
and doesn't toggle the list.

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

Title:
  Firefox menus are misplaced

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Sometimes Firefox places its menus at incorrect locations. See attached 
screenshot and video. This happens at least with the main (hamburger icon) 
menu, bookmark folders, and context menu. Moving the Firefox window temporarily 
solves the problem. It usually happens after resume from suspend, which in 
general in my case is accompanied by a display reconfiguration (unplug external 
monitor, suspend, resume, plug other external monitor).
  This looks very similar to this another bug 
(https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1641629) which I 
reported against Firefox 49 and that was resolved by installing Firefox 52. 
This time, it occurred in Firefox 55, and also now in Firefox 56. It started 
occurring sometime during the 17.10 cycle, which I have been using for a few 
months.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: firefox 56.0+build6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   gpothier   2684 F...m pulseaudio
   /dev/snd/controlC1:  gpothier   2684 F pulseaudio
   /dev/snd/controlC0:  gpothier   2684 F pulseaudio
  BuildID: 20171003222101
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Thu Oct  5 15:23:47 2017
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2015-01-23 (985 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MostRecentCrashID: bp-8649eb9a-09b9-49fc-8320-99cbf1171004
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=56.0/20171003222101 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-8649eb9a-09b9-49fc-8320-99cbf1171004
   bp-604f3b87-472e-4026-8588-3d2122160725
   bp-1cd058b7-bfd2-4105-a9b4-1852d2160703
   bp-b5b0d8b4-2b5b-40f5-b468-f5eec2160122
   bp-aba8367f-3da0-4f1c-9342-b377f2151224
  UpgradeStatus: Upgraded to artful on 2017-06-15 (112 days ago)
  dmi.bios.date: 03/30/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN43WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN43WW:bd03/30/2015:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1721614] Re: Firefox menus are misplaced

[Thorsten Munsch]

Tested 58.0a1 tarball -> burger menu not visible but works if you know
the button position. ;-)

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

Title:
  Firefox menus are misplaced

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Sometimes Firefox places its menus at incorrect locations. See attached 
screenshot and video. This happens at least with the main (hamburger icon) 
menu, bookmark folders, and context menu. Moving the Firefox window temporarily 
solves the problem. It usually happens after resume from suspend, which in 
general in my case is accompanied by a display reconfiguration (unplug external 
monitor, suspend, resume, plug other external monitor).
  This looks very similar to this another bug 
(https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1641629) which I 
reported against Firefox 49 and that was resolved by installing Firefox 52. 
This time, it occurred in Firefox 55, and also now in Firefox 56. It started 
occurring sometime during the 17.10 cycle, which I have been using for a few 
months.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: firefox 56.0+build6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   gpothier   2684 F...m pulseaudio
   /dev/snd/controlC1:  gpothier   2684 F pulseaudio
   /dev/snd/controlC0:  gpothier   2684 F pulseaudio
  BuildID: 20171003222101
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Thu Oct  5 15:23:47 2017
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2015-01-23 (985 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MostRecentCrashID: bp-8649eb9a-09b9-49fc-8320-99cbf1171004
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=56.0/20171003222101 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-8649eb9a-09b9-49fc-8320-99cbf1171004
   bp-604f3b87-472e-4026-8588-3d2122160725
   bp-1cd058b7-bfd2-4105-a9b4-1852d2160703
   bp-b5b0d8b4-2b5b-40f5-b468-f5eec2160122
   bp-aba8367f-3da0-4f1c-9342-b377f2151224
  UpgradeStatus: Upgraded to artful on 2017-06-15 (112 days ago)
  dmi.bios.date: 03/30/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN43WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN43WW:bd03/30/2015:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1721614] Re: Firefox menus are misplaced

[Thorsten Munsch]

I'm affected of the "invisible" burger menu aswell. After click hovering
over it shows there are the menu buttons below.

I didn't notice the problems with the bookmarkbar or context menus
mentioned by gpothier.

Burger button stopped being displayed normal since FF56. Downloaded the
FF56.01 tarball, same behaviour.

Xubuntu 14.04.5 LTS (4.4.0-97-lowlatency)
Firefox 56.0+build6-0ubuntu0.14.04.2

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

Title:
  Firefox menus are misplaced

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Sometimes Firefox places its menus at incorrect locations. See attached 
screenshot and video. This happens at least with the main (hamburger icon) 
menu, bookmark folders, and context menu. Moving the Firefox window temporarily 
solves the problem. It usually happens after resume from suspend, which in 
general in my case is accompanied by a display reconfiguration (unplug external 
monitor, suspend, resume, plug other external monitor).
  This looks very similar to this another bug 
(https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1641629) which I 
reported against Firefox 49 and that was resolved by installing Firefox 52. 
This time, it occurred in Firefox 55, and also now in Firefox 56. It started 
occurring sometime during the 17.10 cycle, which I have been using for a few 
months.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: firefox 56.0+build6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   gpothier   2684 F...m pulseaudio
   /dev/snd/controlC1:  gpothier   2684 F pulseaudio
   /dev/snd/controlC0:  gpothier   2684 F pulseaudio
  BuildID: 20171003222101
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Thu Oct  5 15:23:47 2017
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2015-01-23 (985 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MostRecentCrashID: bp-8649eb9a-09b9-49fc-8320-99cbf1171004
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=56.0/20171003222101 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-8649eb9a-09b9-49fc-8320-99cbf1171004
   bp-604f3b87-472e-4026-8588-3d2122160725
   bp-1cd058b7-bfd2-4105-a9b4-1852d2160703
   bp-b5b0d8b4-2b5b-40f5-b468-f5eec2160122
   bp-aba8367f-3da0-4f1c-9342-b377f2151224
  UpgradeStatus: Upgraded to artful on 2017-06-15 (112 days ago)
  dmi.bios.date: 03/30/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN43WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN43WW:bd03/30/2015:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM

[Thorsten Munsch]

I can confirm this one on (X)ubuntu 14.04.5 LTS with XFCE 4.10 desktop.

The suggested fixes work for me aswell.

Another problem appears when bluetooth is disabled on boot (which I
always do because of paranoia ;)).

Both Pulseaudio modules won't get loaded by my XFCE autostart script. I
have to run it again after bluetooth is enabled manually.

Then my JBL Flip 3 speaker appers instantly in the Pulseaudio settings
besides the onboard sound device.

Everything else works like a charm.

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

Title:
  Bluetooth audio devices/profiles are missing after logging in from GDM

Status in gdm:
  Confirmed
Status in PulseAudio:
  Confirmed
Status in gdm3 package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Triaged
Status in gdm3 source package in Xenial:
  Triaged
Status in pulseaudio source package in Xenial:
  Triaged
Status in gdm3 source package in Zesty:
  Triaged
Status in pulseaudio source package in Zesty:
  Triaged
Status in gdm3 package in Debian:
  New

Bug description:
  This is actually a PulseAudio bug, but the workaround is to disable
  Bluetooth audio in GDM.

  Further discussion (and the source of my understanding about this
  issue) upstream are here:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805414

  To summarise:

  GDM opens the A2DP profile for a11y purposes to allow screenreaders to
  output over BT audio devices. However Pulse doesn't release those
  devices when no audio is being played and the upshot is that once in
  the users session A2DP is not available for any Bluetooth audio
  devices, this means that you can only use the low quality profile
  HSP/HFP.

  There is a proposed workaround, but this means that a11y tools which
  need to output audio won't be able to use Bluetooth devices within
  GDM.

  I think that for 17.10 shipping this work-around is acceptable, and we
  should revisit in the 18.04 cycle to try and get a proper fix in PA.
  The suggested PA bug is:

  https://bugs.freedesktop.org/show_bug.cgi?id=57167

  but that hasn't seen movement since 2012.

  = The work around =

  From the Debian wiki:  https://wiki.debian.org/BluetoothUser/a2dp

  Disable the Bluetooth sink in the GDM PA daemon.

  Add this to /var/lib/gdm3/.config/pulse/default.pa

  #!/usr/bin/pulseaudio -nF
  #

  # load system wide configuration
  .include /etc/pulse/default.pa

  ### unload driver modules for Bluetooth hardware
  .ifexists module-bluetooth-policy.so
unload-module module-bluetooth-policy
  .endif

  .ifexists module-bluetooth-discover.so
unload-module module-bluetooth-discover
  .endif


  I have tested this, and I can confirm that it allows access to A2DP
  again in the user session.

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

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

[Desktop-packages] [Bug 1130571] Re: wired network disabled after resume (AR9485)

[Thorsten Greeb]

Interesting: Today network-manager 1.2.4 was published in "Xenial
(16.04) proposed" which contains the cherry-picked fix from 1.2.6...

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

Title:
  wired network disabled after resume (AR9485)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have both a wired network and wireless. On first boot both are
  functional, but on resuming from sleep the wired controller is
  disabled (wireless still works). This behaviour started with the
  latest kernel installed yesterday.

  From syslog on resume

  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  Unmanaged Device 
found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  Unmanaged Device 
found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  (eth4): now managed
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  (eth4): device state 
change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  (eth4): bringing up 
device.
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  (eth4): deactivating 
device (reason 'managed') [2]

   uname -a
  Linux mark-PBL21 3.5.0-24-generic #37-Ubuntu SMP Thu Feb 7 01:50:30 UTC 2013 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo lshw -C network
  [sudo] password for mthornton: 
*-network   
 description: Wireless interface
 product: AR9485 Wireless Network Adapter
 vendor: Atheros Communications Inc.
 physical id: 0
 bus info: pci@:03:00.0
 logical name: wlan3
 version: 01
 serial: dc:85:de:03:c8:ce
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list rom ethernet 
physical wireless
 configuration: broadcast=yes driver=ath9k 
driverversion=3.5.0-24-generic firmware=N/A ip=192.168.41.214 latency=0 
link=yes multicast=yes wireless=IEEE 802.11bgn
 resources: irq:17 memory:f790-f797 memory:f798-f798
*-network DISABLED
 description: Ethernet interface
 product: AR8161 Gigabit Ethernet
 vendor: Atheros Communications Inc.
 physical id: 0
 bus info: pci@:04:00.0
 logical name: eth4
 version: 10
 serial: 10:bf:48:9f:e9:c6
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi msix bus_master cap_list ethernet 
physical
 configuration: broadcast=yes driver=alx latency=0 multicast=yes
 resources: irq:19 memory:f780-f783 ioport:d000(size=128)

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

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

[Desktop-packages] [Bug 1130571] Re: wired network disabled after resume (AR9485)

[Thorsten Greeb]

I also have this problem on several machines running Ubuntu 16.04. After
resume from suspend no IPv4 address is assigned to the network
interfaces (both wired and wireless). Seems to be not related to
hardware or driver but to NetworkManager.

Maybe this (known) problem is corrected in version 1.2.6 (see change
log).

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

Title:
  wired network disabled after resume (AR9485)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have both a wired network and wireless. On first boot both are
  functional, but on resuming from sleep the wired controller is
  disabled (wireless still works). This behaviour started with the
  latest kernel installed yesterday.

  From syslog on resume

  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  Unmanaged Device 
found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  Unmanaged Device 
found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  (eth4): now managed
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  (eth4): device state 
change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  (eth4): bringing up 
device.
  Feb 20 08:48:31 mark-PBL21 NetworkManager[1109]:  (eth4): deactivating 
device (reason 'managed') [2]

   uname -a
  Linux mark-PBL21 3.5.0-24-generic #37-Ubuntu SMP Thu Feb 7 01:50:30 UTC 2013 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo lshw -C network
  [sudo] password for mthornton: 
*-network   
 description: Wireless interface
 product: AR9485 Wireless Network Adapter
 vendor: Atheros Communications Inc.
 physical id: 0
 bus info: pci@:03:00.0
 logical name: wlan3
 version: 01
 serial: dc:85:de:03:c8:ce
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list rom ethernet 
physical wireless
 configuration: broadcast=yes driver=ath9k 
driverversion=3.5.0-24-generic firmware=N/A ip=192.168.41.214 latency=0 
link=yes multicast=yes wireless=IEEE 802.11bgn
 resources: irq:17 memory:f790-f797 memory:f798-f798
*-network DISABLED
 description: Ethernet interface
 product: AR8161 Gigabit Ethernet
 vendor: Atheros Communications Inc.
 physical id: 0
 bus info: pci@:04:00.0
 logical name: eth4
 version: 10
 serial: 10:bf:48:9f:e9:c6
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi msix bus_master cap_list ethernet 
physical
 configuration: broadcast=yes driver=alx latency=0 multicast=yes
 resources: irq:19 memory:f780-f783 ioport:d000(size=128)

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

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

[Desktop-packages] [Bug 1422143] Re: No wifi connection after suspend with systemd due to missing "wpa_cli suspend"

[Thorsten]

I am also affected by this bug. It only occurs in ~1 out of 3
suspend/resumes and can be fixed by sudo systemctl restart
NetworkManager. I am using ubuntu 16.04, with all updates available
until today. My hardware is a thinkpad t440s with the following wlan
card Intel Corporation Wireless 7260 (rev 83).

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

Title:
  No wifi connection after suspend with systemd due to missing "wpa_cli
  suspend"

Status in One Hundred Papercuts:
  Confirmed
Status in NetworkManager:
  Unknown
Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Wily:
  Fix Committed
Status in wpa source package in Xenial:
  Fix Released

Bug description:
  Using systemd as my default init system if I resume from suspend my
  laptop, it doesn't automatically reconnect to the wireless network and
  it doesn't list the available network connections.

  The only way to get a wireless connection is to restart the network-
  manager daemon or going to the gnome-control-center, disable wireless
  and enable it again.

  SRU INFORMATION
  ===
  In some of these cases this bug can be worked around by calling "wpa_cli 
suspend/resume" before/after suspend, like we used to do with the old pm-utils 
quirks (/usr/lib/pm-utils/sleep.d/60_wpa_supplicant). This only affects 
particular hardware, and thus this needs to be tested by affected reporters, 
there is no general reproducer for arbitrary systems.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu6
  Uname: Linux 3.19.0-031900-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Sun Feb 15 18:27:39 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-10-22 (116 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  IpRoute:
   default via 10.0.0.1 dev wlan0  proto static  metric 1024
   10.0.0.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.36
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-01-13 (32 days ago)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlan0wifi  connected/org/freedesktop/NetworkManager/Devices/2  
openhost_caldas  09d1f69d-d3da-4978-a69c-d94455db7ecf  
/org/freedesktop/NetworkManager/ActiveConnection/0
   docker0  bridgeunavailable  /org/freedesktop/NetworkManager/Devices/3  
--   ----
   eth0 ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--   ----
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--   ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1589836] Re: package libxml2-utils 2.9.3+dfsg1-1 failed to install/upgrade: krijg geen toegang tot archief: Bestand of map bestaat niet

[Thorsten Glaser]

AUB niet de files verwijderen tijdens apt nog aan’t werken is.

Probeer es:

$ sudo apt-get update
$ sudo apt-get -f install

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

Title:
  package libxml2-utils 2.9.3+dfsg1-1 failed to install/upgrade: krijg
  geen toegang tot archief: Bestand of map bestaat niet

Status in libxml2 package in Ubuntu:
  Invalid

Bug description:
  The package failed to upgrade in the terminal.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libxml2-utils 2.9.3+dfsg1-1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Jun  7 09:40:41 2016
  ErrorMessage: krijg geen toegang tot archief: Bestand of map bestaat niet
  InstallationDate: Installed on 2016-04-23 (44 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: libxml2
  Title: package libxml2-utils 2.9.3+dfsg1-1 failed to install/upgrade: krijg 
geen toegang tot archief: Bestand of map bestaat niet
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1589679] Re: package libxml2 2.9.3+dfsg1-1 failed to install/upgrade: unable to securely remove '/usr/share/doc/libxml2/AUTHORS.dpkg-new': Read-only file system

[Thorsten Glaser]

I suggest to learn to read.

Mount your filesystems read-write when you install packages.

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

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

Title:
  package libxml2 2.9.3+dfsg1-1 failed to install/upgrade: unable to
  securely remove '/usr/share/doc/libxml2/AUTHORS.dpkg-new': Read-only
  file system

Status in libxml2 package in Ubuntu:
  Invalid

Bug description:
  occur when i update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libxml2 2.9.3+dfsg1-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Mon Jun  6 17:10:44 2016
  DuplicateSignature:
   package:libxml2:2.9.3+dfsg1-1
   Unpacking libxml2:i386 (2.9.3+dfsg1-1ubuntu0.1) over (2.9.3+dfsg1-1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libxml2_2.9.3+dfsg1-1ubuntu0.1_i386.deb (--unpack):
unable to securely remove '/usr/share/doc/libxml2/AUTHORS.dpkg-new': 
Read-only file system
  ErrorMessage: unable to securely remove 
'/usr/share/doc/libxml2/AUTHORS.dpkg-new': Read-only file system
  InstallationDate: Installed on 2016-05-26 (10 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: libxml2
  Title: package libxml2 2.9.3+dfsg1-1 failed to install/upgrade: unable to 
securely remove '/usr/share/doc/libxml2/AUTHORS.dpkg-new': Read-only file system
  UpgradeStatus: Upgraded to xenial on 2016-05-27 (10 days ago)

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

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

[Desktop-packages] [Bug 1438494] Re: ghostscript fails to correctly substitute cidf fonts

[Thorsten]

Thanks a lot! I created a new bug report, which is hopefully accurate
enough:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1525225

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

Title:
  ghostscript fails to correctly substitute cidf fonts

Status in poppler-data package in Ubuntu:
  Triaged

Bug description:
  I reported this bug first with ghostscript
  (http://bugs.ghostscript.com/show_bug.cgi?id=695874), but it is
  apparently a packaging issue.

  The general issue is that when there is a CIDF font in a .pdf that is
  not embedded in the document, ghostscript will stop processing the
  file at that font (see the file attached to the ghostscript bug).  The
  packaging issue is that CIDF fonts that are not on the system are in
  the default Ubuntu cidfmap file.

  System info is:

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.10
  Release:14.10
  Codename:   utopic

  $ ghostscript --version
  9.14

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

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

[Desktop-packages] [Bug 1525225] [NEW] gs has issues with pdfs which only consist of large images

[Thorsten]

Public bug reported:

Hello,

there seems to be a bug in the version 9.16 of ghostscript which prevents using 
ghostscript with pdfs created by some canon scanners which only consist of 
large images.
I wrongly associated this error with the following bug 
https://bugs.launchpad.net/ubuntu/+source/poppler-data/+bug/1438494, however 
cliddell corrected me and also directly pointed to his committed patch:
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=668406a5 which should 
fix this issue.

With version 9.18 from http://www.ghostscript.com/download/gsdnld.html
its working flawlessly.

The bug occurs when attempting to minimize the file size of such a pdf
and the following error message is shown: (an example pdf is attached to
this post)

$ gs -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -dCompatibilityLevel=1.4 
-dPDFSETTINGS=/printer -sOutputFile=out.pdf SCN_0002.pdf
GPL Ghostscript 9.16 (2015-03-30)
Copyright (C) 2015 Artifex Software, Inc. All rights reserved.
This software comes with NO WARRANTY: see the file PUBLIC for details.
Processing pages 1 through 1.
Page 1
 Error reading a content stream. The page may be incomplete.
 File did not complete the page properly and may be damaged.

 This file had errors that were repaired or ignored.
 The file was produced by:
  MP540 series 
 Please notify the author of the software that produced this
 file that it does not conform to Adobe's published PDF
 specification.

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

** Attachment added: "SCN_0002.pdf"
   
https://bugs.launchpad.net/bugs/1525225/+attachment/4533172/+files/SCN_0002.pdf

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

Title:
  gs has issues with pdfs which only consist of large images

Status in ghostscript package in Ubuntu:
  New

Bug description:
  Hello,

  there seems to be a bug in the version 9.16 of ghostscript which prevents 
using ghostscript with pdfs created by some canon scanners which only consist 
of large images.
  I wrongly associated this error with the following bug 
https://bugs.launchpad.net/ubuntu/+source/poppler-data/+bug/1438494, however 
cliddell corrected me and also directly pointed to his committed patch:
  http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=668406a5 which 
should fix this issue.

  With version 9.18 from http://www.ghostscript.com/download/gsdnld.html
  its working flawlessly.

  The bug occurs when attempting to minimize the file size of such a pdf
  and the following error message is shown: (an example pdf is attached
  to this post)

  $ gs -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -dCompatibilityLevel=1.4 
-dPDFSETTINGS=/printer -sOutputFile=out.pdf SCN_0002.pdf
  GPL Ghostscript 9.16 (2015-03-30)
  Copyright (C) 2015 Artifex Software, Inc. All rights reserved.
  This software comes with NO WARRANTY: see the file PUBLIC for details.
  Processing pages 1 through 1.
  Page 1
   Error reading a content stream. The page may be incomplete.
   File did not complete the page properly and may be damaged.

   This file had errors that were repaired or ignored.
   The file was produced by:
    MP540 series 
   Please notify the author of the software that produced this
   file that it does not conform to Adobe's published PDF
   specification.

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

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

[Desktop-packages] [Bug 1438494] Re: ghostscript fails to correctly substitute cidf fonts

[Thorsten]

Does this bug also occur if there are no embedded fonts in a pdf? Because my 
canon scanner seems to produce pdfs  without embedded fonts, at least pdffonts 
shows no fonts:
$ pdffonts SCN_0002.pdf 
name type  encoding emb sub 
uni object ID
 -  --- --- 
--- -

 and i get a very similar error when trying to minimize the filesize
with ghostscript:

$ gs -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -dCompatibilityLevel=1.4 
-dPDFSETTINGS=/printer  -sOutputFile=out.pdf SCN_0002.pdf 
GPL Ghostscript 9.16 (2015-03-30)
Copyright (C) 2015 Artifex Software, Inc.  All rights reserved.
This software comes with NO WARRANTY: see the file PUBLIC for details.
Processing pages 1 through 1.
Page 1
    Error reading a content stream. The page may be incomplete.
    File did not complete the page properly and may be damaged.

    This file had errors that were repaired or ignored.
    The file was produced by: 
     MP540 series 
    Please notify the author of the software that produced this
    file that it does not conform to Adobe's published PDF
    specification.

With the minimal gs version from
http://www.ghostscript.com/download/gsdnld.html its working flawlessly.

i attached a pdf created by my scanner to this comment.

(i m using ubuntu 15.10)


** Attachment added: "SCN_0002.pdf"
   
https://bugs.launchpad.net/ubuntu/+source/poppler-data/+bug/1438494/+attachment/4532873/+files/SCN_0002.pdf

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

Title:
  ghostscript fails to correctly substitute cidf fonts

Status in poppler-data package in Ubuntu:
  Triaged

Bug description:
  I reported this bug first with ghostscript
  (http://bugs.ghostscript.com/show_bug.cgi?id=695874), but it is
  apparently a packaging issue.

  The general issue is that when there is a CIDF font in a .pdf that is
  not embedded in the document, ghostscript will stop processing the
  file at that font (see the file attached to the ghostscript bug).  The
  packaging issue is that CIDF fonts that are not on the system are in
  the default Ubuntu cidfmap file.

  System info is:

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.10
  Release:14.10
  Codename:   utopic

  $ ghostscript --version
  9.14

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

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

[Desktop-packages] [Bug 1474003] Re: Firefox 39 keeps crashing

[Thorsten Munsch]

I don't know if there is a ppa for Firefox 38.

- Purge Firefox 39
- Download and install Firefox 38 
(https://launchpad.net/~ubuntu-mozilla-security/+archive/ubuntu/ppa/+build/7412429)
- Open a terminal and hold the package with "sudo apt-mark hold firefox"

Don't forget to unhold, when we know what's causing the issue.

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

Title:
  Firefox 39 keeps crashing

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

Bug description:
  Firefox 39 keeps crashing after update from Firefox 38.
  Crashes are random but when idle happens at least once a hour or more 
frequently when actively used.

  When replaced with binaries from Mozilla there is no problems at same
  machine with same profile.

  There are at least 1100 identical reports and they seems to be unique
  for Ubuntu build.

  # cat /proc/cpuinfo 
  processor : 0
  vendor_id : GenuineIntel
  cpu family: 6
  model : 42
  model name: Intel(R) Celeron(R) CPU 847 @ 1.10GHz
  stepping  : 7
  microcode : 0x28
  cpu MHz   : 892.546
  cache size: 2048 KB
  physical id   : 0
  siblings  : 2
  core id   : 0
  cpu cores : 2
  apicid: 0
  initial apicid: 0
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 13
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 
xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave lahf_lm 
arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid xsaveopt
  bugs  :
  bogomips  : 2195.00
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 36 bits physical, 48 bits virtual
  power management:

  
  Below is part of crash report:

  Crashing Thread
  Frame Module  Signature   Source
  0 libxul.so   mozilla::dom::CrashReporterParent::GenerateChildData
/build/firefox-4CFcvq/firefox-39.0+build5/dom/ipc/CrashReporterParent.cpp:114
  1 libxul.so   
mozilla::plugins::PluginModuleChromeParent::ProcessFirstMinidump
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1415
  2 libxul.so   
mozilla::plugins::PluginModuleChromeParent::ActorDestroy
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1503
  3 libxul.so   mozilla::plugins::PPluginModuleParent::DestroySubtree   
/build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1588
  4 libxul.so   mozilla::plugins::PPluginModuleParent::OnChannelError   
/build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1462
  5 libxul.so   mozilla::ipc::MessageChannel::NotifyMaybeChannelError   
/build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1622
  6 libxul.so   mozilla::ipc::MessageChannel::Close 
/build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1744
  7 libxul.so   mozilla::plugins::PluginModuleParent::DoShutdown
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2326
  8 libxul.so   mozilla::plugins::PluginModuleParent::NP_Shutdown   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2307
  9 libxul.so   
mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:705
  10libxul.so   
mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:741
  11libxul.so   nsNPAPIPlugin::~nsNPAPIPlugin   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:237
  12libxul.so   nsNPAPIPlugin::~nsNPAPIPlugin   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:239
  13libxul.so   nsNPAPIPlugin::Release  
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:224
  14libxul.so   nsPluginHost::Notify
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsPluginHost.cpp:3716
  15libxul.so   nsTimerImpl::Fire   
/build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:634
  16libxul.so   nsTimerEvent::Run   
/build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:724
  17libxul.so   nsThread::ProcessNextEvent  
/build/firefox-4CFcvq/firefox-39.0+build5/xpcom/th

[Desktop-packages] [Bug 1474003] Re: Firefox 39 keeps crashing

[Thorsten Munsch]

Downgraded to Firefox 38 from the Trusty repo, still no crash with
pepperflash and 18.0.0.209 since half an hour...

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

Title:
  Firefox 39 keeps crashing

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

Bug description:
  Firefox 39 keeps crashing after update from Firefox 38.
  Crashes are random but when idle happens at least once a hour or more 
frequently when actively used.

  When replaced with binaries from Mozilla there is no problems at same
  machine with same profile.

  There are at least 1100 identical reports and they seems to be unique
  for Ubuntu build.

  # cat /proc/cpuinfo 
  processor : 0
  vendor_id : GenuineIntel
  cpu family: 6
  model : 42
  model name: Intel(R) Celeron(R) CPU 847 @ 1.10GHz
  stepping  : 7
  microcode : 0x28
  cpu MHz   : 892.546
  cache size: 2048 KB
  physical id   : 0
  siblings  : 2
  core id   : 0
  cpu cores : 2
  apicid: 0
  initial apicid: 0
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 13
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 
xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave lahf_lm 
arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid xsaveopt
  bugs  :
  bogomips  : 2195.00
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 36 bits physical, 48 bits virtual
  power management:

  
  Below is part of crash report:

  Crashing Thread
  Frame Module  Signature   Source
  0 libxul.so   mozilla::dom::CrashReporterParent::GenerateChildData
/build/firefox-4CFcvq/firefox-39.0+build5/dom/ipc/CrashReporterParent.cpp:114
  1 libxul.so   
mozilla::plugins::PluginModuleChromeParent::ProcessFirstMinidump
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1415
  2 libxul.so   
mozilla::plugins::PluginModuleChromeParent::ActorDestroy
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1503
  3 libxul.so   mozilla::plugins::PPluginModuleParent::DestroySubtree   
/build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1588
  4 libxul.so   mozilla::plugins::PPluginModuleParent::OnChannelError   
/build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1462
  5 libxul.so   mozilla::ipc::MessageChannel::NotifyMaybeChannelError   
/build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1622
  6 libxul.so   mozilla::ipc::MessageChannel::Close 
/build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1744
  7 libxul.so   mozilla::plugins::PluginModuleParent::DoShutdown
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2326
  8 libxul.so   mozilla::plugins::PluginModuleParent::NP_Shutdown   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2307
  9 libxul.so   
mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:705
  10libxul.so   
mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:741
  11libxul.so   nsNPAPIPlugin::~nsNPAPIPlugin   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:237
  12libxul.so   nsNPAPIPlugin::~nsNPAPIPlugin   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:239
  13libxul.so   nsNPAPIPlugin::Release  
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:224
  14libxul.so   nsPluginHost::Notify
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsPluginHost.cpp:3716
  15libxul.so   nsTimerImpl::Fire   
/build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:634
  16libxul.so   nsTimerEvent::Run   
/build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:724
  17libxul.so   nsThread::ProcessNextEvent  
/build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsThread.cpp:855
  18libxul.so   NS_ProcessNextEvent 
/build/firefox-4CFcvq/firefox-39.0+build5/xpcom/glue/nsThreadUtils.cpp:265
  19libxul.so   mozilla::ipc::MessagePump::Run  
/bu

[Desktop-packages] [Bug 1474003] Re: Firefox 39 keeps crashing

[Thorsten Munsch]

So, little update here. As I've sent #24 Firefox 39 crashed on my
notebook, too!

I googled for the freshplayer Bug, but only found
https://support.mozilla.org/en-US/questions/1071421 which suggest, that
Firefox 40 developer doesn't crash with freshplayer.

After downloading I copied all my profile data into the dev-profile,
started FF40 and it crashed.

Created a new profile without any data import -> Firefox 40 crashed.

Downgraded to Flash 11.2 from the official repo -> Firefox 40 crashed.

Tried Firefox 39 from the repo with 11.2 from the repo -> Firefox 39
crashed!

So this is a Firefox bug, because it exists since the update to 39 from
the official Ubuntu 14.04 repos.

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

Title:
  Firefox 39 keeps crashing

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

Bug description:
  Firefox 39 keeps crashing after update from Firefox 38.
  Crashes are random but when idle happens at least once a hour or more 
frequently when actively used.

  When replaced with binaries from Mozilla there is no problems at same
  machine with same profile.

  There are at least 1100 identical reports and they seems to be unique
  for Ubuntu build.

  # cat /proc/cpuinfo 
  processor : 0
  vendor_id : GenuineIntel
  cpu family: 6
  model : 42
  model name: Intel(R) Celeron(R) CPU 847 @ 1.10GHz
  stepping  : 7
  microcode : 0x28
  cpu MHz   : 892.546
  cache size: 2048 KB
  physical id   : 0
  siblings  : 2
  core id   : 0
  cpu cores : 2
  apicid: 0
  initial apicid: 0
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 13
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 
xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave lahf_lm 
arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid xsaveopt
  bugs  :
  bogomips  : 2195.00
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 36 bits physical, 48 bits virtual
  power management:

  
  Below is part of crash report:

  Crashing Thread
  Frame Module  Signature   Source
  0 libxul.so   mozilla::dom::CrashReporterParent::GenerateChildData
/build/firefox-4CFcvq/firefox-39.0+build5/dom/ipc/CrashReporterParent.cpp:114
  1 libxul.so   
mozilla::plugins::PluginModuleChromeParent::ProcessFirstMinidump
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1415
  2 libxul.so   
mozilla::plugins::PluginModuleChromeParent::ActorDestroy
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1503
  3 libxul.so   mozilla::plugins::PPluginModuleParent::DestroySubtree   
/build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1588
  4 libxul.so   mozilla::plugins::PPluginModuleParent::OnChannelError   
/build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1462
  5 libxul.so   mozilla::ipc::MessageChannel::NotifyMaybeChannelError   
/build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1622
  6 libxul.so   mozilla::ipc::MessageChannel::Close 
/build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1744
  7 libxul.so   mozilla::plugins::PluginModuleParent::DoShutdown
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2326
  8 libxul.so   mozilla::plugins::PluginModuleParent::NP_Shutdown   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2307
  9 libxul.so   
mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:705
  10libxul.so   
mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:741
  11libxul.so   nsNPAPIPlugin::~nsNPAPIPlugin   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:237
  12libxul.so   nsNPAPIPlugin::~nsNPAPIPlugin   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:239
  13libxul.so   nsNPAPIPlugin::Release  
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:224
  14libxul.so   nsPluginHost::Notify
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsPluginHost.cpp:37

[Desktop-packages] [Bug 1474003] Re: Firefox 39 keeps crashing

[Thorsten Munsch]

The Xfce 4.10 is my machine in the office, not at home.

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

Title:
  Firefox 39 keeps crashing

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

Bug description:
  Firefox 39 keeps crashing after update from Firefox 38.
  Crashes are random but when idle happens at least once a hour or more 
frequently when actively used.

  When replaced with binaries from Mozilla there is no problems at same
  machine with same profile.

  There are at least 1100 identical reports and they seems to be unique
  for Ubuntu build.

  # cat /proc/cpuinfo 
  processor : 0
  vendor_id : GenuineIntel
  cpu family: 6
  model : 42
  model name: Intel(R) Celeron(R) CPU 847 @ 1.10GHz
  stepping  : 7
  microcode : 0x28
  cpu MHz   : 892.546
  cache size: 2048 KB
  physical id   : 0
  siblings  : 2
  core id   : 0
  cpu cores : 2
  apicid: 0
  initial apicid: 0
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 13
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 
xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave lahf_lm 
arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid xsaveopt
  bugs  :
  bogomips  : 2195.00
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 36 bits physical, 48 bits virtual
  power management:

  
  Below is part of crash report:

  Crashing Thread
  Frame Module  Signature   Source
  0 libxul.so   mozilla::dom::CrashReporterParent::GenerateChildData
/build/firefox-4CFcvq/firefox-39.0+build5/dom/ipc/CrashReporterParent.cpp:114
  1 libxul.so   
mozilla::plugins::PluginModuleChromeParent::ProcessFirstMinidump
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1415
  2 libxul.so   
mozilla::plugins::PluginModuleChromeParent::ActorDestroy
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1503
  3 libxul.so   mozilla::plugins::PPluginModuleParent::DestroySubtree   
/build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1588
  4 libxul.so   mozilla::plugins::PPluginModuleParent::OnChannelError   
/build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1462
  5 libxul.so   mozilla::ipc::MessageChannel::NotifyMaybeChannelError   
/build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1622
  6 libxul.so   mozilla::ipc::MessageChannel::Close 
/build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1744
  7 libxul.so   mozilla::plugins::PluginModuleParent::DoShutdown
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2326
  8 libxul.so   mozilla::plugins::PluginModuleParent::NP_Shutdown   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2307
  9 libxul.so   
mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:705
  10libxul.so   
mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:741
  11libxul.so   nsNPAPIPlugin::~nsNPAPIPlugin   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:237
  12libxul.so   nsNPAPIPlugin::~nsNPAPIPlugin   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:239
  13libxul.so   nsNPAPIPlugin::Release  
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:224
  14libxul.so   nsPluginHost::Notify
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsPluginHost.cpp:3716
  15libxul.so   nsTimerImpl::Fire   
/build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:634
  16libxul.so   nsTimerEvent::Run   
/build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:724
  17libxul.so   nsThread::ProcessNextEvent  
/build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsThread.cpp:855
  18libxul.so   NS_ProcessNextEvent 
/build/firefox-4CFcvq/firefox-39.0+build5/xpcom/glue/nsThreadUtils.cpp:265
  19libxul.so   mozilla::ipc::MessagePump::Run  
/build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessagePump.

[Desktop-packages] [Bug 1474003] Re: Firefox 39 keeps crashing

[Thorsten Munsch]

@Matt: Thanks.

@Chris: Sorry for not mentioning the pepperflash plugin. It wasn't my
intention to let you work hours for no reason.

On my notebook Firefox 39 with the same plugins/extensions run fine. I
only have this problem my workstation at home. The only difference is
that the notebook uses onboard Intel graphics and the workstation Nvidia
propritary drivers. With my 14.04 workstation with Xcfe 4.10, two AMD
cards with propritary driver and four monitors connected there's also no
problem.

Btw. 11.2.* may be still supported and gets security updates, but why
shouln't we enjoy the much much better performance of the newer flash
versions..

So you think it's a pepperflash bug?

I'll provide a gdb logfile from my workstation at home this evening,
when I find the time for it.

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

Title:
  Firefox 39 keeps crashing

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

Bug description:
  Firefox 39 keeps crashing after update from Firefox 38.
  Crashes are random but when idle happens at least once a hour or more 
frequently when actively used.

  When replaced with binaries from Mozilla there is no problems at same
  machine with same profile.

  There are at least 1100 identical reports and they seems to be unique
  for Ubuntu build.

  # cat /proc/cpuinfo 
  processor : 0
  vendor_id : GenuineIntel
  cpu family: 6
  model : 42
  model name: Intel(R) Celeron(R) CPU 847 @ 1.10GHz
  stepping  : 7
  microcode : 0x28
  cpu MHz   : 892.546
  cache size: 2048 KB
  physical id   : 0
  siblings  : 2
  core id   : 0
  cpu cores : 2
  apicid: 0
  initial apicid: 0
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 13
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 
xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave lahf_lm 
arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid xsaveopt
  bugs  :
  bogomips  : 2195.00
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 36 bits physical, 48 bits virtual
  power management:

  
  Below is part of crash report:

  Crashing Thread
  Frame Module  Signature   Source
  0 libxul.so   mozilla::dom::CrashReporterParent::GenerateChildData
/build/firefox-4CFcvq/firefox-39.0+build5/dom/ipc/CrashReporterParent.cpp:114
  1 libxul.so   
mozilla::plugins::PluginModuleChromeParent::ProcessFirstMinidump
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1415
  2 libxul.so   
mozilla::plugins::PluginModuleChromeParent::ActorDestroy
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1503
  3 libxul.so   mozilla::plugins::PPluginModuleParent::DestroySubtree   
/build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1588
  4 libxul.so   mozilla::plugins::PPluginModuleParent::OnChannelError   
/build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1462
  5 libxul.so   mozilla::ipc::MessageChannel::NotifyMaybeChannelError   
/build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1622
  6 libxul.so   mozilla::ipc::MessageChannel::Close 
/build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1744
  7 libxul.so   mozilla::plugins::PluginModuleParent::DoShutdown
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2326
  8 libxul.so   mozilla::plugins::PluginModuleParent::NP_Shutdown   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2307
  9 libxul.so   
mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:705
  10libxul.so   
mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:741
  11libxul.so   nsNPAPIPlugin::~nsNPAPIPlugin   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:237
  12libxul.so   nsNPAPIPlugin::~nsNPAPIPlugin   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:239
  13libxul.so   nsNPAPIPlugin::Release  
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:224
  14libxul.so

[Desktop-packages] [Bug 1474003] Re: Firefox 39 keeps crashing

[Thorsten Munsch]

Update: Firefox greys out when gdb stops at the message above. Quitting
gdb let's Firefox awake immediately.

I have libstdc++-dev package installed..

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

Title:
  Firefox 39 keeps crashing

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

Bug description:
  Firefox 39 keeps crashing after update from Firefox 38.
  Crashes are random but when idle happens at least once a hour or more 
frequently when actively used.

  When replaced with binaries from Mozilla there is no problems at same
  machine with same profile.

  There are at least 1100 identical reports and they seems to be unique
  for Ubuntu build.

  # cat /proc/cpuinfo 
  processor : 0
  vendor_id : GenuineIntel
  cpu family: 6
  model : 42
  model name: Intel(R) Celeron(R) CPU 847 @ 1.10GHz
  stepping  : 7
  microcode : 0x28
  cpu MHz   : 892.546
  cache size: 2048 KB
  physical id   : 0
  siblings  : 2
  core id   : 0
  cpu cores : 2
  apicid: 0
  initial apicid: 0
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 13
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 
xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave lahf_lm 
arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid xsaveopt
  bugs  :
  bogomips  : 2195.00
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 36 bits physical, 48 bits virtual
  power management:

  
  Below is part of crash report:

  Crashing Thread
  Frame Module  Signature   Source
  0 libxul.so   mozilla::dom::CrashReporterParent::GenerateChildData
/build/firefox-4CFcvq/firefox-39.0+build5/dom/ipc/CrashReporterParent.cpp:114
  1 libxul.so   
mozilla::plugins::PluginModuleChromeParent::ProcessFirstMinidump
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1415
  2 libxul.so   
mozilla::plugins::PluginModuleChromeParent::ActorDestroy
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1503
  3 libxul.so   mozilla::plugins::PPluginModuleParent::DestroySubtree   
/build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1588
  4 libxul.so   mozilla::plugins::PPluginModuleParent::OnChannelError   
/build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1462
  5 libxul.so   mozilla::ipc::MessageChannel::NotifyMaybeChannelError   
/build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1622
  6 libxul.so   mozilla::ipc::MessageChannel::Close 
/build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1744
  7 libxul.so   mozilla::plugins::PluginModuleParent::DoShutdown
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2326
  8 libxul.so   mozilla::plugins::PluginModuleParent::NP_Shutdown   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2307
  9 libxul.so   
mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:705
  10libxul.so   
mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:741
  11libxul.so   nsNPAPIPlugin::~nsNPAPIPlugin   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:237
  12libxul.so   nsNPAPIPlugin::~nsNPAPIPlugin   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:239
  13libxul.so   nsNPAPIPlugin::Release  
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:224
  14libxul.so   nsPluginHost::Notify
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsPluginHost.cpp:3716
  15libxul.so   nsTimerImpl::Fire   
/build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:634
  16libxul.so   nsTimerEvent::Run   
/build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:724
  17libxul.so   nsThread::ProcessNextEvent  
/build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsThread.cpp:855
  18libxul.so   NS_ProcessNextEvent 
/build/firefox-4CFcvq/firefox-39.0+build5/xpcom/glue/nsThreadUtils.cpp:265
  19libxul.so   m

[Desktop-packages] [Bug 1474003] Re: Firefox 39 keeps crashing

[Thorsten Munsch]

It greys out, after closing the tab with the loaded flash plugin!

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

Title:
  Firefox 39 keeps crashing

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

Bug description:
  Firefox 39 keeps crashing after update from Firefox 38.
  Crashes are random but when idle happens at least once a hour or more 
frequently when actively used.

  When replaced with binaries from Mozilla there is no problems at same
  machine with same profile.

  There are at least 1100 identical reports and they seems to be unique
  for Ubuntu build.

  # cat /proc/cpuinfo 
  processor : 0
  vendor_id : GenuineIntel
  cpu family: 6
  model : 42
  model name: Intel(R) Celeron(R) CPU 847 @ 1.10GHz
  stepping  : 7
  microcode : 0x28
  cpu MHz   : 892.546
  cache size: 2048 KB
  physical id   : 0
  siblings  : 2
  core id   : 0
  cpu cores : 2
  apicid: 0
  initial apicid: 0
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 13
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 
xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave lahf_lm 
arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid xsaveopt
  bugs  :
  bogomips  : 2195.00
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 36 bits physical, 48 bits virtual
  power management:

  
  Below is part of crash report:

  Crashing Thread
  Frame Module  Signature   Source
  0 libxul.so   mozilla::dom::CrashReporterParent::GenerateChildData
/build/firefox-4CFcvq/firefox-39.0+build5/dom/ipc/CrashReporterParent.cpp:114
  1 libxul.so   
mozilla::plugins::PluginModuleChromeParent::ProcessFirstMinidump
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1415
  2 libxul.so   
mozilla::plugins::PluginModuleChromeParent::ActorDestroy
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1503
  3 libxul.so   mozilla::plugins::PPluginModuleParent::DestroySubtree   
/build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1588
  4 libxul.so   mozilla::plugins::PPluginModuleParent::OnChannelError   
/build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1462
  5 libxul.so   mozilla::ipc::MessageChannel::NotifyMaybeChannelError   
/build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1622
  6 libxul.so   mozilla::ipc::MessageChannel::Close 
/build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1744
  7 libxul.so   mozilla::plugins::PluginModuleParent::DoShutdown
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2326
  8 libxul.so   mozilla::plugins::PluginModuleParent::NP_Shutdown   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2307
  9 libxul.so   
mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:705
  10libxul.so   
mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:741
  11libxul.so   nsNPAPIPlugin::~nsNPAPIPlugin   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:237
  12libxul.so   nsNPAPIPlugin::~nsNPAPIPlugin   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:239
  13libxul.so   nsNPAPIPlugin::Release  
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:224
  14libxul.so   nsPluginHost::Notify
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsPluginHost.cpp:3716
  15libxul.so   nsTimerImpl::Fire   
/build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:634
  16libxul.so   nsTimerEvent::Run   
/build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:724
  17libxul.so   nsThread::ProcessNextEvent  
/build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsThread.cpp:855
  18libxul.so   NS_ProcessNextEvent 
/build/firefox-4CFcvq/firefox-39.0+build5/xpcom/glue/nsThreadUtils.cpp:265
  19libxul.so   mozilla::ipc::MessagePump::Run  
/build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/Me

[Desktop-packages] [Bug 1474003] Re: Firefox 39 keeps crashing

[Thorsten Munsch]

Chris, I'm trying, but now Firefox just greys out and does nothing
anymore.

With ps -A I only see a  after the plugincontainer process. So
it died already? Nothing happens since minutes, no cpu-usage, it just
hangs.

Even killing the plugin-process doesn't work.

The last gdb message is:

Reading symbols from /usr/lib/x86_64-linux-gnu/vdpau/libvdpau_nvidia.so.1...(no 
debugging symbols found)...done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/vdpau/libvdpau_nvidia.so.1
0x7f5beb71d12d in poll () at ../sysdeps/unix/syscall-template.S:81
81  ../sysdeps/unix/syscall-template.S: Datei oder Verzeichnis nicht 
gefunden.
Traceback (most recent call last):
  File 
"/usr/share/gdb/auto-load/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19-gdb.py", 
line 63, in 
from libstdcxx.v6.printers import register_libstdcxx_printers
ImportError: No module named 'libstdcxx'
(gdb) t a a bt f
Cannot find new threads: generic error
(gdb)

I don't know if that's related to this...

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

Title:
  Firefox 39 keeps crashing

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

Bug description:
  Firefox 39 keeps crashing after update from Firefox 38.
  Crashes are random but when idle happens at least once a hour or more 
frequently when actively used.

  When replaced with binaries from Mozilla there is no problems at same
  machine with same profile.

  There are at least 1100 identical reports and they seems to be unique
  for Ubuntu build.

  # cat /proc/cpuinfo 
  processor : 0
  vendor_id : GenuineIntel
  cpu family: 6
  model : 42
  model name: Intel(R) Celeron(R) CPU 847 @ 1.10GHz
  stepping  : 7
  microcode : 0x28
  cpu MHz   : 892.546
  cache size: 2048 KB
  physical id   : 0
  siblings  : 2
  core id   : 0
  cpu cores : 2
  apicid: 0
  initial apicid: 0
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 13
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 
xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave lahf_lm 
arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid xsaveopt
  bugs  :
  bogomips  : 2195.00
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 36 bits physical, 48 bits virtual
  power management:

  
  Below is part of crash report:

  Crashing Thread
  Frame Module  Signature   Source
  0 libxul.so   mozilla::dom::CrashReporterParent::GenerateChildData
/build/firefox-4CFcvq/firefox-39.0+build5/dom/ipc/CrashReporterParent.cpp:114
  1 libxul.so   
mozilla::plugins::PluginModuleChromeParent::ProcessFirstMinidump
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1415
  2 libxul.so   
mozilla::plugins::PluginModuleChromeParent::ActorDestroy
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1503
  3 libxul.so   mozilla::plugins::PPluginModuleParent::DestroySubtree   
/build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1588
  4 libxul.so   mozilla::plugins::PPluginModuleParent::OnChannelError   
/build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1462
  5 libxul.so   mozilla::ipc::MessageChannel::NotifyMaybeChannelError   
/build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1622
  6 libxul.so   mozilla::ipc::MessageChannel::Close 
/build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1744
  7 libxul.so   mozilla::plugins::PluginModuleParent::DoShutdown
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2326
  8 libxul.so   mozilla::plugins::PluginModuleParent::NP_Shutdown   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2307
  9 libxul.so   
mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:705
  10libxul.so   
mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:741
  11libxul.so   nsNPAPIPlugin::~nsNPAPIPlugin   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:237
  12libxul.so   nsNPAPIPlugin::~nsNPAPIPlugin   
/build/firefox-4CFcvq/firefox-39.0+build

[Desktop-packages] [Bug 1474003] Re: Firefox 39 keeps crashing

[Thorsten Munsch]

Really annoying. Keeps crashing and crashing. Not usable to surf through
the web here.

Only two extensions are Adblock Edge and NoScript. Flashplayer and H264
plugins have to be enabled to load.

There were no problems until I installed the updates yesterday.

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

Title:
  Firefox 39 keeps crashing

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Firefox 39 keeps crashing after update from Firefox 38.
  Crashes are random but when idle happens at least once a hour or more 
frequently when actively used.

  When replaced with binaries from Mozilla there is no problems at same
  machine with same profile.

  There are at least 1100 identical reports and they seems to be unique
  for Ubuntu build.

  Below is part of crash report:

  Crashing Thread
  Frame Module  Signature   Source
  0 libxul.so   mozilla::dom::CrashReporterParent::GenerateChildData
/build/firefox-4CFcvq/firefox-39.0+build5/dom/ipc/CrashReporterParent.cpp:114
  1 libxul.so   
mozilla::plugins::PluginModuleChromeParent::ProcessFirstMinidump
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1415
  2 libxul.so   
mozilla::plugins::PluginModuleChromeParent::ActorDestroy
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1503
  3 libxul.so   mozilla::plugins::PPluginModuleParent::DestroySubtree   
/build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1588
  4 libxul.so   mozilla::plugins::PPluginModuleParent::OnChannelError   
/build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1462
  5 libxul.so   mozilla::ipc::MessageChannel::NotifyMaybeChannelError   
/build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1622
  6 libxul.so   mozilla::ipc::MessageChannel::Close 
/build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1744
  7 libxul.so   mozilla::plugins::PluginModuleParent::DoShutdown
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2326
  8 libxul.so   mozilla::plugins::PluginModuleParent::NP_Shutdown   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2307
  9 libxul.so   
mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:705
  10libxul.so   
mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:741
  11libxul.so   nsNPAPIPlugin::~nsNPAPIPlugin   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:237
  12libxul.so   nsNPAPIPlugin::~nsNPAPIPlugin   
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:239
  13libxul.so   nsNPAPIPlugin::Release  
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:224
  14libxul.so   nsPluginHost::Notify
/build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsPluginHost.cpp:3716
  15libxul.so   nsTimerImpl::Fire   
/build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:634
  16libxul.so   nsTimerEvent::Run   
/build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:724
  17libxul.so   nsThread::ProcessNextEvent  
/build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsThread.cpp:855
  18libxul.so   NS_ProcessNextEvent 
/build/firefox-4CFcvq/firefox-39.0+build5/xpcom/glue/nsThreadUtils.cpp:265
  19libxul.so   mozilla::ipc::MessagePump::Run  
/build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessagePump.cpp:140
  20libxul.so   MessageLoop::Run
/build/firefox-4CFcvq/firefox-39.0+build5/ipc/chromium/src/base/message_loop.cc:226
  21libxul.so   nsBaseAppShell::Run 
/build/firefox-4CFcvq/firefox-39.0+build5/widget/nsBaseAppShell.cpp:164
  22libxul.so   nsAppStartup::Run   
/build/firefox-4CFcvq/firefox-39.0+build5/toolkit/components/startup/nsAppStartup.cpp:281
  23libxul.so   XREMain::XRE_mainRun
/build/firefox-4CFcvq/firefox-39.0+build5/toolkit/xre/nsAppRunner.cpp:4170
  24libxul.so   XREMain::XRE_main   
/build/firefox-4CFcvq/firefox-39.0+build5/toolkit/xre/nsAppRunner.cpp:4250
  25libxul.so   XRE_main
/build/firefox-4CFcvq/firefox-39.0+build5/toolkit/xre/nsAppRunner.cpp:4469
  26firefox do_main 
/build/firefox-4CFcvq/firefox-39.0+build5/browser/app/nsBrowserApp.cpp:294
  27firefox main
/build/firefox-4CFcvq/firefox-39.0+build5/browser/app/ns

[Desktop-packages] [Bug 1464324] [NEW] package jackd2 1.9.10+20140719git3eb0ae6a~dfsg-2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

[Thorsten Lauer]

Public bug reported:

apt-get reports an error

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: jackd2 1.9.10+20140719git3eb0ae6a~dfsg-2
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
Date: Thu Jun 11 18:38:53 2015
DpkgHistoryLog:
 Start-Date: 2015-06-11  18:38:35
 Commandline: apt-get --reinstall install grub-common grub-pc os-prober
 Reinstall: os-prober:amd64 (1.63ubuntu1), grub-common:amd64 
(2.02~beta2-22ubuntu1), grub-pc:amd64 (2.02~beta2-22ubuntu1)
DuplicateSignature: 
package:jackd2:1.9.10+20140719git3eb0ae6a~dfsg-2:Unterprozess installiertes 
post-installation-Skript gab den Fehlerwert 1 zurück
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4
SourcePackage: jackd2
Title: package jackd2 1.9.10+20140719git3eb0ae6a~dfsg-2 failed to 
install/upgrade: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
UpgradeStatus: Upgraded to vivid on 2015-04-28 (44 days ago)

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


** Tags: amd64 apport-package vivid

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

Title:
  package jackd2 1.9.10+20140719git3eb0ae6a~dfsg-2 failed to
  install/upgrade: Unterprozess installiertes post-installation-Skript
  gab den Fehlerwert 1 zurück

Status in jackd2 package in Ubuntu:
  New

Bug description:
  apt-get reports an error

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: jackd2 1.9.10+20140719git3eb0ae6a~dfsg-2
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Thu Jun 11 18:38:53 2015
  DpkgHistoryLog:
   Start-Date: 2015-06-11  18:38:35
   Commandline: apt-get --reinstall install grub-common grub-pc os-prober
   Reinstall: os-prober:amd64 (1.63ubuntu1), grub-common:amd64 
(2.02~beta2-22ubuntu1), grub-pc:amd64 (2.02~beta2-22ubuntu1)
  DuplicateSignature: 
package:jackd2:1.9.10+20140719git3eb0ae6a~dfsg-2:Unterprozess installiertes 
post-installation-Skript gab den Fehlerwert 1 zurück
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: jackd2
  Title: package jackd2 1.9.10+20140719git3eb0ae6a~dfsg-2 failed to 
install/upgrade: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
  UpgradeStatus: Upgraded to vivid on 2015-04-28 (44 days ago)

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

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

[Desktop-packages] [Bug 1311983] Re: firefox window suddenly resize to about 10x100 mm to upperleft screen corner

[Thorsten]

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

** This bug has been marked a duplicate of bug 1408894
   pre-grid size of application window is lost, when restoring an application 
in maximized mode and then moving to left/right edge using + 
keybind

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

Title:
  firefox window suddenly resize to about 10x100 mm to upperleft screen
  corner

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  While browsing with Firefox, for UNKNOWN REASON, suddenly resize to
  about 10x100 mm aligned to upper left corner of the screen. Grabbing
  is not possible, resizing is possible using "Shift"+"Ctrl"+"Left
  Arrow" short cut.

  In other instance it suddenly maximize to whole screen, the left side
  is behind the unity dash column and can not be accessed by mouse /
  cursor. Resizing using "Shift"+"Ctrl"+"Left Arrow" is possible. Back
  to "normal" from there.

  What activities lead to this anormality is not clear to me.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 28.0+build2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  toni   1953 F pulseaudio
  BrokenPermissions: 
extensions/printPages2Pdf@reinhold.ripper/libraries/wkhtmltopdf-i386 (0o500)
  BuildID: 20140410211200
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Thu Apr 24 11:24:26 2014
  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 2014-04-19 (4 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.43.1 dev wlan0  proto static 
   192.168.43.0/24 dev wlan0  proto kernel  scope link  src 192.168.43.214  
metric 9
  Locales: extensions.sqlite corrupt or missing
  PrefSources:
   prefs.js
   
[Profile]/extensions/printPages2Pdf@reinhold.ripper/defaults/preferences/defaults.js
   
[Profile]/extensions/artur.dubo...@gmail.com/defaults/preferences/fvd_single_setup.js
  Profiles: Profile0 (Default) - LastVersion=28.0/20140410211200 (In use)
  RelatedPackageVersions:
   rhythmbox-mozilla 3.0.2-0ubuntu1
   totem-mozilla 3.10.1-1ubuntu4
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K43E.217
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K43E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK43E.217:bd10/24/2011:svnASUSTeKComputerInc.:pnK43E:pvr1.0:rvnASUSTeKComputerInc.:rnK43E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K43E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

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

[Desktop-packages] [Bug 1408894] Re: pre-grid size of application window is lost, when restoring an application in maximized mode and then moving to left/right edge using + keybind

[Thorsten]

I am also affected by this bug and it is especially annoying when using eclipse 
IDE, which "collapses" to a tiny barely visible line (see attachment).
This bug is besides ubuntu 14.04.x also present in 14.10 and 15.04! I asked 
about this beaviour in ubuntu ask 
(https://askubuntu.com/questions/569574/ubuntu-eclipse-window-disappears) and 
there is one more person affected by this bug

** Attachment added: "eclipse_collapse.png"
   
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1408894/+attachment/4388630/+files/eclipse_collapse.png

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

Title:
  pre-grid size of application window is lost, when restoring an
  application in maximized mode and then moving to left/right edge using
  + keybind

Status in compiz package in Ubuntu:
  Confirmed

Bug description:
  1) Release of Ubuntu:

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  2) Version of Package:

  compiz:
    Installed: 1:0.9.11.3+14.04.20141104-0ubuntu1
    Candidate: 1:0.9.11.3+14.04.20141104-0ubuntu1
    Version table:
   *** 1:0.9.11.3+14.04.20141104-0ubuntu1 0
  500 http://sa.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:0.9.11+14.04.20140409-0ubuntu1 0
  500 http://sa.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  3) What you expected to happen:

  upon restoring a maximized application, and then moving the
  application window to a grid on the left or right part of the screen
  using the ++left/right keybinding, i should be able to
  restore the window to a pre-grid size if dragged away from the gridded
  position.

  4) What happened instead:

  window collapses to minimal size after dragging away application
  window from gridded position. this happens with almost all
  applications. i have also tried enabling "snap windows back to
  original size" from the CCSM grid-plugin settings, with no success.

  thanks

  i'v attached a screencast video of the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jan  9 08:53:28 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 3.13.0-43-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-43-generic, x86_64: installed
   nvidia-331-updates, 331.113, 3.13.0-43-generic, x86_64: installed
   virtualbox, 4.3.10, 3.13.0-43-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Device [1025:054f]
   NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2014-08-27 (134 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Acer Aspire 4830TG
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic 
root=UUID=375cafcf-e638-4d16-968c-078fab2bbc55 ro quiet splash acpi_osi=Linux 
acpi_backlight=vendor nmi_watchdog=0 vt.handoff=7
  SourcePackage: compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.12
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM40_HR
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.12
  dmi.modalias: 
dmi:bvnAcer:bvrV1.12:bd08/14/2012:svnAcer:pnAspire4830TG:pvrV1.12:rvnAcer:rnJM40_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.12:
  dmi.product.name: Aspire 4830TG
  dmi.product.version: V1.12
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0u

[Desktop-packages] [Bug 830663] Re: default window size is too small

[Thorsten Rochelmeyer]

Thanks for fixing!

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

Title:
  default window size is too small

Status in Inkscape: Vector Graphics Editor:
  Fix Released
Status in inkscape package in Ubuntu:
  Fix Released

Bug description:
  The default window size for Inkscape is too small. Attached is a
  screenshot showing how it starts for me every time. It would be nice
  if Inkscape started maximised or at least a whole lot bigger than it
  is now, so it can be useful immediately.

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

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

[Desktop-packages] [Bug 1394929] Re: Please provide 'locales-all' as in Debian

[Thorsten Glaser]

Hi Doko,

the package *is* required if you programmatically need to have “all”, or
at least a large set of, locales available.

Possible use case here is a package dependency (declaratively).

In the specific case of FusionForge, I have seen it (both the native
tracker and the embedded mediawiki) malfunction if locales-all was not
installed, even getting PHP to segfault.

Another use case is to ensure something is available to users,
especially nōn-root users, in the default location (so there is no need
to set LOCPATH. (This can help ssh, sudo, etc.)

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

Title:
  Please provide 'locales-all' as in Debian

Status in “glibc” package in Ubuntu:
  Confirmed
Status in “langpack-locales” package in Ubuntu:
  New

Bug description:
  Hi,

  Debian provides a 'locales-all' package, which is very convenient to
  ensure all locales are available, and installs very quickly.

  It's particularly handy when providing i18n'd web applications (e.g. that use 
php-gettext).
  As they may be accessed by visitors of all supported languages, rather than 
documenting how the server administrator should enable a list of 10-15 
languages by reconfiguring 'locales', the packager can just add 'locales-all' 
to the Recommends or Depends.
  See for instance the FusionForge package in Debian 
(https://packages.debian.org/jessie/gforge-web-apache2).

  Cheers!
  Sylvain

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

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

[Desktop-packages] [Bug 1311983] Re: firefox window suddenly resize to about 10x100 mm to upperleft screen corner

[Thorsten]

i am also affected by this bug. But its not only limited to firefox! It
occours on all windows and also occured last month!

I can reproduce this behaviour in firefox by using ctrl-down to minimize
the window. Bug also occurs on my laptop and pc.

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

Title:
  firefox window suddenly resize to about 10x100 mm to upperleft screen
  corner

Status in “firefox” package in Ubuntu:
  Confirmed

Bug description:
  While browsing with Firefox, for UNKNOWN REASON, suddenly resize to
  about 10x100 mm aligned to upper left corner of the screen. Grabbing
  is not possible, resizing is possible using "Shift"+"Ctrl"+"Left
  Arrow" short cut.

  In other instance it suddenly maximize to whole screen, the left side
  is behind the unity dash column and can not be accessed by mouse /
  cursor. Resizing using "Shift"+"Ctrl"+"Left Arrow" is possible. Back
  to "normal" from there.

  What activities lead to this anormality is not clear to me.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 28.0+build2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  toni   1953 F pulseaudio
  BrokenPermissions: 
extensions/printPages2Pdf@reinhold.ripper/libraries/wkhtmltopdf-i386 (0o500)
  BuildID: 20140410211200
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Thu Apr 24 11:24:26 2014
  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 2014-04-19 (4 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.43.1 dev wlan0  proto static 
   192.168.43.0/24 dev wlan0  proto kernel  scope link  src 192.168.43.214  
metric 9
  Locales: extensions.sqlite corrupt or missing
  PrefSources:
   prefs.js
   
[Profile]/extensions/printPages2Pdf@reinhold.ripper/defaults/preferences/defaults.js
   
[Profile]/extensions/artur.dubo...@gmail.com/defaults/preferences/fvd_single_setup.js
  Profiles: Profile0 (Default) - LastVersion=28.0/20140410211200 (In use)
  RelatedPackageVersions:
   rhythmbox-mozilla 3.0.2-0ubuntu1
   totem-mozilla 3.10.1-1ubuntu4
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K43E.217
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K43E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK43E.217:bd10/24/2011:svnASUSTeKComputerInc.:pnK43E:pvr1.0:rvnASUSTeKComputerInc.:rnK43E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K43E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

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

[Desktop-packages] [Bug 1357227]

[Thorsten Glaser]

Created attachment 8474434
public part of test GPG key

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

Title:
  broken charset/encoding autodetection for encrypted messages

Status in Mozilla Thunderbird Mail and News:
  New
Status in “thunderbird” package in Ubuntu:
  New
Status in “kdepim” package in Debian:
  Confirmed

Bug description:
  Version: 1:31.0+build1-0ubuntu0.12.04.1

  Hi,

  this is a bug Mozilla™ Thunderbird and KDEPIM share:

  When I send an Inline PGP encrypted message, whose body is using
  UTF-8, to another user, the message is ASCII armoured (and thus 7bit).
  The other user, running Thunderbird or Kontact, (or my own Kontact
  instance in the “sent-mail” folder), gets the message and interprets
  the post-decryption body as ISO-8859-1 (or Windows-1252, probably)
  instead of UTF-8.

  Manually switching the encoding to Unicode in the menu corrects this…
  for this one message. (See
  https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980 as
  well.)

  The problem here is that the human message encoding (everything within
  the PGP armour) must be separated from the transport message encoding
  (the RFC822 message in which the “-BEGIN PGP MESSAGE”…“END PGP
  MESSAGE-” is transmitted) must be separated from each other, which
  they aren’t.

  Please fix this, it harms using those MUAs in an enterprise
  environment.

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

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

[Desktop-packages] [Bug 1357227]

[Thorsten Glaser]

Created attachment 8474435
secret part of test GPG key

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

Title:
  broken charset/encoding autodetection for encrypted messages

Status in Mozilla Thunderbird Mail and News:
  New
Status in “thunderbird” package in Ubuntu:
  New
Status in “kdepim” package in Debian:
  Confirmed

Bug description:
  Version: 1:31.0+build1-0ubuntu0.12.04.1

  Hi,

  this is a bug Mozilla™ Thunderbird and KDEPIM share:

  When I send an Inline PGP encrypted message, whose body is using
  UTF-8, to another user, the message is ASCII armoured (and thus 7bit).
  The other user, running Thunderbird or Kontact, (or my own Kontact
  instance in the “sent-mail” folder), gets the message and interprets
  the post-decryption body as ISO-8859-1 (or Windows-1252, probably)
  instead of UTF-8.

  Manually switching the encoding to Unicode in the menu corrects this…
  for this one message. (See
  https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980 as
  well.)

  The problem here is that the human message encoding (everything within
  the PGP armour) must be separated from the transport message encoding
  (the RFC822 message in which the “-BEGIN PGP MESSAGE”…“END PGP
  MESSAGE-” is transmitted) must be separated from each other, which
  they aren’t.

  Please fix this, it harms using those MUAs in an enterprise
  environment.

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

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

[Desktop-packages] [Bug 1357227]

[Thorsten Glaser]

Created attachment 8474439
eMail exhibiting the bug

OK. This eMail contains a PGP message encrypted to 0xD1D8EFD2 whose
public and secret (passphrase is 123123) key I also attached. I just
confirmed with a coworker that this does exhibit the bug.

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

Title:
  broken charset/encoding autodetection for encrypted messages

Status in Mozilla Thunderbird Mail and News:
  New
Status in “thunderbird” package in Ubuntu:
  New
Status in “kdepim” package in Debian:
  Confirmed

Bug description:
  Version: 1:31.0+build1-0ubuntu0.12.04.1

  Hi,

  this is a bug Mozilla™ Thunderbird and KDEPIM share:

  When I send an Inline PGP encrypted message, whose body is using
  UTF-8, to another user, the message is ASCII armoured (and thus 7bit).
  The other user, running Thunderbird or Kontact, (or my own Kontact
  instance in the “sent-mail” folder), gets the message and interprets
  the post-decryption body as ISO-8859-1 (or Windows-1252, probably)
  instead of UTF-8.

  Manually switching the encoding to Unicode in the menu corrects this…
  for this one message. (See
  https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980 as
  well.)

  The problem here is that the human message encoding (everything within
  the PGP armour) must be separated from the transport message encoding
  (the RFC822 message in which the “-BEGIN PGP MESSAGE”…“END PGP
  MESSAGE-” is transmitted) must be separated from each other, which
  they aren’t.

  Please fix this, it harms using those MUAs in an enterprise
  environment.

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

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

[Desktop-packages] [Bug 1357227] Re: broken charset/encoding autodetection for encrypted messages

[Thorsten Glaser]

** Bug watch added: Mozilla Bugzilla #1054187
   https://bugzilla.mozilla.org/show_bug.cgi?id=1054187

** Also affects: thunderbird via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1054187
   Importance: Unknown
   Status: Unknown

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

Title:
  broken charset/encoding autodetection for encrypted messages

Status in Mozilla Thunderbird Mail and News:
  Unknown
Status in “thunderbird” package in Ubuntu:
  New
Status in “kdepim” package in Debian:
  Unknown

Bug description:
  Version: 1:31.0+build1-0ubuntu0.12.04.1

  Hi,

  this is a bug Mozilla™ Thunderbird and KDEPIM share:

  When I send an Inline PGP encrypted message, whose body is using
  UTF-8, to another user, the message is ASCII armoured (and thus 7bit).
  The other user, running Thunderbird or Kontact, (or my own Kontact
  instance in the “sent-mail” folder), gets the message and interprets
  the post-decryption body as ISO-8859-1 (or Windows-1252, probably)
  instead of UTF-8.

  Manually switching the encoding to Unicode in the menu corrects this…
  for this one message. (See
  https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980 as
  well.)

  The problem here is that the human message encoding (everything within
  the PGP armour) must be separated from the transport message encoding
  (the RFC822 message in which the “-BEGIN PGP MESSAGE”…“END PGP
  MESSAGE-” is transmitted) must be separated from each other, which
  they aren’t.

  Please fix this, it harms using those MUAs in an enterprise
  environment.

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

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

[Desktop-packages] [Bug 1357227] [NEW] broken charset/encoding autodetection for encrypted messages

[Thorsten Glaser]

Public bug reported:

Version: 1:31.0+build1-0ubuntu0.12.04.1

Hi,

this is a bug Mozilla™ Thunderbird and KDEPIM share:

When I send an Inline PGP encrypted message, whose body is using UTF-8,
to another user, the message is ASCII armoured (and thus 7bit). The
other user, running Thunderbird or Kontact, (or my own Kontact instance
in the “sent-mail” folder), gets the message and interprets the post-
decryption body as ISO-8859-1 (or Windows-1252, probably) instead of
UTF-8.

Manually switching the encoding to Unicode in the menu corrects this…
for this one message. (See
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980 as
well.)

The problem here is that the human message encoding (everything within
the PGP armour) must be separated from the transport message encoding
(the RFC822 message in which the “-BEGIN PGP MESSAGE”…“END PGP
MESSAGE-” is transmitted) must be separated from each other, which
they aren’t.

Please fix this, it harms using those MUAs in an enterprise environment.

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

** Affects: kdepim (Debian)
 Importance: Unknown
 Status: Unknown

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

** Also affects: kdepim (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754265
   Importance: Unknown
   Status: Unknown

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

Title:
  broken charset/encoding autodetection for encrypted messages

Status in “thunderbird” package in Ubuntu:
  New
Status in “kdepim” package in Debian:
  Unknown

Bug description:
  Version: 1:31.0+build1-0ubuntu0.12.04.1

  Hi,

  this is a bug Mozilla™ Thunderbird and KDEPIM share:

  When I send an Inline PGP encrypted message, whose body is using
  UTF-8, to another user, the message is ASCII armoured (and thus 7bit).
  The other user, running Thunderbird or Kontact, (or my own Kontact
  instance in the “sent-mail” folder), gets the message and interprets
  the post-decryption body as ISO-8859-1 (or Windows-1252, probably)
  instead of UTF-8.

  Manually switching the encoding to Unicode in the menu corrects this…
  for this one message. (See
  https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1108980 as
  well.)

  The problem here is that the human message encoding (everything within
  the PGP armour) must be separated from the transport message encoding
  (the RFC822 message in which the “-BEGIN PGP MESSAGE”…“END PGP
  MESSAGE-” is transmitted) must be separated from each other, which
  they aren’t.

  Please fix this, it harms using those MUAs in an enterprise
  environment.

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

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

[Desktop-packages] [Bug 1108980] Re: thunderbird message preview pane do not honor global character encoding settings

[Thorsten Glaser]

Confirmed in Thunderbird 1:31.0+build1-0ubuntu0.12.04.1

Please fix!

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

Title:
  thunderbird message preview pane do not honor global character
  encoding settings

Status in “thunderbird” package in Ubuntu:
  Confirmed

Bug description:
  character encoding is set to UTF-8 for incoming and outgoing messages in Edit 
> Preferences : Display > Advanced.
  In the review pane, the message is shown with Western ISO-8859-1 as seen in 
View > Character Encoding. When manually change it to UTF-8 it work, but when 
clicking on other message and going back, te Western character encoding is 
restored.

  Is there other global character encoding hidden in somwhere else?

  If not, this is defenitey a bug.

  P.S: The "auto-detect" menu in View > Character Encoding changes
  nothing. I tried set auto detect to "off" and "Universal" and no
  change.

  Best Regards,

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: thunderbird 17.0.2+build1-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  NonfreeKernelModules: fglrx
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  BuildID: 20130106044124
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xfeb0 irq 16'
 Mixer name : 'Realtek ALC892'
 Components : 'HDA:10ec0892,10438410,00100302'
 Controls  : 44
 Simple ctrls  : 21
  Card1.Amixer.info:
   Card hw:1 'U0x46d0x991'/'USB Device 0x46d:0x991 at usb-:00:13.2-2, high 
speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:0991'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 8
 Mono: Capture 6 [75%] [27.00dB] [off]
  Card2.Amixer.info:
   Card hw:2 'Generic'/'HD-Audio Generic at 0xfea4 irq 89'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 6
 Simple ctrls  : 1
  Card2.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Channel: Unavailable
  Date: Tue Jan 29 13:20:58 2013
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Beta amd64 (20120228)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.33  metric 
2
  MarkForUpload: True
  Plugins:
   Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
   IcedTea-Web Plugin (using IcedTea-Web 1.2 (1.2-2ubuntu1.3)) - 
/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so 
(icedtea-7-plugin)
  PrefSources:
   prefs.js
   
[Profile]/extensions/masterpasswordtimeoutplus@vano/defaults/preferences/masterpasswordplus.js
   
[Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
   
[Profile]/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=17.0.2/20130106044124 (In use)
  RelatedPackageVersions: icedtea-7-plugin 1.2-2ubuntu1.3
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0901
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99X EVO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr0901:bd12/02/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVO:rvrRev1.xx: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/ubuntu/+source/thunderbird/+bug/1108980/+subscriptions

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

[Desktop-packages] [Bug 1320019] [NEW] Wrong recognition of Touchinput

[Thorsten]

Public bug reported:

Touchinput is not correct recognisied in different programms:

1. In Firefox: i am not able to open dropdown menus like for example folders in 
the bookmarks-toolbar but also dropdown lists on websites: they open and are 
immediately closed again
2. In chromium there is also a strange behavior in dropdown menus, like the 
bookmarks-folder or the settings menu: they can be opened by touch but one can 
only select an element if one touches it very very fast, almost instantly 
otherwise there is just no reaction until i open the menu again.

I only notice this bug on a thinkpad t440s and not on a x220t (there is
all working flawlessly). This behaviour also occurs on ubuntu 14.04 live
version. This bug does NOT occur in Kubuntu 14.04!

Ubuntu release:

Description:Ubuntu 14.04 LTS
Release:14.04

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelModules: sep3_10 pax apwr3_1
ApportVersion: 2.14.1-0ubuntu3.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Fri May 16 00:15:23 2014
InstallationDate: Installed on 2014-04-28 (16 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

** Description changed:

  Touchinput is not correct recognisied in different programms:
  
  1. In Firefox: i am not able to open dropdown menus like for example folders 
in the bookmarks-toolbar but also dropdown lists on websites: they open and are 
immediately closed again
  2. In chromium there is also a strange behavior in dropdown menus, like the 
bookmarks-folder or the settings menu: they can be opened by touch but one can 
only select an element if one touches it very very fast, almost instantly 
otherwise there is just no reaction until i open the menu again.
  
  I only notice this bug on a thinkpad t440s and not on a x220t (there is
  all working flawlessly). This behaviour also occurs on ubuntu 14.04 live
- version. This bug does NOT occur in Kubuntu 14.04 or Ubuntu Gnome 14.04!
+ version. This bug does NOT occur in Kubuntu 14.04!
  
  Ubuntu release:
  
  Description:  Ubuntu 14.04 LTS
  Release:  14.04
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: sep3_10 pax apwr3_1
  ApportVersion: 2.14.1-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri May 16 00:15:23 2014
  InstallationDate: Installed on 2014-04-28 (16 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Wrong recognition of Touchinput

Status in “unity” package in Ubuntu:
  New

Bug description:
  Touchinput is not correct recognisied in different programms:

  1. In Firefox: i am not able to open dropdown menus like for example folders 
in the bookmarks-toolbar but also dropdown lists on websites: they open and are 
immediately closed again
  2. In chromium there is also a strange behavior in dropdown menus, like the 
bookmarks-folder or the settings menu: they can be opened by touch but one can 
only select an element if one touches it very very fast, almost instantly 
otherwise there is just no reaction until i open the menu again.

  I only notice this bug on a thinkpad t440s and not on a x220t (there
  is all working flawlessly). This behaviour also occurs on ubuntu 14.04
  live version. This bug does NOT occur in Kubuntu 14.04!

  Ubuntu release:

  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: sep3_10 pax apwr3_1
  ApportVersion: 2.14.1-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri May 16 00:15:23 2014
  InstallationDate: Installed on 2014-04-28 (16 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh insta

[Desktop-packages] [Bug 467825] Re: Battery state always "fully charged"

[Thorsten Goetzke]

Same here, i need to restart upowerd to get the correct charge status on my 
laptop.
My upower version is 
0.9.22-1ubuntu2 i386

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

Title:
  Battery state always "fully charged"

Status in Gnome Powermanager:
  In Progress
Status in “upower” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gnome-power-manager

  gnome-power-manager always detects my battery state as "fully charged"
  in karmic. (on 9.04 it detected the battery state correctly.) - this
  ends up in data loss because my machine does not perform any shutdown
  tasks when the it runs out of battery.

  The output of acpi -V says:

  $ acpi -V
  Battery 0: Charging, 22%, rate information unavailable
  Battery 0: design capacity 4000 mAh, last full capacity 2980 mAh = 74%
  Adapter 0: on-line
  Thermal 0: ok, 68.8 degrees C
  Thermal 0: trip point 0 switches to mode critical at temperature 104.8 
degrees C
  Thermal 0: trip point 1 switches to mode passive at temperature 88.8 degrees C
  Cooling 0: Processor 0 of 7

  "Charging, 22%".

  The output of devkit-power says:

  $ devkit-power -d
  Device: /org/freedesktop/DeviceKit/Power/devices/line_power_AC
native-path:  
/sys/devices/LNXSYSTM:00/device:00/ACPI0003:00/power_supply/AC
power supply: yes
updated:  Sat Oct 31 23:31:03 2009 (14629 seconds ago)
has history:  no
has statistics:   no
line-power
  online: yes

  Device: /org/freedesktop/DeviceKit/Power/devices/battery_BAT0
native-path:  
/sys/devices/LNXSYSTM:00/device:00/PNP0C0A:00/power_supply/BAT0
vendor:   NOTEBOOK
model:BAT1
serial:   0001
power supply: yes
updated:  Sat Oct 31 23:31:03 2009 (14629 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   fully-charged
  energy:  32.184 Wh
  energy-empty:0 Wh
  energy-full: 32.184 Wh
  energy-full-design:  43.2 Wh
  energy-rate: 0.0108 W
  percentage:  100%
  capacity:74.5%
  technology:  lithium-ion

  Daemon:
daemon-version:  011
can-suspend: yes
can-hibernateyes
on-battery:  no
on-low-battery:  no
lid-is-closed:   yes
lid-is-present:   yes

  "fully-charged".

  This might be a devkit-power-bug, though.

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

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

[Desktop-packages] [Bug 325641]

[Thorsten-behrens]

My responsibilities have changed, returning bug to general LibreOffice
maintainer pool.

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

Title:
  [ooo-build] fix to frame in text box in openoffice.org 3.0.1 doesn't
  work

Status in The OpenOffice.org Suite:
  Confirmed
Status in “openoffice.org” package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  Ubuntu 8.10 Intrepid Ibex (64 bit)
  Create a text box in OpenOffice.org 3.0.1 Draw (italian)
  Write something.
  Click right on the box, choose Text, deselect fix height to text and select 
fix to frame.
  The text insight the box doesn't  change.
  The text should become as big as the text box is.

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

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

[Desktop-packages] [Bug 1126633] AUTO: Thorsten Hesemeyer is out of the office (returning 06/02/2013)

[Thorsten Hesemeyer]

I am out of the office until 06/02/2013.


For urgent cases please contact:
martin.schwei...@de.ibm.com or andreas.la...@de.ibm.com

Thank you,
Thorsten Hesemeyer


Note: This is an automated response to your message  "[Bug 1126633] Re:
Please mark alsa-utils Multi-Arch: foreign" sent on 09/05/2013 12:17:23.

This is the only notification you will receive while this person is
away.

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

Title:
  Please mark alsa-utils Multi-Arch: foreign

Status in “alsa-utils” package in Ubuntu:
  Fix Released
Status in “alsa-utils” source package in Precise:
  Fix Released
Status in “alsa-utils” source package in Quantal:
  Fix Released

Bug description:
  [Impact]
  Marking alsa-utils as M-A: foreign will allow i386 packages that depend on 
alsa-utils to install on a amd64 system. Since alsa interfaces are architecture 
independent, foreign seems like the correct marking.

  $ sudo apt-get install my-32-bit-app
  my-32-bit-app:i386 : PreDepends: alsa-utils:i386 but it is not installable

  [Test Case]
  Install a 32-bit package that depends or pre-depends on alsa-utils and have 
it properly install.

  [Regression Potential]
  Minimal as this change on affects multi-arch status only.

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

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

[Desktop-packages] [Bug 1126633] AUTO: Thorsten Hesemeyer is ill / out of the office (returning 04/03/2013)

[Thorsten Hesemeyer]

I am out of the office until 04/03/2013.


For urgent cases please contact:
andreas.la...@de.ibm.com or melanie.hal...@de.ibm.com

Thank you,
Thorsten Hesemeyer


Note: This is an automated response to your message  "[Bug 1126633] Re:
Please mark alsa-utils Multi-Arch: foreign" sent on 28/03/2013 22:47:25.

This is the only notification you will receive while this person is
away.

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

Title:
  Please mark alsa-utils Multi-Arch: foreign

Status in “alsa-utils” package in Ubuntu:
  Fix Released
Status in “alsa-utils” source package in Precise:
  Fix Committed
Status in “alsa-utils” source package in Quantal:
  Fix Committed

Bug description:
  [Impact]
  Marking alsa-utils as M-A: foreign will allow i386 packages that depend on 
alsa-utils to install on a amd64 system. Since alsa interfaces are architecture 
independent, foreign seems like the correct marking.

  $ sudo apt-get install my-32-bit-app
  my-32-bit-app:i386 : PreDepends: alsa-utils:i386 but it is not installable

  [Test Case]
  Install a 32-bit package that depends or pre-depends on alsa-utils and have 
it properly install.

  [Regression Potential]
  Minimal as this change on affects multi-arch status only.

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

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

[Desktop-packages] [Bug 932882] Re: Update of a printer driver package does not update the PPD files of the existing queues for this driver

[Thorsten Hirsch]

This bug re-occured when upgrading from 12.04 to 12.10. There's only a
difference in the version numbers in the error message:

"The PPD version (5.2.8-pre1) is not compatible with Gutenprint 5.2.9."

I had to "sudo cups-genppdupdate" manually to resolve the issue. Why is
this command not being called automatically when upgrading the cups
package?

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

Title:
  Update of a printer driver package does not update the PPD files of
  the existing queues for this driver

Status in “cups” package in Ubuntu:
  Fix Released
Status in “gutenprint” package in Ubuntu:
  Invalid
Status in “cups” source package in Precise:
  Invalid
Status in “gutenprint” source package in Precise:
  Fix Released
Status in “cups” source package in Quantal:
  Fix Released
Status in “gutenprint” source package in Quantal:
  Invalid

Bug description:
  I needed to print few tickets for travel. But as they did not appeared
  on my printer I took a look at http://localhost:631/ and discovered
  this:

  "The PPD version (5.2.7) is not compatible with Gutenprint
  5.2.8-pre1."

  Had to print to PDF and do printing from MS Windows laptop...

  [Impact] Printers used with Gutenprint do not work for all users who
  update from an older Ubuntu version to Precise.

  [Test Case] To reproduce: Upgrade from Gutenprint 5.2.7 to
  5.2.8~pre1-0ubuntu2 does not update the PPD files of existing queues.
  To test, create a Gutenprint-based print queue on a system with 5.2.7
  then run

  grep -i gutenprint /etc/cups/ppd/*.ppd

  and see that the PPD files are of Gutenprint version 5.2.7. Update to
  5.2.8~pre1-0ubuntu2 and run

  grep -i gutenprint /etc/cups/ppd/*.ppd

  The PPDs are still not upgraded. Update from 5.2.7 or
  5.2.8~pre1-0ubuntu2 to 5.2.8~pre1-0ubuntu2.1 and your PPD files get
  updated to 5.2.8pre1.

  [Regression Potential] Only change is the timestamp of one file. So
  regressions should not be possible.

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

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

[Desktop-packages] [Bug 1054537] Re: Unable to select other installed desktop environments when logging in.

[Thorsten Hirsch]

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

Same problem here.

As a side-note: /etc/lightdm/lightdm.conf still had "gnome-shell" as
default session, but there's no /usr/share/xsession/gnome-shell.desktop.
The file has been renamed to gnome.desktop. However, fixing the wrong
entry in /etc/lightdm/lightdm.conf had no effect on this bug. I'm just
adding this note, because I suppose that there are more old/wrong
references to gnome-shell that might cause this bug...

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

Title:
  Unable to select other installed desktop environments when logging in.

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  I am using lightdm 1.3.3-0ubuntu4, in Ubuntu 12.10. I installed gnome-
  shell 3.5.92-0ubuntu1.

  Gnome, Gnome Classic and Gnome Classic (No Effects) show up as
  selectable in lightdm as expected, along with Unity. However, Gnome
  Shell and Gnome Classic can not be selected. Clicking on them results
  in no response.

  EDIT: I tried to see if the problem was the same with other desktop
  environments. It is possible to install and select xubuntu-desktop and
  use it properly. The buttons for selecting KDE and LXDE in lightDM
  respond visually to a click, unlike for Gnome Shell/Gnome Classic, but
  clicking on them does not result on them being selected.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: lightdm 1.3.3-0ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  Date: Sat Sep 22 21:09:44 2012
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120921)
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1056716] Re: installation doesn't work (remote usage via ssh -X -C)

[Thorsten Hirsch]

** Attachment added: "error messages due to missing root privileges"
   
https://bugs.launchpad.net/bugs/1056716/+attachment/3344547/+files/errors-from-step-7-to-end.txt

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

Title:
  installation doesn't work (remote usage via ssh -X -C)

Status in “software-center” package in Ubuntu:
  New

Bug description:
  Local usage of Software Center works fine, but when using a ssh
  connection (ssh -X -C nearby.computer.lan) I can't install software.
  Here's how to reproduce:

  1.) Buy Humble Indie Bundle 6
  2.) ssh -X -C nearby.computer.lan
  3.) search for "bit runner"
  4.) choose BIT.TRIP RUNNER
  5.) click on "buy" ($ 9.99, but you won't get charged, because you bought 
Humble Indie Bundle 6)
  6.) login to Ubuntu SSO
  -- something's missing here, I'll explain it later, let's just say "step 6.5 
is missing" --
  7.) 1st problem (minor): BIT.TRIP RUNNER still displays the "Buy..." button 
(instead of install)
  8.) click on "More Info"
  9.) Now you can click on the "Install" button
  10.) 2nd problem (major): nothing happens

  Comparing this process to a local install, there's one thing missing -
  that's what I mean with step 6.5. A local install asks me for root
  privileges after the single sign on (step 6). So Software-Center can't
  get root privileges and that's why it cannot install the package.

  I attached the errors in STDOUT beginning with step 7.

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

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

[Desktop-packages] [Bug 1056716] Re: installation doesn't work (remote usage via ssh -X -C)

[Thorsten Hirsch]

Now since I already installed bittrip runner locally, I had to look for
another package to re-produce the missing authentication. I've chosen to
install a free software package - which is even easier as it reproduces
the error without the payment process (i.e. without single sign on).

So the steps needed to reproduce the error with free software are just
1, 2, 3, 4 and 9 (click on install). I've attached STDOUT again.

** Attachment added: "stdout for free software package"
   
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1056716/+attachment/3344558/+files/step-1-2-3-4-9-with-free-software.txt

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

Title:
  installation doesn't work (remote usage via ssh -X -C)

Status in “software-center” package in Ubuntu:
  New

Bug description:
  Local usage of Software Center works fine, but when using a ssh
  connection (ssh -X -C nearby.computer.lan) I can't install software.
  Here's how to reproduce:

  1.) Buy Humble Indie Bundle 6
  2.) ssh -X -C nearby.computer.lan
  3.) search for "bit runner"
  4.) choose BIT.TRIP RUNNER
  5.) click on "buy" ($ 9.99, but you won't get charged, because you bought 
Humble Indie Bundle 6)
  6.) login to Ubuntu SSO
  -- something's missing here, I'll explain it later, let's just say "step 6.5 
is missing" --
  7.) 1st problem (minor): BIT.TRIP RUNNER still displays the "Buy..." button 
(instead of install)
  8.) click on "More Info"
  9.) Now you can click on the "Install" button
  10.) 2nd problem (major): nothing happens

  Comparing this process to a local install, there's one thing missing -
  that's what I mean with step 6.5. A local install asks me for root
  privileges after the single sign on (step 6). So Software-Center can't
  get root privileges and that's why it cannot install the package.

  I attached the errors in STDOUT beginning with step 7.

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

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

[Desktop-packages] [Bug 833762] Re: hidden-users and hidden-shells has no effect

[Thorsten Greeb]

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

** This bug has been marked a duplicate of bug 857651
   Unable to hide users from login screen / user switcher

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

Title:
  hidden-users and hidden-shells has no effect

Status in “lightdm” package in Ubuntu:
  Invalid

Bug description:
  Hiding users on the LightDM login screen does not appear to work.
  (LightDM 0.9.3-0ubuntu7)

  I installed BitDefender, which creates a login-disabled user
  'bitdefender' with a shell of '/bin/false'.  The user shows up on the
  LightDM login screen, even though it seems that the default hidden-
  shells string includes /bin/false.  Forcing the hidden-shells setting
  had no effect, nor did adding the bitdefender user to the hidden-users
  string.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lightdm 0.9.3-0ubuntu7
  ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
  Uname: Linux 3.0.0-9-generic x86_64
  Architecture: amd64
  Date: Thu Aug 25 08:08:35 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64+mac 
(20110427.1)
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.lightdm.lightdm.conf: 2011-08-24T14:58:25.546256

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

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

[Desktop-packages] [Bug 928293] Re: always adds a “created with the GIMP” comment to files

[Thorsten Glaser]

Thanks, that _seems_ to do the trick. As for why, when storing large
binaries in LDAP, every three-octet group is precious (we have user
photos in LDAP for perusal by the company’s Jabber server with
mod_vcard_ldap and mod_shared_roster_ldap) as there are timeouts. We
found that jpegPhoto attributes of about 4K (before base64 encoding)
work best, and more than about 8K are unreasonable.

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

Title:
  always adds a “created with the GIMP” comment to files

Status in “gimp” package in Ubuntu:
  Incomplete

Bug description:
  Version: 2.6.6-0ubuntu1~hardy1~andre1

  GIMP always adds a comment “Created with the GIMP” to files when
  saving. This is inacceptable, as it severely raises the file size,
  especially when trying to use GIMP to make photos smaller to get them
  to fit into space-constrained database fields or LDAP.

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

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

[Desktop-packages] [Bug 928293] [NEW] always adds a “created with the GIMP” comment to files

[Thorsten Glaser]

Public bug reported:

Version: 2.6.6-0ubuntu1~hardy1~andre1

GIMP always adds a comment “Created with the GIMP” to files when saving.
This is inacceptable, as it severely raises the file size, especially
when trying to use GIMP to make photos smaller to get them to fit into
space-constrained database fields or LDAP.

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


** Tags: hardy

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

Title:
  always adds a “created with the GIMP” comment to files

Status in “gimp” package in Ubuntu:
  New

Bug description:
  Version: 2.6.6-0ubuntu1~hardy1~andre1

  GIMP always adds a comment “Created with the GIMP” to files when
  saving. This is inacceptable, as it severely raises the file size,
  especially when trying to use GIMP to make photos smaller to get them
  to fit into space-constrained database fields or LDAP.

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

-- 
Mailing list: https://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 912322] Re: Libre Office causes the windows manager to crash

[Thorsten]

Hi Christopher,

I've reproduced the crash several times but there is no libreoffice or
windowmanager related file in the directory you mentoined.

I've also tested libreoffice on two other machines (both amd64) and on
both I got the same problem.

So, how can I gain helpful informations on this bug? Apport is running
fine (it reports every crash of bitcoin-qt an other applications) but it
doesnt report anything about libreoffice and libreoffice doesnt send any
helpful informations on the console.

Kind Regards,

Thorsten

On 06.01.2012 01:54, Christopher M. Penalver wrote:
> Thorsten, thank you for reporting this and helping make Ubuntu better. 
> However, your crash report is missing. Please follow these instructions to 
> have apport report a new bug about your crash that can be dealt with by the 
> automatic retracer. One may execute at the Terminal:
> sudo service apport start force_start=1
> 
> If you are running the Ubuntu Stable Release you might need to enable
> apport in /etc/default/apport and restart.
> 
> Now open your file manager, navigate to your /var/crash directory and open 
> the crash report you wish to submit.
> If this fails you will have to open a terminal and file your report with 
> 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash 
> is the crash you would like to report. If you get an error that you aren't 
> allowed to access this report you will have to file it with 'sudo ubuntu-bug 
> /var/crash/_my_crash_report.crash'.
> 
> I'm closing this bug report since the process outlined above will
> automatically open a new bug report which can then dealt with more
> efficiently. Thanks in advance for your cooperation and understanding.
> 
> ** Changed in: libreoffice (Ubuntu)
>Status: New => Invalid
>

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

Title:
  Libre Office causes the windows manager to crash

Status in “libreoffice” package in Ubuntu:
  Invalid

Bug description:
  Using any Libre Office Program causes the windowmanager in GNOME3 to
  crash. Libre Office gives the following report but I dont think its
  helpful.

  (soffice:7456): GConf-WARNING **: Client failed to connect to the D-BUS 
daemon:
  Failed to connect to socket /tmp/dbus-rmjGw9pMuy: Connection refused
  GConf Error: No D-BUS daemon running

  
  ** (soffice:7456): WARNING **: Unable to create Ubuntu Menu Proxy: Error 
connecting: Connection refused

  (soffice:7456): GConf-WARNING **: Client failed to connect to the D-BUS 
daemon:
  Failed to connect to socket /tmp/dbus-rmjGw9pMuy: Connection refused
  GConf Error: No D-BUS daemon running

  
  (soffice:7456): GConf-WARNING **: Client failed to connect to the D-BUS 
daemon:
  Failed to connect to socket /tmp/dbus-rmjGw9pMuy: Connection refused
  GConf Error: No D-BUS daemon running

  
  (soffice:7456): GConf-WARNING **: Client failed to connect to the D-BUS 
daemon:
  Failed to connect to socket /tmp/dbus-rmjGw9pMuy: Connection refused
  GConf Error: No D-BUS daemon running

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libreoffice 1:3.4.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7
  Uname: Linux 3.2.0-7-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Thu Jan  5 16:01:21 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 912322] [NEW] Libre Office causes the windows manager to crash

[Thorsten]

Public bug reported:

Using any Libre Office Program causes the windowmanager in GNOME3 to
crash. Libre Office gives the following report but I dont think its
helpful.

(soffice:7456): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Failed to connect to socket /tmp/dbus-rmjGw9pMuy: Connection refused
GConf Error: No D-BUS daemon running


** (soffice:7456): WARNING **: Unable to create Ubuntu Menu Proxy: Error 
connecting: Connection refused

(soffice:7456): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Failed to connect to socket /tmp/dbus-rmjGw9pMuy: Connection refused
GConf Error: No D-BUS daemon running


(soffice:7456): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Failed to connect to socket /tmp/dbus-rmjGw9pMuy: Connection refused
GConf Error: No D-BUS daemon running


(soffice:7456): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Failed to connect to socket /tmp/dbus-rmjGw9pMuy: Connection refused
GConf Error: No D-BUS daemon running

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: libreoffice 1:3.4.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7
Uname: Linux 3.2.0-7-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Thu Jan  5 16:01:21 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug oneiric

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

Title:
  Libre Office causes the windows manager to crash

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  Using any Libre Office Program causes the windowmanager in GNOME3 to
  crash. Libre Office gives the following report but I dont think its
  helpful.

  (soffice:7456): GConf-WARNING **: Client failed to connect to the D-BUS 
daemon:
  Failed to connect to socket /tmp/dbus-rmjGw9pMuy: Connection refused
  GConf Error: No D-BUS daemon running

  
  ** (soffice:7456): WARNING **: Unable to create Ubuntu Menu Proxy: Error 
connecting: Connection refused

  (soffice:7456): GConf-WARNING **: Client failed to connect to the D-BUS 
daemon:
  Failed to connect to socket /tmp/dbus-rmjGw9pMuy: Connection refused
  GConf Error: No D-BUS daemon running

  
  (soffice:7456): GConf-WARNING **: Client failed to connect to the D-BUS 
daemon:
  Failed to connect to socket /tmp/dbus-rmjGw9pMuy: Connection refused
  GConf Error: No D-BUS daemon running

  
  (soffice:7456): GConf-WARNING **: Client failed to connect to the D-BUS 
daemon:
  Failed to connect to socket /tmp/dbus-rmjGw9pMuy: Connection refused
  GConf Error: No D-BUS daemon running

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libreoffice 1:3.4.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7
  Uname: Linux 3.2.0-7-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Thu Jan  5 16:01:21 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 912322] Re: Libre Office causes the windows manager to crash

[Thorsten]

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

Title:
  Libre Office causes the windows manager to crash

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  Using any Libre Office Program causes the windowmanager in GNOME3 to
  crash. Libre Office gives the following report but I dont think its
  helpful.

  (soffice:7456): GConf-WARNING **: Client failed to connect to the D-BUS 
daemon:
  Failed to connect to socket /tmp/dbus-rmjGw9pMuy: Connection refused
  GConf Error: No D-BUS daemon running

  
  ** (soffice:7456): WARNING **: Unable to create Ubuntu Menu Proxy: Error 
connecting: Connection refused

  (soffice:7456): GConf-WARNING **: Client failed to connect to the D-BUS 
daemon:
  Failed to connect to socket /tmp/dbus-rmjGw9pMuy: Connection refused
  GConf Error: No D-BUS daemon running

  
  (soffice:7456): GConf-WARNING **: Client failed to connect to the D-BUS 
daemon:
  Failed to connect to socket /tmp/dbus-rmjGw9pMuy: Connection refused
  GConf Error: No D-BUS daemon running

  
  (soffice:7456): GConf-WARNING **: Client failed to connect to the D-BUS 
daemon:
  Failed to connect to socket /tmp/dbus-rmjGw9pMuy: Connection refused
  GConf Error: No D-BUS daemon running

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libreoffice 1:3.4.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7
  Uname: Linux 3.2.0-7-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Thu Jan  5 16:01:21 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 606272] Re: scrolling with pagedown gets stuck

[Thorsten Hirsch]

Here's another one, where scrolling down gets stuck (on page 98):

http://eldiss.uni-
kiel.de/macau/servlets/MCRFileNodeServlet/dissertation_derivate_1687/d1687.pdf;jsessionid=5FB4373623B5C4A7CEE8A195A5FE8EA2

(You have to click on "Bestätigung" in order to download the PDF file)

Scrolling down does NOT get stuck when using the mouse.
You have to use the page down key to reproduce this bug.

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

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

Title:
  scrolling with pagedown gets stuck

Status in “evince” package in Ubuntu:
  New

Bug description:
  Binary package hint: evince

  When scrolling down the document from
  http://www.cs.wustl.edu/~schmidt/PDF/design-principles4.pdf with the
  pagedown key, the scrolling stucks at approximately the center, it
  does not jump to the next page. I can scroll it over that page with
  the scrollbar or the mouse, and after that, pagedown is working again,
  but there is a section it can't get past.

  Steps to repro:

  1. Open the file from 
http://www.cs.wustl.edu/~schmidt/PDF/design-principles4.pdf
  2. Press Scrolldown and see the pages scrolling

  expected: the document should scroll until the end of the page
  current: the scrolling stops at a given page, page 11 of 17.

  This is always reproducible on my pc running lucid and evince 2.30.3.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: evince 2.30.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 2.6.32-24.38-generic-pae 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-24-generic-pae i686
  NonfreeKernelModules: fglrx wl
  Architecture: i386
  Date: Fri Jul 16 15:34:06 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: evince

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

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

[Desktop-packages] [Bug 877339] Re: Totem crashes instantly on start, freezes the whole system

[Thorsten Reinbold]

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

Title:
  Totem crashes instantly on start, freezes the whole system

Status in “totem” package in Ubuntu:
  New

Bug description:
  When trying to launch totem or try to play a video with it, totem
  crashes the system completly. There are no other options than a hard
  reset (even magic sysrq isn't working). I was not able to get any
  further information. When starting totem via terminal, there are no
  massages before the crash occours. Totem shows up half blended (seems
  to crash while fading in the window).

  I'm not using Unity, instead I'm on Gnome-Shell. With Unity from a
  live-usb, this does not happen. I've tested totem 3.2 from Ricotz
  Testing PPA, the error does not occure with that version.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: totem 3.0.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Tue Oct 18 12:59:30 2011
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 877339] [NEW] Totem crashes instantly on start, freezes the whole system

[Thorsten Reinbold]

Public bug reported:

When trying to launch totem or try to play a video with it, totem
crashes the system completly. There are no other options than a hard
reset (even magic sysrq isn't working). I was not able to get any
further information. When starting totem via terminal, there are no
massages before the crash occours. Totem shows up half blended (seems to
crash while fading in the window).

I'm not using Unity, instead I'm on Gnome-Shell. With Unity from a live-
usb, this does not happen. I've tested totem 3.2 from Ricotz Testing
PPA, the error does not occure with that version.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: totem 3.0.1-0ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Tue Oct 18 12:59:30 2011
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: totem
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 oneiric

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

Title:
  Totem crashes instantly on start, freezes the whole system

Status in “totem” package in Ubuntu:
  New

Bug description:
  When trying to launch totem or try to play a video with it, totem
  crashes the system completly. There are no other options than a hard
  reset (even magic sysrq isn't working). I was not able to get any
  further information. When starting totem via terminal, there are no
  massages before the crash occours. Totem shows up half blended (seems
  to crash while fading in the window).

  I'm not using Unity, instead I'm on Gnome-Shell. With Unity from a
  live-usb, this does not happen. I've tested totem 3.2 from Ricotz
  Testing PPA, the error does not occure with that version.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: totem 3.0.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Tue Oct 18 12:59:30 2011
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 874248] Re: nautilus very unstable

[Thorsten]

Thanks for your answer, after installing the update, it's indeed fixed!

Am 17.10.2011 14:11, schrieb Sebastien Bacher:
> Thank you for your bug report, it's an issue due to ubuntuone-client-
> gnome which leads to conflict if you install nautilus code using gconf,
> you should install the ubuntuone-client-gnome stable update published
> today which fixes this issue
>
> ** Changed in: nautilus (Ubuntu)
> Importance: Undecided =>  Low
>
> ** Changed in: nautilus (Ubuntu)
> Status: New =>  Invalid
>

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

Title:
  nautilus very unstable

Status in “nautilus” package in Ubuntu:
  Invalid

Bug description:
  nautilus is nearly unusable, crahes all the time, e.g. when creating
  previews or when hitting F3

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: nautilus 1:3.2.0-0ubuntu5
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Fri Oct 14 16:01:35 2011
  ExecutablePath: /usr/bin/nautilus
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (0 days ago)

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

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

[Desktop-packages] [Bug 874248] [NEW] nautilus very unstable

[Thorsten]

Public bug reported:

nautilus is nearly unusable, crahes all the time, e.g. when creating
previews or when hitting F3

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.2.0-0ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Fri Oct 14 16:01:35 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: Upgraded to oneiric on 2011-10-14 (0 days ago)

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


** Tags: apport-bug apport-lpi i386 oneiric running-unity

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

Title:
  nautilus very unstable

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  nautilus is nearly unusable, crahes all the time, e.g. when creating
  previews or when hitting F3

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: nautilus 1:3.2.0-0ubuntu5
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Fri Oct 14 16:01:35 2011
  ExecutablePath: /usr/bin/nautilus
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (0 days ago)

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

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

[Desktop-packages] [Bug 874248] Re: nautilus very unstable

[Thorsten]

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

Title:
  nautilus very unstable

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  nautilus is nearly unusable, crahes all the time, e.g. when creating
  previews or when hitting F3

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: nautilus 1:3.2.0-0ubuntu5
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Fri Oct 14 16:01:35 2011
  ExecutablePath: /usr/bin/nautilus
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (0 days ago)

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

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

[Desktop-packages] [Bug 787465] Re: View->Show MenuBar isn't working in 11.04 and later

[Thorsten Reinbold]

For me it works after purging everything related to "appmenu" and
"application indicators".

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

Title:
  View->Show MenuBar isn't working in 11.04 and later

Status in “gnome-terminal” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gnome-terminal

  If you click on the global menus the View->Show MenuBar and (un)check
  it, it won't work, the menu will stay at the 'global menus panel' or
  whatever it is. In my opinion this option shouldn't exist now,
  considering that global menus are the future, and also considering
  that a global menu has the advantage not to keep its own space on the
  screen  :)

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

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

[Desktop-packages] [Bug 863038] Re: If turnoff the screen setting set to 'never' screen turns off instantly

[Thorsten Reinbold]

That's not the case on my System. When I set to never, the Screen stays
bright, but the buttom panel (I'm using gnome shell) comes up every time
I move the mouse (or type). This goes away if I revert the setting to
anything but "never".

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

Title:
  If turnoff the screen setting set to 'never' screen turns off
  instantly

Status in “gnome-control-center” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  In Progress

Bug description:
  If turnoff the screen setting set to 'never' screen turns off
  instantly!!!

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.2.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 1.23-0ubuntu2
  Architecture: i386
  Date: Fri Sep 30 09:17:59 2011
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   deja-dup   20.0-0ubuntu3
   gnome-bluetooth3.2.0-0ubuntu1
   indicator-datetime 0.3.0-0ubuntu1

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

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

[Desktop-packages] [Bug 833916] Re: unable to unzip a file

[Thorsten Reinbold]

Me, too. I'm getting an error message about an unsupported filetype with
every .zip. But it only fails with file-roller. When I'm using the
"unzip XYZ.zip"-command it is working.

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

Title:
  unable to unzip a file

Status in “file-roller” package in Ubuntu:
  Incomplete

Bug description:
  since a while , I'm unable to unzip a file. How many times I may try,
  I can't unzip a file.

  attached here is a screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: file-roller 3.1.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
  Uname: Linux 3.0.0-9-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Thu Aug 25 18:15:27 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: file-roller
  UpgradeStatus: Upgraded to oneiric on 2011-08-19 (6 days ago)

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

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