[Desktop-packages] [Bug 1586493] Re: "Expand on landscape screens" option not working in trunk

[marmuta]

** Changed in: onboard
   Status: Fix Committed => Fix Released

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

Title:
  "Expand on landscape screens" option not working in trunk

Status in Onboard:
  Fix Released
Status in onboard package in Ubuntu:
  Invalid

Bug description:
  "Expand on landscape screens" option not working in trunk, revision
  2152.

  Ubuntu Gnome 16.04 x86_64.
  Gnome Shell 3.18
  1920x1080 screen.

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

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

[Desktop-packages] [Bug 1352549] Re: layout reverts to default after inserting unicode character via long press on a key

[marmuta]

Fix released in Onboard 1.3.0.

** Changed in: onboard
   Status: Fix Committed => Fix Released

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

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

Title:
  layout reverts to default after inserting unicode character via long
  press on a key

Status in Onboard:
  Fix Released
Status in onboard package in Ubuntu:
  Fix Released

Bug description:
  I use onboard with 2 layouts. The english one (default) and the greek one 
(secondary). I change layouts via Ctrl+Space.
  When I use the greek layout, if I long press on a key and insert a unicode 
char, then while the greek layout is still visible (as it should be), pressing 
on a button results to the corresponding english char!
  For example, in greek layout I long press "ε" to insert "έ". After that, if I 
press again "ε" it results to "e".
  So while I still see the greek layout, pressing the keys results to the 
corresponding english chars. Obviously it should result to the greek chars

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  onboard:
Installed: 1.0.0-0ubuntu4
Candidate: 1.0.0-0ubuntu4
Version table:
   *** 1.0.0-0ubuntu4 0
  500 http://gr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1613063] Re: Request for sponsorship for new upstream release (yakkety deb provided)

[marmuta]

Thank you and thanks for the reminder. Francesco already left for
holiday. I'll be available in case anything breaks.

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

Title:
  Request for sponsorship for new upstream release (yakkety deb
  provided)

Status in onboard package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  A new Onboard version has just been released. Here is the relevant
  part of the debian/changelog from the debianisation I prepared for
  yakkety:

  onboard (1.2.0+2177-0ppa1~yakkety) yakkety; urgency=medium

* Request for sponsorship for new upstream release (LP: #1613063)
* debian/control: 
- Bump Standards-Version to 3.9.8
- Add libwayland-dev to Build-Depends
- Add libxkbcommon-dev to Build-Depends
* debian/copyright: update
* debian/onboard.install: add usr/share/dbus-1/services entry
* debian/patches:
  - Drop bzr_fix_untranslatable_buttons.patch: applied upstream
  - Drop fix_arrows_on_compact_layout.patch: applied upstream
  - Refresh add_defaults_for_ubuntu.patch
* debian/source.lintian-overrides: update entries line number
* Status icon:
  - Move AppIndicator and GtkStatusIcon into separate backends
  - Allow left-clicking AppIndicator in KDE Plasma
  - Don't crash when Appindicator or Atspi are not available
  - Fix fallback to GtkStatusIcon when Applndicator is not available
  - Fix tooltip of status icon provider (LP: #1570318). Thanks Ubuntu-QC-1
* Word suggestions and auto-correction:
  - Add Esperanto language model
  - Elipsize very large words and fix them being invisible
  - Fix Compact layout not showing the "More suggestions" arrows
  - Improve auto-correction of URLs and filenames in long texts
* Virtkey:
  - Improve search for available keysyms in X (LP:1562381)
  - Move key mapping from X functions to Xkb
  - Make Xkb-based mapping also work in Ubuntu-GNOME
  - Add uinput backend to virtkey for initial support of non-X desktops
  - Isolate X related parts of virtkey in preparation for non-X desktops
  - Add initial Wayland support (blocker: gtk_window_set_accept_focus())
* D-Bus service:
  - Add support for properties via python decorator
  - Setup D-Bus activation to simplify showing on hotkey press (LP: 
#1607235)
  - Update D-Bus usage examples in README
* Add fallback to default system font family for themes:
  - High contrast themes get a font this way
  - Fixes Ubuntu logo not appearing in yakkety
* Add aspect ratio limits when the keyboard is docked or expanded 
(LP:1586493)
* Add touch handle to adjust the docking aspect ratio limit
* Expand docked keyboard on landscape oriented screens by default
* Auto-detect default status-icon provider in major desktop environments
* Improve alignment of some labels in the Preferences dialog
* Fix former stock buttons in Preferences not being translated (LP: 
#1567301)
* Add small bitmap icons to prevent aliasing issues (LP: #1552484)
* Add more example keys to onboard-defaults.conf.example (LP: #1546654)
* Improve pep8 compliance of various source files
* Don't let the return key leave the screen for Small and Phone layouts
* Prevent setting new home position after accidental resize frame clicks
* Work around shadows becoming visible during resize when docked with 
sidebars
* Fix errors uncovered in Keyboard.py by flake8
* Fix unwanted key-repeats when typing into Gtk-3 applications (LP: 
#1562381)
* Fix keyboard sometimes starting up at unexpected positions on system start
* Fix build failure with gcc-6 that switched to C++14. Thanks Jeremy Bicha
* Fix warning when building with gcc versions before 6, i.e. C++98 by 
default
* Remove entries with default values from desktop files. Thanks Mike Gabriel
* Add 3.20 and 3.22 to shell-version field of GNOME extension. Thanks J. 
Bicha
* Care for compatibility with Ubuntu Precise (12.04)
* Update PPA link in README

   -- Francesco Fumanti   Sun, 13 Aug 2016
  22:23:14 +0200

  The debianisation attached to this request for sponsorship has been
  based on the Onboard package currently in the main yakkety repository.
  On my uptodate Ubuntu yakkety installation, the debianisation provided
  here successfully builds and the resulting packages seem to be running
  fine here.

  Could you please review the package for inclusion into the main
  yakkety repository.

  Don't hesitate to contact us if you need further information:
  https://launchpad.net/~onboard/+contactuser or simply be writing in this bug 
thread.

  Thanks in advance for your help.

  Have a good day.

  Francesco

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1613708] Re: Some Xapps buttons are not responding

[Daniel van Vugt]

I can think of two more reasons why buttons would become unclickable:

1. One of your modifier keys (Alt/Shift/Ctrl) are either physically or
logically (in software) stuck down. Try tapping all the Alt/Shift/Ctrl
keys. This is definitely a problem for X apps under the Mir demo servers
after you Alt+Tab but not a problem under Unity8 AFAIK.

2. Try rotating the tablet to a different orientation. You might be
experiencing a problem similar to bug 1502805.

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

Title:
  Some Xapps buttons are not responding

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Enviroment:

  current build number: 169
  device name: frieza
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
  last update: 2016-08-16 10:23:29
  version version: 169
  version ubuntu: 20160816
  version device: 20160809.0
  version custom: 20160805--42-20-vivid

  Product: BQ M10 FHD

  Steps to reproduce:

  1º Open LibreOffice and try to print something
  2º Print settings window appear, try to click on Accept/Cancel/Exit etc
  3º Buttons on LibreOffice won't respond

  1º Open Firefox
  2º Mouse-over on search,downloads,bookmarks etc
  3º Seems like mouse-over is not focused and is clicking is not responding

  Current result: Some Xapps buttons are not responding(tested on
  Firefox and LibreOffice Writer)

  Expected result:

  Add info: This is using xmir from https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/landing-053/+packages.

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

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

[Desktop-packages] [Bug 1613708] Re: Some Xapps buttons are not responding

[Daniel van Vugt]

Sorry, ignore bug 1590553... Both its description and its fix apply to
-rootless mode only, which we don't use in Unity8.

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

Title:
  Some Xapps buttons are not responding

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Enviroment:

  current build number: 169
  device name: frieza
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
  last update: 2016-08-16 10:23:29
  version version: 169
  version ubuntu: 20160816
  version device: 20160809.0
  version custom: 20160805--42-20-vivid

  Product: BQ M10 FHD

  Steps to reproduce:

  1º Open LibreOffice and try to print something
  2º Print settings window appear, try to click on Accept/Cancel/Exit etc
  3º Buttons on LibreOffice won't respond

  1º Open Firefox
  2º Mouse-over on search,downloads,bookmarks etc
  3º Seems like mouse-over is not focused and is clicking is not responding

  Current result: Some Xapps buttons are not responding(tested on
  Firefox and LibreOffice Writer)

  Expected result:

  Add info: This is using xmir from https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/landing-053/+packages.

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

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

[Desktop-packages] [Bug 1613954] [NEW] Sync appstream-glib 0.6.1-1 (main) from Debian unstable (main)

[Jeremy Bicha]

Public bug reported:

Please sync appstream-glib 0.6.1-1 (main) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * New upstream release
  * debian/libappstream-glib8.symbols:
- Updated
  * New upstream release
  * debian/patches/yaml-icon-spec-compliant.patch:
- Applied upstream

All of that was applied in Debian.

The new upstream release is needed for some GNOME 3.22 modules
like gnome-chess or swell-foop which are now using the translate
URL type.

The new release allows addons to magically work in GNOME Software.

Changelog entries since current yakkety version 0.5.17-0ubuntu1:

appstream-glib (0.6.1-1) unstable; urgency=medium

  * New upstream release: 0.6.1
  * Drop all patches: Applied upstream
  * Build-depend on gperf
  * Update symbols file

 -- Matthias Klumpp   Tue, 16 Aug 2016 19:48:46 +0200

appstream-glib (0.5.17-1) unstable; urgency=medium

  * New upstream release: 0.5.17
- Closes: #833293
  * no-redundant-monitor.patch: Fix redundant monitoring of files
  * read-component-types.patch: Read modern component type names
  * yaml-fix-component-types.patch: Fix reading of components that aren't apps
  * Update symbols file
  * Make dev package depend on GIR package (Closes: #833290)

 -- Matthias Klumpp   Thu, 11 Aug 2016 19:54:06 +0200

** Affects: appstream-glib (Ubuntu)
 Importance: Wishlist
 Status: New

** Changed in: appstream-glib (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Sync appstream-glib 0.6.1-1 (main) from Debian unstable (main)

Status in appstream-glib package in Ubuntu:
  New

Bug description:
  Please sync appstream-glib 0.6.1-1 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* New upstream release
* debian/libappstream-glib8.symbols:
  - Updated
* New upstream release
* debian/patches/yaml-icon-spec-compliant.patch:
  - Applied upstream

  All of that was applied in Debian.

  The new upstream release is needed for some GNOME 3.22 modules
  like gnome-chess or swell-foop which are now using the translate
  URL type.

  The new release allows addons to magically work in GNOME Software.

  Changelog entries since current yakkety version 0.5.17-0ubuntu1:

  appstream-glib (0.6.1-1) unstable; urgency=medium

* New upstream release: 0.6.1
* Drop all patches: Applied upstream
* Build-depend on gperf
* Update symbols file

   -- Matthias Klumpp   Tue, 16 Aug 2016 19:48:46 +0200

  appstream-glib (0.5.17-1) unstable; urgency=medium

* New upstream release: 0.5.17
  - Closes: #833293
* no-redundant-monitor.patch: Fix redundant monitoring of files
* read-component-types.patch: Read modern component type names
* yaml-fix-component-types.patch: Fix reading of components that aren't apps
* Update symbols file
* Make dev package depend on GIR package (Closes: #833290)

   -- Matthias Klumpp   Thu, 11 Aug 2016 19:54:06 +0200

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

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

[Desktop-packages] [Bug 115086] news from my family

[Wanderlust]

Hi friend!

I just wanted to tell you that we are all ok, and we have some  good
news,  read it here  please


Sent from my iPhone, Andrii Borovyi

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

Title:
  firefox crashed

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: firefox

  ... Firefox crash with "BadShmSeg" error

  
  Firefox crashes on website http://my.nnm.ru/bookmarks/316189 (requires 
autorisation).
  Error in gnome-terminal:

  wanderlust@eagle:/home/Video$ firefox 
  ** Message: GetValue variable 1 (1)
  ** Message: GetValue variable 2 (2)
  ** Message: GetValue variable 1 (1)
  ** Message: GetValue variable 2 (2)
  ** Message: GetValue variable 1 (1)
  ** Message: GetValue variable 2 (2)
  ** Message: GetValue variable 1 (1)
  ** Message: GetValue variable 2 (2)
  Improper call to JPEG library in state 202
  Unable to read JPEG data
  Improper call to JPEG library in state 202
  Unable to read JPEG data
  The program 'Gecko' received an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadShmSeg (invalid shared segment parameter)'.
(Details: serial 230 error_code 166 request_code 143 minor_code 2)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the --sync command line
 option to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)

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

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

[Desktop-packages] [Bug 1562381] Re: Typing special characters with non-US layout get repeated indefinitely

[RussianNeuroMancer]

** Changed in: onboard
   Status: Fix Committed => Fix Released

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

Title:
  Typing special characters with non-US layout get repeated indefinitely

Status in Onboard:
  Fix Released
Status in onboard package in Ubuntu:
  Fix Released

Bug description:
  Typing special characters like .,:;-()"@# (and other) or numbers with
  non-US keyboard layout get repeated indefinitely, like this:

  
тест...

  This will continue to happen untl other symbol is entered or other
  button is pressed. Reproducible with GTK and Xinput. Testng was done
  on Ubuntu Gnome 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: onboard 1.2.0-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 27 02:29:05 2016
  InstallationDate: Installed on 2016-03-19 (6 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160319)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: onboard
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1613708] Re: Some Xapps buttons are not responding

[Daniel van Vugt]

I've been trying and can't seem to reproduce any such bug with the
latest Unity8 and the latest Xmir in yakkety. Everything is clickable in
LibreOffer and Firefox.

It's possible your vivid image is missing the most recent Xmir fix that
was bug 1590553 (like what you describe).

It's also possible matchbox-wm is misplacing windows as looks like the
case in your video (the dialog should not appear on the right hand
side). It also seems that matchbox-wm will ignore mouse input in the
non-focused window without making it obvious which one that is. So try
clicking around to see what is responding.

Sorry, I also don't have an M10 to test with. But I can at least say
that I can't reproduce this with the latest Xmir.

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

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

Title:
  Some Xapps buttons are not responding

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Enviroment:

  current build number: 169
  device name: frieza
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
  last update: 2016-08-16 10:23:29
  version version: 169
  version ubuntu: 20160816
  version device: 20160809.0
  version custom: 20160805--42-20-vivid

  Product: BQ M10 FHD

  Steps to reproduce:

  1º Open LibreOffice and try to print something
  2º Print settings window appear, try to click on Accept/Cancel/Exit etc
  3º Buttons on LibreOffice won't respond

  1º Open Firefox
  2º Mouse-over on search,downloads,bookmarks etc
  3º Seems like mouse-over is not focused and is clicking is not responding

  Current result: Some Xapps buttons are not responding(tested on
  Firefox and LibreOffice Writer)

  Expected result:

  Add info: This is using xmir from https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/landing-053/+packages.

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

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

[Desktop-packages] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics

[Chris Martin]

@adconrad, fix works for me as well. Thank you!

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

Title:
  Mouse cursor lost when unlocking with Intel graphics

Status in elementary OS:
  Fix Released
Status in xf86-video-intel:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-intel package in Debian:
  Fix Released

Bug description:
  [Impact]
  Mouse cursor is no longer visible after VT-switch for systems with Intel 
graphics.

  Switching VTs again may cause the cursor to become visible again.
  - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7)

  This is often observed in systems that lock the session and return to
  the greeter (including at least Xubuntu, Ubuntu Mate, and elementary
  OS).

  [Test Case]
  (Requires a lightdm-based screen locking solution)
  1. Start a new session.
  2. Lock your screen.
  2a. You are redirected to the lightdm greeter.
  3. Login/Unlock your session.
  4. Cursor is no longer visible.

  [Regression Potential]
  remains to be seen

  ===

  [Original Report]
  Cursor is visible at unlock screen either after returning from suspend or 
just locking.

  After unlocking screen cursor is invisible.

  Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor
  returns

  

  no matter if you suspend or sleep, to swap or disk when you return
  from it, the mouse cursor is missing.you can still move the mouse
  and you can see (because it highlights the window) as you move it
  around.   But the cursor is not displayed on the screen.

  i am using a lenovo W540 laptop.   I downloaded the latest beta on
  april 8 2016.

  this is xubuntu using the xfce window manager.

  the cursor does return if i log off and log back in, but that actually 
defeats the purpose of going to sleep.
  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-08 (2 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1613600] Re: package liba11y-profile-manager-data 0.1.11-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/a11y-profile-manager/profiles/blindness/profile.man

[Launchpad Bug Tracker]

This bug was fixed in the package a11y-profile-manager - 0.1.11-0ubuntu2

---
a11y-profile-manager (0.1.11-0ubuntu2) yakkety; urgency=medium

  * Add breaks against accessibility profiles packages for
liba11y-profile-manager-data (LP: #1613600)

 -- Luke Yelavich   Wed, 17 Aug 2016 10:16:19 +1000

** Changed in: a11y-profile-manager (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  package liba11y-profile-manager-data 0.1.11-0ubuntu1 failed to
  install/upgrade: trying to overwrite '/usr/share/a11y-profile-
  manager/profiles/blindness/profile.manifest', which is also in package
  unity-accessibility-profiles 0.1.10-0ubuntu3

Status in a11y-profile-manager package in Ubuntu:
  Fix Released

Bug description:
  This is 16.10, and apparently an error happened while I was trying to
  fix apt. Don't know really what it was.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: liba11y-profile-manager-data 0.1.11-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 16 00:55:09 2016
  DuplicateSignature:
   package:liba11y-profile-manager-data:0.1.11-0ubuntu1
   Unpacking liba11y-profile-manager-data (0.1.11-0ubuntu1) over 
(0.1.10-0ubuntu3) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-3A0in8/04-liba11y-profile-manager-data_0.1.11-0ubuntu1_all.deb
 (--unpack):
trying to overwrite 
'/usr/share/a11y-profile-manager/profiles/blindness/profile.manifest', which is 
also in package unity-accessibility-profiles 0.1.10-0ubuntu3
  ErrorMessage: trying to overwrite 
'/usr/share/a11y-profile-manager/profiles/blindness/profile.manifest', which is 
also in package unity-accessibility-profiles 0.1.10-0ubuntu3
  InstallationDate: Installed on 2016-08-16 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160815)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.9ubuntu2
   apt  1.3~rc1ubuntu2
  SourcePackage: a11y-profile-manager
  Title: package liba11y-profile-manager-data 0.1.11-0ubuntu1 failed to 
install/upgrade: trying to overwrite 
'/usr/share/a11y-profile-manager/profiles/blindness/profile.manifest', which is 
also in package unity-accessibility-profiles 0.1.10-0ubuntu3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1586539] Re: Major screen flickering in Chromium and Google Chrome

[byj.tea]

I had the same problem of screen flickering or tearing, not only in
Chrome but also in wine Warcraft III in opengl mode(D3D mode works
fine), and by removing package xserver-xorg-video-intel as #11 gave,
every thing just works perfectly so far.

I use this link to test, http://animated-gifs-funny.tumblr.com/archive,
mentioned by
https://bugs.chromium.org/p/chromium/issues/detail?id=606152#c44,
confirmed after the fix the problem is gone.

My system is HP xps15, Intel skylake i7-6500u, Linux mint 18, kernel
4.4.0-21-generic.

>From what apt show xserver-xorg-video-intel tells it seems it is safe to 
>remove the package if your hw is new enough.
"
This package is built from the X.org xf86-video-intel driver module.
 .
 The use of this driver is discouraged if your hw is new enough (ca.
 2007 and newer). You can try uninstalling this driver and let the
 server use it's builtin modesetting driver instead.
"

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

Title:
  Major screen flickering in Chromium and Google Chrome

Status in X.Org X server:
  Unknown
Status in xserver-xorg-video-intel package in Ubuntu:
  Triaged

Bug description:
  On a fresh installation of Ubuntu 16.04 I noticed major screen
  flickering issues in Chromium and Google Chrome browsers. Since this
  never happened in Ubuntu 15.10 with exactly the same Google Chrome
  binary, I believe, bug is caused by something that was added/updated
  in 16.04. I came across some discussions where different people
  suggested that it is related to new X.Org version.

  Here's a video to show what is happening:
  https://youtu.be/l21WsKz3fZc?t=45s

  I could fix this flickering with --disable-gpu-compositing switch, but
  this slows down page drawing significantly so it can't be considered a
  workaround. There is also a Chromium bug report:
  https://bugs.chromium.org/p/chromium/issues/detail?id=606152, but I
  don't think they will fix an Ubuntu-specific bug.

  Update: this indeed happens only when browser window is maximized.

  WORKAROUND: Add in /usr/share/X11/xorg.conf.d/20-intel.conf:

  Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "AccelMethod" "uxa"
  EndSection

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.6.0-040600-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:

  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: Sat May 28 00:01:20 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.20, 4.4.0-22-generic, x86_64: installed
   vboxhost, 5.0.20, 4.6.0-040600-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:13bd]
  InstallationDate: Installed on 2016-05-01 (26 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. UX301LAA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.0-040600-generic 
root=UUID=172b2d49-444a-466b-ab91-b74605125b29 ro quiet splash rootfstype=ext4 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX301LAA.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX301LAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX301LAA.211:bd06/05/2015:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX301LAA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  

[Desktop-packages] [Bug 1613708] Re: Some Xapps buttons are not responding

[Daniel van Vugt]

Sounds like bug 1590553, but the PPA you refer to seems to have that fix
already.

** Changed in: xorg-server (Ubuntu)
   Importance: Undecided => High

** Changed in: xorg-server (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

Title:
  Some Xapps buttons are not responding

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Enviroment:

  current build number: 169
  device name: frieza
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
  last update: 2016-08-16 10:23:29
  version version: 169
  version ubuntu: 20160816
  version device: 20160809.0
  version custom: 20160805--42-20-vivid

  Product: BQ M10 FHD

  Steps to reproduce:

  1º Open LibreOffice and try to print something
  2º Print settings window appear, try to click on Accept/Cancel/Exit etc
  3º Buttons on LibreOffice won't respond

  1º Open Firefox
  2º Mouse-over on search,downloads,bookmarks etc
  3º Seems like mouse-over is not focused and is clicking is not responding

  Current result: Some Xapps buttons are not responding(tested on
  Firefox and LibreOffice Writer)

  Expected result:

  Add info: This is using xmir from https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/landing-053/+packages.

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

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

[Desktop-packages] [Bug 1316873] Re: Left mouse button stops working

[Archer Zhao]

The mouse works well on 12.04. After upgrade to 14.04, it start to have
this same problem. It still exist after upgrade to 16.04.

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

Title:
  Left mouse button stops working

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  This  problem has plagued me for a few years across different laptops
  and Ubuntu versions. Current I am experiencing this on a Dell Inspiron
  15z running Ubuntu 14.04 LTS.

  It typically starts after I have used the chat or call feature in
  gmail, by clicking on the phone icon in the left chat margin. I am a
  Firefox user and have not tested this with chrome etc. It has not
  happened if i dont install google-talkplugin so it is quite possible
  that the plugin is to blame.

  Symptom
  ===
  The left mouse button on all attached mice - USB , Trackpad and touch - will 
not do anything  however the right mouse button continues to work.  This 
happens to all applications and also to the desktop. The keyboard continues to 
function as normal.

  When this occurs , my solution is to Alt-F4 close all windows and log
  out of the X session. When I re-login the left mouse button works as
  normal.

  
  This is an irritant and work disruptor as I have to save all browser and 
desktop applications to  safe state before I logout to reset the mouse. I will 
appreciate any soltion or workaround.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  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: Tue May  6 21:41:29 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:058f]
  InstallationDate: Installed on 2014-04-17 (19 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 5523
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=f5004b03-b37f-4733-88a8-51c6f3bd0a4d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0GKGJG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/18/2013:svnDellInc.:pnInspiron5523:pvrNotSpecified:rvnDellInc.:rn0GKGJG:rvrA05:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5523
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  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
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue May  6 21:20:40 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5558 
   vendor CMN
  xserver.version: 2:1.15.1-0ubuntu2

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

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

[Desktop-packages] [Bug 872483] Re: laser printer only prints first job correct

[benohb]

Kyocera Ecosys M3020DN 
ubuntu 15.04 64bit
 Gutenprint,Foomatic/pxlmono, Generic PCL-5e +  original Kyocera driver (PPD )
-
The printer works well .until printer go to mode  sleep (~1mn without any job) 
. .You can not print after the re-activation
(Symbols or lines unknown)
---
Thanks for Solutions above .

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

Title:
  laser printer only prints first job correct

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Oneiric:
  Won't Fix
Status in cups source package in Precise:
  Fix Released

Bug description:
  please also refer to this bug - this seems to be exactly my issue and does 
not seem to be solved.
  https://bugs.launchpad.net/ubuntu/+source/foomatic-db/+bug/855412

  
  ProblemType: Bug
  DistroRelease: Ubuntu 11.10 - all updates as of today applied.

  I followed https://wiki.ubuntu.com/DebuggingPrintingProblems according
  to https://bugs.launchpad.net/ubuntu/+source/foomatic-
  db/+bug/855412/comments/20

  I printed two copies of the same document, since this forces the error
  easily.

  The content under /var/spool/cups/d... look fine - see attached files.

  after cupsenable  the first copy comes out fine - the second
  as random character - I stopped after some pages.

  The test is with Samsung ML-2250 Series (SPL II) - which worked fine under 
all previous versions of Ubuntu
  Samsung ML-2250 Foomatic/pxlmono (recommended) generates basically the same 
result.

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

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

[Desktop-packages] [Bug 1613925] [NEW] PPC system locks up after sas3ircu command is issued during RAID rebuild

[dexterb]

Public bug reported:

We have a PPC system on Ubuntu 16.04.1 LTS that will lock up if we issue a 
display or status command to the RAID controller during RAID rebuild process.  
The HDDs where the Operating system resides will change to RO (Read Only) once 
we trigger the problem.  This will only occur if the Operating System's HDDs 
are also connected to the RAID controller.  We've tried this problem with the 
OS residing on a USB and this problem does not occur.
  
Apport is not writing or reporting anything in the "/etc/apport/" directory
"ubuntu-bug" is not accessible after the crash.


Ubuntu 16.04.1 LTS
4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 ppc64le
PPC64EL (Power8)
RAID Controller: LSI SAS3008
   - Driver: mpt3sas
   - Driver version: 12.100.00.00
HDDs:
   - 2x WD Re SATA WD5003ABYZ-011FA0 (RAID0 / OS resides)
   - 2x Seagate ST6000NM0034 (FW: E001) (RAID1)

1.) Ubuntu 16.04.1 LTS
2.) 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 ppc64le
3.) A driver update to prevent this from crashing the system.
4.) The system crashed.  Please read the first paragraph above.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: udisks2 (not installed)
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic ppc64le
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: ppc64el
Date: Tue Aug 16 18:23:32 2016
InstallationDate: Installed on 2016-08-16 (0 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release ppc64el 
(20160719)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcLoadAvg: 0.00 0.01 0.00 1/1117 9416
ProcLocks:
 1: FLOCK  ADVISORY  WRITE 7727 00:17:5 0 EOF
 2: FLOCK  ADVISORY  WRITE 7723 00:14:631 0 EOF
ProcSwaps:
 Filename   TypeSizeUsedPriority
 /dev/sda3   partition  394321280   
-1
ProcVersion: Linux version 4.4.0-31-generic (buildd@bos01-ppc64el-028) (gcc 
version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2.1) ) #50-Ubuntu SMP Wed Jul 
13 00:05:18 UTC 2016
SourcePackage: udisks2
Symptom: storage
Title: No permission to access files on storage device
UpgradeStatus: No upgrade log present (probably fresh install)
cpu_cores: Number of cores present = 20
cpu_coreson: Number of cores online = 20
cpu_smt: SMT=8

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


** Tags: apport-bug ppc64el xenial

** Attachment added: "copies of dmesg, kernlog, mount, syslog files."
   
https://bugs.launchpad.net/bugs/1613925/+attachment/4722422/+files/compile-logs.zip

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

Title:
  PPC system locks up after sas3ircu command is issued during RAID
  rebuild

Status in udisks2 package in Ubuntu:
  New

Bug description:
  We have a PPC system on Ubuntu 16.04.1 LTS that will lock up if we issue a 
display or status command to the RAID controller during RAID rebuild process.  
The HDDs where the Operating system resides will change to RO (Read Only) once 
we trigger the problem.  This will only occur if the Operating System's HDDs 
are also connected to the RAID controller.  We've tried this problem with the 
OS residing on a USB and this problem does not occur.

  Apport is not writing or reporting anything in the "/etc/apport/" directory
  "ubuntu-bug" is not accessible after the crash.

  
  Ubuntu 16.04.1 LTS
  4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 ppc64le
  PPC64EL (Power8)
  RAID Controller: LSI SAS3008
 - Driver: mpt3sas
 - Driver version: 12.100.00.00
  HDDs:
 - 2x WD Re SATA WD5003ABYZ-011FA0 (RAID0 / OS resides)
 - 2x Seagate ST6000NM0034 (FW: E001) (RAID1)

  1.) Ubuntu 16.04.1 LTS
  2.) 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 ppc64le
  3.) A driver update to prevent this from crashing the system.
  4.) The system crashed.  Please read the first paragraph above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udisks2 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic ppc64le
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: ppc64el
  Date: Tue Aug 16 18:23:32 2016
  InstallationDate: Installed on 2016-08-16 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release ppc64el 
(20160719)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcLoadAvg: 0.00 0.01 0.00 1/1117 9416
  ProcLocks:
   1: FLOCK  ADVISORY  WRITE 7727 00:17:5 0 EOF
   2: FLOCK  ADVISORY  WRITE 7723 00:14:631 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /dev/sda3   partition394321280   
-1
  ProcVersion: Linux 

Re: [Desktop-packages] [Bug 1613763] Re: package liba11y-profile-manager-data 0.1.10-0ubuntu3 failed to install/upgrade: trying to overwrite '/usr/share/a11y-profile-manager/profiles/blindness/profile

[Luke Yelavich]

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

 duplicate 1613600


** This bug has been marked a duplicate of bug 1613600
   package liba11y-profile-manager-data 0.1.11-0ubuntu1 failed to 
install/upgrade: trying to overwrite 
'/usr/share/a11y-profile-manager/profiles/blindness/profile.manifest', which is 
also in package unity-accessibility-profiles 0.1.10-0ubuntu3

** This bug has been marked a duplicate of bug 1613600
   package liba11y-profile-manager-data 0.1.11-0ubuntu1 failed to 
install/upgrade: trying to overwrite 
'/usr/share/a11y-profile-manager/profiles/blindness/profile.manifest', which is 
also in package unity-accessibility-profiles 0.1.10-0ubuntu3

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

Title:
  package liba11y-profile-manager-data 0.1.10-0ubuntu3 failed to
  install/upgrade: trying to overwrite '/usr/share/a11y-profile-
  manager/profiles/blindness/profile.manifest', which is also in package
  unity-accessibility-profiles 0.1.10-0ubuntu3

Status in a11y-profile-manager package in Ubuntu:
  Confirmed

Bug description:
  software updater crashed while updating   --please fix

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: liba11y-profile-manager-data 0.1.10-0ubuntu3
  ProcVersionSignature: Ubuntu 4.6.0-10.12-generic 4.6.5
  Uname: Linux 4.6.0-10-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 16 09:53:35 2016
  DuplicateSignature:
   package:liba11y-profile-manager-data:0.1.10-0ubuntu3
   Unpacking liba11y-profile-manager-data (0.1.11-0ubuntu1) over 
(0.1.10-0ubuntu3) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-QPwYOH/12-liba11y-profile-manager-data_0.1.11-0ubuntu1_all.deb
 (--unpack):
trying to overwrite 
'/usr/share/a11y-profile-manager/profiles/blindness/profile.manifest', which is 
also in package unity-accessibility-profiles 0.1.10-0ubuntu3
  ErrorMessage: trying to overwrite 
'/usr/share/a11y-profile-manager/profiles/blindness/profile.manifest', which is 
also in package unity-accessibility-profiles 0.1.10-0ubuntu3
  InstallationDate: Installed on 2016-06-11 (65 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160515)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc1ubuntu2
  SourcePackage: a11y-profile-manager
  Title: package liba11y-profile-manager-data 0.1.10-0ubuntu3 failed to 
install/upgrade: trying to overwrite 
'/usr/share/a11y-profile-manager/profiles/blindness/profile.manifest', which is 
also in package unity-accessibility-profiles 0.1.10-0ubuntu3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1613911] [NEW] /usr/bin/gs:11:gs_heap_resize_object:gdev_prn_allocate:gdev_prn_reallocate_memory:gdev_prn_maybe_realloc_memory:cups_put_params

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding ghostscript.  This problem was most recently seen with version
9.18~dfsg~0-0ubuntu2, the problem page at
https://errors.ubuntu.com/problem/1e30e804632624f8205c303fb42faa9cd8e7bb5d
contains more details.

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


** Tags: vivid wily xenial

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

Title:
  
/usr/bin/gs:11:gs_heap_resize_object:gdev_prn_allocate:gdev_prn_reallocate_memory:gdev_prn_maybe_realloc_memory:cups_put_params

Status in ghostscript package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding ghostscript.  This problem was most recently seen with
  version 9.18~dfsg~0-0ubuntu2, the problem page at
  https://errors.ubuntu.com/problem/1e30e804632624f8205c303fb42faa9cd8e7bb5d
  contains more details.

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

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

[Desktop-packages] [Bug 913434] Re: ImageIO crashes (core dumped) while reading many image files

[Launchpad Bug Tracker]

This bug was fixed in the package openjdk-7 -
7u111-2.6.7-0ubuntu0.12.04.2

---
openjdk-7 (7u111-2.6.7-0ubuntu0.12.04.2) precise-security; urgency=medium

  * Backport to Ubuntu 12.04.

openjdk-7 (7u111-2.6.7-0ubuntu0.14.04.2) trusty-security; urgency=medium

  * debian/patches/it-jamvm-8158260-unsafe-methods.patch: fix JAMVM
after the introduction of two new Unsafe methods in the OpenJDK
hotspot. Closes: #833933. (LP: #1611598)

openjdk-7 (7u111-2.6.7-0ubuntu0.12.04.1) precise-security;
urgency=medium

  * Backport to Ubuntu 12.04.

openjdk-7 (7u111-2.6.7-0ubuntu0.14.04.1) trusty-security; urgency=medium

  [ Matthias Klose ]
  * Fix handling of /usr/lib/jvm/*/jre/lib/zi if internal tzdata is used
(Andreas Beckmann). Closes: #821858.
  * Add missing includes for aarch64 hotspot backport (building without pch).
  * Use in-tree lcms for backports.

  [ Tiago Stürmer Daitx ]
  * IcedTea release 2.6.7 (based on 7u111):
  * Security fixes
- S8079718, CVE-2016-3458: IIOP Input Stream Hooking
- S8145446, CVE-2016-3485: Perfect pipe placement (Windows only)
- S8147771: Construction of static protection domains under Javax
  custom policy
- S8148872, CVE-2016-3500: Complete name checking
- S8149962, CVE-2016-3508: Better delineation of XML processing
- S8150752: Share Class Data
- S8151925: Font reference improvements
- S8152479, CVE-2016-3550: Coded byte streams
- S8155981, CVE-2016-3606: Bolster bytecode verification
- S8155985, CVE-2016-3598: Persistent Parameter Processing
- S8158571, CVE-2016-3610: Additional method handle validation
  * debian/rules:
- Create symbolic link in source package (thanks Avinash).
  Closes: #832720.
- Use in-tree lcms (LP: #913434)
  * debian/JB-jre-headless.prerm.in: check for /var/lib/binfmts/jar
instead of /var/lib/binfmts/@basename@ before removing jar entry
from binfmts. Closes: #821146.

 -- Tiago Stürmer Daitx   Wed, 10 Aug 2016
20:46:47 +

** Changed in: openjdk-7 (Ubuntu)
   Status: Incomplete => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-3458

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-3485

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-3500

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-3508

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-3550

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-3598

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-3606

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-3610

** Changed in: openjdk-7 (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  ImageIO crashes (core dumped) while reading many image files

Status in OpenJDK:
  Fix Released
Status in lcms2 package in Ubuntu:
  Incomplete
Status in openjdk-7 package in Ubuntu:
  Fix Released

Bug description:
  Code that uses ImageIO.read() to read many image files (on my system:
  270 files, totalling 522.9 MiB) crashes the JVM.

  ~~~ My system information:

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

  $ uname -a
  Linux dowah 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 
x86_64 x86_64 x86_64 GNU/Linux

  $ javac -version
  javac 1.7.0_147

  $ java -version
  java version "1.7.0_147-icedtea"

  ~~~ To reproduce the error:

  $ javac BugIIO.java

  $ ulimit -c unlimited # to enable core dump

  $ java BugIIO

  ~~~ Terminal output that signifies the error:

  #
  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7fb5babe31f8, pid=4978, tid=140418842154752
  #
  # JRE version: 7.0_147-b147
  # Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 
compressed oops)
  # Derivative: IcedTea7 2.0
  # Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.1
  # Problematic frame:
  # C  [liblcms2.so.2+0x121f8]  cmsSaveProfileToIOhandler+0x38
  #
  # Core dump written. Default location: /home/joshua/core or core.4978
  #
  # An error report file with more information is saved as:
  # /home/joshua/hs_err_pid4978.log
  #
  # If you would like to submit a bug report, please include
  # instructions on how to reproduce the bug and visit:
  #   https://bugs.launchpad.net/ubuntu/+source/openjdk-7/
  #
  Dibatalkan (core didump)

  ~~~ PS
  When I tried to compile BugIIO.java on openjdk-6 and run it on openjdk-6, the 
program finishes normally (no crash).

  To clarify:
  1. This bug affect OpenJDK 7 (7~b147-2.0-0ubuntu0.11.10.1) (tested on 
oneiric).
  2. This bug does *not* affect OpenJDK 6 

[Desktop-packages] [Bug 913434] Re: ImageIO crashes (core dumped) while reading many image files

[Launchpad Bug Tracker]

This bug was fixed in the package openjdk-7 -
7u111-2.6.7-0ubuntu0.14.04.3

---
openjdk-7 (7u111-2.6.7-0ubuntu0.14.04.3) trusty-security; urgency=medium

  * debian/rules:
- fix typo (aarch64 -> arm64) and disable precompiled headers for
  arm64
- remove compile file generated by automake during debian cleanup

openjdk-7 (7u111-2.6.7-0ubuntu0.14.04.2) trusty-security; urgency=medium

  * debian/patches/it-jamvm-8158260-unsafe-methods.patch: fix JAMVM
after the introduction of two new Unsafe methods in the OpenJDK
hotspot. Closes: #833933. (LP: #1611598)

openjdk-7 (7u111-2.6.7-0ubuntu0.14.04.1) trusty-security; urgency=medium

  [ Matthias Klose ]
  * Fix handling of /usr/lib/jvm/*/jre/lib/zi if internal tzdata is used
(Andreas Beckmann). Closes: #821858.
  * Add missing includes for aarch64 hotspot backport (building without pch).
  * Use in-tree lcms for backports.

  [ Tiago Stürmer Daitx ]
  * IcedTea release 2.6.7 (based on 7u111):
  * Security fixes
- S8079718, CVE-2016-3458: IIOP Input Stream Hooking
- S8145446, CVE-2016-3485: Perfect pipe placement (Windows only)
- S8147771: Construction of static protection domains under Javax
  custom policy
- S8148872, CVE-2016-3500: Complete name checking
- S8149962, CVE-2016-3508: Better delineation of XML processing
- S8150752: Share Class Data
- S8151925: Font reference improvements
- S8152479, CVE-2016-3550: Coded byte streams
- S8155981, CVE-2016-3606: Bolster bytecode verification
- S8155985, CVE-2016-3598: Persistent Parameter Processing
- S8158571, CVE-2016-3610: Additional method handle validation
  * debian/rules:
- Create symbolic link in source package (thanks Avinash).
  Closes: #832720.
- Use in-tree lcms (LP: #913434)
  * debian/JB-jre-headless.prerm.in: check for /var/lib/binfmts/jar
instead of /var/lib/binfmts/@basename@ before removing jar entry
from binfmts. Closes: #821146.

 -- Tiago Stürmer Daitx   Thu, 11 Aug 2016
23:28:50 +

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

Title:
  ImageIO crashes (core dumped) while reading many image files

Status in OpenJDK:
  Fix Released
Status in lcms2 package in Ubuntu:
  Incomplete
Status in openjdk-7 package in Ubuntu:
  Fix Released

Bug description:
  Code that uses ImageIO.read() to read many image files (on my system:
  270 files, totalling 522.9 MiB) crashes the JVM.

  ~~~ My system information:

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

  $ uname -a
  Linux dowah 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 
x86_64 x86_64 x86_64 GNU/Linux

  $ javac -version
  javac 1.7.0_147

  $ java -version
  java version "1.7.0_147-icedtea"

  ~~~ To reproduce the error:

  $ javac BugIIO.java

  $ ulimit -c unlimited # to enable core dump

  $ java BugIIO

  ~~~ Terminal output that signifies the error:

  #
  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7fb5babe31f8, pid=4978, tid=140418842154752
  #
  # JRE version: 7.0_147-b147
  # Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 
compressed oops)
  # Derivative: IcedTea7 2.0
  # Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.1
  # Problematic frame:
  # C  [liblcms2.so.2+0x121f8]  cmsSaveProfileToIOhandler+0x38
  #
  # Core dump written. Default location: /home/joshua/core or core.4978
  #
  # An error report file with more information is saved as:
  # /home/joshua/hs_err_pid4978.log
  #
  # If you would like to submit a bug report, please include
  # instructions on how to reproduce the bug and visit:
  #   https://bugs.launchpad.net/ubuntu/+source/openjdk-7/
  #
  Dibatalkan (core didump)

  ~~~ PS
  When I tried to compile BugIIO.java on openjdk-6 and run it on openjdk-6, the 
program finishes normally (no crash).

  To clarify:
  1. This bug affect OpenJDK 7 (7~b147-2.0-0ubuntu0.11.10.1) (tested on 
oneiric).
  2. This bug does *not* affect OpenJDK 6 (6b23~pre11-0ubuntu1.11.10) (tested 
on oneiric).

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

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

[Desktop-packages] [Bug 1613895] Re: SCSI error on write(0, 16): [3 73 03] Medium error. Power calibration area error

[jimmy]

** Attachment added: "brasero-session1.log"
   
https://bugs.launchpad.net/ubuntu/+source/dvd+rw-tools/+bug/1613895/+attachment/4722339/+files/brasero-session1.log

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

Title:
  SCSI error on write(0,16): [3 73 03] Medium error. Power calibration
  area error

Status in dvd+rw-tools package in Ubuntu:
  New

Bug description:
  file:///home/jimbo/brasero-session1.log

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dvd+rw-tools/+bug/1613895/+subscriptions

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

[Desktop-packages] [Bug 1613895] [NEW] SCSI error on write(0, 16): [3 73 03] Medium error. Power calibration area error

[jimmy]

Public bug reported:

file:///home/jimbo/brasero-session1.log

** Affects: dvd+rw-tools (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  SCSI error on write(0,16): [3 73 03] Medium error. Power calibration
  area error

Status in dvd+rw-tools package in Ubuntu:
  New

Bug description:
  file:///home/jimbo/brasero-session1.log

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dvd+rw-tools/+bug/1613895/+subscriptions

-- 
Mailing list: https://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 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

[Luke Yelavich]

>From the log I saw from the original reporter, there was no crash, it
was an assertion error, and pulse just shut down.

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

Title:
  pulseaudio crashes when connecting to bluetooth headphones (due to
  ubuntu changes?)

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads
  me to believe it's an intermittent problem with some hardware. This
  did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

  pulseaudio:
Installed: 1:8.0-0ubuntu3
Candidate: 1:8.0-0ubuntu3
Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Device info:

  [bluetooth]# info 44:5E:F3:B4:07:29 
  Device 44:5E:F3:B4:07:29
Name: BlueBuds X
Alias: BlueBuds X
Class: 0x240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: Unknown   (80ff--1000-8000-00805f9b34fb)

  I have also attached a debug dump of Pulseaudio when attempting to
  connect to the headphones.

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

-- 
Mailing list: https://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 1613600] Re: package liba11y-profile-manager-data 0.1.11-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/a11y-profile-manager/profiles/blindness/profile

[Luke Yelavich]

affects ubuntu/a11y-profile-manager
 status inprogress


** Changed in: a11y-profile-manager (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  package liba11y-profile-manager-data 0.1.11-0ubuntu1 failed to
  install/upgrade: trying to overwrite '/usr/share/a11y-profile-
  manager/profiles/blindness/profile.manifest', which is also in package
  unity-accessibility-profiles 0.1.10-0ubuntu3

Status in a11y-profile-manager package in Ubuntu:
  In Progress

Bug description:
  This is 16.10, and apparently an error happened while I was trying to
  fix apt. Don't know really what it was.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: liba11y-profile-manager-data 0.1.11-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 16 00:55:09 2016
  DuplicateSignature:
   package:liba11y-profile-manager-data:0.1.11-0ubuntu1
   Unpacking liba11y-profile-manager-data (0.1.11-0ubuntu1) over 
(0.1.10-0ubuntu3) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-3A0in8/04-liba11y-profile-manager-data_0.1.11-0ubuntu1_all.deb
 (--unpack):
trying to overwrite 
'/usr/share/a11y-profile-manager/profiles/blindness/profile.manifest', which is 
also in package unity-accessibility-profiles 0.1.10-0ubuntu3
  ErrorMessage: trying to overwrite 
'/usr/share/a11y-profile-manager/profiles/blindness/profile.manifest', which is 
also in package unity-accessibility-profiles 0.1.10-0ubuntu3
  InstallationDate: Installed on 2016-08-16 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160815)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.9ubuntu2
   apt  1.3~rc1ubuntu2
  SourcePackage: a11y-profile-manager
  Title: package liba11y-profile-manager-data 0.1.11-0ubuntu1 failed to 
install/upgrade: trying to overwrite 
'/usr/share/a11y-profile-manager/profiles/blindness/profile.manifest', which is 
also in package unity-accessibility-profiles 0.1.10-0ubuntu3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1581229] Re: "Started" column not displayed for processes when column is enabled in settings

[Mathew Hodson]

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

** Tags added: patch

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

Title:
  "Started" column not displayed for processes when column is enabled in
  settings

Status in Gnome System Monitor:
  Fix Released
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-system-monitor package in Ubuntu:
  Fix Committed

Bug description:
  I have recently noticed that in the gnome-system-monitor if I go into
  the settings and tick the box for "Started" in the "Information
  fields" section of that the "Processes" tab that the "Started" column
  is not added and in fact this information is not seemingly displayed
  anywhere except for in the "Properties" window for a process. But it
  would be really useful if it did actually appear as a column so that
  you could easily view the start times for multiple processes at the
  same time and to also sort them in terms of that. I am running Ubuntu
  GNOME 15.10 with GNOME 3.18 but I have also experienced the behaviour
  on Ubuntu GNOME 16.04 with GNOME 3.20, in fact when running it on that
  system through Terminal this was the output (the exact moment I
  checked the "Started" box in the settings to add that column I got the
  first bit of output and then very quickly the other output followed):

  (gnome-system-monitor:2252): GLib-CRITICAL **: Source ID 73 was not found 
when attempting to remove it
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)

[Desktop-packages] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics

[d3b null]

It also works for me. THANK YOU! and good work!

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

Title:
  Mouse cursor lost when unlocking with Intel graphics

Status in elementary OS:
  Fix Released
Status in xf86-video-intel:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-intel package in Debian:
  Fix Released

Bug description:
  [Impact]
  Mouse cursor is no longer visible after VT-switch for systems with Intel 
graphics.

  Switching VTs again may cause the cursor to become visible again.
  - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7)

  This is often observed in systems that lock the session and return to
  the greeter (including at least Xubuntu, Ubuntu Mate, and elementary
  OS).

  [Test Case]
  (Requires a lightdm-based screen locking solution)
  1. Start a new session.
  2. Lock your screen.
  2a. You are redirected to the lightdm greeter.
  3. Login/Unlock your session.
  4. Cursor is no longer visible.

  [Regression Potential]
  remains to be seen

  ===

  [Original Report]
  Cursor is visible at unlock screen either after returning from suspend or 
just locking.

  After unlocking screen cursor is invisible.

  Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor
  returns

  

  no matter if you suspend or sleep, to swap or disk when you return
  from it, the mouse cursor is missing.you can still move the mouse
  and you can see (because it highlights the window) as you move it
  around.   But the cursor is not displayed on the screen.

  i am using a lenovo W540 laptop.   I downloaded the latest beta on
  april 8 2016.

  this is xubuntu using the xfce window manager.

  the cursor does return if i log off and log back in, but that actually 
defeats the purpose of going to sleep.
  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-08 (2 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1613886] [NEW] Xorg freeze

[Horea Aflat]

Public bug reported:

In Ubuntu 16.04 from my account I switched to Guest account and after that 
logout from guest and come back to my account.
In this moment I lost the mouse pointer and I needed to make logout/login to 
recover the mouse pointer.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
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: Tue Aug 16 17:03:43 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 vboxhost, 5.0.26, 4.4.0-31-generic, x86_64: installed
 vboxhost, 5.0.26, 4.4.0-34-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
InstallationDate: Installed on 2016-07-29 (17 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Dell Inc. Inspiron 5537
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=0e31254e-b1f5-448d-81e4-986c38a1ebff ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/19/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0XFXDP
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A04
dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd08/19/2013:svnDellInc.:pnInspiron5537:pvrA04:rvnDellInc.:rn0XFXDP:rvrA00:cvnDellInc.:ct8:cvrA04:
dmi.product.name: Inspiron 5537
dmi.product.version: A04
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Aug 16 16:58:47 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 991 
 vendor LGD
xserver.version: 2:1.18.3-1ubuntu2.2

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


** Tags: amd64 apport-bug compiz-0.9 false-gpu-hang freeze ubuntu xenial

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  In Ubuntu 16.04 from my account I switched to Guest account and after that 
logout from guest and come back to my account.
  In this moment I lost the mouse pointer and I needed to make logout/login to 
recover the mouse pointer.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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: Tue Aug 16 17:03:43 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.26, 4.4.0-31-generic, x86_64: installed
   vboxhost, 5.0.26, 4.4.0-34-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2016-07-29 (17 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 5537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=0e31254e-b1f5-448d-81e4-986c38a1ebff ro quiet splash vt.handoff=7
  SourcePackage: 

[Desktop-packages] [Bug 1613805] Re: [evolution/wip/webkit2] EHTMLEditorView - Restore the selection end mark correctly when processing HTML to plain text

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  [evolution/wip/webkit2] EHTMLEditorView - Restore the selection end
  mark correctly when processing HTML to plain text

Status in evolution package in Ubuntu:
  New

Bug description:
  From https://mail.gnome.org/archives/commits-
  list/2016-May/msg06756.html:

  "EHTMLEditorView - Restore the selection end mark correctly when
  processing HTML to plain text

  Otherwise the ##SELECTON_END## string could be left in the output."

  I sometimes see this from people on xenial. Patch is in the commit
  list needs a light backport. I will attach a debdiff if it works.

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

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

[Desktop-packages] [Bug 553912] Re: Cannot create offset parallel tiled clones of vertical or horizontal lines

[Beluga]

Repro.

Arch Linux 64-bit, KDE Plasma 5
Inkscape 0.92pre1 15054 (GTK3)

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

Title:
  Cannot create offset parallel tiled clones of vertical or horizontal
  lines

Status in Inkscape:
  Triaged
Status in inkscape package in Ubuntu:
  Triaged
Status in inkscape package in Debian:
  Confirmed

Bug description:
  Binary package hint: inkscape

  The tiled clones tool does not create any offset between parallel
  clones of vertical or horizontal lines, no matter what is specified on
  the "Shift" tab of the tiled clones dialog

  To reproduce:

  1.  Draw a vertical line (hold CTRL while drawing to ensure it is perfectly 
vertical)
  2.  Edit->Clone->Create Tiled Clones...
  3.  On the "Symmetry" tab, select P1: Simple translation
  4.  Enter Rows, Columns = 1, 5
  5.  Click "Create"
  >> five clones of the line are created, all stacked on top of each other.
  6.  Undo
  7.  On the "Shift" tab, select 200% per column for Shift X.
  8.  Click "Create"
  >> five clones of the line are created, all stacked on top of each other.

  In other words, the width of the stroke is ignored when calculating
  the offset between clones.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: inkscape 0.47.0-1ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-19-generic x86_64
  Architecture: amd64
  Date: Fri Apr  2 13:12:48 2010
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
  ProcEnviron:
   LANG=en_GB.utf8
   SHELL=/bin/bash
  SourcePackage: inkscape

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

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

[Desktop-packages] [Bug 1607774] Re: i915 kernel module stops working occasionally

[dbacc]

Seems to only affect Displayport (needed for high resolution). After
screen gets black, can switch monitor setting to HDMI. Then screen is
showing something again (in FHD resolution). xrandr shows DP as
disconnected.

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

Title:
  i915 kernel module stops working occasionally

Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  Occasionally my screen gets black. The machine is still alive, can
  login via ssh.

  
  journalctl -k -b-2 | grep drm
  Jul 26 10:22:34  kernel: [drm] Initialized drm 1.1.0 20060810
  Jul 26 10:22:34  kernel: [drm] Memory usable by graphics device = 2048M
  Jul 26 10:22:34  kernel: fb: switching to inteldrmfb from VESA VGA
  Jul 26 10:22:34  kernel: [drm] Replacing VGA console driver
  Jul 26 10:22:34  kernel: [drm] Supports vblank timestamp caching Rev 2 
(21.10.2013).
  Jul 26 10:22:34  kernel: [drm] Driver supports precise vblank timestamp query.
  Jul 26 10:22:34  kernel: [drm:intel_opregion_init [i915]] *ERROR* No ACPI 
video bus found
  Jul 26 10:22:34  kernel: [drm] Initialized i915 1.6.0 20151010 for 
:00:02.0 on minor 0
  Jul 26 10:22:34  kernel: [drm] GMBUS [i915 gmbus vga] timed out, falling back 
to bit banging on pin 2
  Jul 26 10:22:34  kernel: fbcon: inteldrmfb (fb0) is primary device
  Jul 26 10:22:34  kernel: i915 :00:02.0: fb0: inteldrmfb frame buffer 
device
  Jul 27 16:25:30  kernel: [drm] stuck on render ring
  Jul 27 16:25:30  kernel: [drm] GPU HANG: ecode 6:0:0x85eefffc, in 
chromium-browse [18427], reason: Ring hung, action: reset
  Jul 27 16:25:30  kernel: [drm] GPU hangs can indicate a bug anywhere in the 
entire gfx stack, including userspace.
  Jul 27 16:25:30  kernel: [drm] Please file a _new_ bug report on 
bugs.freedesktop.org against DRI -> DRM/Intel
  Jul 27 16:25:30  kernel: [drm] drm/i915 developers can then reassign to the 
right component if it's not a kernel issue.
  Jul 27 16:25:30  kernel: [drm] The gpu crash dump is required to analyze gpu 
hangs, so please always attach it.
  Jul 27 16:25:30  kernel: [drm] GPU crash dump saved to 
/sys/class/drm/card0/error
  Jul 27 16:25:30  kernel: drm/i915: Resetting chip after gpu hang
  Jul 27 16:36:14  kernel: [drm] stuck on render ring
  Jul 27 16:36:14  kernel: [drm] GPU HANG: ecode 6:0:0x85eefffc, in 
chromium-browse [26940], reason: Ring hung, action: reset
  Jul 27 16:36:14  kernel: drm/i915: Resetting chip after gpu hang
  Jul 27 17:28:30  kernel: [drm] stuck on render ring
  Jul 27 17:28:30  kernel: [drm] GPU HANG: ecode 6:0:0x85eefffc, in 
chromium-browse [27028], reason: Ring hung, action: reset
  Jul 27 17:28:30  kernel: drm/i915: Resetting chip after gpu hang
  Jul 27 18:55:17  kernel: [drm] stuck on render ring
  Jul 27 18:55:17  kernel: [drm] GPU HANG: ecode 6:0:0x85eecffc, in plasmashell 
[27304], reason: Ring hung, action: reset
  Jul 27 18:55:17  kernel: drm/i915: Resetting chip after gpu hang
  Jul 27 18:55:23  kernel: [drm] stuck on render ring
  Jul 27 18:55:23  kernel: [drm] GPU HANG: ecode 6:0:0x85eeeffc, in plasmashell 
[27304], reason: Ring hung, action: reset
  Jul 27 18:55:23  kernel: drm/i915: Resetting chip after gpu hang
  Jul 27 18:55:29  kernel: [drm] stuck on render ring
  Jul 27 18:55:29  kernel: [drm] GPU HANG: ecode 6:0:0x85eefffc, in 
chromium-browse [27590], reason: Ring hung, action: reset
  Jul 27 18:55:29  kernel: drm/i915: Resetting chip after gpu hang
  Jul 28 15:24:23  kernel: [drm] stuck on render ring
  Jul 28 15:24:23  kernel: [drm] GPU HANG: ecode 6:0:0xbc17, in 
chromium-browse [29032], reason: Ring hung, action: reset
  Jul 28 15:24:23  kernel: drm/i915: Resetting chip after gpu hang
  Jul 28 18:04:52  kernel: [drm:intel_dp_link_training_clock_recovery [i915]] 
*ERROR* failed to enable link training
  Jul 28 18:04:52  kernel: [drm:intel_dp_link_training_channel_equalization 
[i915]] *ERROR* failed to start channel equalization


  The error Jul 26 10:22:34  kernel: [drm:intel_opregion_init [i915]]
  *ERROR* No ACPI video bus found happens at every boot

  The last two errors coincide with the times the screen gets blank.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Fri Jul 29 08:45:47 2016
  DistUpgraded: 2016-04-26 11:22:19,544 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: kubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core 

[Desktop-packages] [Bug 1613863] [NEW] Fails to power off monitor when locking screen

[Anders Magnus Andersen]

Public bug reported:

Screen left black with only the cursor showing.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-video-nouveau 1:1.0.12-1build2
Uname: Linux 4.5.7-040507-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
BootLog:
 
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: Tue Aug 16 21:37:46 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: nvidia-361, 361.42, 4.5.7-040507-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GK107 [GeForce GTX 650] 
[1462:2809]
InstallationDate: Installed on 2016-08-14 (2 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: LENOVO 10120
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.5.7-040507-generic 
root=UUID=79953082-1ec8-42c2-b754-bcb468e0c457 ro rootflags=subvol=@
SourcePackage: xserver-xorg-video-nouveau
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/24/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: I1KT24AUS
dmi.board.vendor: LENOVO
dmi.board.version: 3193 STD
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.modalias: 
dmi:bvnLENOVO:bvrI1KT24AUS:bd07/24/2013:svnLENOVO:pn10120:pvrIdeaCentreK450:rvnLENOVO:rn:rvr3193STD:cvnLENOVO:ct3:cvr:
dmi.product.name: 10120
dmi.product.version: IdeaCentre K450
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Aug 16 19:35:02 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.3-1ubuntu2.3

** Affects: xserver-xorg-video-nouveau (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  Fails to power off monitor when locking screen

Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  Screen left black with only the cursor showing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-nouveau 1:1.0.12-1build2
  Uname: Linux 4.5.7-040507-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No 

[Desktop-packages] [Bug 1589073] Re: nm-applet not showing existing wifi connection

[Peter S]

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

** This bug is no longer a duplicate of bug 1576747
   Network manager applet unable to control wifi after suspend in 16.04
** This bug has been marked a duplicate of bug 1589401
   cannot view wifi networks after re-enabling wifi

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

Title:
  nm-applet not showing existing wifi connection

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

Bug description:
  Frequently, not always, the wifi connection and the existing wifi
  networks don't show up on nm-applet. Still, the default network
  connection is established in the background. But nm-applet does not
  allow connection management.

  In the picture: nm-applet shows no connections/netowrks but in the
  connection information dialog you can confirm that the wifi connection
  was established

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  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
  CurrentDesktop: Unity
  Date: Sat Jun  4 11:33:41 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-16 (18 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.254 dev wlp13s0  proto static  metric 600
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown
   192.168.1.0/24 dev wlp13s0  proto kernel  scope link  src 192.168.1.113  
metric 600
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/ubuntu/+source/network-manager-applet/+bug/1589073/+subscriptions

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

[Desktop-packages] [Bug 1612928] Re: ARM symbols not available on crash-stats.mozilla.com when Firefox crashes

[Henri Sivonen]

Wouldn't it make more sense to upload the symbols to let people who care
diagnose bugs but not include ARM crashes in Mozilla's crash statistics?

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

Title:
  ARM symbols not available on crash-stats.mozilla.com when Firefox
  crashes

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

Bug description:
  When Firefox crashes on Ubuntu on ARMv7, it offers to report the crash
  to Mozilla, which is good, but Mozilla's crash reporting system
  appears to be unable to extract symbols for a stack trace.

  See e.g. https://crash-stats.mozilla.com/report/index/c6aa6dc1-90f3
  -44ec-8f7f-337f72160813

  I'm guessing that whatever process is used to upload symbols for
  Ubuntu's x86/x86_64 builds to Mozilla's server is not being followed
  for ARMv7. Please make the ARM symbols available to Mozilla for more
  useful crash reporting.

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

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

[Desktop-packages] [Bug 1612928] Re: ARM symbols not available on crash-stats.mozilla.com when Firefox crashes

[Henri Sivonen]

As a user who might be able to fix the crash, having a crash stack show
up without building a debug build myself is more important than on
x86_64, because my Raspberry Pi 3 doesn't have enough RAM to link
libxul, so just making a debug build on my own and running it under gdb
when it crashes doesn't work.

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

Title:
  ARM symbols not available on crash-stats.mozilla.com when Firefox
  crashes

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

Bug description:
  When Firefox crashes on Ubuntu on ARMv7, it offers to report the crash
  to Mozilla, which is good, but Mozilla's crash reporting system
  appears to be unable to extract symbols for a stack trace.

  See e.g. https://crash-stats.mozilla.com/report/index/c6aa6dc1-90f3
  -44ec-8f7f-337f72160813

  I'm guessing that whatever process is used to upload symbols for
  Ubuntu's x86/x86_64 builds to Mozilla's server is not being followed
  for ARMv7. Please make the ARM symbols available to Mozilla for more
  useful crash reporting.

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

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

[Desktop-packages] [Bug 1613763] Re: package liba11y-profile-manager-data 0.1.10-0ubuntu3 failed to install/upgrade: trying to overwrite '/usr/share/a11y-profile-manager/profiles/blindness/profile.man

[Launchpad Bug Tracker]

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

** Changed in: a11y-profile-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  package liba11y-profile-manager-data 0.1.10-0ubuntu3 failed to
  install/upgrade: trying to overwrite '/usr/share/a11y-profile-
  manager/profiles/blindness/profile.manifest', which is also in package
  unity-accessibility-profiles 0.1.10-0ubuntu3

Status in a11y-profile-manager package in Ubuntu:
  Confirmed

Bug description:
  software updater crashed while updating   --please fix

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: liba11y-profile-manager-data 0.1.10-0ubuntu3
  ProcVersionSignature: Ubuntu 4.6.0-10.12-generic 4.6.5
  Uname: Linux 4.6.0-10-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 16 09:53:35 2016
  DuplicateSignature:
   package:liba11y-profile-manager-data:0.1.10-0ubuntu3
   Unpacking liba11y-profile-manager-data (0.1.11-0ubuntu1) over 
(0.1.10-0ubuntu3) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-QPwYOH/12-liba11y-profile-manager-data_0.1.11-0ubuntu1_all.deb
 (--unpack):
trying to overwrite 
'/usr/share/a11y-profile-manager/profiles/blindness/profile.manifest', which is 
also in package unity-accessibility-profiles 0.1.10-0ubuntu3
  ErrorMessage: trying to overwrite 
'/usr/share/a11y-profile-manager/profiles/blindness/profile.manifest', which is 
also in package unity-accessibility-profiles 0.1.10-0ubuntu3
  InstallationDate: Installed on 2016-06-11 (65 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160515)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc1ubuntu2
  SourcePackage: a11y-profile-manager
  Title: package liba11y-profile-manager-data 0.1.10-0ubuntu3 failed to 
install/upgrade: trying to overwrite 
'/usr/share/a11y-profile-manager/profiles/blindness/profile.manifest', which is 
also in package unity-accessibility-profiles 0.1.10-0ubuntu3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1604421] Re: Unity 8 fails to start on staging (xenial) on the phone when --wipe is used for flashing

[Andrea Azzarone]

** No longer affects: unity (Ubuntu)

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

Title:
  Unity 8 fails to start on staging (xenial) on the phone when --wipe is
  used for flashing

Status in Canonical System Image:
  Confirmed
Status in gsettings-ubuntu-touch-schemas package in Ubuntu:
  New
Status in ubuntu-touch-session package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Update: this only happens when --wipe (or --bootstrap) is used for
  flashing. It is possible to get functional xenial/staging running by
  doing non-destructive flash update from rc-proposed.

  Unity 8 fails to start on staging (=xenial + xenial-overlay) on my
  krillin.

  unity-system-compositor.log: http://paste.ubuntu.com/20035267/ - shows
  Opening/Closing/Opening/Closing when starting unity8.

  unity8.log attached.

  Using ubuntu-touch/staging/bq-aquaris.en channel on krillin.
  version_detail:
  ubuntu=20160719,device=20160606-ab415b2,custom=20160701-981-38-14,version=49

  Crash file at http://people.ubuntu.com/~timo-
  jyrinki/unity8/_usr_bin_unity8.32011.crash

  Xenial can be flashed on the phone with eg:
  ubuntu-device-flash touch --channel=ubuntu-touch/staging/ubuntu 
--developer-mode --password= --wipe --boostrap
  (ubuntu channel)
  ubuntu-device-flash touch --channel=ubuntu-touch/staging/bq-aquaris.en 
--developer-mode --password= --wipe --recovery-image recovery-krillin.img
  (Bq channel)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604421/+subscriptions

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

[Desktop-packages] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics

[David Pearson]

tested on a toshiba satellite pro... works a treat...

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

Title:
  Mouse cursor lost when unlocking with Intel graphics

Status in elementary OS:
  Fix Released
Status in xf86-video-intel:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-intel package in Debian:
  Fix Released

Bug description:
  [Impact]
  Mouse cursor is no longer visible after VT-switch for systems with Intel 
graphics.

  Switching VTs again may cause the cursor to become visible again.
  - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7)

  This is often observed in systems that lock the session and return to
  the greeter (including at least Xubuntu, Ubuntu Mate, and elementary
  OS).

  [Test Case]
  (Requires a lightdm-based screen locking solution)
  1. Start a new session.
  2. Lock your screen.
  2a. You are redirected to the lightdm greeter.
  3. Login/Unlock your session.
  4. Cursor is no longer visible.

  [Regression Potential]
  remains to be seen

  ===

  [Original Report]
  Cursor is visible at unlock screen either after returning from suspend or 
just locking.

  After unlocking screen cursor is invisible.

  Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor
  returns

  

  no matter if you suspend or sleep, to swap or disk when you return
  from it, the mouse cursor is missing.you can still move the mouse
  and you can see (because it highlights the window) as you move it
  around.   But the cursor is not displayed on the screen.

  i am using a lenovo W540 laptop.   I downloaded the latest beta on
  april 8 2016.

  this is xubuntu using the xfce window manager.

  the cursor does return if i log off and log back in, but that actually 
defeats the purpose of going to sleep.
  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-08 (2 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1571454] Re: Wifi + cable only works after network-manager restart

[Peter S]

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

** This bug is no longer a duplicate of bug 1576747
   Network manager applet unable to control wifi after suspend in 16.04
** This bug has been marked a duplicate of bug 1589401
   cannot view wifi networks after re-enabling wifi

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

Title:
  Wifi + cable only works after network-manager restart

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Wifi and cable only get activated after i sudo service network-manager
  restart, before wifi and cable are greyed out

  Ubuntu 16.04 daily with all recent updates on 18/4/2016

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 18 04:35:49 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-04 (13 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  IpRoute:
   default via 192.168.1.1 dev wlp7s0  proto static  metric 600 
   169.254.0.0/16 dev wlp7s0  scope link  metric 1000 
   192.168.1.0/24 dev wlp7s0  proto kernel  scope link  src 192.168.1.2  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   belkin7 67e4a5b3-4e8e-4428-bc43-c25952f33558  802-11-wireless  
1460946871  ma 18 apr 2016 04:34:31 CEST  yes  0 no 
   /org/freedesktop/NetworkManager/Settings/0  yes wlp7s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   Wired connection 1  bab26653-acb8-45fe-8b43-c5fe98488989  802-3-ethernet   
1460946867  ma 18 apr 2016 04:34:27 CEST  yes  4294966297no 
   /org/freedesktop/NetworkManager/Settings/1  no  --  -- --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp7s0  wifi  connected/org/freedesktop/NetworkManager/Devices/0  
belkin7 67e4a5b3-4e8e-4428-bc43-c25952f33558  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp6s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
 ----
  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/ubuntu/+source/network-manager/+bug/1571454/+subscriptions

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

[Desktop-packages] [Bug 1576747] Re: Network manager applet unable to control wifi after suspend in 16.04

[Peter S]

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

** This bug has been marked a duplicate of bug 1589401
   cannot view wifi networks after re-enabling wifi

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

Title:
  Network manager applet unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1690] device 

[Desktop-packages] [Bug 1613720] Re: Display arrangement settings are reset after reboot

[Andrea Azzarone]

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

** No longer affects: unity (Ubuntu)

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

Title:
  Display arrangement settings are reset after reboot

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

Bug description:
  Display arrangement settings are reset after reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160715-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: openafs zfs zunicode zcommon znvpair zavl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: »/apps/compiz-1/general/screen0/options/active_plugins« wurde 
kein Wert zugewiesen
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Aug 16 15:28:45 2016
  DistUpgraded: 2016-03-14 15:43:39,246 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3904]
  InstallationDate: Installed on 2015-12-12 (248 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20221
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic 
root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro 
rootflags=subvol=ubuntu-main-root
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-03-14 (154 days ago)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Aug 16 15:22:31 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5557 
   vendor CMN
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Desktop-packages] [Bug 1604421] Re: Unity 8 fails to start on staging (xenial) on the phone when --wipe is used for flashing

[Łukasz Zemczak]

It seems as if XDG_DATA_DIRS gets cleared out at some time (you can see
the "::" where the previous XDG_DATA_DIRS content should have been),
wonder what component could have caused this. There was no change in
ubuntu-touch-session that actually sets the .profile file.

As Pat pointed out on IRC a valid lead would be to check what's being
run in /etc/profile.d/ on the broken machine. The only script that
touches XDG_DATA_DIRS is my old hack for enabling customized
notification sounds, /etc/profile.d/add_custom_to_xdg_data.sh. Maybe it
would be a good experiment to try and remove it in the broken system.
Doesn't look like much could have gotten broken there. Could anyone list
the contents of the /etc/profile.d directory on the xenial non-booting
device?

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

Title:
  Unity 8 fails to start on staging (xenial) on the phone when --wipe is
  used for flashing

Status in Canonical System Image:
  Confirmed
Status in gsettings-ubuntu-touch-schemas package in Ubuntu:
  New
Status in ubuntu-touch-session package in Ubuntu:
  New
Status in unity package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Update: this only happens when --wipe (or --bootstrap) is used for
  flashing. It is possible to get functional xenial/staging running by
  doing non-destructive flash update from rc-proposed.

  Unity 8 fails to start on staging (=xenial + xenial-overlay) on my
  krillin.

  unity-system-compositor.log: http://paste.ubuntu.com/20035267/ - shows
  Opening/Closing/Opening/Closing when starting unity8.

  unity8.log attached.

  Using ubuntu-touch/staging/bq-aquaris.en channel on krillin.
  version_detail:
  ubuntu=20160719,device=20160606-ab415b2,custom=20160701-981-38-14,version=49

  Crash file at http://people.ubuntu.com/~timo-
  jyrinki/unity8/_usr_bin_unity8.32011.crash

  Xenial can be flashed on the phone with eg:
  ubuntu-device-flash touch --channel=ubuntu-touch/staging/ubuntu 
--developer-mode --password= --wipe --boostrap
  (ubuntu channel)
  ubuntu-device-flash touch --channel=ubuntu-touch/staging/bq-aquaris.en 
--developer-mode --password= --wipe --recovery-image recovery-krillin.img
  (Bq channel)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604421/+subscriptions

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

[Desktop-packages] [Bug 1613854] [NEW] Same as #1613852, but with Totem

[Shahar Or]

Public bug reported:

This is probably the same issue as bug #1613852, only that it happens in
Totem.

Totem, seems to work better, though. It fails to play at all. Which is
better than playing the video and playing very loud noise with it.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libgstreamer1.0-0 1.8.2-1~ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Tue Aug 16 21:49:51 2016
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2010-10-12 (2135 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
SourcePackage: gstreamer1.0
UpgradeStatus: Upgraded to xenial on 2015-11-13 (277 days ago)

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  Same as #1613852, but with Totem

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  This is probably the same issue as bug #1613852, only that it happens
  in Totem.

  Totem, seems to work better, though. It fails to play at all. Which is
  better than playing the video and playing very loud noise with it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgstreamer1.0-0 1.8.2-1~ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Aug 16 21:49:51 2016
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2010-10-12 (2135 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: gstreamer1.0
  UpgradeStatus: Upgraded to xenial on 2015-11-13 (277 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1613854/+subscriptions

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

[Desktop-packages] [Bug 170049] Re: Inverted ruler co-ordinate system

[Adrian Carter]

You know.. I appreciate theres probably tons of other issues that have
been knocked over... but in what, 12 years? , you'd hope they could have
closed this out by now.

Is there any progress other than the declined patch to date ?

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

Title:
  Inverted ruler co-ordinate system

Status in Inkscape:
  Triaged
Status in inkscape package in Ubuntu:
  Triaged

Bug description:
  The y-axis of the rulers' co-ordinate system is
  inverted (increasing upwards), and places the origin on
  the bottom left of the viewport. The SVG spec places the
  default origin on the top left of the viewport, and has
  the co-ordinate system increasing to the right and
  downwards.

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

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

[Desktop-packages] [Bug 1571454] Re: Wifi + cable only works after network-manager restart

[Peter S]

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

** This bug has been marked a duplicate of bug 1576747
   Network manager applet unable to control wifi after suspend in 16.04

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

Title:
  Wifi + cable only works after network-manager restart

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Wifi and cable only get activated after i sudo service network-manager
  restart, before wifi and cable are greyed out

  Ubuntu 16.04 daily with all recent updates on 18/4/2016

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 18 04:35:49 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-04 (13 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  IpRoute:
   default via 192.168.1.1 dev wlp7s0  proto static  metric 600 
   169.254.0.0/16 dev wlp7s0  scope link  metric 1000 
   192.168.1.0/24 dev wlp7s0  proto kernel  scope link  src 192.168.1.2  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   belkin7 67e4a5b3-4e8e-4428-bc43-c25952f33558  802-11-wireless  
1460946871  ma 18 apr 2016 04:34:31 CEST  yes  0 no 
   /org/freedesktop/NetworkManager/Settings/0  yes wlp7s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   Wired connection 1  bab26653-acb8-45fe-8b43-c5fe98488989  802-3-ethernet   
1460946867  ma 18 apr 2016 04:34:27 CEST  yes  4294966297no 
   /org/freedesktop/NetworkManager/Settings/1  no  --  -- --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp7s0  wifi  connected/org/freedesktop/NetworkManager/Devices/0  
belkin7 67e4a5b3-4e8e-4428-bc43-c25952f33558  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp6s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
 ----
  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/ubuntu/+source/network-manager/+bug/1571454/+subscriptions

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

[Desktop-packages] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics

[olbiv]

Tested xserver-xorg-video-intel package.

Works on Lenovo X250.
Thanks.

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

Title:
  Mouse cursor lost when unlocking with Intel graphics

Status in elementary OS:
  Fix Released
Status in xf86-video-intel:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-intel package in Debian:
  Fix Released

Bug description:
  [Impact]
  Mouse cursor is no longer visible after VT-switch for systems with Intel 
graphics.

  Switching VTs again may cause the cursor to become visible again.
  - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7)

  This is often observed in systems that lock the session and return to
  the greeter (including at least Xubuntu, Ubuntu Mate, and elementary
  OS).

  [Test Case]
  (Requires a lightdm-based screen locking solution)
  1. Start a new session.
  2. Lock your screen.
  2a. You are redirected to the lightdm greeter.
  3. Login/Unlock your session.
  4. Cursor is no longer visible.

  [Regression Potential]
  remains to be seen

  ===

  [Original Report]
  Cursor is visible at unlock screen either after returning from suspend or 
just locking.

  After unlocking screen cursor is invisible.

  Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor
  returns

  

  no matter if you suspend or sleep, to swap or disk when you return
  from it, the mouse cursor is missing.you can still move the mouse
  and you can see (because it highlights the window) as you move it
  around.   But the cursor is not displayed on the screen.

  i am using a lenovo W540 laptop.   I downloaded the latest beta on
  april 8 2016.

  this is xubuntu using the xfce window manager.

  the cursor does return if i log off and log back in, but that actually 
defeats the purpose of going to sleep.
  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-08 (2 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1613805] Re: [evolution/wip/webkit2] EHTMLEditorView - Restore the selection end mark correctly when processing HTML to plain text

[Jamie Strandboge]

** Patch added: "evolution_3.18.5.2-0ubuntu3.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1613805/+attachment/4722194/+files/evolution_3.18.5.2-0ubuntu3.2.debdiff

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

Title:
  [evolution/wip/webkit2] EHTMLEditorView - Restore the selection end
  mark correctly when processing HTML to plain text

Status in evolution package in Ubuntu:
  New

Bug description:
  From https://mail.gnome.org/archives/commits-
  list/2016-May/msg06756.html:

  "EHTMLEditorView - Restore the selection end mark correctly when
  processing HTML to plain text

  Otherwise the ##SELECTON_END## string could be left in the output."

  I sometimes see this from people on xenial. Patch is in the commit
  list needs a light backport. I will attach a debdiff if it works.

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

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

[Desktop-packages] [Bug 1613805] Re: [evolution/wip/webkit2] EHTMLEditorView - Restore the selection end mark correctly when processing HTML to plain text

[Jamie Strandboge]

Here is a debdiff that fixes an obviously wrong piece of code that is
simple for an SRU. I don't yet have a reproducer.

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

Title:
  [evolution/wip/webkit2] EHTMLEditorView - Restore the selection end
  mark correctly when processing HTML to plain text

Status in evolution package in Ubuntu:
  New

Bug description:
  From https://mail.gnome.org/archives/commits-
  list/2016-May/msg06756.html:

  "EHTMLEditorView - Restore the selection end mark correctly when
  processing HTML to plain text

  Otherwise the ##SELECTON_END## string could be left in the output."

  I sometimes see this from people on xenial. Patch is in the commit
  list needs a light backport. I will attach a debdiff if it works.

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

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

[Desktop-packages] [Bug 1581229] Re: "Started" column not displayed for processes when column is enabled in settings

[Nikita Yerenkov-Scott]

I hope that I have done it correctly and as you wanted. Please let me
know if there is anything else I need to fix or if I have done this in
the wrong way. I will be unavailable for a few hours starting from now
but should be able to have a look later tonight (if not, then tomorrow).

** Patch added: "FixDefaultColumnWidth3-20.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1581229/+attachment/4722193/+files/FixDefaultColumnWidth3-20.debdiff

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

Title:
  "Started" column not displayed for processes when column is enabled in
  settings

Status in Gnome System Monitor:
  Fix Released
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-system-monitor package in Ubuntu:
  Fix Committed

Bug description:
  I have recently noticed that in the gnome-system-monitor if I go into
  the settings and tick the box for "Started" in the "Information
  fields" section of that the "Processes" tab that the "Started" column
  is not added and in fact this information is not seemingly displayed
  anywhere except for in the "Properties" window for a process. But it
  would be really useful if it did actually appear as a column so that
  you could easily view the start times for multiple processes at the
  same time and to also sort them in terms of that. I am running Ubuntu
  GNOME 15.10 with GNOME 3.18 but I have also experienced the behaviour
  on Ubuntu GNOME 16.04 with GNOME 3.20, in fact when running it on that
  system through Terminal this was the output (the exact moment I
  checked the "Started" box in the settings to add that column I got the
  first bit of output and then very quickly the other output followed):

  (gnome-system-monitor:2252): GLib-CRITICAL **: Source ID 73 was not found 
when attempting to remove it
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, 

[Desktop-packages] [Bug 1581229] Re: "Started" column not displayed for processes when column is enabled in settings

[Nikita Yerenkov-Scott]

Do you need me to just change "unstable" to "yakkety" in the debdiff and
reupload? Or do you need me to rerun the entire process of making the
debdiff after I've made the appropriate changes in the changelog?

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

Title:
  "Started" column not displayed for processes when column is enabled in
  settings

Status in Gnome System Monitor:
  Fix Released
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-system-monitor package in Ubuntu:
  Fix Committed

Bug description:
  I have recently noticed that in the gnome-system-monitor if I go into
  the settings and tick the box for "Started" in the "Information
  fields" section of that the "Processes" tab that the "Started" column
  is not added and in fact this information is not seemingly displayed
  anywhere except for in the "Properties" window for a process. But it
  would be really useful if it did actually appear as a column so that
  you could easily view the start times for multiple processes at the
  same time and to also sort them in terms of that. I am running Ubuntu
  GNOME 15.10 with GNOME 3.18 but I have also experienced the behaviour
  on Ubuntu GNOME 16.04 with GNOME 3.20, in fact when running it on that
  system through Terminal this was the output (the exact moment I
  checked the "Started" box in the settings to add that column I got the
  first bit of output and then very quickly the other output followed):

  (gnome-system-monitor:2252): GLib-CRITICAL **: Source ID 73 was not found 
when attempting to remove it
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 

[Desktop-packages] [Bug 1493673] Re: no info dir entry in `/usr/share/info/gtkdialog.info.gz'

[Launchpad Bug Tracker]

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

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

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

Title:
   no info dir entry in `/usr/share/info/gtkdialog.info.gz'

Status in texinfo package in Ubuntu:
  Confirmed

Bug description:
  Error i get while upgrading:

  Processing triggers for install-info (6.0.0.dfsg.1-3) ...
  install-info: warning: no info dir entry in 
`/usr/share/info/gtkdialog.info.gz'

  so the installed documentation index is not available.
  note: 'gtkdialog' is installed by the 'multisystem' app from 'liveusb.info'

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: install-info 6.0.0.dfsg.1-3
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18-0ubuntu9
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Wed Sep  9 08:07:15 2015
  SourcePackage: texinfo
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1581229] Re: "Started" column not displayed for processes when column is enabled in settings

[Nikita Yerenkov-Scott]

Oh, ok, so I don't actually need to do any more debdiffs? Would it be
preferable if I did or can I just correct the unstable to yakkety and
not need to do any more? If it's needed of me or would be preferable for
you I will do it, but as my system is rather slow and overheating due to
its fan being broken I would prefer not to be doing anything on it that
isn't actually needed of me.

So you just need me to change unstable to yakkety in the changelog,
resign and reupload and that is it or do I need to do anything else?

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

Title:
  "Started" column not displayed for processes when column is enabled in
  settings

Status in Gnome System Monitor:
  Fix Released
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-system-monitor package in Ubuntu:
  Fix Committed

Bug description:
  I have recently noticed that in the gnome-system-monitor if I go into
  the settings and tick the box for "Started" in the "Information
  fields" section of that the "Processes" tab that the "Started" column
  is not added and in fact this information is not seemingly displayed
  anywhere except for in the "Properties" window for a process. But it
  would be really useful if it did actually appear as a column so that
  you could easily view the start times for multiple processes at the
  same time and to also sort them in terms of that. I am running Ubuntu
  GNOME 15.10 with GNOME 3.18 but I have also experienced the behaviour
  on Ubuntu GNOME 16.04 with GNOME 3.20, in fact when running it on that
  system through Terminal this was the output (the exact moment I
  checked the "Started" box in the settings to add that column I got the
  first bit of output and then very quickly the other output followed):

  (gnome-system-monitor:2252): GLib-CRITICAL **: Source ID 73 was not found 
when attempting to remove it
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 

[Desktop-packages] [Bug 1613430] Re: lightdm not showing gnome desktop option

[Gunnar Hjalmarsson]

Ok, then we know that the issue is not a result of your $HOME having
been messed up due to multiple desktops. (A guest session is started
with a fresh $HOME.)

Thanks for your helpful responsiveness! Now let's wait for someone else
to attend to this bug report.

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

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

Title:
  lightdm not showing gnome desktop option

Status in lightdm package in Ubuntu:
  New

Bug description:
  I installed ubuntu-gnome-desktop and selected lightdm as the display
  manager (tried gdm and received only a purple screen).  When I click
  on the ubuntu logo to the right of my login (where I believe I should
  be able to select the desktop I would like to use) the login name(s)
  disappear and nothing happens until I hit enter at which point the
  login names reappear

  I have tried logging out and back in again as well as rebooting with the same 
results.  I am currently on a Dell XPS 13 Developer Edition (Ubuntu laptop).  I 
am able to log into Unity with no problem but I would like to use Gnome.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-07-26 (19 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  Package: lightdm 1.18.2-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Tags: xenial third-party-packages
  Uname: Linux 4.4.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1581229] Re: "Started" column not displayed for processes when column is enabled in settings

[Sebastien Bacher]

the debdiff can easily be adapted but if you want to do the xenial SRU
that would be welcome, the team working on the GNOME3 ppa should be able
to use the yakkety debdiff or adapt don't worry, also you probably don't
need to bother much using VMs and build/testing on each serie, just get
the source for xenial, do the change and generate a debdiff using
whatever version of ubuntu you are on, for those sort of changes it
should be safe enough and the sponsor can test before uploading

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

Title:
  "Started" column not displayed for processes when column is enabled in
  settings

Status in Gnome System Monitor:
  Fix Released
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-system-monitor package in Ubuntu:
  Fix Committed

Bug description:
  I have recently noticed that in the gnome-system-monitor if I go into
  the settings and tick the box for "Started" in the "Information
  fields" section of that the "Processes" tab that the "Started" column
  is not added and in fact this information is not seemingly displayed
  anywhere except for in the "Properties" window for a process. But it
  would be really useful if it did actually appear as a column so that
  you could easily view the start times for multiple processes at the
  same time and to also sort them in terms of that. I am running Ubuntu
  GNOME 15.10 with GNOME 3.18 but I have also experienced the behaviour
  on Ubuntu GNOME 16.04 with GNOME 3.20, in fact when running it on that
  system through Terminal this was the output (the exact moment I
  checked the "Started" box in the settings to add that column I got the
  first bit of output and then very quickly the other output followed):

  (gnome-system-monitor:2252): GLib-CRITICAL **: Source ID 73 was not found 
when attempting to remove it
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node 

[Desktop-packages] [Bug 1604421] Re: Unity 8 fails to start on staging (xenial) on the phone when --wipe is used for flashing

[Michał Sawicz]

The problem seems to be:

$ initctl get-env -g XDG_DATA_DIRS
/usr/share/ubuntu-touch:/usr/share/ubuntu-touch:/usr/share/ubuntu-touch:/usr/share/ubuntu-touch::/custom/usr/share/:/custom/usr/share/

Compared to a working, upgraded device:
$ initctl get-env -g XDG_DATA_DIRS
/custom/xdg/data:/usr/share/ubuntu-touch:/usr/share/ubuntu-touch:/usr/share/ubuntu-touch:/usr/local/share:/usr/share:/custom/usr/share/

** Also affects: ubuntu-touch-session (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  Unity 8 fails to start on staging (xenial) on the phone when --wipe is
  used for flashing

Status in Canonical System Image:
  Confirmed
Status in gsettings-ubuntu-touch-schemas package in Ubuntu:
  New
Status in ubuntu-touch-session package in Ubuntu:
  New
Status in unity package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Update: this only happens when --wipe (or --bootstrap) is used for
  flashing. It is possible to get functional xenial/staging running by
  doing non-destructive flash update from rc-proposed.

  Unity 8 fails to start on staging (=xenial + xenial-overlay) on my
  krillin.

  unity-system-compositor.log: http://paste.ubuntu.com/20035267/ - shows
  Opening/Closing/Opening/Closing when starting unity8.

  unity8.log attached.

  Using ubuntu-touch/staging/bq-aquaris.en channel on krillin.
  version_detail:
  ubuntu=20160719,device=20160606-ab415b2,custom=20160701-981-38-14,version=49

  Crash file at http://people.ubuntu.com/~timo-
  jyrinki/unity8/_usr_bin_unity8.32011.crash

  Xenial can be flashed on the phone with eg:
  ubuntu-device-flash touch --channel=ubuntu-touch/staging/ubuntu 
--developer-mode --password= --wipe --boostrap
  (ubuntu channel)
  ubuntu-device-flash touch --channel=ubuntu-touch/staging/bq-aquaris.en 
--developer-mode --password= --wipe --recovery-image recovery-krillin.img
  (Bq channel)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604421/+subscriptions

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

[Desktop-packages] [Bug 1610434] Re: Ubuntu GNOME Trusty HWE upgrade fails to install libwayland-egl1-mesa-lts-xenial

[Launchpad Bug Tracker]

This bug was fixed in the package update-manager - 1:0.196.19

---
update-manager (1:0.196.19) trusty-proposed; urgency=medium

  * hwe-support-status: utilize a virtualbox metapackage set.  (LP:
#1498059)

 -- Brian Murray   Mon, 15 Aug 2016 11:14:48 -0700

** Changed in: update-manager (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  Ubuntu GNOME Trusty HWE upgrade fails to install libwayland-egl1-mesa-
  lts-xenial

Status in update-manager package in Ubuntu:
  New
Status in xorg-lts-xenial package in Ubuntu:
  Won't Fix
Status in update-manager source package in Trusty:
  Fix Released
Status in xorg-lts-xenial source package in Trusty:
  Won't Fix

Bug description:
  Test Case
  -
  1) Install libwayland-egl1-mesa-lts-(utopic|vivid)
  2) Install update-manager from Trusty -proposed
  3) Run hwe-support-status --show-replacements
  4) Ensure libwayland-egl1-mesa-lts-xenial shows up as a replacement

  We should also verify that if libwayland-egl1-mesa-lts-(utopic|vivid)
  is not installed that the equivalent -xenial version is not shown as a
  replacement or installed.

  Updated info; You should be able to reproduce this as follows:

  Step #1: Install Ubuntu GNOME 14.04.2, 14.04.3, or 14.04.4. Boot into
  the fresh installation when complete and apply all available updates
  via UI, then reboot when instructed. It seems important to apply the
  post-install updates via UI rather than using the terminal!

  Step #2: Enable trusty-proposed, update the cache and run "apt-get
  install update-manager". (That will update the components needed to
  display HWE EOL notifications). Then disable trusty-proposed, set
  Notify me of a new release to Never, and update the apt cache again.

  Step #3: Based on recent tests completing step #2 should be enough to
  launch the HWE EOL upgrade notification in which case you just need to
  choose to install the HWE upgrade and reboot when prompted.

  If the HWE EOL notification fails to appear close any open update or
  notifier UI, then from terminal run "apt-get update" followed by
  "update-manager". If the HWE EOL notification still fails to appear
  then I'll have to go back to the drawing board.

  Original content begins here:

  Having updated update-manager from trusty-proposed yesterday I booted
  into Ubuntu GNOME Trusty w/Utopic HWE and update-notifier told me that
  my HWE was EOL so I accepted the upgrade. Everything seemed to
  complete successfully and I was notified to reboot. Upon doing so boot
  freezes with the message "Restoring resolver state". I was unsure what
  package to file this against and since I can't boot that install I was
  unable to file using ubuntu-bug anyway. This freeze occurs whether
  trying to boot the lts-xenial kernel or the older lts-utopic kernel.

  I can collect info as needed, the only useful info I see in the logs
  in from apt/history beginning with the update-manager update yesterday
  and ending with the HWE EOL upgrade just a short time ago:

  Start-Date: 2016-08-04  19:23:23
  Commandline: apt-get install update-manager
  Upgrade: update-manager:i386 (0.196.14, 0.196.15), 
python3-update-manager:i386 (0.196.14, 0.196.15), update-manager-core:i386 
(0.196.14, 0.196.15)
  End-Date: 2016-08-04  19:23:35

  Start-Date: 2016-08-05  13:57:56
  Commandline: aptdaemon role='role-commit-packages' sender=':1.50'
  Install: xserver-xorg-input-synaptics-lts-xenial:i386 
(1.8.2-1ubuntu3~trusty1, automatic), libgl1-mesa-dri-lts-xenial:i386 
(11.2.0-1ubuntu2~trusty1, automatic), xserver-xorg-video-amdgpu-lts-xenial:i386 
(1.1.0-1~trusty1, automatic), libgles2-mesa-lts-xenial:i386 
(11.2.0-1ubuntu2~trusty1), linux-headers-4.4.0-31-generic:i386 
(4.4.0-31.50~14.04.1, automatic), xserver-xorg-video-qxl-lts-xenial:i386 
(0.1.4-3ubuntu3~trusty1, automatic), xserver-xorg-video-savage-lts-xenial:i386 
(2.3.8-1ubuntu3~trusty1, automatic), linux-image-4.4.0-31-generic:i386 
(4.4.0-31.50~14.04.1, automatic), xserver-xorg-video-trident-lts-xenial:i386 
(1.3.7-1build2~trusty1, automatic), 
xserver-xorg-video-siliconmotion-lts-xenial:i386 (1.7.8-1ubuntu6~trusty1, 
automatic), libegl1-mesa-lts-xenial:i386 (11.2.0-1ubuntu2~trusty1), 
xserver-xorg-lts-xenial:i386 (7.7+13ubuntu3~trusty2), 
xserver-xorg-input-vmmouse-lts-xenial:i386 (13.1.0-1ubuntu2~trusty1, 
automatic), libglapi-mesa-lts-xenial:i386 (11.2.0-1ubuntu2~trusty1, a
 utomatic), xserver-xorg-video-nouveau-lts-xenial:i386 (1.0.12-1build2~trusty1, 
automatic), xserver-xorg-input-wacom-lts-xenial:i386 (0.32.0-0ubuntu3~trusty1, 
automatic), linux-generic-lts-xenial:i386 (4.4.0.31.21), 
xserver-xorg-video-openchrome-lts-xenial:i386 (0.3.3+git20160310-1~trusty1, 
automatic), xserver-xorg-input-all-lts-xenial:i386 (7.7+13ubuntu3~trusty2), 

[Desktop-packages] [Bug 1581229] Re: "Started" column not displayed for processes when column is enabled in settings

[Sebastien Bacher]

the debdiff looks great, thanks! (just the changelog targets needs to be
changed to yakkety for upload). I've subscribed ubuntu-sponsors to the
bug

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

Title:
  "Started" column not displayed for processes when column is enabled in
  settings

Status in Gnome System Monitor:
  Fix Released
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-system-monitor package in Ubuntu:
  Fix Committed

Bug description:
  I have recently noticed that in the gnome-system-monitor if I go into
  the settings and tick the box for "Started" in the "Information
  fields" section of that the "Processes" tab that the "Started" column
  is not added and in fact this information is not seemingly displayed
  anywhere except for in the "Properties" window for a process. But it
  would be really useful if it did actually appear as a column so that
  you could easily view the start times for multiple processes at the
  same time and to also sort them in terms of that. I am running Ubuntu
  GNOME 15.10 with GNOME 3.18 but I have also experienced the behaviour
  on Ubuntu GNOME 16.04 with GNOME 3.20, in fact when running it on that
  system through Terminal this was the output (the exact moment I
  checked the "Started" box in the settings to add that column I got the
  first bit of output and then very quickly the other output followed):

  (gnome-system-monitor:2252): GLib-CRITICAL **: Source ID 73 was not found 
when attempting to remove it
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node 

[Desktop-packages] [Bug 1612488] Re: Window too small for Facebook authorization

[Sebastien Bacher]

You can easily reproduce on a yakkety livecd, you just need to delete
the ubuntu entry on the facebook account to get that page which asks for
confirmation of the rights you want to give to "ubuntu"

** Changed in: account-plugins (Ubuntu)
   Importance: Undecided => High

** Changed in: account-plugins (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: account-plugins (Ubuntu)
 Assignee: (unassigned) => Alberto Mardegan (mardy)

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

Title:
  Window too small for Facebook authorization

Status in account-plugins package in Ubuntu:
  Confirmed

Bug description:
  When trying to add a Facebook account under System Settings -> Online
  Accounts it says the following after trying to login to Facebook.

  "Your popup is too small to display this page. Please enlarge it to
  proceed."

  This is a gray overlay blocking the ability to accept Ubuntu access to
  Facebook. There is no way to enlarge the window so it can't proceed.

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

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

[Desktop-packages] [Bug 1581229] Re: "Started" column not displayed for processes when column is enabled in settings

[Nikita Yerenkov-Scott]

Anyway, so you need me to do what I have done for the 3.20 in Yakkety
and the 3.18 in Xenial? I hope that at least the Ubuntu GNOME
gnome3-staging PPA can make use of my current debdiff. I will do the
work for the next debdiffs in VMs so I may take a little while to submit
them, I hope to get another submitted by the end of today, but my
Yakkety VM is a bit on the slow side so there might be a delay in one of
them, but should all be there by some time tomorrow.

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

Title:
  "Started" column not displayed for processes when column is enabled in
  settings

Status in Gnome System Monitor:
  Fix Released
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-system-monitor package in Ubuntu:
  Fix Committed

Bug description:
  I have recently noticed that in the gnome-system-monitor if I go into
  the settings and tick the box for "Started" in the "Information
  fields" section of that the "Processes" tab that the "Started" column
  is not added and in fact this information is not seemingly displayed
  anywhere except for in the "Properties" window for a process. But it
  would be really useful if it did actually appear as a column so that
  you could easily view the start times for multiple processes at the
  same time and to also sort them in terms of that. I am running Ubuntu
  GNOME 15.10 with GNOME 3.18 but I have also experienced the behaviour
  on Ubuntu GNOME 16.04 with GNOME 3.20, in fact when running it on that
  system through Terminal this was the output (the exact moment I
  checked the "Started" box in the settings to add that column I got the
  first bit of output and then very quickly the other output followed):

  (gnome-system-monitor:2252): GLib-CRITICAL **: Source ID 73 was not found 
when attempting to remove it
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)

[Desktop-packages] [Bug 1581229] Re: "Started" column not displayed for processes when column is enabled in settings

[Nikita Yerenkov-Scott]

Strange, I didn't get the message you sent before I sent mine... We must
have sent them at the same time.

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

Title:
  "Started" column not displayed for processes when column is enabled in
  settings

Status in Gnome System Monitor:
  Fix Released
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-system-monitor package in Ubuntu:
  Fix Committed

Bug description:
  I have recently noticed that in the gnome-system-monitor if I go into
  the settings and tick the box for "Started" in the "Information
  fields" section of that the "Processes" tab that the "Started" column
  is not added and in fact this information is not seemingly displayed
  anywhere except for in the "Properties" window for a process. But it
  would be really useful if it did actually appear as a column so that
  you could easily view the start times for multiple processes at the
  same time and to also sort them in terms of that. I am running Ubuntu
  GNOME 15.10 with GNOME 3.18 but I have also experienced the behaviour
  on Ubuntu GNOME 16.04 with GNOME 3.20, in fact when running it on that
  system through Terminal this was the output (the exact moment I
  checked the "Started" box in the settings to add that column I got the
  first bit of output and then very quickly the other output followed):

  (gnome-system-monitor:2252): GLib-CRITICAL **: Source ID 73 was not found 
when attempting to remove it
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)

To manage 

[Desktop-packages] [Bug 1613805] Re: [evolution/wip/webkit2] EHTMLEditorView - Restore the selection end mark correctly when processing HTML to plain text

[Jamie Strandboge]

** Description changed:

  From https://mail.gnome.org/archives/commits-
  list/2016-May/msg06756.html:
  
- "EHTMLEditorView - Restore the selection end mark correctly when processing 
HTML to plain text
- 
+ "EHTMLEditorView - Restore the selection end mark correctly when
+ processing HTML to plain text
+ 
  Otherwise the ##SELECTON_END## string could be left in the output."
  
- I see this on xenial. Patch is in the commit list.
+ I sometimes see this from people on xenial. Patch is in the commit list
+ needs a light backport. I will attach a debdiff if it works.

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

Title:
  [evolution/wip/webkit2] EHTMLEditorView - Restore the selection end
  mark correctly when processing HTML to plain text

Status in evolution package in Ubuntu:
  New

Bug description:
  From https://mail.gnome.org/archives/commits-
  list/2016-May/msg06756.html:

  "EHTMLEditorView - Restore the selection end mark correctly when
  processing HTML to plain text

  Otherwise the ##SELECTON_END## string could be left in the output."

  I sometimes see this from people on xenial. Patch is in the commit
  list needs a light backport. I will attach a debdiff if it works.

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

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

[Desktop-packages] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics

[José Jorge Enríquez Rodríguez]

Tested succesfully xserver-xorg-video-intel from xenial proposed on an
Inspiron 14 3000 series laptop.

Installed 2:2.99.917+git20160325-1ubuntu1.1, restarted system, tested
from lock, then suspend and finally lock again, cursor returned
everytime.

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

Title:
  Mouse cursor lost when unlocking with Intel graphics

Status in elementary OS:
  Fix Released
Status in xf86-video-intel:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-intel package in Debian:
  Fix Released

Bug description:
  [Impact]
  Mouse cursor is no longer visible after VT-switch for systems with Intel 
graphics.

  Switching VTs again may cause the cursor to become visible again.
  - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7)

  This is often observed in systems that lock the session and return to
  the greeter (including at least Xubuntu, Ubuntu Mate, and elementary
  OS).

  [Test Case]
  (Requires a lightdm-based screen locking solution)
  1. Start a new session.
  2. Lock your screen.
  2a. You are redirected to the lightdm greeter.
  3. Login/Unlock your session.
  4. Cursor is no longer visible.

  [Regression Potential]
  remains to be seen

  ===

  [Original Report]
  Cursor is visible at unlock screen either after returning from suspend or 
just locking.

  After unlocking screen cursor is invisible.

  Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor
  returns

  

  no matter if you suspend or sleep, to swap or disk when you return
  from it, the mouse cursor is missing.you can still move the mouse
  and you can see (because it highlights the window) as you move it
  around.   But the cursor is not displayed on the screen.

  i am using a lenovo W540 laptop.   I downloaded the latest beta on
  april 8 2016.

  this is xubuntu using the xfce window manager.

  the cursor does return if i log off and log back in, but that actually 
defeats the purpose of going to sleep.
  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-08 (2 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1604421] Re: Unity 8 fails to start on staging (xenial) on the phone when --wipe is used for flashing

[Sebastien Bacher]

** No longer affects: glib2.0 (Ubuntu)

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

Title:
  Unity 8 fails to start on staging (xenial) on the phone when --wipe is
  used for flashing

Status in Canonical System Image:
  Confirmed
Status in gsettings-ubuntu-touch-schemas package in Ubuntu:
  New
Status in unity package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Update: this only happens when --wipe (or --bootstrap) is used for
  flashing. It is possible to get functional xenial/staging running by
  doing non-destructive flash update from rc-proposed.

  Unity 8 fails to start on staging (=xenial + xenial-overlay) on my
  krillin.

  unity-system-compositor.log: http://paste.ubuntu.com/20035267/ - shows
  Opening/Closing/Opening/Closing when starting unity8.

  unity8.log attached.

  Using ubuntu-touch/staging/bq-aquaris.en channel on krillin.
  version_detail:
  ubuntu=20160719,device=20160606-ab415b2,custom=20160701-981-38-14,version=49

  Crash file at http://people.ubuntu.com/~timo-
  jyrinki/unity8/_usr_bin_unity8.32011.crash

  Xenial can be flashed on the phone with eg:
  ubuntu-device-flash touch --channel=ubuntu-touch/staging/ubuntu 
--developer-mode --password= --wipe --boostrap
  (ubuntu channel)
  ubuntu-device-flash touch --channel=ubuntu-touch/staging/bq-aquaris.en 
--developer-mode --password= --wipe --recovery-image recovery-krillin.img
  (Bq channel)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604421/+subscriptions

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

[Desktop-packages] [Bug 1581229] Re: "Started" column not displayed for processes when column is enabled in settings

[Nikita Yerenkov-Scott]

Here is the debdiff for the 3.20 version. I assume that I also need to
make on for 3.18. Is that correct and does my 3.20 debdiff look ok or
does anything need improving/changing (I haven't really done this
before, at least not for a long time, and back then I had help, this
time I had none)?

** Patch added: "FixDefaultColumnWidth3-20.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1581229/+attachment/4722180/+files/FixDefaultColumnWidth3-20.debdiff

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

Title:
  "Started" column not displayed for processes when column is enabled in
  settings

Status in Gnome System Monitor:
  Fix Released
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-system-monitor package in Ubuntu:
  Fix Committed

Bug description:
  I have recently noticed that in the gnome-system-monitor if I go into
  the settings and tick the box for "Started" in the "Information
  fields" section of that the "Processes" tab that the "Started" column
  is not added and in fact this information is not seemingly displayed
  anywhere except for in the "Properties" window for a process. But it
  would be really useful if it did actually appear as a column so that
  you could easily view the start times for multiple processes at the
  same time and to also sort them in terms of that. I am running Ubuntu
  GNOME 15.10 with GNOME 3.18 but I have also experienced the behaviour
  on Ubuntu GNOME 16.04 with GNOME 3.20, in fact when running it on that
  system through Terminal this was the output (the exact moment I
  checked the "Started" box in the settings to add that column I got the
  first bit of output and then very quickly the other output followed):

  (gnome-system-monitor:2252): GLib-CRITICAL **: Source ID 73 was not found 
when attempting to remove it
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node 

[Desktop-packages] [Bug 1581229] Re: "Started" column not displayed for processes when column is enabled in settings

[Sebastien Bacher]

depends of what serie you want to get fixed, ideally just using the
patch on top of what is currently in the archive so 3.20 for yakkety and
3.18 for xenial

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

Title:
  "Started" column not displayed for processes when column is enabled in
  settings

Status in Gnome System Monitor:
  Fix Released
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-system-monitor package in Ubuntu:
  Fix Committed

Bug description:
  I have recently noticed that in the gnome-system-monitor if I go into
  the settings and tick the box for "Started" in the "Information
  fields" section of that the "Processes" tab that the "Started" column
  is not added and in fact this information is not seemingly displayed
  anywhere except for in the "Properties" window for a process. But it
  would be really useful if it did actually appear as a column so that
  you could easily view the start times for multiple processes at the
  same time and to also sort them in terms of that. I am running Ubuntu
  GNOME 15.10 with GNOME 3.18 but I have also experienced the behaviour
  on Ubuntu GNOME 16.04 with GNOME 3.20, in fact when running it on that
  system through Terminal this was the output (the exact moment I
  checked the "Started" box in the settings to add that column I got the
  first bit of output and then very quickly the other output followed):

  (gnome-system-monitor:2252): GLib-CRITICAL **: Source ID 73 was not found 
when attempting to remove it
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget 

[Desktop-packages] [Bug 1613781] Re: Mouse (tracker) way too fast

[Paul White]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1550988, so it is being marked as such.

Please look at the other bug report to see if there is any missing
information that you can provide, or to see if there is a workaround for
the bug. Additionally, any further discussion regarding the bug should
occur in the other report. Feel free to continue to report any other
bugs you may find.

** This bug has been marked a duplicate of bug 1550988
   Mouse pointer speed too fast

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

Title:
  Mouse (tracker) way too fast

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading from 14.04 to 16.04 on a Lenovo x230, the mouse
  pointer speed is way too high even if set at minimum. It's so bad it's
  almost unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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: Tue Aug 16 17:59:43 2016
  DistUpgraded: 2016-08-16 17:52:45,075 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.24, 3.13.0-93-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa]
  InstallationDate: Installed on 2014-07-11 (767 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 2325D93
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-08-16 (0 days ago)
  dmi.bios.date: 04/30/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET94WW (2.54 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325D93
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 10623
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET94WW(2.54):bd04/30/2013:svnLENOVO:pn2325D93:pvrThinkPadX230:rvnLENOVO:rn2325D93:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325D93
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Aug 16 17:53:58 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 931 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Desktop-packages] [Bug 1613805] [NEW] [evolution/wip/webkit2] EHTMLEditorView - Restore the selection end mark correctly when processing HTML to plain text

[Jamie Strandboge]

Public bug reported:

>From https://mail.gnome.org/archives/commits-
list/2016-May/msg06756.html:

"EHTMLEditorView - Restore the selection end mark correctly when processing 
HTML to plain text

Otherwise the ##SELECTON_END## string could be left in the output."

I see this on xenial. Patch is in the commit list.

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

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

Title:
  [evolution/wip/webkit2] EHTMLEditorView - Restore the selection end
  mark correctly when processing HTML to plain text

Status in evolution package in Ubuntu:
  New

Bug description:
  From https://mail.gnome.org/archives/commits-
  list/2016-May/msg06756.html:

  "EHTMLEditorView - Restore the selection end mark correctly when processing 
HTML to plain text
  
  Otherwise the ##SELECTON_END## string could be left in the output."

  I see this on xenial. Patch is in the commit list.

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

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

[Desktop-packages] [Bug 1604421] Re: Unity 8 fails to start on staging (xenial) on the phone when --wipe is used for flashing

[Łukasz Zemczak]

Looking at the commitlog, from the packages that could have touched
anything related to schemas, I see two package uploads happening between
image #40 (xenial working) and image #41 (xenial broken):

- gsettings-ubuntu-touch-schemas (0.0.7+16.04.20160615.1-0ubuntu1) > 
gsettings-ubuntu-schemas:
http://launchpadlibrarian.net/267243088/gsettings-ubuntu-touch-schemas_0.0.6+16.04.20160414-0ubuntu1_0.0.7+16.10.20160615.1-0ubuntu1.diff.gz
- unity (7.4.0+16.04.20160705-0ubuntu1) > unity-schemas:
http://launchpadlibrarian.net/272410280/unity_7.4.0+16.04.20160526.1-0ubuntu1_7.4.0+16.04.20160705-0ubuntu1.diff.gz

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

Title:
  Unity 8 fails to start on staging (xenial) on the phone when --wipe is
  used for flashing

Status in Canonical System Image:
  Confirmed
Status in glib2.0 package in Ubuntu:
  New
Status in gsettings-ubuntu-touch-schemas package in Ubuntu:
  New
Status in unity package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Update: this only happens when --wipe (or --bootstrap) is used for
  flashing. It is possible to get functional xenial/staging running by
  doing non-destructive flash update from rc-proposed.

  Unity 8 fails to start on staging (=xenial + xenial-overlay) on my
  krillin.

  unity-system-compositor.log: http://paste.ubuntu.com/20035267/ - shows
  Opening/Closing/Opening/Closing when starting unity8.

  unity8.log attached.

  Using ubuntu-touch/staging/bq-aquaris.en channel on krillin.
  version_detail:
  ubuntu=20160719,device=20160606-ab415b2,custom=20160701-981-38-14,version=49

  Crash file at http://people.ubuntu.com/~timo-
  jyrinki/unity8/_usr_bin_unity8.32011.crash

  Xenial can be flashed on the phone with eg:
  ubuntu-device-flash touch --channel=ubuntu-touch/staging/ubuntu 
--developer-mode --password= --wipe --boostrap
  (ubuntu channel)
  ubuntu-device-flash touch --channel=ubuntu-touch/staging/bq-aquaris.en 
--developer-mode --password= --wipe --recovery-image recovery-krillin.img
  (Bq channel)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604421/+subscriptions

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

[Desktop-packages] [Bug 1598316] Re: gtk2-engines-murrine desktop text shadow problem

[Jeremy Bicha]

I posted it to http://iso.qa.ubuntu.com/qatracker/milestones/363/builds
so I think you should have seen it there

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

Title:
  gtk2-engines-murrine desktop text shadow problem

Status in Arc Theme:
  New
Status in Numix GTK theme:
  Fix Released
Status in arc-theme package in Ubuntu:
  Triaged
Status in gtk2-engines-murrine package in Ubuntu:
  Triaged
Status in shimmer-themes package in Ubuntu:
  Invalid
Status in xfdesktop4 package in Ubuntu:
  Confirmed
Status in gtk2-engines-murrine package in Debian:
  New

Bug description:
  Upgraded my xubuntu 16.04 system on 01 Jul 2016.  The apt update
  included an upgrade to gtk2-engines-murrine.  However, after the
  upgrade and boot, the any desktop text, folder, launcher, etc. had a
  problem with the text and shadow being quite far apart.

  This bug affects themes that use the textstyle feature of the murrine
  engine on xfdesktop4. Ubuntu MATE 16.04, which also uses gtk2 but has
  caja draw the desktop icons instead of xfdesktop, is not affected.

  The only known affected theme packaged in Xubuntu 16.04 is numix-gtk-
  theme. Third-party affected themes include Arc and Vertex.

To manage notifications about this bug go to:
https://bugs.launchpad.net/arc-theme/+bug/1598316/+subscriptions

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

[Desktop-packages] [Bug 1613802] [NEW] When Amazon Fire tablet is connected via USB information on tablet is written to syslog every 15 minutes

[chris pollock]

Public bug reported:

Description: Ubuntu 16.04.1 LTS Release:16.04
gvfs information
chris@localhost:~$ apt-cache policy gvfs
gvfs:
  Installed: 1.28.2-1ubuntu1~16.04.1
  Candidate: 1.28.2-1ubuntu1~16.04.1
  Version table:
 *** 1.28.2-1ubuntu1~16.04.1 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1.28.1-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages


Every 15 minutes when I have my Amazon Fire HDX 8.9 tablet connected via USB to 
my desktop information on the tablet is being written to my syslog causing it 
to grow very large. This same issue did NOT occur in 14.04 LTS. I've tried a 
different USB port and a different USB cable with the same results. Below is 
what is put into the syslog. What should have happened - if anything just this 
which is the tablet:

Aug 16 10:59:14 localhost kernel: [661846.880021] usb 2-1: new high-speed USB 
device number 28 using ehci-pci
Aug 16 10:59:14 localhost kernel: [661847.021290] usb 2-1: New USB device 
found, idVendor=1949, idProduct=0012
Aug 16 10:59:14 localhost kernel: [661847.021295] usb 2-1: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
Aug 16 10:59:14 localhost kernel: [661847.021298] usb 2-1: Product: Android
Aug 16 10:59:14 localhost kernel: [661847.021300] usb 2-1: Manufacturer: Android
Aug 16 10:59:14 localhost kernel: [661847.021303] usb 2-1: SerialNumber: 
B0850706443401A1

Which is what used to be written in 14.04 whenver I plugged in the
tablet or my Samsung phone. One note when the phone is plugged in the
below lines are not written to syslog just the typical information
above.

I've attached a file with what is written to syslog.

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

** Attachment added: "fire-tablet.txt"
   
https://bugs.launchpad.net/bugs/1613802/+attachment/4722170/+files/fire-tablet.txt

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

Title:
  When Amazon Fire tablet is connected via USB information on tablet is
  written to syslog every 15 minutes

Status in gvfs package in Ubuntu:
  New

Bug description:
  Description: Ubuntu 16.04.1 LTS Release:16.04
  gvfs information
  chris@localhost:~$ apt-cache policy gvfs
  gvfs:
Installed: 1.28.2-1ubuntu1~16.04.1
Candidate: 1.28.2-1ubuntu1~16.04.1
Version table:
   *** 1.28.2-1ubuntu1~16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.28.1-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  
  Every 15 minutes when I have my Amazon Fire HDX 8.9 tablet connected via USB 
to my desktop information on the tablet is being written to my syslog causing 
it to grow very large. This same issue did NOT occur in 14.04 LTS. I've tried a 
different USB port and a different USB cable with the same results. Below is 
what is put into the syslog. What should have happened - if anything just this 
which is the tablet:

  Aug 16 10:59:14 localhost kernel: [661846.880021] usb 2-1: new high-speed USB 
device number 28 using ehci-pci
  Aug 16 10:59:14 localhost kernel: [661847.021290] usb 2-1: New USB device 
found, idVendor=1949, idProduct=0012
  Aug 16 10:59:14 localhost kernel: [661847.021295] usb 2-1: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
  Aug 16 10:59:14 localhost kernel: [661847.021298] usb 2-1: Product: Android
  Aug 16 10:59:14 localhost kernel: [661847.021300] usb 2-1: Manufacturer: 
Android
  Aug 16 10:59:14 localhost kernel: [661847.021303] usb 2-1: SerialNumber: 
B0850706443401A1

  Which is what used to be written in 14.04 whenver I plugged in the
  tablet or my Samsung phone. One note when the phone is plugged in the
  below lines are not written to syslog just the typical information
  above.

  I've attached a file with what is written to syslog.

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

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

[Desktop-packages] [Bug 1613729] Re: NetworkManager autoconnects to wired profiles in reverse order

[Ubuntu Foundations Team Bug Bot]

The attachment "Patch to fix this" seems to be a patch.  If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

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

** Tags added: patch

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

Title:
  NetworkManager autoconnects to wired profiles in reverse order

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I select a wired profile manually and reboot, NetworkManager
  instead connects to the profile that has the oldest timestamp. So it's
  not connecting to the last used profile, which is troublesome.

  On all of our machines (about 500), we define three wired network
  profiles, one DHCP and two static. We're migrating from Debian to
  Ubuntu, so this bug has only surfaced now for us.

  This can be reproduced by creating a couple of network profiles on the
  same wired interface and then rebooting or restarting network-manager.
  It will loop through the network profiles in the same order always. So
  it's doing the exact reverse of what's supposed to happen.

  I did some digging and I applied a simple patch to the source code.
  This seems to have fixed the issue. I posted my patch for verification
  on the networkmanager mailing list and it was verified as being
  correct by Beniamino Galvani, one of the developers.

  Here is the link to the network-manager topic:
  https://mail.gnome.org/archives/networkmanager-
  list/2016-August/msg00053.html

  This is the patch (also included as attachment):

  --- nm-device.c 2016-08-16 15:37:50.0 +0200
  +++ nm-device_patched.c 2016-08-16 15:44:08.308729955 +0200
  @@ -1267,7 +1267,7 @@
  s_con = nm_connection_get_setting_connection (connection);
  g_assert (s_con);
  if (nm_setting_connection_get_autoconnect (s_con))
  -   available_conns = g_slist_prepend (available_conns, 
connection);
  +   available_conns = g_slist_append (available_conns, 
connection);
  }

  if (!available_conns)

  I hope to get this patch included in the trusty package, so somebody
  else can benefit from this.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.3
  ProcVersionSignature: Ubuntu 4.4.0-34.53~14.04.1-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CRDA: Error: [Errno 2] Bestand of map bestaat niet: 'iw'
  CurrentDesktop: Unity
  Date: Tue Aug 16 15:23:17 2016
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.30.6.1 dev em1  proto static 
   10.30.6.0/24 dev em1  proto kernel  scope link  src 10.30.6.204  metric 1 
   10.40.8.0/21 dev tun0  proto kernel  scope link  src 10.40.8.31
  IwConfig:
   tun0  no wireless extensions.
   
   em1   no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=nl_BE:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_BE
   SHELL=/bin/bash
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   DHCP  702624f9-f052-473a-b131-acd2045e6ec2   
802-3-ethernet1471353746   di 16 aug 2016 15:22:26 CEST   yes   
no /org/freedesktop/NetworkManager/Settings/1
   Proximus  7a9a5bc2-d51a-46b4-b721-050a607951bc   
802-3-ethernet1471353744   di 16 aug 2016 15:22:24 CEST   yes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   em1802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Desktop-packages] [Bug 1613430] Re: lightdm not showing gnome desktop option

[bgblanch]

I tried logging in with the guest account and got dumped back out to the
login screen again.

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

Title:
  lightdm not showing gnome desktop option

Status in lightdm package in Ubuntu:
  New

Bug description:
  I installed ubuntu-gnome-desktop and selected lightdm as the display
  manager (tried gdm and received only a purple screen).  When I click
  on the ubuntu logo to the right of my login (where I believe I should
  be able to select the desktop I would like to use) the login name(s)
  disappear and nothing happens until I hit enter at which point the
  login names reappear

  I have tried logging out and back in again as well as rebooting with the same 
results.  I am currently on a Dell XPS 13 Developer Edition (Ubuntu laptop).  I 
am able to log into Unity with no problem but I would like to use Gnome.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-07-26 (19 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  Package: lightdm 1.18.2-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Tags: xenial third-party-packages
  Uname: Linux 4.4.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics

[Wilfried]

I installed lxdm and that fixed it for me on a Lubuntu machine

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

Title:
  Mouse cursor lost when unlocking with Intel graphics

Status in elementary OS:
  Fix Released
Status in xf86-video-intel:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-intel package in Debian:
  Fix Released

Bug description:
  [Impact]
  Mouse cursor is no longer visible after VT-switch for systems with Intel 
graphics.

  Switching VTs again may cause the cursor to become visible again.
  - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7)

  This is often observed in systems that lock the session and return to
  the greeter (including at least Xubuntu, Ubuntu Mate, and elementary
  OS).

  [Test Case]
  (Requires a lightdm-based screen locking solution)
  1. Start a new session.
  2. Lock your screen.
  2a. You are redirected to the lightdm greeter.
  3. Login/Unlock your session.
  4. Cursor is no longer visible.

  [Regression Potential]
  remains to be seen

  ===

  [Original Report]
  Cursor is visible at unlock screen either after returning from suspend or 
just locking.

  After unlocking screen cursor is invisible.

  Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor
  returns

  

  no matter if you suspend or sleep, to swap or disk when you return
  from it, the mouse cursor is missing.you can still move the mouse
  and you can see (because it highlights the window) as you move it
  around.   But the cursor is not displayed on the screen.

  i am using a lenovo W540 laptop.   I downloaded the latest beta on
  april 8 2016.

  this is xubuntu using the xfce window manager.

  the cursor does return if i log off and log back in, but that actually 
defeats the purpose of going to sleep.
  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-08 (2 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1598316] Re: gtk2-engines-murrine desktop text shadow problem

[flocculant]

@jbicha, I certainly didn't see the SRU (perhaps because of bug
subscription(S)), first we knew of the issue was someone in #xubuntu ;)

I'm still catching people in the irc channel - been away, updating, boom

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

Title:
  gtk2-engines-murrine desktop text shadow problem

Status in Arc Theme:
  New
Status in Numix GTK theme:
  Fix Released
Status in arc-theme package in Ubuntu:
  Triaged
Status in gtk2-engines-murrine package in Ubuntu:
  Triaged
Status in shimmer-themes package in Ubuntu:
  Invalid
Status in xfdesktop4 package in Ubuntu:
  Confirmed
Status in gtk2-engines-murrine package in Debian:
  New

Bug description:
  Upgraded my xubuntu 16.04 system on 01 Jul 2016.  The apt update
  included an upgrade to gtk2-engines-murrine.  However, after the
  upgrade and boot, the any desktop text, folder, launcher, etc. had a
  problem with the text and shadow being quite far apart.

  This bug affects themes that use the textstyle feature of the murrine
  engine on xfdesktop4. Ubuntu MATE 16.04, which also uses gtk2 but has
  caja draw the desktop icons instead of xfdesktop, is not affected.

  The only known affected theme packaged in Xubuntu 16.04 is numix-gtk-
  theme. Third-party affected themes include Arc and Vertex.

To manage notifications about this bug go to:
https://bugs.launchpad.net/arc-theme/+bug/1598316/+subscriptions

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

[Desktop-packages] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics

[Yosuke Kabuto]

Works on Lenovo X201s :)

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

Title:
  Mouse cursor lost when unlocking with Intel graphics

Status in elementary OS:
  Fix Released
Status in xf86-video-intel:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-intel package in Debian:
  Fix Released

Bug description:
  [Impact]
  Mouse cursor is no longer visible after VT-switch for systems with Intel 
graphics.

  Switching VTs again may cause the cursor to become visible again.
  - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7)

  This is often observed in systems that lock the session and return to
  the greeter (including at least Xubuntu, Ubuntu Mate, and elementary
  OS).

  [Test Case]
  (Requires a lightdm-based screen locking solution)
  1. Start a new session.
  2. Lock your screen.
  2a. You are redirected to the lightdm greeter.
  3. Login/Unlock your session.
  4. Cursor is no longer visible.

  [Regression Potential]
  remains to be seen

  ===

  [Original Report]
  Cursor is visible at unlock screen either after returning from suspend or 
just locking.

  After unlocking screen cursor is invisible.

  Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor
  returns

  

  no matter if you suspend or sleep, to swap or disk when you return
  from it, the mouse cursor is missing.you can still move the mouse
  and you can see (because it highlights the window) as you move it
  around.   But the cursor is not displayed on the screen.

  i am using a lenovo W540 laptop.   I downloaded the latest beta on
  april 8 2016.

  this is xubuntu using the xfce window manager.

  the cursor does return if i log off and log back in, but that actually 
defeats the purpose of going to sleep.
  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-08 (2 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1613063] Re: Request for sponsorship for new upstream release (yakkety deb provided)

[Launchpad Bug Tracker]

This bug was fixed in the package onboard - 1.3.0-0ubuntu1

---
onboard (1.3.0-0ubuntu1) yakkety; urgency=medium

  * Request for sponsorship for new upstream release (LP: #1613063)
  * debian/control:
  - Bump Standards-Version to 3.9.8
  - Add libwayland-dev to Build-Depends
  - Add libxkbcommon-dev to Build-Depends
  * debian/copyright: update
  * debian/onboard.install: add usr/share/dbus-1/services entry
  * debian/patches:
- Drop bzr_fix_untranslatable_buttons.patch: applied upstream
- Drop fix_arrows_on_compact_layout.patch: applied upstream
- Refresh add_defaults_for_ubuntu.patch
  * debian/source.lintian-overrides: update entries line number
  * Status icon:
- Move AppIndicator and GtkStatusIcon into separate backends
- Allow left-clicking AppIndicator in KDE Plasma
- Don't crash when Appindicator or Atspi are not available
- Fix fallback to GtkStatusIcon when Applndicator is not available
- Fix tooltip of status icon provider (LP: #1570318). Thanks Ubuntu-QC-1
  * Word suggestions and auto-correction:
- Add Esperanto language model
- Elipsize very large words and fix them being invisible
- Fix Compact layout not showing the "More suggestions" arrows
- Improve auto-correction of URLs and filenames in long texts
  * Virtkey:
- Improve search for available keysyms in X (LP:1562381)
- Move key mapping from X functions to Xkb
- Make Xkb-based mapping also work in Ubuntu-GNOME
- Add uinput backend to virtkey for initial support of non-X desktops
- Isolate X related parts of virtkey in preparation for non-X desktops
- Add initial Wayland support (blocker: gtk_window_set_accept_focus())
  * D-Bus service:
- Add support for properties via python decorator
- Setup D-Bus activation to simplify showing on hotkey press (LP: #1607235)
- Update D-Bus usage examples in README
  * Add fallback to default system font family for themes:
- High contrast themes get a font this way
- Fixes Ubuntu logo not appearing in yakkety
  * Add aspect ratio limits when the keyboard is docked or expanded (LP:1586493)
  * Add touch handle to adjust the docking aspect ratio limit
  * Expand docked keyboard on landscape oriented screens by default
  * Auto-detect default status-icon provider in major desktop environments
  * Improve alignment of some labels in the Preferences dialog
  * Fix former stock buttons in Preferences not being translated (LP: #1567301)
  * Add small bitmap icons to prevent aliasing issues (LP: #1552484)
  * Add more example keys to onboard-defaults.conf.example (LP: #1546654)
  * Improve pep8 compliance of various source files
  * Don't let the return key leave the screen for Small and Phone layouts
  * Prevent setting new home position after accidental resize frame clicks
  * Work around shadows becoming visible during resize when docked with sidebars
  * Fix errors uncovered in Keyboard.py by flake8
  * Fix unwanted key-repeats when typing into Gtk-3 applications (LP: #1562381)
  * Fix keyboard sometimes starting up at unexpected positions on system start
  * Fix build failure with gcc-6 that switched to C++14. Thanks Jeremy Bicha
  * Fix warning when building with gcc versions before 6, i.e. C++98 by default
  * Remove entries with default values from desktop files. Thanks Mike Gabriel
  * Add 3.20 and 3.22 to shell-version field of GNOME extension. Thanks J. Bicha
  * Care for compatibility with Ubuntu Precise (12.04)
  * Update PPA link in README

 -- Francesco Fumanti   Sun, 13 Aug 2016
22:23:14 +0200

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

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

Title:
  Request for sponsorship for new upstream release (yakkety deb
  provided)

Status in onboard package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  A new Onboard version has just been released. Here is the relevant
  part of the debian/changelog from the debianisation I prepared for
  yakkety:

  onboard (1.2.0+2177-0ppa1~yakkety) yakkety; urgency=medium

* Request for sponsorship for new upstream release (LP: #1613063)
* debian/control: 
- Bump Standards-Version to 3.9.8
- Add libwayland-dev to Build-Depends
- Add libxkbcommon-dev to Build-Depends
* debian/copyright: update
* debian/onboard.install: add usr/share/dbus-1/services entry
* debian/patches:
  - Drop bzr_fix_untranslatable_buttons.patch: applied upstream
  - Drop fix_arrows_on_compact_layout.patch: applied upstream
  - Refresh add_defaults_for_ubuntu.patch
* debian/source.lintian-overrides: update entries line number
* Status icon:
  - Move AppIndicator and GtkStatusIcon into separate backends
  - Allow left-clicking AppIndicator in KDE Plasma
  - Don't crash when 

[Desktop-packages] [Bug 1562381] Re: Typing special characters with non-US layout get repeated indefinitely

[Launchpad Bug Tracker]

This bug was fixed in the package onboard - 1.3.0-0ubuntu1

---
onboard (1.3.0-0ubuntu1) yakkety; urgency=medium

  * Request for sponsorship for new upstream release (LP: #1613063)
  * debian/control:
  - Bump Standards-Version to 3.9.8
  - Add libwayland-dev to Build-Depends
  - Add libxkbcommon-dev to Build-Depends
  * debian/copyright: update
  * debian/onboard.install: add usr/share/dbus-1/services entry
  * debian/patches:
- Drop bzr_fix_untranslatable_buttons.patch: applied upstream
- Drop fix_arrows_on_compact_layout.patch: applied upstream
- Refresh add_defaults_for_ubuntu.patch
  * debian/source.lintian-overrides: update entries line number
  * Status icon:
- Move AppIndicator and GtkStatusIcon into separate backends
- Allow left-clicking AppIndicator in KDE Plasma
- Don't crash when Appindicator or Atspi are not available
- Fix fallback to GtkStatusIcon when Applndicator is not available
- Fix tooltip of status icon provider (LP: #1570318). Thanks Ubuntu-QC-1
  * Word suggestions and auto-correction:
- Add Esperanto language model
- Elipsize very large words and fix them being invisible
- Fix Compact layout not showing the "More suggestions" arrows
- Improve auto-correction of URLs and filenames in long texts
  * Virtkey:
- Improve search for available keysyms in X (LP:1562381)
- Move key mapping from X functions to Xkb
- Make Xkb-based mapping also work in Ubuntu-GNOME
- Add uinput backend to virtkey for initial support of non-X desktops
- Isolate X related parts of virtkey in preparation for non-X desktops
- Add initial Wayland support (blocker: gtk_window_set_accept_focus())
  * D-Bus service:
- Add support for properties via python decorator
- Setup D-Bus activation to simplify showing on hotkey press (LP: #1607235)
- Update D-Bus usage examples in README
  * Add fallback to default system font family for themes:
- High contrast themes get a font this way
- Fixes Ubuntu logo not appearing in yakkety
  * Add aspect ratio limits when the keyboard is docked or expanded (LP:1586493)
  * Add touch handle to adjust the docking aspect ratio limit
  * Expand docked keyboard on landscape oriented screens by default
  * Auto-detect default status-icon provider in major desktop environments
  * Improve alignment of some labels in the Preferences dialog
  * Fix former stock buttons in Preferences not being translated (LP: #1567301)
  * Add small bitmap icons to prevent aliasing issues (LP: #1552484)
  * Add more example keys to onboard-defaults.conf.example (LP: #1546654)
  * Improve pep8 compliance of various source files
  * Don't let the return key leave the screen for Small and Phone layouts
  * Prevent setting new home position after accidental resize frame clicks
  * Work around shadows becoming visible during resize when docked with sidebars
  * Fix errors uncovered in Keyboard.py by flake8
  * Fix unwanted key-repeats when typing into Gtk-3 applications (LP: #1562381)
  * Fix keyboard sometimes starting up at unexpected positions on system start
  * Fix build failure with gcc-6 that switched to C++14. Thanks Jeremy Bicha
  * Fix warning when building with gcc versions before 6, i.e. C++98 by default
  * Remove entries with default values from desktop files. Thanks Mike Gabriel
  * Add 3.20 and 3.22 to shell-version field of GNOME extension. Thanks J. Bicha
  * Care for compatibility with Ubuntu Precise (12.04)
  * Update PPA link in README

 -- Francesco Fumanti   Sun, 13 Aug 2016
22:23:14 +0200

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

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

Title:
  Typing special characters with non-US layout get repeated indefinitely

Status in Onboard:
  Fix Committed
Status in onboard package in Ubuntu:
  Fix Released

Bug description:
  Typing special characters like .,:;-()"@# (and other) or numbers with
  non-US keyboard layout get repeated indefinitely, like this:

  
тест...

  This will continue to happen untl other symbol is entered or other
  button is pressed. Reproducible with GTK and Xinput. Testng was done
  on Ubuntu Gnome 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: onboard 1.2.0-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 27 02:29:05 2016
  InstallationDate: Installed on 2016-03-19 (6 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160319)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   

[Desktop-packages] [Bug 1021375] Re: Nautilus says the USB stick is read only when it is not

[ile]

I have this problem on 16.04 and a normal SATA disk. "killall nautilus"
helped.

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

Title:
  Nautilus says the USB stick is read only when it is not

Status in Nautilus:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  First time I use an USB drive since I updated to 12.04 and I found a
  really annoying bug on Nautilus. Nautilus claims that the destination
  drive is read-only when in fact it is not.

  How to reproduce:

  1. Connect a USB stick drive to your competer.
  2. The USB will appear in the desktop.
  3. Open two Nautilus windows one in your home folder, other in the USB stick 
drive.
  4. Select any file from your home folder (small enough to fit the free space 
in the USB drive)
  5. Drag the file and drop it in the USB drive window.

  -- Nautilus will say that it cannot copy the file because the
  destination is read ony --

  If you try the copy the same file with the terminal you will see that
  the file is copied without problem, other programs like gedit or
  LibreOffice can write in the usb stick drive just fine.

  It is not a problem with the USB stick, as shown here:

  [ 6232.288064] usb 2-1: new high-speed USB device number 6 using ehci_hcd
  [ 6232.426378] scsi8 : usb-storage 2-1:1.0
  [ 6233.468489] scsi 8:0:0:0: Direct-Access Kingston DT 101 IIPMAP 
PQ: 0 ANSI: 0 CCS
  [ 6233.469862] sd 8:0:0:0: Attached scsi generic sg2 type 0
  [ 6234.178262] sd 8:0:0:0: [sdb] 3909632 512-byte logical blocks: (2.00 
GB/1.86 GiB)
  [ 6234.178735] sd 8:0:0:0: [sdb] Write Protect is off
  [ 6234.178740] sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00
  [ 6234.179251] sd 8:0:0:0: [sdb] No Caching mode page present
  [ 6234.179256] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6234.183369] sd 8:0:0:0: [sdb] No Caching mode page present
  [ 6234.183376] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6234.210138]  sdb: sdb1
  [ 6234.212732] sd 8:0:0:0: [sdb] No Caching mode page present
  [ 6234.212736] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6234.212740] sd 8:0:0:0: [sdb] Attached SCSI removable disk

  The permisions on the removable drive are set correctly:

  sergio@shana:/media$ ls -lah
  total 12K
  drwxr-xr-x  3 root   root   4,0K jul  5 10:20 .
  drwxr-xr-x 23 root   root   4,0K jul  3 11:01 ..
  drwx--  5 sergio sergio 4,0K dic 31  1969 DESIGNPLUS

  There is enough free space in the drive:

  sergio@shana:/media/DESIGNPLUS$ df -h
  S.ficheros Tamaño Usado  Disp Uso% Montado en
  /dev/sda2 50G  5,5G   42G  12% /
  udev 1,5G  4,0K  1,5G   1% /dev
  tmpfs579M  872K  579M   1% /run
  none 5,0M 0  5,0M   0% /run/lock
  none 1,5G  1,1M  1,5G   1% /run/shm
  /dev/sda1497M  113M  360M  24% /boot
  /dev/sda5245G  111G  122G  48% /home
  /dev/sdb11,9G  681M  1,2G  36% /media/DESIGNPLUS

  A file can be copied to the USB stick using the cp command for
  example.

  sergio@shana:~/Trash$ cp wireless.txt /media/DESIGNPLUS
  sergio@shana:~/Trash$ cd /media/DESIGNPLUS
  sergio@shana:/media/DESIGNPLUS$ ls -lah
  total 204K
  drwx-- 5 sergio sergio 4,0K jul  5 10:38 .
  drwxr-xr-x 3 root   root   4,0K jul  5 10:20 ..
  -rw-r--r-- 1 sergio sergio 117K jul  5 10:14 ._Screen Shot 2012-06-30 at 
8.50.37 AM.png
  -rw-r--r-- 1 sergio sergio  55K jun 30 08:51 Screen Shot 2012-06-30 at 
8.50.37 AM.png
  drwx-- 4 sergio sergio 4,0K jul  5 10:05 .Spotlight-V100
  drwx-- 2 sergio sergio 4,0K jul  5 10:05 .Trashes
  -rw-r--r-- 1 sergio sergio 4,0K jul  5 10:05 ._.Trashes
  -rw-r--r-- 1 sergio sergio   73 jul  5 10:38 wireless.txt

  But nautilus just dennies to copy the file claming that the
  destination is read only, when it is not.

  I tested it with two different USB sticks in two different computers
  running Ubuntu 12.04 and the same result.

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

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

[Desktop-packages] [Bug 572074] Re: New tabs open to the right of all existing tabs instead of opening next to the current tab

[Bug Watch Updater]

** Changed in: firefox
   Status: Confirmed => In Progress

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

Title:
  New tabs open to the right of all existing tabs instead of opening
  next to the current tab

Status in Mozilla Firefox:
  In Progress
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: firefox

  As the summary says: when a user opens a new, empty tab, it opens next
  to the rightmost of tabs currently open in the browser. This is
  inconsistent with the way links in new tabs are opened, which is to
  have them next to the currently active tab.

  Steps to reproduce:
  1. Open multiple tabs in the browser.
  2. Select the leftmost tab.
  3. Press Ctrl + T.

  Expected result:
  Have a new, empty tab next to the leftmost tab.

  Actual result:
  The new, empty tab opens next to the rightmost tab.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: firefox 3.6.3+nobinonly-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic x86_64
  Architecture: amd64
  CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Fri Apr 30 09:19:58 2010
  EcryptfsInUse: Yes
  FirefoxPackages:
   firefox 3.6.3+nobinonly-0ubuntu4
   firefox-gnome-support 3.6.3+nobinonly-0ubuntu4
   firefox-branding 3.6.3+nobinonly-0ubuntu4
   abroswer N/A
   abrowser-branding N/A
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  ProcEnviron:
   PATH=(custom, user)
   LANG=fi_FI.utf8
   SHELL=/bin/bash
  SourcePackage: firefox

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

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

[Desktop-packages] [Bug 1570318] Re: Bad wording in string

[Launchpad Bug Tracker]

This bug was fixed in the package onboard - 1.3.0-0ubuntu1

---
onboard (1.3.0-0ubuntu1) yakkety; urgency=medium

  * Request for sponsorship for new upstream release (LP: #1613063)
  * debian/control:
  - Bump Standards-Version to 3.9.8
  - Add libwayland-dev to Build-Depends
  - Add libxkbcommon-dev to Build-Depends
  * debian/copyright: update
  * debian/onboard.install: add usr/share/dbus-1/services entry
  * debian/patches:
- Drop bzr_fix_untranslatable_buttons.patch: applied upstream
- Drop fix_arrows_on_compact_layout.patch: applied upstream
- Refresh add_defaults_for_ubuntu.patch
  * debian/source.lintian-overrides: update entries line number
  * Status icon:
- Move AppIndicator and GtkStatusIcon into separate backends
- Allow left-clicking AppIndicator in KDE Plasma
- Don't crash when Appindicator or Atspi are not available
- Fix fallback to GtkStatusIcon when Applndicator is not available
- Fix tooltip of status icon provider (LP: #1570318). Thanks Ubuntu-QC-1
  * Word suggestions and auto-correction:
- Add Esperanto language model
- Elipsize very large words and fix them being invisible
- Fix Compact layout not showing the "More suggestions" arrows
- Improve auto-correction of URLs and filenames in long texts
  * Virtkey:
- Improve search for available keysyms in X (LP:1562381)
- Move key mapping from X functions to Xkb
- Make Xkb-based mapping also work in Ubuntu-GNOME
- Add uinput backend to virtkey for initial support of non-X desktops
- Isolate X related parts of virtkey in preparation for non-X desktops
- Add initial Wayland support (blocker: gtk_window_set_accept_focus())
  * D-Bus service:
- Add support for properties via python decorator
- Setup D-Bus activation to simplify showing on hotkey press (LP: #1607235)
- Update D-Bus usage examples in README
  * Add fallback to default system font family for themes:
- High contrast themes get a font this way
- Fixes Ubuntu logo not appearing in yakkety
  * Add aspect ratio limits when the keyboard is docked or expanded (LP:1586493)
  * Add touch handle to adjust the docking aspect ratio limit
  * Expand docked keyboard on landscape oriented screens by default
  * Auto-detect default status-icon provider in major desktop environments
  * Improve alignment of some labels in the Preferences dialog
  * Fix former stock buttons in Preferences not being translated (LP: #1567301)
  * Add small bitmap icons to prevent aliasing issues (LP: #1552484)
  * Add more example keys to onboard-defaults.conf.example (LP: #1546654)
  * Improve pep8 compliance of various source files
  * Don't let the return key leave the screen for Small and Phone layouts
  * Prevent setting new home position after accidental resize frame clicks
  * Work around shadows becoming visible during resize when docked with sidebars
  * Fix errors uncovered in Keyboard.py by flake8
  * Fix unwanted key-repeats when typing into Gtk-3 applications (LP: #1562381)
  * Fix keyboard sometimes starting up at unexpected positions on system start
  * Fix build failure with gcc-6 that switched to C++14. Thanks Jeremy Bicha
  * Fix warning when building with gcc versions before 6, i.e. C++98 by default
  * Remove entries with default values from desktop files. Thanks Mike Gabriel
  * Add 3.20 and 3.22 to shell-version field of GNOME extension. Thanks J. Bicha
  * Care for compatibility with Ubuntu Precise (12.04)
  * Update PPA link in README

 -- Francesco Fumanti   Sun, 13 Aug 2016
22:23:14 +0200

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

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

Title:
  Bad wording in string

Status in Onboard:
  Fix Committed
Status in onboard package in Ubuntu:
  Fix Released

Bug description:
  The string "AppIndicater (default) is recommend for broadest compatibility. 
GtkStatusIcon isn't supported well anymore by various desktop environments, but 
allows to show Onboard on left click. Requires restart.
  " needs to be corrected.
  Should read "AppIndicator (default) is recommended for broadest 
compatibility. GtkStatusIcon isn't supported well anymore by various desktop 
environments, but allows to show Onboard on left click. Requires restart."

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

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

[Desktop-packages] [Bug 1613781] [NEW] Mouse (tracker) way too fast

[Marco Ceresa]

Public bug reported:

After upgrading from 14.04 to 16.04 on a Lenovo x230, the mouse pointer
speed is way too high even if set at minimum. It's so bad it's almost
unusable.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
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: Tue Aug 16 17:59:43 2016
DistUpgraded: 2016-08-16 17:52:45,075 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.24, 3.13.0-93-generic, x86_64: installed
 virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa]
InstallationDate: Installed on 2014-07-11 (767 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: LENOVO 2325D93
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to xenial on 2016-08-16 (0 days ago)
dmi.bios.date: 04/30/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ET94WW (2.54 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2325D93
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: 10623
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET94WW(2.54):bd04/30/2013:svnLENOVO:pn2325D93:pvrThinkPadX230:rvnLENOVO:rn2325D93:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2325D93
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Aug 16 17:53:58 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 931 
 vendor LGD
xserver.version: 2:1.18.3-1ubuntu2.3

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

** Attachment removed: "BootLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1613781/+attachment/4722085/+files/BootLog.txt

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1613781/+attachment/4722086/+files/CurrentDmesg.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1613781/+attachment/4722087/+files/Dependencies.txt

** Attachment removed: "MonitorsUser.xml.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1613781/+attachment/4722092/+files/MonitorsUser.xml.txt

** Attachment removed: "DpkgLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1613781/+attachment/4722088/+files/DpkgLog.txt

** Attachment removed: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1613781/+attachment/4722093/+files/ProcCpuinfo.txt

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1613781/+attachment/4722089/+files/JournalErrors.txt

** Attachment removed: "Lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1613781/+attachment/4722090/+files/Lspci.txt

** Attachment removed: "Lsusb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1613781/+attachment/4722091/+files/Lsusb.txt

** Attachment removed: "UnitySupportTest.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1613781/+attachment/4722098/+files/UnitySupportTest.txt

** Attachment removed: "ProcEnviron.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1613781/+attachment/4722094/+files/ProcEnviron.txt

** Attachment removed: "xdpyinfo.txt"
   

[Desktop-packages] [Bug 1598316] Re: gtk2-engines-murrine desktop text shadow problem

[Jeremy Bicha]

@flocculant, had this bug been noticed before the SRU went out
everywhere, it wouldn't have been released. I feel I was fairly
proactive on this issue (I don't even use Xfce) pinging the original
commit writer and the Debian maintainer and pushing a bit on some theme
developers. And I release-noted the issue. I thought Xubuntu was aware
of the issue but maybe I should have made sure of that.

At this point, the bug is "fixed" in yakkety in that the only distro
theme I am aware of that is still affected is arc-theme (I just have to
ping the maintainer of the arc-theme to backport the upstream commit,
but arc-theme isn't packaged in Xenial.)

For Xenial, we can just backport the numix-gtk-theme patch to the
shimmer-themes package and then this bug is fixed for all distro themes
I believe. That is on my to-do list unless someone gets to it sooner. It
took me longer than I expected to get numix-gtk-theme repackaged in
Yakkety.

If you still think the murrine bugfix to be reverted, you can go ahead.
It might not be necessary now though...

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

Title:
  gtk2-engines-murrine desktop text shadow problem

Status in Arc Theme:
  New
Status in Numix GTK theme:
  Fix Released
Status in arc-theme package in Ubuntu:
  Triaged
Status in gtk2-engines-murrine package in Ubuntu:
  Triaged
Status in shimmer-themes package in Ubuntu:
  Invalid
Status in xfdesktop4 package in Ubuntu:
  Confirmed
Status in gtk2-engines-murrine package in Debian:
  New

Bug description:
  Upgraded my xubuntu 16.04 system on 01 Jul 2016.  The apt update
  included an upgrade to gtk2-engines-murrine.  However, after the
  upgrade and boot, the any desktop text, folder, launcher, etc. had a
  problem with the text and shadow being quite far apart.

  This bug affects themes that use the textstyle feature of the murrine
  engine on xfdesktop4. Ubuntu MATE 16.04, which also uses gtk2 but has
  caja draw the desktop icons instead of xfdesktop, is not affected.

  The only known affected theme packaged in Xubuntu 16.04 is numix-gtk-
  theme. Third-party affected themes include Arc and Vertex.

To manage notifications about this bug go to:
https://bugs.launchpad.net/arc-theme/+bug/1598316/+subscriptions

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

[Desktop-packages] [Bug 1604421] Re: Unity 8 fails to start on staging (xenial) on the phone when --wipe is used for flashing

[Michał Sawicz]

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

** Also affects: gsettings-ubuntu-touch-schemas (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Unity 8 fails to start on staging (xenial) on the phone when --wipe is
  used for flashing

Status in Canonical System Image:
  Confirmed
Status in glib2.0 package in Ubuntu:
  New
Status in gsettings-ubuntu-touch-schemas package in Ubuntu:
  New
Status in unity package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Update: this only happens when --wipe (or --bootstrap) is used for
  flashing. It is possible to get functional xenial/staging running by
  doing non-destructive flash update from rc-proposed.

  Unity 8 fails to start on staging (=xenial + xenial-overlay) on my
  krillin.

  unity-system-compositor.log: http://paste.ubuntu.com/20035267/ - shows
  Opening/Closing/Opening/Closing when starting unity8.

  unity8.log attached.

  Using ubuntu-touch/staging/bq-aquaris.en channel on krillin.
  version_detail:
  ubuntu=20160719,device=20160606-ab415b2,custom=20160701-981-38-14,version=49

  Crash file at http://people.ubuntu.com/~timo-
  jyrinki/unity8/_usr_bin_unity8.32011.crash

  Xenial can be flashed on the phone with eg:
  ubuntu-device-flash touch --channel=ubuntu-touch/staging/ubuntu 
--developer-mode --password= --wipe --boostrap
  (ubuntu channel)
  ubuntu-device-flash touch --channel=ubuntu-touch/staging/bq-aquaris.en 
--developer-mode --password= --wipe --recovery-image recovery-krillin.img
  (Bq channel)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604421/+subscriptions

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

[Desktop-packages] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics

[Rudi Servo]

Works on Lenovo T450 i5-5300U

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

Title:
  Mouse cursor lost when unlocking with Intel graphics

Status in elementary OS:
  Fix Released
Status in xf86-video-intel:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-intel package in Debian:
  Fix Released

Bug description:
  [Impact]
  Mouse cursor is no longer visible after VT-switch for systems with Intel 
graphics.

  Switching VTs again may cause the cursor to become visible again.
  - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7)

  This is often observed in systems that lock the session and return to
  the greeter (including at least Xubuntu, Ubuntu Mate, and elementary
  OS).

  [Test Case]
  (Requires a lightdm-based screen locking solution)
  1. Start a new session.
  2. Lock your screen.
  2a. You are redirected to the lightdm greeter.
  3. Login/Unlock your session.
  4. Cursor is no longer visible.

  [Regression Potential]
  remains to be seen

  ===

  [Original Report]
  Cursor is visible at unlock screen either after returning from suspend or 
just locking.

  After unlocking screen cursor is invisible.

  Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor
  returns

  

  no matter if you suspend or sleep, to swap or disk when you return
  from it, the mouse cursor is missing.you can still move the mouse
  and you can see (because it highlights the window) as you move it
  around.   But the cursor is not displayed on the screen.

  i am using a lenovo W540 laptop.   I downloaded the latest beta on
  april 8 2016.

  this is xubuntu using the xfce window manager.

  the cursor does return if i log off and log back in, but that actually 
defeats the purpose of going to sleep.
  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-08 (2 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)

[Launchpad Bug Tracker]

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

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

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

Title:
  No sound notification for new SMS (Ubuntu Touch)

Status in Canonical System Image:
  In Progress
Status in indicator-sound package in Ubuntu:
  Confirmed
Status in media-hub package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  I noticed for last 2-3 days there is no sound notification for a new
  SMS, but there's a blinking green LED notification. Also in the
  indicator menu the envelope icon turns green and the new SMS is listed
  as usual. Things are working alright for Telegram, Gmail etc.
  (sound+LED+indicator menu).

  Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9)

  UPDATE: Screenshots get silent too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+subscriptions

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

[Desktop-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)

[Launchpad Bug Tracker]

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

** Changed in: indicator-sound (Ubuntu)
   Status: New => Confirmed

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

Title:
  No sound notification for new SMS (Ubuntu Touch)

Status in Canonical System Image:
  In Progress
Status in indicator-sound package in Ubuntu:
  Confirmed
Status in media-hub package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  I noticed for last 2-3 days there is no sound notification for a new
  SMS, but there's a blinking green LED notification. Also in the
  indicator menu the envelope icon turns green and the new SMS is listed
  as usual. Things are working alright for Telegram, Gmail etc.
  (sound+LED+indicator menu).

  Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9)

  UPDATE: Screenshots get silent too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+subscriptions

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

[Desktop-packages] [Bug 1604421] Re: Unity 8 fails to start on staging (xenial) on the phone when --wipe is used for flashing

[Łukasz Zemczak]

Commitlog for 41 if needed.

** Attachment added: "41.commitlog"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1604421/+attachment/4722067/+files/41.commitlog

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

Title:
  Unity 8 fails to start on staging (xenial) on the phone when --wipe is
  used for flashing

Status in Canonical System Image:
  Confirmed
Status in glib2.0 package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Update: this only happens when --wipe (or --bootstrap) is used for
  flashing. It is possible to get functional xenial/staging running by
  doing non-destructive flash update from rc-proposed.

  Unity 8 fails to start on staging (=xenial + xenial-overlay) on my
  krillin.

  unity-system-compositor.log: http://paste.ubuntu.com/20035267/ - shows
  Opening/Closing/Opening/Closing when starting unity8.

  unity8.log attached.

  Using ubuntu-touch/staging/bq-aquaris.en channel on krillin.
  version_detail:
  ubuntu=20160719,device=20160606-ab415b2,custom=20160701-981-38-14,version=49

  Crash file at http://people.ubuntu.com/~timo-
  jyrinki/unity8/_usr_bin_unity8.32011.crash

  Xenial can be flashed on the phone with eg:
  ubuntu-device-flash touch --channel=ubuntu-touch/staging/ubuntu 
--developer-mode --password= --wipe --boostrap
  (ubuntu channel)
  ubuntu-device-flash touch --channel=ubuntu-touch/staging/bq-aquaris.en 
--developer-mode --password= --wipe --recovery-image recovery-krillin.img
  (Bq channel)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604421/+subscriptions

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

[Desktop-packages] [Bug 1613557] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Paul White]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1514474, so it is being marked as such.

Please look at the other bug report to see if there is any missing
information that you can provide, or to see if there is a workaround for
the bug. Additionally, any further discussion regarding the bug should
occur in the other report. Feel free to continue to report any other
bugs you may find.

** This bug has been marked a duplicate of bug 1514474
   package tex-common 6.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  Just happened when I elected to install the latest update when
  prompted by update manager.  I seem to have had intermittent problems
  with update manager ever since upgrading to 16.04 - possibly all
  related to this.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Aug 16 07:03:55 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2012-04-18 (1580 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120417)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-05 (10 days ago)

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

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

[Desktop-packages] [Bug 1613774] [NEW] ubuntu-bug xorg /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without specifying a version first. Use gi.require_version('Wnck', '3.0') before

[Matt]

Public bug reported:

$ $ ubuntu-bug xorg
dash: 1: $: not found
$ ^C   
$ $ ubuntu-bug xorg^C
$ $ ubuntu-bug xorg
dash: 2: $: not found
$ ubuntu-bug xorg
/usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without 
specifying a version first. Use gi.require_version('Wnck', '3.0') before import 
to ensure that the right version gets loaded.
  from gi.repository import GLib, Wnck, GdkX11, Gdk
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
cat: /var/log/lightdm/x-0-greeter.log: No such file or directory
cat: /var/log/lightdm/x-0-greeter.log.old: No such file or directory
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
$ ubuntu-bug xorg
/usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without 
specifying a version first. Use gi.require_version('Wnck', '3.0') before import 
to ensure that the right version gets loaded.
  from gi.repository import GLib, Wnck, GdkX11, Gdk
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
cat: /var/log/lightdm/x-0-greeter.log.old: No such file or directory
cat: /var/log/lightdm/x-0-greeter.log: No such file or directory
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
Specifying boot ID has no effect, no persistent journal was found
Specifying boot ID has no effect, no persistent journal was found
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
$ Created new window in existing browser session.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
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: Tue Aug 16 08:39:05 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:80e6]
   Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80e6]
InstallationDate: Installed on 2016-07-30 (16 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: HP HP ENVY m7 Notebook
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/04/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.35
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 80E6
dmi.board.vendor: HP
dmi.board.version: 87.60
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd03/04/2016:svnHP:pnHPENVYm7Notebook:pvrType1ProductConfigId:rvnHP:rn80E6:rvr87.60:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP ENVY m7 Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Aug 16 05:18:40 2016
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2.3

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is 

[Desktop-packages] [Bug 1514474] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Larry Kovnat]

Worked for me as well - thanks!

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  Confirmed

Bug description:
  dist-upgrade from wily to xenial

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu4
  Architecture: amd64
  Date: Mon Nov  9 09:56:09 2015
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2011-07-12 (1580 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.3ubuntu1
   apt  1.0.10.2ubuntu1
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2011-12-23 (1416 days ago)

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

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

[Desktop-packages] [Bug 1604421] Re: Unity 8 fails to start on staging (xenial) on the phone when --wipe is used for flashing

[Michał Sawicz]

Confirmed, something on vivid makes the schemas work, if you wipe or
bootstrap, glib can't find them.

glib-compile-schemas doesn't help, something else must be different
between a vivid upgrade and fresh xenial.

** Also affects: glib2.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Unity 8 fails to start on staging (xenial) on the phone when --wipe is
  used for flashing

Status in Canonical System Image:
  Confirmed
Status in glib2.0 package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Update: this only happens when --wipe (or --bootstrap) is used for
  flashing. It is possible to get functional xenial/staging running by
  doing non-destructive flash update from rc-proposed.

  Unity 8 fails to start on staging (=xenial + xenial-overlay) on my
  krillin.

  unity-system-compositor.log: http://paste.ubuntu.com/20035267/ - shows
  Opening/Closing/Opening/Closing when starting unity8.

  unity8.log attached.

  Using ubuntu-touch/staging/bq-aquaris.en channel on krillin.
  version_detail:
  ubuntu=20160719,device=20160606-ab415b2,custom=20160701-981-38-14,version=49

  Crash file at http://people.ubuntu.com/~timo-
  jyrinki/unity8/_usr_bin_unity8.32011.crash

  Xenial can be flashed on the phone with eg:
  ubuntu-device-flash touch --channel=ubuntu-touch/staging/ubuntu 
--developer-mode --password= --wipe --boostrap
  (ubuntu channel)
  ubuntu-device-flash touch --channel=ubuntu-touch/staging/bq-aquaris.en 
--developer-mode --password= --wipe --recovery-image recovery-krillin.img
  (Bq channel)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604421/+subscriptions

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

[Desktop-packages] [Bug 1612554] Re: duplicity backup fails with OverflowError: size does not fit in an int

[Peter Van Rompaey]

Some more testing:

I installed a virtualenv with python 2.7.12 and duplicity 0.7.09, but
the problem still remains.

Then I ran the little test mentioned in
https://bugs.python.org/issue27130 which shows that zlib has a problem
zipping files > 4Gb:

When looking at the timestamps of the comments, it seems this issue was
fixed after 2.7.12 came out, so it will probably be in the next release.

I am currently running a backup with all files >4Gb excluded to see if
that completes OK.


---

$ python --version
Python 2.7.6

$ python -c "import zlib;zlib.crc32('a'*(1<<31 - 1))"

$ python -c "import zlib;zlib.crc32('a'*(1<<31))"
Traceback (most recent call last):
  File "", line 1, in 
OverflowError: size does not fit in an int

---

$ . venv.2.7.12/bin/activate

(venv.2.7.12) $ python --version
Python 2.7.12

(venv.2.7.12) $ python -c "import zlib;zlib.crc32('a'*(1<<31 - 1))"

(venv.2.7.12) $ python -c "import zlib;zlib.crc32('a'*(1<<31))"
Traceback (most recent call last):
  File "", line 1, in 
OverflowError: size does not fit in an int


** Bug watch added: Python Roundup #27130
   http://bugs.python.org/issue27130

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

Title:
  duplicity backup fails with OverflowError: size does not fit in an int

Status in Duplicity:
  New
Status in duplicity package in Ubuntu:
  New

Bug description:
  Ubuntu 14.04.4 LTS
  duplicity 0.6.23-1ubuntu4.1
  python2.7 2.7.6-8ubuntu0.2

  Backup command used:
  duplicity --exclude-filelist "/root/.duplicity_excludes" --full-if-older-than 
7D --log-file "/var/log/duplicity" --no-encryption --volsize 100 / "$S3BUCKET"

  Backups have been running fine for several months, but since last
  night it started giving following error:

  ---

  Reading filelist /root/.duplicity_excludes

  Sorting filelist /root/.duplicity_excludes

  Local and Remote metadata are synchronized, no sync needed.

  Last full backup date: Sun Aug  7 23:30:02 2016

  Traceback (most recent call last):

File "/usr/bin/duplicity", line 1494, in 

  with_tempdir(main)

File "/usr/bin/duplicity", line 1488, in with_tempdir

  fn()

File "/usr/bin/duplicity", line 1337, in main

  do_backup(action)

File "/usr/bin/duplicity", line 1470, in do_backup

  incremental_backup(sig_chain)

File "/usr/bin/duplicity", line 637, in incremental_backup

  globals.backend)

File "/usr/bin/duplicity", line 405, in write_multivol

  at_end = gpg.GzipWriteFile(tarblock_iter, tdp.name,
  globals.volsize)

File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 383,
  in GzipWriteFile

  new_block = block_iter.next()

File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line
  518, in next

  result = self.process(self.input_iter.next())

File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line
  213, in get_delta_iter

  (new_path, sig_path, sigTarFile))

File "/usr/lib/python2.7/dist-packages/duplicity/robust.py", line
  37, in check_common_error

  return function(*args)

File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line
  134, in get_delta_path

  delta_path.setfileobj(librsync.DeltaFile(old_sigfp, newfp))

File "/usr/lib/python2.7/dist-packages/duplicity/librsync.py", line
  150, in __init__

  self.maker = _librsync.new_deltamaker(sig_string)

  OverflowError: size does not fit in an int

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

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

[Desktop-packages] [Bug 1581229] Re: "Started" column not displayed for processes when column is enabled in settings

[Nikita Yerenkov-Scott]

** Changed in: gnome-system-monitor (Ubuntu)
 Assignee: (unassigned) => Nikita Yerenkov-Scott (yerenkov-scott)

** Changed in: ubuntu-gnome
 Assignee: (unassigned) => Nikita Yerenkov-Scott (yerenkov-scott)

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

Title:
  "Started" column not displayed for processes when column is enabled in
  settings

Status in Gnome System Monitor:
  Fix Released
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-system-monitor package in Ubuntu:
  Fix Committed

Bug description:
  I have recently noticed that in the gnome-system-monitor if I go into
  the settings and tick the box for "Started" in the "Information
  fields" section of that the "Processes" tab that the "Started" column
  is not added and in fact this information is not seemingly displayed
  anywhere except for in the "Properties" window for a process. But it
  would be really useful if it did actually appear as a column so that
  you could easily view the start times for multiple processes at the
  same time and to also sort them in terms of that. I am running Ubuntu
  GNOME 15.10 with GNOME 3.18 but I have also experienced the behaviour
  on Ubuntu GNOME 16.04 with GNOME 3.20, in fact when running it on that
  system through Terminal this was the output (the exact moment I
  checked the "Started" box in the settings to add that column I got the
  first bit of output and then very quickly the other output followed):

  (gnome-system-monitor:2252): GLib-CRITICAL **: Source ID 73 was not found 
when attempting to remove it
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width 

[Desktop-packages] [Bug 1598316] Re: gtk2-engines-murrine desktop text shadow problem

[flocculant]

It's hard enough for a flavour to get testing while a development
version is running - changing things and breaking them when we have
tested isn't very fair socially ...

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

Title:
  gtk2-engines-murrine desktop text shadow problem

Status in Arc Theme:
  New
Status in Numix GTK theme:
  Fix Released
Status in arc-theme package in Ubuntu:
  Triaged
Status in gtk2-engines-murrine package in Ubuntu:
  Triaged
Status in shimmer-themes package in Ubuntu:
  Invalid
Status in xfdesktop4 package in Ubuntu:
  Confirmed
Status in gtk2-engines-murrine package in Debian:
  New

Bug description:
  Upgraded my xubuntu 16.04 system on 01 Jul 2016.  The apt update
  included an upgrade to gtk2-engines-murrine.  However, after the
  upgrade and boot, the any desktop text, folder, launcher, etc. had a
  problem with the text and shadow being quite far apart.

  This bug affects themes that use the textstyle feature of the murrine
  engine on xfdesktop4. Ubuntu MATE 16.04, which also uses gtk2 but has
  caja draw the desktop icons instead of xfdesktop, is not affected.

  The only known affected theme packaged in Xubuntu 16.04 is numix-gtk-
  theme. Third-party affected themes include Arc and Vertex.

To manage notifications about this bug go to:
https://bugs.launchpad.net/arc-theme/+bug/1598316/+subscriptions

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

[Desktop-packages] [Bug 1598316] Re: gtk2-engines-murrine desktop text shadow problem

[flocculant]

@~jbicha

This might be a bit obvious - but why are we not reverting to the
package that doesn't cause the issue?

In addition - why did this package land anyway?

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

Title:
  gtk2-engines-murrine desktop text shadow problem

Status in Arc Theme:
  New
Status in Numix GTK theme:
  Fix Released
Status in arc-theme package in Ubuntu:
  Triaged
Status in gtk2-engines-murrine package in Ubuntu:
  Triaged
Status in shimmer-themes package in Ubuntu:
  Invalid
Status in xfdesktop4 package in Ubuntu:
  Confirmed
Status in gtk2-engines-murrine package in Debian:
  New

Bug description:
  Upgraded my xubuntu 16.04 system on 01 Jul 2016.  The apt update
  included an upgrade to gtk2-engines-murrine.  However, after the
  upgrade and boot, the any desktop text, folder, launcher, etc. had a
  problem with the text and shadow being quite far apart.

  This bug affects themes that use the textstyle feature of the murrine
  engine on xfdesktop4. Ubuntu MATE 16.04, which also uses gtk2 but has
  caja draw the desktop icons instead of xfdesktop, is not affected.

  The only known affected theme packaged in Xubuntu 16.04 is numix-gtk-
  theme. Third-party affected themes include Arc and Vertex.

To manage notifications about this bug go to:
https://bugs.launchpad.net/arc-theme/+bug/1598316/+subscriptions

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

[Desktop-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)

[Alfonso Sanchez-Beato]

I have tested the screenshot case in turbo, where I heard no sound, and
in frieza, where sound is working (see attached logs). In turbo I saw in
unity8.log:

[2016-08-16:15:21:08.524] [PERFORMANCE]: Last frame took 32 ms to render.
[2016-08-16:15:21:09.087] virtual void AalMediaPlayerControl::stop() 
...
[2016-08-16:15:21:09.090] virtual void AalMediaPlayerControl::play() 
[2016-08-16:15:21:09.091] void AalMediaPlayerService::play()
...
[2016-08-16:15:21:09.689] qml: ItemGrabber: Saving image to 
/home/phablet/Pictures/Screenshots/screenshot20160816_152109689.png


While in frieza we have:


[2016-08-16:15:46:01.447] virtual void AalMediaPlayerControl::play() 
[2016-08-16:15:46:01.447] void AalMediaPlayerService::play()
[2016-08-16:15:46:01.450] Actually calling m_hubPlayerSession->play()
...
[2016-08-16:15:46:02.102] virtual void AalMediaPlayerControl::stop() 
...
[2016-08-16:15:46:02.378] qml: ItemGrabber: Saving image to 
/home/phablet/Pictures/Screenshots/screenshot20160816_154602378.png


It seems that unity8 is doing something weird here, as it is stopping audio 
before it has called the "play" method in turbo. Looking at media-hub log, the 
stop command is received, but there is no play command.

** Attachment added: "screenshot-sound.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/1544477/+attachment/4722033/+files/screenshot-sound.tar.gz

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

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

Title:
  No sound notification for new SMS (Ubuntu Touch)

Status in Canonical System Image:
  In Progress
Status in indicator-sound package in Ubuntu:
  New
Status in media-hub package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  New

Bug description:
  I noticed for last 2-3 days there is no sound notification for a new
  SMS, but there's a blinking green LED notification. Also in the
  indicator menu the envelope icon turns green and the new SMS is listed
  as usual. Things are working alright for Telegram, Gmail etc.
  (sound+LED+indicator menu).

  Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9)

  UPDATE: Screenshots get silent too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+subscriptions

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

[Desktop-packages] [Bug 1613763] Re: package liba11y-profile-manager-data 0.1.10-0ubuntu3 failed to install/upgrade: trying to overwrite '/usr/share/a11y-profile-manager/profiles/blindness/profile.man

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package liba11y-profile-manager-data 0.1.10-0ubuntu3 failed to
  install/upgrade: trying to overwrite '/usr/share/a11y-profile-
  manager/profiles/blindness/profile.manifest', which is also in package
  unity-accessibility-profiles 0.1.10-0ubuntu3

Status in a11y-profile-manager package in Ubuntu:
  New

Bug description:
  software updater crashed while updating   --please fix

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: liba11y-profile-manager-data 0.1.10-0ubuntu3
  ProcVersionSignature: Ubuntu 4.6.0-10.12-generic 4.6.5
  Uname: Linux 4.6.0-10-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 16 09:53:35 2016
  DuplicateSignature:
   package:liba11y-profile-manager-data:0.1.10-0ubuntu3
   Unpacking liba11y-profile-manager-data (0.1.11-0ubuntu1) over 
(0.1.10-0ubuntu3) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-QPwYOH/12-liba11y-profile-manager-data_0.1.11-0ubuntu1_all.deb
 (--unpack):
trying to overwrite 
'/usr/share/a11y-profile-manager/profiles/blindness/profile.manifest', which is 
also in package unity-accessibility-profiles 0.1.10-0ubuntu3
  ErrorMessage: trying to overwrite 
'/usr/share/a11y-profile-manager/profiles/blindness/profile.manifest', which is 
also in package unity-accessibility-profiles 0.1.10-0ubuntu3
  InstallationDate: Installed on 2016-06-11 (65 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160515)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc1ubuntu2
  SourcePackage: a11y-profile-manager
  Title: package liba11y-profile-manager-data 0.1.10-0ubuntu3 failed to 
install/upgrade: trying to overwrite 
'/usr/share/a11y-profile-manager/profiles/blindness/profile.manifest', which is 
also in package unity-accessibility-profiles 0.1.10-0ubuntu3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1613430] Re: lightdm not showing gnome desktop option

[Gunnar Hjalmarsson]

Thanks! The latter seems to be useful info for some experienced
developer (i.e. not me). I have one more suggestion, though, before
someone else looks at it:

When having selected GNOME on the login screen, try to enter a guest
session instead of your regular account, and let us know if that
succeeds.

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

Title:
  lightdm not showing gnome desktop option

Status in lightdm package in Ubuntu:
  New

Bug description:
  I installed ubuntu-gnome-desktop and selected lightdm as the display
  manager (tried gdm and received only a purple screen).  When I click
  on the ubuntu logo to the right of my login (where I believe I should
  be able to select the desktop I would like to use) the login name(s)
  disappear and nothing happens until I hit enter at which point the
  login names reappear

  I have tried logging out and back in again as well as rebooting with the same 
results.  I am currently on a Dell XPS 13 Developer Edition (Ubuntu laptop).  I 
am able to log into Unity with no problem but I would like to use Gnome.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-07-26 (19 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  Package: lightdm 1.18.2-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Tags: xenial third-party-packages
  Uname: Linux 4.4.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1613763] [NEW] package liba11y-profile-manager-data 0.1.10-0ubuntu3 failed to install/upgrade: trying to overwrite '/usr/share/a11y-profile-manager/profiles/blindness/profile.m

[Ubert Lankin]

Public bug reported:

software updater crashed while updating   --please fix

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: liba11y-profile-manager-data 0.1.10-0ubuntu3
ProcVersionSignature: Ubuntu 4.6.0-10.12-generic 4.6.5
Uname: Linux 4.6.0-10-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Tue Aug 16 09:53:35 2016
DuplicateSignature:
 package:liba11y-profile-manager-data:0.1.10-0ubuntu3
 Unpacking liba11y-profile-manager-data (0.1.11-0ubuntu1) over 
(0.1.10-0ubuntu3) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-QPwYOH/12-liba11y-profile-manager-data_0.1.11-0ubuntu1_all.deb
 (--unpack):
  trying to overwrite 
'/usr/share/a11y-profile-manager/profiles/blindness/profile.manifest', which is 
also in package unity-accessibility-profiles 0.1.10-0ubuntu3
ErrorMessage: trying to overwrite 
'/usr/share/a11y-profile-manager/profiles/blindness/profile.manifest', which is 
also in package unity-accessibility-profiles 0.1.10-0ubuntu3
InstallationDate: Installed on 2016-06-11 (65 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160515)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3~rc1ubuntu2
SourcePackage: a11y-profile-manager
Title: package liba11y-profile-manager-data 0.1.10-0ubuntu3 failed to 
install/upgrade: trying to overwrite 
'/usr/share/a11y-profile-manager/profiles/blindness/profile.manifest', which is 
also in package unity-accessibility-profiles 0.1.10-0ubuntu3
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check package-conflict yakkety

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

Title:
  package liba11y-profile-manager-data 0.1.10-0ubuntu3 failed to
  install/upgrade: trying to overwrite '/usr/share/a11y-profile-
  manager/profiles/blindness/profile.manifest', which is also in package
  unity-accessibility-profiles 0.1.10-0ubuntu3

Status in a11y-profile-manager package in Ubuntu:
  New

Bug description:
  software updater crashed while updating   --please fix

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: liba11y-profile-manager-data 0.1.10-0ubuntu3
  ProcVersionSignature: Ubuntu 4.6.0-10.12-generic 4.6.5
  Uname: Linux 4.6.0-10-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 16 09:53:35 2016
  DuplicateSignature:
   package:liba11y-profile-manager-data:0.1.10-0ubuntu3
   Unpacking liba11y-profile-manager-data (0.1.11-0ubuntu1) over 
(0.1.10-0ubuntu3) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-QPwYOH/12-liba11y-profile-manager-data_0.1.11-0ubuntu1_all.deb
 (--unpack):
trying to overwrite 
'/usr/share/a11y-profile-manager/profiles/blindness/profile.manifest', which is 
also in package unity-accessibility-profiles 0.1.10-0ubuntu3
  ErrorMessage: trying to overwrite 
'/usr/share/a11y-profile-manager/profiles/blindness/profile.manifest', which is 
also in package unity-accessibility-profiles 0.1.10-0ubuntu3
  InstallationDate: Installed on 2016-06-11 (65 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160515)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc1ubuntu2
  SourcePackage: a11y-profile-manager
  Title: package liba11y-profile-manager-data 0.1.10-0ubuntu3 failed to 
install/upgrade: trying to overwrite 
'/usr/share/a11y-profile-manager/profiles/blindness/profile.manifest', which is 
also in package unity-accessibility-profiles 0.1.10-0ubuntu3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1528735] Re: Suspend fails every second time on some laptops in UEFI mode

[Brad]

what log files could I supply that would help debugging this problem? Is
there some kinda tutorial on how to do this?

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

Title:
  Suspend fails every second time on some laptops in UEFI mode

Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of Xubuntu 14.04.3, replacing existing OEM Windows 10.
  Install detected UEFI, and installed in UEFI mode. (I have attempted
  to change to legacy boot, and got it to a state where it was booting
  without /sys/firmware/efi/ being present, but behaviour persisted.)

  Suspending the laptop, whether by closing the lid, choosing the
  suspend option from the menu, or directly typing "sudo pm-suspend"
  works perfectly well... once.

  The second attempt to suspend, whether immediately or hours later,
  suspends the laptop (I can see the screen turn off, and hear the disk
  and fans stop, but a moment later the screen shows bright yellow
  console text declaring "Warning!!! Boot script table modified!!!
  Please contact your vendor.", and then it hard reboots.

  This appears to be a weird interaction between suspend and UEFI
  protection, but others have reported that they have had working
  suspend when installed alone (and presumably in legacy from the
  start), but this behaviour appeared when reinstalled as dual-boot
  (when presumably UEFI would have had to be on).
  (http://askubuntu.com/questions/675683/suspend-does-not-work-more-
  than-once-after-reboot-ubuntu-15-04-dual-boot/712232 and earlier
  http://askubuntu.com/questions/651481/boot-script-table-modified-
  please-contact-vendor, from different people.)

  Beyond the investigations I have done, I know next to nothing about
  UEFI, or how Suspend might be interacting with it. Much less why it
  appears to work perfectly exactly once.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.1
  ProcVersionSignature: Ubuntu 4.2.0-22.27~14.04.1-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Dec 23 13:27:11 2015
  InstallationDate: Installed on 2015-12-19 (3 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1528735] Re: Suspend fails every second time on some laptops in UEFI mode

[Brad]

It's even worse with kernel 4.8-rc1. It now fails on first resume
attempt - shows screen with time and logo but no login prompt and
requires hard reboot.

System:Host: G50 Kernel: 4.8.0-040800rc1-generic x86_64 (64 bit gcc: 6.1.1)
   Desktop: MATE 1.14.1 (Gtk 3.18.9-1ubuntu3.1) Distro: Linux Mint 18 
Sarah
Machine:   System: LENOVO product: 80E3 v: Lenovo G50-45
   Mobo: LENOVO model: Lancer 5B2 v: 31900058 STD Bios: LENOVO v: 
A2CN38WW(V2.06) date: 07/15/2015
CPU:   Quad core AMD A6-6310 APU with AMD Radeon R4 Graphics (-MCP-) cache: 
8192 KB
   flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 
14372
   clock speeds: max: 1800 MHz 1: 1800 MHz 2: 1600 MHz 3: 1800 MHz 4: 
1800 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Mullins [Radeon R4/R5 
Graphics] bus-ID: 00:01.0
   Display Server: X.Org 1.18.3 drivers: ati,radeon (unloaded: 
fbdev,vesa) Resolution: 1366x768@59.99hz
   GLX Renderer: Gallium 0.4 on AMD MULLINS (DRM 2.46.0, LLVM 3.8.0)
   GLX Version: 3.0 Mesa 11.2.0 Direct Rendering: Yes

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

Title:
  Suspend fails every second time on some laptops in UEFI mode

Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of Xubuntu 14.04.3, replacing existing OEM Windows 10.
  Install detected UEFI, and installed in UEFI mode. (I have attempted
  to change to legacy boot, and got it to a state where it was booting
  without /sys/firmware/efi/ being present, but behaviour persisted.)

  Suspending the laptop, whether by closing the lid, choosing the
  suspend option from the menu, or directly typing "sudo pm-suspend"
  works perfectly well... once.

  The second attempt to suspend, whether immediately or hours later,
  suspends the laptop (I can see the screen turn off, and hear the disk
  and fans stop, but a moment later the screen shows bright yellow
  console text declaring "Warning!!! Boot script table modified!!!
  Please contact your vendor.", and then it hard reboots.

  This appears to be a weird interaction between suspend and UEFI
  protection, but others have reported that they have had working
  suspend when installed alone (and presumably in legacy from the
  start), but this behaviour appeared when reinstalled as dual-boot
  (when presumably UEFI would have had to be on).
  (http://askubuntu.com/questions/675683/suspend-does-not-work-more-
  than-once-after-reboot-ubuntu-15-04-dual-boot/712232 and earlier
  http://askubuntu.com/questions/651481/boot-script-table-modified-
  please-contact-vendor, from different people.)

  Beyond the investigations I have done, I know next to nothing about
  UEFI, or how Suspend might be interacting with it. Much less why it
  appears to work perfectly exactly once.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.1
  ProcVersionSignature: Ubuntu 4.2.0-22.27~14.04.1-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Dec 23 13:27:11 2015
  InstallationDate: Installed on 2015-12-19 (3 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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