date:20170904

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-zesty

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

Title:
  Developer name not shown for snaps

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  The snap developer is not shown in GNOME Software.

  [Test Case]
  1. Open GNOME Software
  2. Search for "Moon Buggy" and click on it

  Expected result:
  The developer name is shown as "dholbach"

  Observed result:
  The developer name is not shown anywhere.

  [Regression Potential]
  Low, as we just populate the "project group" (shows as developer) with the 
snap "developer" field.

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

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

[Desktop-packages] [Bug 1715054] Re: Developer name not shown for snaps

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-xenial

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

Title:
  Developer name not shown for snaps

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  The snap developer is not shown in GNOME Software.

  [Test Case]
  1. Open GNOME Software
  2. Search for "Moon Buggy" and click on it

  Expected result:
  The developer name is shown as "dholbach"

  Observed result:
  The developer name is not shown anywhere.

  [Regression Potential]
  Low, as we just populate the "project group" (shows as developer) with the 
snap "developer" field.

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

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

[Desktop-packages] [Bug 1715054] Re: Developer name not shown for snaps

2017-09-04 Thread Robert Ancell

GNOME Software 3.24 added an explicit "developer" field which we use in
artful.

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

Title:
  Developer name not shown for snaps

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  The snap developer is not shown in GNOME Software.

  [Test Case]
  1. Open GNOME Software
  2. Search for "Moon Buggy" and click on it

  Expected result:
  The developer name is shown as "dholbach"

  Observed result:
  The developer name is not shown anywhere.

  [Regression Potential]
  Low, as we just populate the "project group" (shows as developer) with the 
snap "developer" field.

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

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

[Desktop-packages] [Bug 1715054] [NEW] Developer name not shown for snaps

2017-09-04 Thread Robert Ancell

Public bug reported:

[Impact]
The snap developer is not shown in GNOME Software.

[Test Case]
1. Open GNOME Software
2. Search for "Moon Buggy" and click on it

Expected result:
The developer name is shown as "dholbach"

Observed result:
The developer name is not shown anywhere.

[Regression Potential]
Low, as we just populate the "project group" (shows as developer) with the snap 
"developer" field.

** Affects: gnome-software (Ubuntu)
 Importance: Medium
 Status: Fix Released

** Affects: gnome-software (Ubuntu Xenial)
 Importance: Medium
 Assignee: Robert Ancell (robert-ancell)
 Status: Fix Committed

** Affects: gnome-software (Ubuntu Zesty)
 Importance: Medium
 Assignee: Robert Ancell (robert-ancell)
 Status: Fix Committed

** Affects: gnome-software (Ubuntu Artful)
 Importance: Medium
 Status: Fix Released

** Also affects: gnome-software (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: gnome-software (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: gnome-software (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Changed in: gnome-software (Ubuntu Artful)
   Status: New => Fix Released

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

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

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

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

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

** Changed in: gnome-software (Ubuntu Zesty)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: gnome-software (Ubuntu Xenial)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  Developer name not shown for snaps

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  The snap developer is not shown in GNOME Software.

  [Test Case]
  1. Open GNOME Software
  2. Search for "Moon Buggy" and click on it

  Expected result:
  The developer name is shown as "dholbach"

  Observed result:
  The developer name is not shown anywhere.

  [Regression Potential]
  Low, as we just populate the "project group" (shows as developer) with the 
snap "developer" field.

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

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

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

** Changed in: firefox
   Status: New => Confirmed

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

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

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

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

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

[Desktop-packages] [Bug 1700764] Re: snap policykit prompt in Turkish language

2017-09-04 Thread Douglas Mellon

Just encountered this. September 4, 2017.

** Attachment added: "Screenshot from 2017-09-04 19-54-40.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1700764/+attachment/4944427/+files/Screenshot%20from%202017-09-04%2019-54-40.png

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

Title:
  snap policykit prompt in Turkish language

Status in gnome-software package in Ubuntu:
  Triaged
Status in snapd-glib package in Ubuntu:
  Triaged

Bug description:
  I for the first time installed a snap package via gnome-software, and
  was asked to init the snap system by entering my credentials/creating
  an account. After doing that, a Gnome dialog popped up where I should
  enter my password - I am in Austria and using Ubuntu GNOME in German -
  but the words there seem Turkish (?) to me - or at least a language I
  can't understand. See screenshot.

  I suppose there was a problem picking the right translation - bu I
  don't know if this is a snap problem or a gnome-software one - I just
  picked one to start this bug report here.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-software 3.22.7-0ubuntu3.17.04.2
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun 26 22:05:01 2017
  InstallationDate: Installed on 2016-11-27 (211 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to zesty on 2017-06-17 (8 days ago)

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

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

[Desktop-packages] [Bug 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text()

** Summary changed:

- gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
+ gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from 
st_label_set_text()

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Saw some reports with the same title but they're all for previous
  versions.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  4 16:52:13 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-04-21 (135 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fd97c8e7e5d :
movzbl 0x16(%rax),%edx
   PC (0x7fd97c8e7e5d) ok
   source "0x16(%rax)" (0xeb1e) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_label_set_text () from /usr/lib/gnome-shell/libst-1.0.so
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1714330] Re: gnome-shell crashed with SIGSEGV in on_crtc_flipped() from g_closure_invoke() from invoke_flip_closure() from page_flip_handler() from drmHandleEvent()

Yes, I spoke too soon. The crash is still happening in today's gnome-shell 
3.25.91-0ubuntu3:
  https://errors.ubuntu.com/problem/196617236bfd49c847a208a8eda38e2bd701ca99

Curiously no reports of it happening in 3.25.91+20170902~ce515c5*
though.

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

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

** Also affects: mutter via
   https://bugzilla.gnome.org/show_bug.cgi?id=787240
   Importance: Unknown
   Status: Unknown

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

Title:
  gnome-shell crashed with SIGSEGV in on_crtc_flipped() from
  g_closure_invoke() from invoke_flip_closure() from page_flip_handler()
  from drmHandleEvent()

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/196617236bfd49c847a208a8eda38e2bd701ca99

  ---

  Gnome shell crashes when trying to log in to the wayland ubuntu
  session. It works fine on Xorg.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Aug 31 11:39:23 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2017-07-27 (35 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170723)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fdee0bf9296:mov0x1a0(%rax),%rax
   PC (0x7fdee0bf9296) ok
   source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   drmHandleEvent () at /usr/lib/x86_64-linux-gnu/libdrm.so.2
   meta_monitor_manager_kms_wait_for_flip () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

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

** Information type changed from Private to Public

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Saw some reports with the same title but they're all for previous
  versions.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  4 16:52:13 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-04-21 (135 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fd97c8e7e5d :
movzbl 0x16(%rax),%edx
   PC (0x7fd97c8e7e5d) ok
   source "0x16(%rax)" (0xeb1e) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_label_set_text () from /usr/lib/gnome-shell/libst-1.0.so
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1683867] Re: Have to click "Restart" and "Shutdown" button twice to make button work.

I believe this was fixed in gnome-shell 3.25.4, which artful now has.

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

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

Title:
  Have to click "Restart" and "Shutdown" button twice to make button
  work.

Status in GNOME Shell:
  Fix Released
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  After left-clicking the menu in the top-right, then clicking the
  "Shutdown" button, the dialog window appears with three options:
  Cancel, Restart and Shutdown.

  In 16.10 you just have to single-click the buttons to shutdown or
  restart. In 17.04, the buttons don't respond to a single click -- you
  have to click them a second time for the click to register.

  EXPECTED BEHAVIOR: as before, click either button once to shutdown or
  restart PC.

  Bug discovered on:
  Ubuntu GNOME 17.04 x64
  GNOME shell 3.24.0
  Linux kernel 4.10.0-19-generic

  Nvidia GTX 980ti graphics
  Nvidia 375.39 proprietary graphics driver.
  Xorg 1.19.3

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

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

[Desktop-packages] [Bug 1715019] Re: Gnome-Shell on Wayland Poweroff system menu button not working

Carla, does clicking the button twice help (like in bug 1683867)?

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

Title:
  Gnome-Shell on Wayland Poweroff system menu button not working

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I click on the system menu arrow and select the power off button,
  it highlights in orange but when clicked it does not power off, or ask
  to power off as expected.

  In syslog I have these logs:

  
  Sep  4 22:16:58 carla-XPS-8900 gnome-shell[1853]: JS ERROR: TypeError: 
this.systemMenu._onPowerOffClicked is not a 
function#012Extension<._onPowerOffClicked@/home/carla/.local/share/gnome-shell/extensions/suspend-button@laserb/extension.js:188:9#012wrapper@resource:
  ///org/gnome/gjs/modules/_legacy.js:82:22

  I have Ubuntu Artful Aardvark (development branch) with all updates installed.
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-06-01 (95 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170525)
  Package: gnome-shell 3.25.91-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Tags:  wayland-session artful
  Uname: Linux 4.12.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

I'm not sure that would help. A few people above have said that 17.04 is
affected and 17.04 ships with PulseAudio 10.0 already.

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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

[Desktop-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

2017-09-04 Thread Jason Gambrel

Has anyone tried compiling/installing pulseaudio 9 to see if it resolves
the bug as it seems to be present on multiple version of
Ubuntu/derivatives and across multiple kernels?  Just a thought.

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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

[Desktop-packages] [Bug 1705157] Re: "Ubuntu" and "Ubuntu on Xorg" randomly start the same session (maybe Wayland maybe Xorg)

** Summary changed:

- On fresh install or fresh boot greeter always show "ubuntu" though selected 
session may be ubuntu-wayland
+ "Ubuntu" and "Ubuntu on Xorg" randomly start the same session (maybe Wayland 
maybe Xorg)

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

Title:
  "Ubuntu" and "Ubuntu on Xorg" randomly start the same session (maybe
  Wayland maybe Xorg)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  Test case:
  Do a fresh install of current image (july 19 here
  Boot up, check selected session at the greeter - it will say "ubuntu"
  Log in, ck. env., it will actually be ubuntu-wayland

  Ex.
  $ env | grep -i wayland
  DESKTOP_SESSION=ubuntu-wayland
  WAYLAND_DISPLAY=wayland-0
  XDG_SESSION_TYPE=wayland
  XDG_SESSION_DESKTOP=ubuntu-wayland
  GDMSESSION=ubuntu-wayland

  Test 2:
  From above log out, switch session in greeter to wayland on ubuntu,, switch 
back to ubuntu, login.
  Now you'll be in an ubuntu session

  Test 3:
  log out from above ubuntu session, log into ubuntu-wayland session, reboot.
  At greeter notice it says "ubuntu" selected.
  Login, ck. session. You'll actually be in an ubuntu-wayland session

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-session 3.24.1-0ubuntu15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 18 21:48:10 2017
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170718)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1714312] Re: 'Ubuntu' starts an x11 session instead of wayland

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

We're discussing this in bug 1705157 instead. If you can find a better
title for it then feel free to reword :)

** This bug has been marked a duplicate of bug 1705157
   On fresh install or fresh boot greeter always show "ubuntu" though selected 
session may be ubuntu-wayland

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

Title:
  'Ubuntu' starts an x11 session instead of wayland

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  artful desktop up to date on real hardware

  Test Case
  1. In gdm select a user
  2. Click on the cog
    -> Verify the list of sessions available
  4. Select "Ubuntu" and log in
    -> Verify that wayland is running ($WAYLAND_DISPLAY is set)

  Expected Result
  At least "Ubuntu" and "Ubuntu on Xorg" are available
  Wayland is running

  Actual result
  Both entries start xorg instead of wayland. Sometimes it's the opposite, both 
entries start wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-session (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 31 18:59:31 2017
  InstallationDate: Installed on 2013-09-03 (1457 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1713650] Re: Can't Alt+drag windows at all any more

I'm not sure I agree with Gnome's decision to change to Super+drag. It's
been Alt+drag in Ubuntu for so long that I wonder what was conflicting
with that?

On the other hand, in theory yes using Super for the shell is a better
idea because apps are more likely to use Alt than Super.

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

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

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

Title:
  Can't Alt+drag windows at all any more

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Alt+drag doesn't move windows like it should.

  I think this might be a Wayland-specific problem in Gnome Shell.

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

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

[Desktop-packages] [Bug 35347] Re: bookmarks need subfolders

** Changed in: nautilus
   Status: New => Expired

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

Title:
  bookmarks need subfolders

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  ...ever thought about having 100 such bookmarks?

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

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

[Desktop-packages] [Bug 1713323] Re: HiDPI support partially broken after upgrade

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


** Summary changed:

- HiDPI support partially broken after upgrade
+ HiDPI support partially broken after upgrade to Gnome 3.25

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

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

Title:
  HiDPI support partially broken after upgrade to Gnome 3.25

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade this morning that took in the new version of this
  package, and a suite of gnome-session/gnome-settings packages, which
  may also be implicated, support for scaling on HiDPI screens seems to
  have partially failed. Partially.

  BTW I invoked the bug reporter with "ubuntu-bug ubuntu-session" but
  when I got to the launchpad page it had pre-filled "gnome-session".
  One presumes there's a reason for that so I've left it, especially as
  this does affect "GNOME" as well as "Ubuntu" sessions. But I do note a
  settings migrations utility in ubuntu-session which I wonder if it
  might be implicated. (TBH looking at it it's not obvious why, though
  it does reset scaling - that's not the problem, the problem is that it
  can't be set back to a combination that works.)

  Reminder all the stuff I'm reporting below as being wrongly-scaled was
  scaled correctly before the update that just took place. Enpass got a
  little help from having some QT env variables set, but that's it.

  Logging in under session "Ubuntu" (Wayland - on a different machine as
  this one being nvidia doesn't support it) or session "Ubuntu on Xorg"
  - also affects GNOME sessions:

  * The fonts in the top bar, and the menus and indicators accessible
  from there, are unscaled. The indicator icons *are* scaled correctly.

  * The fonts in the applications view are unscaled, but the icons and
  layout *are* scaled correctly.

  * Menu titlebar *text* is unscaled. close/minimize/maximize widgets
  *are* scaled correctly, as is the titlebar's size itself.

  * The mouse pointer is unscaled.

  * Non-Gnome apps, either QT or GTK (examples: enpass, nextcloud-
  client, hexchat, sublime text 3) are unscaled, or in some cases are a
  bit confused, with some elements correctly scaled, but again fonts are
  not.

  * Also on a personal note, Java 9 JavaFX apps are no longer scaled.
  (In Java 8 it was already broken; I was targeting Java 9 with my
  development partly *because* its HiDPI support was working in Linux.)
  FYI Java 9 JavaFX uses GTK3, Java 8 uses GTK2.

  ## What is working:

  * Gnome apps (eg: Terminal, Transmission, Settings, Tweaks, Nautilus,
  Gedit etc. etc.) are all fine. Although note those that use a "normal"
  titlebar (eg: Terminal) rather than an integrated one (eg: Nautilus)
  show small titlebar text as mentioned above

  * Google Chrome, Thunderbird, Firefox are fine (although the latter
  two aren't being updated for Artful yet, just sayin' ;-)

  ## What happens if I try to fix it:

  gsettings org.gnome.desktop.interface scaling-factor appears to no
  longer be operational. Changing its value from 0 (default), 1 and 2
  appears to have no effect on anything any more. It used to be setting
  it to 2 fixed the few things that weren't right by having it set to
  0... Correction, that *does* fix it for Java 9 JavaFX, it must be
  reading that setting directly. But nothing else reported as broken
  above is affected by changing this setting. Nor in fact does setting
  it to 1 cause gnome apps to be unscaled.

  gsettings org.gnome.desktop.interface cursor-size is working. I can
  set it to 48, double its normal size, to get back normal-sized cursors
  when the pointer is over newly-launched applications. But that's
  obviously a workaround.

  gsettings org.gnome.desktop.interface text-scaling-factor set to 2.0,
  also exposed in Gnome Tweaks, unsurprisingly makes text twice as
  large. That "fixes" it for the applications that are reported as being
  unscaled above, but it also doubles the size of text in gnome apps as
  well, so those are now far too large for the windows they're in.
  Google Chrome is unaffected by this, as is Java 9 JavaFX, but
  Thunderbird *is* affected.

  I noticed a new gsetting: com.ubuntu.user-interface scale-factor, but
  it seems to have a nonsense-value "@a{si} {}". I have no idea if this
  is anything in use or if it was an intended Unity 8 thing. I didn't
  try anything with

[Desktop-packages] [Bug 1714826] Re: HiDPI scaling regression on Beta 1

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

** This bug is no longer a duplicate of bug 1714295
   HiDPI scaling broken in Gnome 3.25
** This bug has been marked a duplicate of bug 1713323
   HiDPI support partially broken after upgrade

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

Title:
  HiDPI scaling regression on Beta 1

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After running today's updates, HiDPI scaling on my 4k 15,6" display
  stopped working. Ubuntu dock keeps correct scaling, but top bar,
  context menu, and other UI elements revert back to non-scaled
  dimensions. I can fix most of the UI with

  $ gsettings set org.gnome.desktop.interface scaling-factor 2

  but after reboot or logout it reverts back to wrong setting. I solved
  the topbar scaling by changing the size of the panel by one pixel
  (increase or decrease, doesn't matter. Perplexing, indeed), but can't
  find a way to fix context menu scaling.

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

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

[Desktop-packages] [Bug 1714295] Re: HiDPI scaling broken in Gnome 3.25

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

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


** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

** This bug has been marked a duplicate of bug 1713323
   HiDPI support partially broken after upgrade

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

Title:
  HiDPI scaling broken in Gnome 3.25

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After applying the latest artful updates today and rebooting, the
  login screen is correctly scaled but after I login DPI scaling doesn't
  apply correctly. Everything is super tiny.

  If I launch gnome tweak tool then the screen snaps and then
  applications are correctly scaled. Even then, the top bar remains
  tiny. If I adjust the scaling factor, everything but the top bar
  changes.

  FWIW, I have scaling factor set to 1 in gnome tweak tool. I'm
  wondering if I have a preference somewhere that's sabotaging this but
  I've yet to find it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 31 10:59:17 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-07-23 (38 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  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.
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1713323] Re: HiDPI support partially broken after upgrade to Gnome 3.25

Sorry, let this be the primary bug.

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

Title:
  HiDPI support partially broken after upgrade to Gnome 3.25

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade this morning that took in the new version of this
  package, and a suite of gnome-session/gnome-settings packages, which
  may also be implicated, support for scaling on HiDPI screens seems to
  have partially failed. Partially.

  BTW I invoked the bug reporter with "ubuntu-bug ubuntu-session" but
  when I got to the launchpad page it had pre-filled "gnome-session".
  One presumes there's a reason for that so I've left it, especially as
  this does affect "GNOME" as well as "Ubuntu" sessions. But I do note a
  settings migrations utility in ubuntu-session which I wonder if it
  might be implicated. (TBH looking at it it's not obvious why, though
  it does reset scaling - that's not the problem, the problem is that it
  can't be set back to a combination that works.)

  Reminder all the stuff I'm reporting below as being wrongly-scaled was
  scaled correctly before the update that just took place. Enpass got a
  little help from having some QT env variables set, but that's it.

  Logging in under session "Ubuntu" (Wayland - on a different machine as
  this one being nvidia doesn't support it) or session "Ubuntu on Xorg"
  - also affects GNOME sessions:

  * The fonts in the top bar, and the menus and indicators accessible
  from there, are unscaled. The indicator icons *are* scaled correctly.

  * The fonts in the applications view are unscaled, but the icons and
  layout *are* scaled correctly.

  * Menu titlebar *text* is unscaled. close/minimize/maximize widgets
  *are* scaled correctly, as is the titlebar's size itself.

  * The mouse pointer is unscaled.

  * Non-Gnome apps, either QT or GTK (examples: enpass, nextcloud-
  client, hexchat, sublime text 3) are unscaled, or in some cases are a
  bit confused, with some elements correctly scaled, but again fonts are
  not.

  * Also on a personal note, Java 9 JavaFX apps are no longer scaled.
  (In Java 8 it was already broken; I was targeting Java 9 with my
  development partly *because* its HiDPI support was working in Linux.)
  FYI Java 9 JavaFX uses GTK3, Java 8 uses GTK2.

  ## What is working:

  * Gnome apps (eg: Terminal, Transmission, Settings, Tweaks, Nautilus,
  Gedit etc. etc.) are all fine. Although note those that use a "normal"
  titlebar (eg: Terminal) rather than an integrated one (eg: Nautilus)
  show small titlebar text as mentioned above

  * Google Chrome, Thunderbird, Firefox are fine (although the latter
  two aren't being updated for Artful yet, just sayin' ;-)

  ## What happens if I try to fix it:

  gsettings org.gnome.desktop.interface scaling-factor appears to no
  longer be operational. Changing its value from 0 (default), 1 and 2
  appears to have no effect on anything any more. It used to be setting
  it to 2 fixed the few things that weren't right by having it set to
  0... Correction, that *does* fix it for Java 9 JavaFX, it must be
  reading that setting directly. But nothing else reported as broken
  above is affected by changing this setting. Nor in fact does setting
  it to 1 cause gnome apps to be unscaled.

  gsettings org.gnome.desktop.interface cursor-size is working. I can
  set it to 48, double its normal size, to get back normal-sized cursors
  when the pointer is over newly-launched applications. But that's
  obviously a workaround.

  gsettings org.gnome.desktop.interface text-scaling-factor set to 2.0,
  also exposed in Gnome Tweaks, unsurprisingly makes text twice as
  large. That "fixes" it for the applications that are reported as being
  unscaled above, but it also doubles the size of text in gnome apps as
  well, so those are now far too large for the windows they're in.
  Google Chrome is unaffected by this, as is Java 9 JavaFX, but
  Thunderbird *is* affected.

  I noticed a new gsetting: com.ubuntu.user-interface scale-factor, but
  it seems to have a nonsense-value "@a{si} {}". I have no idea if this
  is anything in use or if it was an intended Unity 8 thing. I didn't
  try anything with it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-session 3.25.90-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 27 13:03:53 2017
  InstallationDate: Installed on 2017-07-30 (27 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to artful on 2017-08-22 (5 days ago)

To manage notifications about this bug go

[Desktop-packages] [Bug 1714810] Re: gnome-terminal shrinks window to nothing

I already confirmed the "non-symmetric" behavior:

> the following padding does NOT cause the problem:
> padding: 1px 1px 1px 1px;
> The following padding DOES cause the problem:
> padding: 2px 1px 1px 1px;

Regarding scrollbars with un-filled space, I guess Linux will keep
sucking on the desktop for the foreseeable future for political reasons
:-)

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

Title:
  gnome-terminal shrinks window to nothing

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Using Ubuntu 17.04, vim, in gnome-terminal. Default everythings from
  the desktop install, default Theme. The only change is the default
  window size in the settings -- I have it at 149x48. This bug happens
  even with the default 80x24 window size. The font is the default (not
  overridden) Monospace Regular 12.

  When running vim in gnome-terminal, there is an ugly margin of
  terminal-background color on the right/bottom of the terminal window.
  My vim background is gray, my terminal background is green, vim
  displays gray background but there is a green border just slightly
  slimmer than one character cell on the right/bottom. This also happens
  for other terminal programs (including the shell) if they set the
  background color of output.

  In an attempt to at least make this less ugly, I tried to add some
  padding to the terminal to center the drawable area that vim paints
  with the background. I added the following to my gtk.css:

  $ cat .config/gtk-3.0/gtk.css 
  vte-terminal {
  padding: 8px 8px 5px 1px;
  }

  Now, when I open gnome-terminal, it keeps resizing itself to be
  shorter in the Y axis, one line at a time, until it is only one line
  high. It's almost like an animation of the window height, collapsing
  the window to be very short. After it stops there, I can manually snap
  the terminal to top/bottom edges of the screen, and it will stay
  there, but trying to resize it will just keep shrinking the height.

  This bug is about the resizing behavior. My totally uneducated guess
  is that there's some off-by-one error when allocating space for the
  terminal window contents. Terminal calculates contents, sets the
  window, measures contents, decides to attempt to "snap" to size of
  character cell, rounds down, window gets shorter, terminal measures
  contents, decides to attempt to "snap" to size of character cell,
  rounds down, window gets shorter, ...

  If that is, indeed, the case, then the other bug (the ugly border) may
  be caused by the same problem, but I will file a separate bug for
  that.

  $ lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  $ apt-cache policy gnome-terminal
  gnome-terminal:
Installed: 3.20.2-1ubuntu8
Candidate: 3.20.2-1ubuntu8

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

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

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

2017-09-04 Thread in8sworld

Same problem on ASUS Chromebook C201 running Xenial under Crouton (armhf). 
firefox 55.0.1 and 55.0.2 (both published 8/17) crash immediately at launch.

firefox 52.0.2 from 8/15 still works for me:
https://launchpad.net/ubuntu/xenial/armhf/firefox/52.0.2+build1-0ubuntu0.16.04.1
firefox_52.0.2+build1-0ubuntu0.16.04.1_armhf.deb (40.4 MiB)

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

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

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

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

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

[Desktop-packages] [Bug 1715030] Re: Please remove firefox from artful on armhf and ppc64el

2017-09-04 Thread Chris Coulson

No, please don't remove it on armhf. We have people actually using it
there, and it needs fixing

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

Title:
  Please remove firefox from artful on armhf and ppc64el

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  As discussed at https://lists.ubuntu.com/archives/ubuntu-
  devel/2017-September/039962.html

  please remove firefox from armhf and ppc64el for artful.

  ppc64el has the same output except without lubuntu-desktop and 
lubuntu-gtk-desktop
  $ reverse-depends src:firefox -a armhf
  Reverse-Recommends
  ==
  * ardour(for firefox)
  * djview-plugin (for firefox)
  * gcu-plugin(for firefox)
  * jclic (for firefox)
  * kubuntu-desktop   (for firefox)
  * kubuntu-full  (for firefox)
  * libknopflerfish-osgi-java-doc  (for firefox)
  * lxde  (for firefox)
  * lxqt  (for firefox)
  * nip2  (for firefox)
  * rhythmbox-mozilla (for firefox)
  * ubuntu-desktop(for firefox)
  * ubuntu-gnome-desktop  (for firefox)
  * ubuntu-mate-core  (for firefox)
  * ubuntu-mate-desktop   (for firefox)
  * ubuntukylin-desktop   (for firefox-locale-zh-hans)
  * ubuntukylin-desktop   (for firefox)
  * ubuntustudio-desktop  (for firefox)
  * xsane (for firefox)
  * xubuntu-desktop   (for firefox)

  Reverse-Depends
  ===
  * cinnamon-desktop-environment  (for firefox) (arch:all)
  * firefox-launchpad-plugin  (for firefox) (arch:all)
  * garmin-plugin (for firefox)
  * gnome-core(for firefox)
  * lubuntu-desktop   (for firefox)
  * lubuntu-gtk-desktop   (for firefox)
  * mediatomb (for firefox)
  * mozplugger(for firefox)
  * sugar-firefox-activity(for firefox)
  * ubuntu-defaults-zh-cn (for firefox-locale-zh-hans)
  * ubuntu-online-tour(for firefox)
  * webhttrack(for firefox)
  * xul-ext-classic-theme-restorer  (for firefox) (arch:all)
  * xul-ext-colorfultabs  (for firefox)(arch:all)
  * xul-ext-form-history-control  (for firefox) (arch:all)
  * xul-ext-https-finder  (for firefox) (arch:all)
  * xul-ext-iceweasel-branding(for firefox) (arch:all)
  * xul-ext-kwallet5  (for firefox)
  * xul-ext-lightbeam (for firefox)
  * xul-ext-mozvoikko (for firefox)
  * xul-ext-password-editor   (for firefox)
  * xul-ext-pdf.js(for firefox)
  * xul-ext-self-destructing-cookies  (for firefox)
  * xul-ext-spdy-indicator(for firefox)
  * xul-ext-ublock-origin (for firefox)
  * xul-ext-video-without-flash   (for firefox)
  * xul-ext-y-u-no-validate   (for firefox)

  Plan
  
  Please also remove 

  garmin-plugin (armhf and ppc64el)
  mozplugger everywhere and blacklist it

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

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

[Desktop-packages] [Bug 1714810] Re: gnome-terminal shrinks window to nothing

Regarding the scrollbar and its surrounding space that looks like
padding: see my opinion (which is not in favor of Ubuntu's custom change
at all) at https://bugzilla.gnome.org/show_bug.cgi?id=754796 comments
17-20.

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

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

Title:
  gnome-terminal shrinks window to nothing

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Using Ubuntu 17.04, vim, in gnome-terminal. Default everythings from
  the desktop install, default Theme. The only change is the default
  window size in the settings -- I have it at 149x48. This bug happens
  even with the default 80x24 window size. The font is the default (not
  overridden) Monospace Regular 12.

  When running vim in gnome-terminal, there is an ugly margin of
  terminal-background color on the right/bottom of the terminal window.
  My vim background is gray, my terminal background is green, vim
  displays gray background but there is a green border just slightly
  slimmer than one character cell on the right/bottom. This also happens
  for other terminal programs (including the shell) if they set the
  background color of output.

  In an attempt to at least make this less ugly, I tried to add some
  padding to the terminal to center the drawable area that vim paints
  with the background. I added the following to my gtk.css:

  $ cat .config/gtk-3.0/gtk.css 
  vte-terminal {
  padding: 8px 8px 5px 1px;
  }

  Now, when I open gnome-terminal, it keeps resizing itself to be
  shorter in the Y axis, one line at a time, until it is only one line
  high. It's almost like an animation of the window height, collapsing
  the window to be very short. After it stops there, I can manually snap
  the terminal to top/bottom edges of the screen, and it will stay
  there, but trying to resize it will just keep shrinking the height.

  This bug is about the resizing behavior. My totally uneducated guess
  is that there's some off-by-one error when allocating space for the
  terminal window contents. Terminal calculates contents, sets the
  window, measures contents, decides to attempt to "snap" to size of
  character cell, rounds down, window gets shorter, terminal measures
  contents, decides to attempt to "snap" to size of character cell,
  rounds down, window gets shorter, ...

  If that is, indeed, the case, then the other bug (the ugly border) may
  be caused by the same problem, but I will file a separate bug for
  that.

  $ lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  $ apt-cache policy gnome-terminal
  gnome-terminal:
Installed: 3.20.2-1ubuntu8
Candidate: 3.20.2-1ubuntu8

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

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

[Desktop-packages] [Bug 1715030] [NEW] Please remove firefox from artful on armhf and ppc64el

2017-09-04 Thread Jeremy Bicha

Public bug reported:

As discussed at https://lists.ubuntu.com/archives/ubuntu-
devel/2017-September/039962.html

please remove firefox from armhf and ppc64el for artful.

ppc64el has the same output except without lubuntu-desktop and 
lubuntu-gtk-desktop
$ reverse-depends src:firefox -a armhf
Reverse-Recommends
==
* ardour(for firefox)
* djview-plugin (for firefox)
* gcu-plugin(for firefox)
* jclic (for firefox)
* kubuntu-desktop   (for firefox)
* kubuntu-full  (for firefox)
* libknopflerfish-osgi-java-doc  (for firefox)
* lxde  (for firefox)
* lxqt  (for firefox)
* nip2  (for firefox)
* rhythmbox-mozilla (for firefox)
* ubuntu-desktop(for firefox)
* ubuntu-gnome-desktop  (for firefox)
* ubuntu-mate-core  (for firefox)
* ubuntu-mate-desktop   (for firefox)
* ubuntukylin-desktop   (for firefox-locale-zh-hans)
* ubuntukylin-desktop   (for firefox)
* ubuntustudio-desktop  (for firefox)
* xsane (for firefox)
* xubuntu-desktop   (for firefox)

Reverse-Depends
===
* cinnamon-desktop-environment  (for firefox) (arch:all)
* firefox-launchpad-plugin  (for firefox) (arch:all)
* garmin-plugin (for firefox)
* gnome-core(for firefox)
* lubuntu-desktop   (for firefox)
* lubuntu-gtk-desktop   (for firefox)
* mediatomb (for firefox)
* mozplugger(for firefox)
* sugar-firefox-activity(for firefox)
* ubuntu-defaults-zh-cn (for firefox-locale-zh-hans)
* ubuntu-online-tour(for firefox)
* webhttrack(for firefox)
* xul-ext-classic-theme-restorer  (for firefox) (arch:all)
* xul-ext-colorfultabs  (for firefox)(arch:all)
* xul-ext-form-history-control  (for firefox) (arch:all)
* xul-ext-https-finder  (for firefox) (arch:all)
* xul-ext-iceweasel-branding(for firefox) (arch:all)
* xul-ext-kwallet5  (for firefox)
* xul-ext-lightbeam (for firefox)
* xul-ext-mozvoikko (for firefox)
* xul-ext-password-editor   (for firefox)
* xul-ext-pdf.js(for firefox)
* xul-ext-self-destructing-cookies  (for firefox)
* xul-ext-spdy-indicator(for firefox)
* xul-ext-ublock-origin (for firefox)
* xul-ext-video-without-flash   (for firefox)
* xul-ext-y-u-no-validate   (for firefox)

Plan

Please also remove 

garmin-plugin (armhf and ppc64el)
mozplugger everywhere and blacklist it

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


** Tags: artful

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

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

Title:
  Please remove firefox from artful on armhf and ppc64el

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  As discussed at https://lists.ubuntu.com/archives/ubuntu-
  devel/2017-September/039962.html

  please remove firefox from armhf and ppc64el for artful.

  ppc64el has the same output except without lubuntu-desktop and 
lubuntu-gtk-desktop
  $ reverse-depends src:firefox -a armhf
  Reverse-Recommends
  ==
  * ardour(for firefox)
  * djview-plugin (for firefox)
  * gcu-plugin(for firefox)
  * jclic (for firefox)
  * kubuntu-desktop   (for firefox)
  * kubuntu-full  (for firefox)
  * libknopflerfish-osgi-java-doc  (for firefox)
  * lxde  (for firefox)
  * lxqt  (for firefox)
  * nip2  (for firefox)
  * rhythmbox-mozilla (for firefox)
  * ubuntu-desktop(for firefox)
  * ubuntu-gnome-desktop  (for firefox)
  * ubuntu-mate-core  (for firefox)
  * ubuntu-mate-desktop   (for firefox)
  * ubuntukylin-desktop   (for firefox-locale-zh-hans)
  * ubuntukylin-desktop   (for firefox)
  * ubuntustudio-desktop  (for firefox)
  * xsane (for firefox)
  * xubuntu-desktop   (for firefox)

  Reverse-Depends
  ===
  * cinnamon-desktop-environment  (for firefox) (arch:all)
  * firefox-launchpad-plugin  (for firefox) (arch:all)
  * garmin-plugin (for firefox)
  * gnome-core(for firefox)
  * lubuntu-desktop   (for firefox)
  * lubuntu-gtk-desktop   (for firefox)
  * mediatomb (for firefox)
  * mozplugger(for firefox)
  * sugar-firefox-activity

[Desktop-packages] [Bug 1714810] Re: gnome-terminal shrinks window to nothing

We're talking about multiple bugs here.

The most serious one, the window automatically shrinking should I
believe stop when you specify paddings so that left+right = top+bottom.
Could you please test/confirm this?

> The window in the screen shot is taken with zero configured padding.

The default padding is 1px on all sides, that tiny thin line that you
can see. Don't set it to 0px because you'll face new bugs then :)

The extra amount on the right side in the screenshot is probably part of
the scrollbar (even though it doesn't look so). I hate it, see
https://bugzilla.gnome.org/show_bug.cgi?id=772134#c3 for a workaround.

> It sounds from your description as if the real problem is in "vte"
which is used by gnome-terminal?

Exactly. (Ubuntu package name is "libvte-2.91-0" and friends, source
package is "vte2.91".)

> Note that, in the worst of cases, when I maximize a window and get a green
> border on the bottom, I will sometimes get a line of text "stuck" there, and
> it's inaccessible by any normal editor commands or cursor movement. I can't
> reproduce this on demand (yet) though.

When you maximize or fullscreen, extra padding might appear on the right
and bottom for the remaining area that's smaller than a full cell. That
area cannot be used normally. An exception is that if you begin to
scroll back with the scrollbar (or touchpad, mouse wheel etc.) then the
bottom extra padding also begins to show contents (this is new as of
vte-0.44, the version that you have).


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

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

Title:
  gnome-terminal shrinks window to nothing

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Using Ubuntu 17.04, vim, in gnome-terminal. Default everythings from
  the desktop install, default Theme. The only change is the default
  window size in the settings -- I have it at 149x48. This bug happens
  even with the default 80x24 window size. The font is the default (not
  overridden) Monospace Regular 12.

  When running vim in gnome-terminal, there is an ugly margin of
  terminal-background color on the right/bottom of the terminal window.
  My vim background is gray, my terminal background is green, vim
  displays gray background but there is a green border just slightly
  slimmer than one character cell on the right/bottom. This also happens
  for other terminal programs (including the shell) if they set the
  background color of output.

  In an attempt to at least make this less ugly, I tried to add some
  padding to the terminal to center the drawable area that vim paints
  with the background. I added the following to my gtk.css:

  $ cat .config/gtk-3.0/gtk.css 
  vte-terminal {
  padding: 8px 8px 5px 1px;
  }

  Now, when I open gnome-terminal, it keeps resizing itself to be
  shorter in the Y axis, one line at a time, until it is only one line
  high. It's almost like an animation of the window height, collapsing
  the window to be very short. After it stops there, I can manually snap
  the terminal to top/bottom edges of the screen, and it will stay
  there, but trying to resize it will just keep shrinking the height.

  This bug is about the resizing behavior. My totally uneducated guess
  is that there's some off-by-one error when allocating space for the
  terminal window contents. Terminal calculates contents, sets the
  window, measures contents, decides to attempt to "snap" to size of
  character cell, rounds down, window gets shorter, terminal measures
  contents, decides to attempt to "snap" to size of character cell,
  rounds down, window gets shorter, ...

  If that is, indeed, the case, then the other bug (the ugly border) may
  be caused by the same problem, but I will file a separate bug for
  that.

  $ lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  $ apt-cache policy gnome-terminal
  gnome-terminal:
Installed: 3.20.2-1ubuntu8
Candidate: 3.20.2-1ubuntu8

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

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

[Desktop-packages] [Bug 1714810] Re: gnome-terminal shrinks window to nothing

Thanks for the pointer!

The window in the screen shot is taken with zero configured padding. The
green strip between the gray vim background and the orange scroll bar is
all ugly padding added by gnome-terminal.

It sounds from your description as if the real problem is in "vte" which is 
used by gnome-terminal?
Note that, in the worst of cases, when I maximize a window and get a green 
border on the bottom, I will sometimes get a line of text "stuck" there, and 
it's inaccessible by any normal editor commands or cursor movement. I can't 
reproduce this on demand (yet) though.

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

Title:
  gnome-terminal shrinks window to nothing

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Using Ubuntu 17.04, vim, in gnome-terminal. Default everythings from
  the desktop install, default Theme. The only change is the default
  window size in the settings -- I have it at 149x48. This bug happens
  even with the default 80x24 window size. The font is the default (not
  overridden) Monospace Regular 12.

  When running vim in gnome-terminal, there is an ugly margin of
  terminal-background color on the right/bottom of the terminal window.
  My vim background is gray, my terminal background is green, vim
  displays gray background but there is a green border just slightly
  slimmer than one character cell on the right/bottom. This also happens
  for other terminal programs (including the shell) if they set the
  background color of output.

  In an attempt to at least make this less ugly, I tried to add some
  padding to the terminal to center the drawable area that vim paints
  with the background. I added the following to my gtk.css:

  $ cat .config/gtk-3.0/gtk.css 
  vte-terminal {
  padding: 8px 8px 5px 1px;
  }

  Now, when I open gnome-terminal, it keeps resizing itself to be
  shorter in the Y axis, one line at a time, until it is only one line
  high. It's almost like an animation of the window height, collapsing
  the window to be very short. After it stops there, I can manually snap
  the terminal to top/bottom edges of the screen, and it will stay
  there, but trying to resize it will just keep shrinking the height.

  This bug is about the resizing behavior. My totally uneducated guess
  is that there's some off-by-one error when allocating space for the
  terminal window contents. Terminal calculates contents, sets the
  window, measures contents, decides to attempt to "snap" to size of
  character cell, rounds down, window gets shorter, terminal measures
  contents, decides to attempt to "snap" to size of character cell,
  rounds down, window gets shorter, ...

  If that is, indeed, the case, then the other bug (the ugly border) may
  be caused by the same problem, but I will file a separate bug for
  that.

  $ lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  $ apt-cache policy gnome-terminal
  gnome-terminal:
Installed: 3.20.2-1ubuntu8
Candidate: 3.20.2-1ubuntu8

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

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

[Desktop-packages] [Bug 1629610] Re: package mono-gac 4.2.1.102+dfsg2-7ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

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

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

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

Title:
  package mono-gac 4.2.1.102+dfsg2-7ubuntu4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 139

Status in mono package in Ubuntu:
  Confirmed

Bug description:
  I'm not sure what details to provide. The upgrade tool asked me to
  fill in this form, so here I am doing that.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: mono-gac 4.2.1.102+dfsg2-7ubuntu4
  Uname: Linux 3.19.3--grspax-ipv6-64 x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Oct  1 23:48:19 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationDate: Installed on 2013-04-26 (1254 days ago)
  InstallationMedia:
   
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.14
  SourcePackage: mono
  Title: package mono-gac 4.2.1.102+dfsg2-7ubuntu4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 139
  UpgradeStatus: Upgraded to xenial on 2016-10-01 (0 days ago)

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

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

[Desktop-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

2017-09-04 Thread mhogo mchungu

Greetings,
two of my projects are on the list(SiriKali and zuluCrypt) and latest versions 
of these projects are not affected by the problem.

The latest version of SiriKali is 1.3.0 but the problem was solved in
version 1.2.9. The latest version of zuluCrypt is 5.2.0 and it also does
not have the problem.

SiriKali uses pkexec not to root elevate its GUI component but to
elevate a CLI background service called "siripolkit".

zuluCrypt uses pkexec not to root elevate its GUI components but to
elevate a CLI background service called "zulupolkit".

zuluCrypt 5.2.0-1 in debian/ubuntu is affected by the problem and the
problem is due to debian/ubuntu packaging and i already informed the
maintainer about it,the old way of raising GUI components in zuluCrypt
is no longer supported since version 5.2.0.

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  New
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gufw package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  New
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  New
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  New
Status in ubuntustudio-default-settings package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  New
Status in zulucrypt package in Ubuntu:
  New

Bug description:
  Posting here what gnome says about porting to wayland, and their
  tests:

  GNOME Applications under Wayland
  GTK+ has a Wayland backend. If it was enabled at compile-time, you can run a 
GTK+ application under Wayland simply by:

  GDK_BACKEND=wayland gnome-calculator
  Applications that use Clutter or clutter-gtk also need the Clutter Wayland 
backend enabled:

  GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese

  https://wiki.gnome.org/Initiatives/Wayland/Applications

  ==> so hope the settings are well set at compile time; maybe a
  rebuilt to get sure all apps are ok.

  
  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug

[Desktop-packages] [Bug 1715021] [NEW] Gnome settings for primary/secondary monitor are not working

2017-09-04 Thread Jeremie Tamburini

Public bug reported:

Fresh install of Ubuntu 17.10 (laptop + external monitor).

Running "Settings → Displays → Primary (or Secondary)", all the options:

- Primary
- Secondary Display
- Mirror
- Turn Off

are not working.

Also "Arrange Combined Displays" is not working.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.24.3-0ubuntu6
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep  4 22:33:37 2017
InstallationDate: Installed on 2017-09-04 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: artful gnome-17.10

** Tags removed: amd64 apport-bug
** Tags added: gnome-17.10

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

Title:
  Gnome settings for primary/secondary monitor are not working

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

Bug description:
  Fresh install of Ubuntu 17.10 (laptop + external monitor).

  Running "Settings → Displays → Primary (or Secondary)", all the
  options:

  - Primary
  - Secondary Display
  - Mirror
  - Turn Off

  are not working.

  Also "Arrange Combined Displays" is not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  4 22:33:37 2017
  InstallationDate: Installed on 2017-09-04 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1715019/+attachment/4944368/+files/GsettingsChanges.txt

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

Title:
  Gnome-Shell on Wayland Poweroff system menu button not working

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I click on the system menu arrow and select the power off button,
  it highlights in orange but when clicked it does not power off, or ask
  to power off as expected.

  In syslog I have these logs:

  
  Sep  4 22:16:58 carla-XPS-8900 gnome-shell[1853]: JS ERROR: TypeError: 
this.systemMenu._onPowerOffClicked is not a 
function#012Extension<._onPowerOffClicked@/home/carla/.local/share/gnome-shell/extensions/suspend-button@laserb/extension.js:188:9#012wrapper@resource:
  ///org/gnome/gjs/modules/_legacy.js:82:22

  I have Ubuntu Artful Aardvark (development branch) with all updates installed.
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-06-01 (95 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170525)
  Package: gnome-shell 3.25.91-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Tags:  wayland-session artful
  Uname: Linux 4.12.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

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

apport information

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

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

Title:
  Gnome-Shell on Wayland Poweroff system menu button not working

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I click on the system menu arrow and select the power off button,
  it highlights in orange but when clicked it does not power off, or ask
  to power off as expected.

  In syslog I have these logs:

  
  Sep  4 22:16:58 carla-XPS-8900 gnome-shell[1853]: JS ERROR: TypeError: 
this.systemMenu._onPowerOffClicked is not a 
function#012Extension<._onPowerOffClicked@/home/carla/.local/share/gnome-shell/extensions/suspend-button@laserb/extension.js:188:9#012wrapper@resource:
  ///org/gnome/gjs/modules/_legacy.js:82:22

  I have Ubuntu Artful Aardvark (development branch) with all updates installed.
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-06-01 (95 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170525)
  Package: gnome-shell 3.25.91-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Tags:  wayland-session artful
  Uname: Linux 4.12.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1715019] JournalErrors.txt

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1715019/+attachment/4944369/+files/JournalErrors.txt

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

Title:
  Gnome-Shell on Wayland Poweroff system menu button not working

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I click on the system menu arrow and select the power off button,
  it highlights in orange but when clicked it does not power off, or ask
  to power off as expected.

  In syslog I have these logs:

  
  Sep  4 22:16:58 carla-XPS-8900 gnome-shell[1853]: JS ERROR: TypeError: 
this.systemMenu._onPowerOffClicked is not a 
function#012Extension<._onPowerOffClicked@/home/carla/.local/share/gnome-shell/extensions/suspend-button@laserb/extension.js:188:9#012wrapper@resource:
  ///org/gnome/gjs/modules/_legacy.js:82:22

  I have Ubuntu Artful Aardvark (development branch) with all updates installed.
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-06-01 (95 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170525)
  Package: gnome-shell 3.25.91-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Tags:  wayland-session artful
  Uname: Linux 4.12.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

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

apport information

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

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

Title:
  Gnome-Shell on Wayland Poweroff system menu button not working

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I click on the system menu arrow and select the power off button,
  it highlights in orange but when clicked it does not power off, or ask
  to power off as expected.

  In syslog I have these logs:

  
  Sep  4 22:16:58 carla-XPS-8900 gnome-shell[1853]: JS ERROR: TypeError: 
this.systemMenu._onPowerOffClicked is not a 
function#012Extension<._onPowerOffClicked@/home/carla/.local/share/gnome-shell/extensions/suspend-button@laserb/extension.js:188:9#012wrapper@resource:
  ///org/gnome/gjs/modules/_legacy.js:82:22

  I have Ubuntu Artful Aardvark (development branch) with all updates installed.
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-06-01 (95 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170525)
  Package: gnome-shell 3.25.91-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Tags:  wayland-session artful
  Uname: Linux 4.12.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1715019] Dependencies.txt

apport information

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

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

Title:
  Gnome-Shell on Wayland Poweroff system menu button not working

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I click on the system menu arrow and select the power off button,
  it highlights in orange but when clicked it does not power off, or ask
  to power off as expected.

  In syslog I have these logs:

  
  Sep  4 22:16:58 carla-XPS-8900 gnome-shell[1853]: JS ERROR: TypeError: 
this.systemMenu._onPowerOffClicked is not a 
function#012Extension<._onPowerOffClicked@/home/carla/.local/share/gnome-shell/extensions/suspend-button@laserb/extension.js:188:9#012wrapper@resource:
  ///org/gnome/gjs/modules/_legacy.js:82:22

  I have Ubuntu Artful Aardvark (development branch) with all updates installed.
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-06-01 (95 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170525)
  Package: gnome-shell 3.25.91-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Tags:  wayland-session artful
  Uname: Linux 4.12.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1715019] [NEW] Gnome-Shell on Wayland Poweroff system menu button not working

Public bug reported:

When I click on the system menu arrow and select the power off button,
it highlights in orange but when clicked it does not power off, or ask
to power off as expected.

In syslog I have these logs:


Sep  4 22:16:58 carla-XPS-8900 gnome-shell[1853]: JS ERROR: TypeError: 
this.systemMenu._onPowerOffClicked is not a 
function#012Extension<._onPowerOffClicked@/home/carla/.local/share/gnome-shell/extensions/suspend-button@laserb/extension.js:188:9#012wrapper@resource:
///org/gnome/gjs/modules/_legacy.js:82:22

I have Ubuntu Artful Aardvark (development branch) with all updates installed.
--- 
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 17.10
InstallationDate: Installed on 2017-06-01 (95 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170525)
Package: gnome-shell 3.25.91-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Tags:  wayland-session artful
Uname: Linux 4.12.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

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


** Tags: apport-collected artful wayland-session

** Tags added: apport-collected artful wayland-session

** Description changed:

  When I click on the system menu arrow and select the power off button,
  it highlights in orange but when clicked it does not power off, or ask
  to power off as expected.
  
  In syslog I have these logs:
  
  
  Sep  4 22:16:58 carla-XPS-8900 gnome-shell[1853]: JS ERROR: TypeError: 
this.systemMenu._onPowerOffClicked is not a 
function#012Extension<._onPowerOffClicked@/home/carla/.local/share/gnome-shell/extensions/suspend-button@laserb/extension.js:188:9#012wrapper@resource:
  ///org/gnome/gjs/modules/_legacy.js:82:22
  
- I have Ubuntu Artful Aardvark (development branch) with all updates
- installed.
+ I have Ubuntu Artful Aardvark (development branch) with all updates installed.
+ --- 
+ ApportVersion: 2.20.7-0ubuntu1
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 17.10
+ InstallationDate: Installed on 2017-06-01 (95 days ago)
+ InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170525)
+ Package: gnome-shell 3.25.91-0ubuntu3
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
+ Tags:  wayland-session artful
+ Uname: Linux 4.12.0-13-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

Title:
  Gnome-Shell on Wayland Poweroff system menu button not working

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I click on the system menu arrow and select the power off button,
  it highlights in orange but when clicked it does not power off, or ask
  to power off as expected.

  In syslog I have these logs:

  
  Sep  4 22:16:58 carla-XPS-8900 gnome-shell[1853]: JS ERROR: TypeError: 
this.systemMenu._onPowerOffClicked is not a 
function#012Extension<._onPowerOffClicked@/home/carla/.local/share/gnome-shell/extensions/suspend-button@laserb/extension.js:188:9#012wrapper@resource:
  ///org/gnome/gjs/modules/_legacy.js:82:22

  I have Ubuntu Artful Aardvark (development branch) with all updates installed.
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-06-01 (95 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170525)
  Package: gnome-shell 3.25.91-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Tags:  wayland-session artful
  Uname: Linux 4.12.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1028617] Re: Cursor shakes violently when connected to power source - makes touchpad cursor unusable

2017-09-04 Thread Janee

I have the same problem, on Asus k55v with Ubuntu Gnome 16.04 LTS.
If i use it unplugged, than its ok, while when its hooked up to the power grid
the cursor constantly jiggling.

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

Title:
Cursor shakes violently when connected to power source - makes
touchpad cursor unusable

Status in xserver-xorg-input-synaptics package in Ubuntu:
Incomplete

Bug description:
Using Ubuntu 12.04, 64-bit version, installed on Lenovo X220 laptop.
Fresh "default" install and settings configuration.

When the laptop is plugged into a power source, the touchpad's
onscreen cursor (the white arrow that shows position) shakes
excessively when trying to use the touchpad to control the cursor. The
shaking is so bad that it essentially makes the touchpad unusable. For
example, trying to click the minimize button in a window's upper left
corner will routinely result in accidentally clicking the close button
because of the cursor's shaking.

The problem is NOT present when Ubuntu is running on battery. But this
means I can never have Ubuntu plugged in and charging while I use it,
which is very inconvenient at times.

I'm using the power block and cable that came with the X220. But I
also tried using a larger power block and cable that came with another
Lenovo model - this power block is approved for use with the X220 and
is sold on the Lenovo website as an X220 accessory. But this larger
power block did not improve the shaking behavior either.

I have no special settings enabled for the touchpad. But changing the
settings has no effect on this shaking behavior either. I attached a
screenshot of my Touchpad settings [please excuse the HUD's presence -
I cannot get the HUD to NOT appear when I press ALT+PrtSc to take a
screenshot (I guess this is another bug)].

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1028617/+subscriptions

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

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

2017-09-04 Thread Steve Desmond

Same problem, Ubuntu MATE 16.04 on ASUS Chromebook Flip (C100P)

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

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

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

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

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

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

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

[Desktop-packages] [Bug 119879] Re: bookmark not refreshed on directory creation

** Changed in: nautilus
   Status: Confirmed => Expired

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

Title:
  bookmark not refreshed on directory creation

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: nautilus

  This is reproducible. Add a folder to the bookmarsk and then delete
  that folder. The bookmark automatically disappears. Now create a new
  folder with the same name and try adding it to bookmarks again. It
  doesnt pick it up. But if you close nautilus and open it again, the
  bookmarks appears!

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

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

[Desktop-packages] [Bug 1252203] Re: hits "nautilus_window_get_slots NAUTILUS_IS_WINDOW (window)" assert on opening bookmarks not available at start

** Changed in: nautilus
   Status: New => Expired

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

Title:
  hits "nautilus_window_get_slots NAUTILUS_IS_WINDOW (window)" assert on
  opening bookmarks not available at start

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding nautilus.  This problem was most recently seen with version
  1:3.6.3-0ubuntu16, the problem page at
  https://errors.ubuntu.com/problem/0e5eee470d33c7f3240a8f1f478183a83c7c4c25
  contains more details.

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

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

[Desktop-packages] [Bug 1714810] Re: gnome-terminal shrinks window to nothing

I suspect that you're facing the bug that was fixed here:
https://git.gnome.org/browse/vte/commit/?id=5bc6b3f

I wasn't clear about what I meant with "symmetric" margin. My wording
was clearly unfortunate, and even my example was incorrect :) I meant
where swapping the X and Y axes doesn't change anything, that is, top ==
left and bottom == right, for example "8px 5px 5px 8px".

Apparently, as per the fix, probably you can loosen this up a bit, and
any setting where left+right == top+bottom should work correctly I
believe. The bug arises when the overall vertical padding differs from
the overall horizontal padding.

Could you please confirm these?

If that's the case, you can:
- choose such paddings for now,
- wait for Artful which will ship vte-0.48 that fixes this,
- or recompile vte2.91 with this patch.

(The scrollback on the right is another story, unfortunately it's hard
to tell from a screenshot where the right paddings ends and the
scrollbar begins.)

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

Title:
  gnome-terminal shrinks window to nothing

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Using Ubuntu 17.04, vim, in gnome-terminal. Default everythings from
  the desktop install, default Theme. The only change is the default
  window size in the settings -- I have it at 149x48. This bug happens
  even with the default 80x24 window size. The font is the default (not
  overridden) Monospace Regular 12.

  When running vim in gnome-terminal, there is an ugly margin of
  terminal-background color on the right/bottom of the terminal window.
  My vim background is gray, my terminal background is green, vim
  displays gray background but there is a green border just slightly
  slimmer than one character cell on the right/bottom. This also happens
  for other terminal programs (including the shell) if they set the
  background color of output.

  In an attempt to at least make this less ugly, I tried to add some
  padding to the terminal to center the drawable area that vim paints
  with the background. I added the following to my gtk.css:

  $ cat .config/gtk-3.0/gtk.css 
  vte-terminal {
  padding: 8px 8px 5px 1px;
  }

  Now, when I open gnome-terminal, it keeps resizing itself to be
  shorter in the Y axis, one line at a time, until it is only one line
  high. It's almost like an animation of the window height, collapsing
  the window to be very short. After it stops there, I can manually snap
  the terminal to top/bottom edges of the screen, and it will stay
  there, but trying to resize it will just keep shrinking the height.

  This bug is about the resizing behavior. My totally uneducated guess
  is that there's some off-by-one error when allocating space for the
  terminal window contents. Terminal calculates contents, sets the
  window, measures contents, decides to attempt to "snap" to size of
  character cell, rounds down, window gets shorter, terminal measures
  contents, decides to attempt to "snap" to size of character cell,
  rounds down, window gets shorter, ...

  If that is, indeed, the case, then the other bug (the ugly border) may
  be caused by the same problem, but I will file a separate bug for
  that.

  $ lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  $ apt-cache policy gnome-terminal
  gnome-terminal:
Installed: 3.20.2-1ubuntu8
Candidate: 3.20.2-1ubuntu8

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

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

[Desktop-packages] [Bug 1712873] Re: autopkgtests failures on i386 and s390x for 5.4.0, assumes wrong architecture

** Tags added: block-proposed

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

Title:
  autopkgtests failures on i386 and s390x for 5.4.0, assumes wrong
  architecture

Status in libreoffice package in Ubuntu:
  Fix Committed

Bug description:
  Looking at autopkgtests failures on i386 and s390x for
  1:5.4.0-0ubuntu2 in artful-proposed (logs attached).

  The following linker failure:

  /usr/bin/ld: cannot find -ljawt

  is due to $JAVA_PROC_TYPE being incorrect ("amd64" instead of "i386"
  or "s390x"), and thus $LINK_JAVA_LIBS has the incorrect architecture
  in its path and the linker doesn't find libjawt.so.

  This is likely caused by $PROCTYPE being incorrect, which itself is
  set from $PLATFORMID.

  There are other hints that $PROCTYPE has a wrong value in the logs,
  even though that doesn't appear to make the tests fail:

  […]
  mkdir -p 
/tmp/tmp.OSVUCMLVqv/out/sdk/LINUXexample.out/misc/CppComponentSample/Linux_x86_64
  […]

  which means $UNOPKG_PLATFORM has an incorrect value, set from
  $PROCTYPE.

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

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

[Desktop-packages] [Bug 1712979] Re: Installation of missing plugins/codecs fails or is gstreamer1.0-packagekit what's needed?

This bug was fixed in the package ubuntu-meta - 1.399

---
ubuntu-meta (1.399) artful; urgency=medium

  * Refreshed dependencies
  * Added gstreamer1.0-packagekit to desktop (LP: #1712979)

 -- Iain Lane   Mon, 04 Sep 2017 18:46:17 +0100

** Changed in: ubuntu-meta (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Installation of missing plugins/codecs fails or  is
  gstreamer1.0-packagekit what's needed?

Status in GNOME Software:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Test case:
  Fresh install
  Try to play any file requiring one or more gst plugins

  What happens:
  pop up informs plugin(s) missing, offers to 'find in software'
  Clicking on that option fails

  Ex.
  totem /home/doug/Videos/bbb_sunflower_1080p_30fps_normal.mp4
  ** Message: Missing plugin: gstreamer|1.0|totem|MPEG-1 Layer 3 (MP3) 
decoder|decoder-audio/mpeg, mpegversion=(int)1, mpegaudioversion=(int)1, 
layer=(int)3 (MPEG-1 Layer 3 (MP3) decoder)
  ** Message: Missing plugin: gstreamer|1.0|totem|AC-3 (ATSC A/52) 
decoder|decoder-audio/x-ac3 (AC-3 (ATSC A/52) decoder)
  ** Message: Missing plugin: gstreamer|1.0|totem|H.264 (High Profile) 
decoder|decoder-video/x-h264, level=(string)4.1, profile=(string)high (H.264 
(High Profile) decoder)
  ** Message: Automatic missing codec installation not supported (helper script 
missing)


  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.25.90.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 25 01:51:47 2017
  InstallationDate: Installed on 2017-08-20 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170818)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 593402] ☀hey! just take a look at that

2017-09-04 Thread Fabio_050420

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

Hello!

I've just seen  something really fantastic, I assume you'd  love that
too. Just have a  look at that products  here
http://www.gdgmumbai.org/register.php?UE81OTM0MDJAYnVncy5sYXVuY2hwYWQubmV0


My best to you, Fabio Pomi


From: Bug 593402 [mailto:593...@bugs.launchpad.net]
Sent: Monday, September 04, 2017 1:50 PM
To: fabio.p...@libero.it
Subject: Thanks Joe Biden.

I just got the  bodum bistro conical burr grinder and absolutely  love
it. It was 79 bucks  on amazon Canada. There  were some negatives in the
reviews on  it, I do experience some grounds falling out  of it when I
remove the recepticle, but for my drip grinder it  makes a fantastic
consistent grind. I havent tried  the finer or coarser ends  of the
spectrum yet. I  was worried  about the  timer settings and getting
enough coffee, but a 15 second  grind time nets me 45  grams of coffee,
which is what I use for  my 8 cup  Bonavita. I highly recommend it for
price/performance.


Sent from Mail for Windows 10

** Attachment added: "FDCE15B2D4E9E766.jpg"
   
https://bugs.launchpad.net/bugs/593402/+attachment/4944335/+files/FDCE15B2D4E9E766.jpg

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

Title:
  package flashplugin-nonfree 10.0.1.218 really9.0.277.0ubuntu1 failed
  to install/upgrade: Package is in a very bad inconsistent state - you
  should  reinstall it before attempting a removal.

Status in flashplugin-nonfree package in Ubuntu:
  New

Bug description:
  Binary package hint: flashplugin-nonfree

  Did not loaded (or loaded with defects) during the upgrade from Ubuntu
  8.04 to 10.04 - I'm not quite familiar with Ubuntu for for me it's hrd
  to add more details.

  ProblemType: Package
  DistroRelease: Ubuntu 10.04
  Package: flashplugin-nonfree 10.0.1.218+really9.0.277.0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic i686
  AptOrdering:
   flashplugin-nonfree: Remove
   flashplugin-installer: Install
   flashplugin-nonfree: Install
   flashplugin-installer: Configure
   flashplugin-nonfree: Configure
  Architecture: i386
  Date: Sun Jun 13 21:14:40 2010
  ErrorMessage: Package is in a very bad inconsistent state - you should  
reinstall it before attempting a removal.
  SourcePackage: flashplugin-nonfree
  Title: package flashplugin-nonfree 10.0.1.218+really9.0.277.0ubuntu1 failed 
to install/upgrade: Package is in a very bad inconsistent state - you should  
reinstall it before attempting a removal.

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

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

[Desktop-packages] [Bug 1615862] Re: nautilus file copy dialog does not always close properly on completion

2017-09-04 Thread Tonton Manu

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

On my config, the 'Moved/Copied' dialog is not detached from the nautilus 
windows, but it remains displayed on all nautilus windows, including those I 
open after the copy/move operation is finished.
The copy bar also remains on the Unity icon.
It only disappears when I close all nautilus windows opened. Then, I can open 
new nautilus window and the copy/move dialog doesn't appear anymore.

This problem seems to appear when I copy many files in one time, or big
files.

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

Title:
  nautilus file copy dialog does not always close properly on completion

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  The new 'Moving/Copying X files to..." dialog in nautilus doesn't
  always close properly on completion (although the text does change to
  'Moved/Copied').

  When this happens, the filled-in circle in nautilus' title bar stays
  on and the nautilus icon in the unity launcher continues to indicate
  that an operation is still in progress, even though it in fact
  complete. If you close nautilus and re-open it, the 'Moved/Copied'
  dialog appears at the top of the screen, detached from the nautilus
  window (see attached image).

  When it does work properly, after a few seconds the filled-in circle
  in nautilus disappears, the move/copy dialog disappears, and the unity
  launcher icon resets to its non-copying mode.

  I don't know exactly what makes this happen, but it occurs reasonably
  frequently.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.2-0ubuntu1
  Uname: Linux 4.6.4-040604-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 23 08:20:44 2016
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'890x550+65+24'"
  InstallationDate: Installed on 2016-07-04 (49 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to yakkety on 2016-07-24 (29 days ago)

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

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

[Desktop-packages] [Bug 1715013] [NEW] Wired Network Stops Working

2017-09-04 Thread Kevin

Public bug reported:

Hi, this is the second bug I report, and I hope I'm reporting that one
in a better way than the first, I'm including a report at least this
time xD

The thing is that sometimes wired network stops working and needs to be
turned off and on to get it back to the work. It's happening weeks ago,
is not a recent problem, that's why I decided to finally learn how to
generate reports and submit the bug ^^

Sorry, but I cant check if it happens as well using wifi... I've got no
wifi card on this PC :(

Thanks and sorry my bad English ^^

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.2-1ubuntu5
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep  4 20:22:31 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-07-19 (47 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170719)
IpRoute:
 default via 192.168.1.1 dev enp2s0 proto static metric 100 
 169.254.0.0/16 dev enp2s0 scope link metric 1000 
 192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.7 metric 100
IwConfig:
 lono wireless extensions.
 
 enp2s0no wireless extensions.
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
RfKill:
 
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME UUID  TYPE
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
 Conexión cableada 1  653b2178-e532-30d6-adbe-28f87300fb98  802-3-ethernet  
1504549178  lun 04 sep 2017 20:19:38 CEST  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/1  yes enp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/2  --
nmcli-dev:
 DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
 enp2s0  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  653b2178-e532-30d6-adbe-28f87300fb98  
/org/freedesktop/NetworkManager/ActiveConnection/2 
 lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  -- 
  ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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


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

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

Title:
  Wired Network Stops Working

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi, this is the second bug I report, and I hope I'm reporting that one
  in a better way than the first, I'm including a report at least this
  time xD

  The thing is that sometimes wired network stops working and needs to
  be turned off and on to get it back to the work. It's happening weeks
  ago, is not a recent problem, that's why I decided to finally learn
  how to generate reports and submit the bug ^^

  Sorry, but I cant check if it happens as well using wifi... I've got
  no wifi card on this PC :(

  Thanks and sorry my bad English ^^

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu5
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  4 20:22:31 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-07-19 (47 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170719)
  IpRoute:
   default via 192.168.1.1 dev enp2s0 proto static metric 100 
   169.254.0.0/16 dev enp2s0 scope link metric 1000 
   192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.7 metric 100
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8

[Desktop-packages] [Bug 1703690] Re: Add support for Budgie Desktop using GNOME Screensaver

This bug was fixed in the package gnome-screensaver - 3.6.1-7ubuntu6

---
gnome-screensaver (3.6.1-7ubuntu6) artful; urgency=medium

  * Add support for Budgie Desktop (LP: #1703690)
- enable support for gnome-control-center
- style the lock-screen using the "Unity" patch-work

 -- David Mohammed   Thu, 31 Aug 2017 20:53:09
+0100

** Changed in: gnome-screensaver (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Add support for Budgie Desktop using GNOME Screensaver

Status in gnome-desktop3 package in Ubuntu:
  Fix Released
Status in gnome-screensaver package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu Budgie and Budgie Desktop uses GNOME Screensaver for its lock-
  screen.

  It also uses gnome-control-center to control both the desktop
  background and the lock-screen background.

  GNOME Screensaver does not support gnome-control-center lock screen
  dialog - GNOME has changed to a gsettings path
  org.gnome.desktop.screensaver.  GNOME Screensaver is expecting the
  path org.gnome.desktop.background.

  To resolve this requires patches in two packages - gnome-screensaver
  and gnome-desktop3.

  1. GNOME Screensaver has been patched to support Budgie Desktop and 
gnome-control-center.
  Note - I've taken the opportunity to reuse the existing "Unity" patchwork 
which is now defunct (I believe) since Unity uses an alternative locking 
mechanism.  The lock-screen is styled as per the old "Unity" implementation 
before Unity 16.04 moved to the new lock screen.

  2. The consequence of making the requisite changes to GNOME
  Screensaver has unfortunately impacted gnome-desktop3.  gnome-desktop3
  has a Ubuntu specific patch to revert a GNOME upstream decision to
  remove a key called draw-background.  GNOME Screensaver calls a public
  function in gnome-desktop3 - the gsettings path causes a segmentation
  fault since draw-background does not exist in
  org.gnome.desktop.screensaver.  I have worked around this to check the
  path being called before pulling the draw-background key.

  All of this is explained in the dep3 headers of the two debdiff
  patches attached

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

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

[Desktop-packages] [Bug 1714330] Re: gnome-shell crashed with SIGSEGV in on_crtc_flipped() from g_closure_invoke() from invoke_flip_closure() from page_flip_handler() from drmHandleEvent()

** Tags added: bugpattern-needed

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

Title:
  gnome-shell crashed with SIGSEGV in on_crtc_flipped() from
  g_closure_invoke() from invoke_flip_closure() from page_flip_handler()
  from drmHandleEvent()

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

Bug description:
  https://errors.ubuntu.com/problem/196617236bfd49c847a208a8eda38e2bd701ca99

  ---

  Gnome shell crashes when trying to log in to the wayland ubuntu
  session. It works fine on Xorg.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Aug 31 11:39:23 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2017-07-27 (35 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170723)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fdee0bf9296:mov0x1a0(%rax),%rax
   PC (0x7fdee0bf9296) ok
   source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   drmHandleEvent () at /usr/lib/x86_64-linux-gnu/libdrm.so.2
   meta_monitor_manager_kms_wait_for_flip () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

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

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  Randomly crashed

  Xubuntu 17.10 Beta

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-calendar 3.25.90-1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Mon Sep  4 12:35:00 2017
  ExecutablePath: /usr/bin/gnome-calendar
  InstallationDate: Installed on 2017-04-29 (127 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170408)
  ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_US
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fa83593d8ea : cmp
%rax,(%rdx)
   PC (0x7fa83593d8ea) ok
   source "%rax" ok
   destination "(%rdx)" (0x4a) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-calendar
  StacktraceTop:
   gtk_widget_queue_draw () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-calendar crashed with SIGSEGV in gtk_widget_queue_draw()
  UpgradeStatus: Upgraded to artful on 2017-08-26 (9 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

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

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

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

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1714330
   gnome-shell crashed with SIGSEGV in on_crtc_flipped() from 
g_closure_invoke() from invoke_flip_closure() from page_flip_handler() from 
drmHandleEvent()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Just using my system when the error popped up. Not sure what might
  have caused it.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-8.9-generic 4.13.0-rc7
  Uname: Linux 4.13.0-8-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Sep  4 08:25:21 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-08-14 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170812)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7effed6ef836:mov0x1a0(%rax),%rax
   PC (0x7effed6ef836) ok
   source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   drmHandleEvent () from /usr/lib/x86_64-linux-gnu/libdrm.so.2
   meta_monitor_manager_kms_wait_for_flip () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

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

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1505409
   gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from 
_XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to 
xwayland lost"]

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  last month, Some bugs with video that crash on start and put screen black. 
  To day, an update... X11 video server libraries make every thing all right... 
BUT this bug appears and i don't know why
  Please say "congratulations" to the technicians who solved video bugs 1713026 
 (Xvideo server )

  pb with x org video driver ub 17.10 with video card geforce 1050   (my
  pc :Asus GL 753V core I7 7700 with Geforce 1050)

  I hope that this new bug don't crashes Xvideo server when you'll
  resolve this new bug.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Sep  4 19:19:51 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-02-16 (199 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5 in _XIOError()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1712979] Re: Installation of missing plugins/codecs fails or is gstreamer1.0-packagekit what's needed?

2017-09-04 Thread Iain Lane

I think this issue was that we missed the gstreamer1.0-packagekit in the
base install. I'm fixing that, then let's see.

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

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

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

Title:
  Installation of missing plugins/codecs fails or  is
  gstreamer1.0-packagekit what's needed?

Status in GNOME Software:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Test case:
  Fresh install
  Try to play any file requiring one or more gst plugins

  What happens:
  pop up informs plugin(s) missing, offers to 'find in software'
  Clicking on that option fails

  Ex.
  totem /home/doug/Videos/bbb_sunflower_1080p_30fps_normal.mp4
  ** Message: Missing plugin: gstreamer|1.0|totem|MPEG-1 Layer 3 (MP3) 
decoder|decoder-audio/mpeg, mpegversion=(int)1, mpegaudioversion=(int)1, 
layer=(int)3 (MPEG-1 Layer 3 (MP3) decoder)
  ** Message: Missing plugin: gstreamer|1.0|totem|AC-3 (ATSC A/52) 
decoder|decoder-audio/x-ac3 (AC-3 (ATSC A/52) decoder)
  ** Message: Missing plugin: gstreamer|1.0|totem|H.264 (High Profile) 
decoder|decoder-video/x-h264, level=(string)4.1, profile=(string)high (H.264 
(High Profile) decoder)
  ** Message: Automatic missing codec installation not supported (helper script 
missing)


  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.25.90.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 25 01:51:47 2017
  InstallationDate: Installed on 2017-08-20 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170818)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1711067] Re: totem is unable to play .mp4. and some .avi, works fine with .webm. Same videos are played successfully by VLC

2017-09-04 Thread Iain Lane

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

I think this is the same as bug #1712979. Thanks for reporting. If there
are still problems after you have that installed, please file a new bug.

** This bug has been marked a duplicate of bug 1712979
   Installation of missing plugins/codecs fails or  is gstreamer1.0-packagekit 
what's needed?

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

Title:
  totem is unable to play .mp4. and some .avi, works fine with .webm.
  Same videos are played successfully by VLC

Status in gstreamer1.0 package in Ubuntu:
  Incomplete

Bug description:
  Problem: totem is unable to play .avi and .mp4. works fine with .webm. Same 
videos are played successfully by VLC media player. totem does not crash, but 
just remains with a black screen.
  Another symptom (of same problem?) is avi and mp4 thumbnails are not resolved 
in images.
  I found the problem with an installation from daily 20170807 and have the 
same problem with daily 20170815. 
  How to reproduce problem: try open a .avi or .mp4 (with videos/totem) results 
in a black screen. Here the output starting it from terminal:

  corrado@corrado-HP-aa-0815:~$ cd /media/corrado/dati1/linux/ArtfulBugs/totem
  corrado@corrado-HP-aa-0815:/media/corrado/dati1/linux/ArtfulBugs/totem$ ls
  cagax.avi  prova  vid.mp4
  corrado@corrado-HP-aa-0815:/media/corrado/dati1/linux/ArtfulBugs/totem$ totem 
cagax.avi
  ** Message: Missing plugin: gstreamer|1.0|totem|MPEG-1 Layer 3 (MP3) 
decoder|decoder-audio/mpeg, mpegversion=(int)1, mpegaudioversion=(int)1, 
layer=(int)3 (MPEG-1 Layer 3 (MP3) decoder)
  ** Message: Missing plugin: gstreamer|1.0|totem|MPEG-4 Video 
decoder|decoder-video/mpeg, mpegversion=(int)4, systemstream=(boolean)false 
(MPEG-4 Video decoder)
  ** Message: Automatic missing codec installation not supported (helper script 
missing)

  (totem:8899): Totem-WARNING **: Failed to reset the playback rate to 1.0
  corrado@corrado-HP-aa-0815:/media/corrado/dati1/linux/ArtfulBugs/totem$ totem 
vid.mp4
  ** Message: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC 
decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)1, 
base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder)
  ** Message: Missing plugin: gstreamer|1.0|totem|H.264 (Constrained Baseline 
Profile) decoder|decoder-video/x-h264, level=(string)3, 
profile=(string)constrained-baseline (H.264 (Constrained Baseline Profile) 
decoder)
  ** Message: Automatic missing codec installation not supported (helper script 
missing)

  (totem:8917): Totem-WARNING **: Failed to reset the playback rate to 1.0
  corrado@corrado-HP-aa-0815:/media/corrado/dati1/linux/ArtfulBugs/totem$ 

  corrado@corrado-HP-aa-0815:/media/corrado/dati1/linux/ArtfulBugs/totem$ apt 
policy totem
  totem:
Installed: 3.25.90.1-0ubuntu1
Candidate: 3.25.90.1-0ubuntu1
Version table:
   *** 3.25.90.1-0ubuntu1 100
  100 /var/lib/dpkg/status
  corrado@corrado-HP-aa-0815:/media/corrado/dati1/linux/ArtfulBugs/totem$ uname 
-a
  Linux corrado-HP-aa-0815 4.11.0-13-generic #19-Ubuntu SMP Thu Aug 3 15:14:11 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  corrado@corrado-HP-aa-0815:/media/corrado/dati1/linux/ArtfulBugs/totem$

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libgstreamer1.0-0 1.12.2-1
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Aug 16 10:00:26 2017
  InstallationDate: Installed on 2017-08-10 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170807)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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

[Desktop-packages] [Bug 1712979] Re: Installation of missing plugins/codecs fails or is gstreamer1.0-packagekit what's needed?

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

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Confirmed

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

Title:
  Installation of missing plugins/codecs fails or  is
  gstreamer1.0-packagekit what's needed?

Status in GNOME Software:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Test case:
  Fresh install
  Try to play any file requiring one or more gst plugins

  What happens:
  pop up informs plugin(s) missing, offers to 'find in software'
  Clicking on that option fails

  Ex.
  totem /home/doug/Videos/bbb_sunflower_1080p_30fps_normal.mp4
  ** Message: Missing plugin: gstreamer|1.0|totem|MPEG-1 Layer 3 (MP3) 
decoder|decoder-audio/mpeg, mpegversion=(int)1, mpegaudioversion=(int)1, 
layer=(int)3 (MPEG-1 Layer 3 (MP3) decoder)
  ** Message: Missing plugin: gstreamer|1.0|totem|AC-3 (ATSC A/52) 
decoder|decoder-audio/x-ac3 (AC-3 (ATSC A/52) decoder)
  ** Message: Missing plugin: gstreamer|1.0|totem|H.264 (High Profile) 
decoder|decoder-video/x-h264, level=(string)4.1, profile=(string)high (H.264 
(High Profile) decoder)
  ** Message: Automatic missing codec installation not supported (helper script 
missing)


  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.25.90.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 25 01:51:47 2017
  InstallationDate: Installed on 2017-08-20 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170818)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1713026] Re: pb with x org video driver ub 17.10 with video card geforce 1050

2017-09-04 Thread ROCHE

CONGRATULATIONS !

Update of this day make resolve bugs. I think it is with update on
Xserver video libraries...

A new bugs appear but It goes... Bug 1715008

A+

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

Title:
  pb with x org video driver ub 17.10 with video card geforce 1050

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  My pc Asus GL 753V core I7 7700

  Since ubuntu version 4.10.0.22  driver x org video bugs and pc don't start. 
only works on recovery mode. I upgrade on ubuntu 4.12.0.12 and same problem. 
  I change to nvidia amd driver and good working but no way to parameter 
colours video. screen was sad
  I change on nvidia driver to use intel graphic included and video crashed... 
No way to return in geforce mode. 
  nvidia prg on recovery don't propose possibility to change!

  I think that is a driver bug of x org video on version ubuntu of superior to 
4.10.0.21
  Good works on 4.10.0.21
  

  ! I Thought That is the problem of this bug :

  It's because Driver X Server video proposed with ubuntu don't work on
  my pc Asus GL753V core I7 7700. in recovery mode XServer x org video
  works. Driver AMD NVIDIA GE Force 1050 (NVIDIA binary driver version
  375.82) works in normal version but NOT in recovery mode  Using
  now Kernel 4.12.0.12

  Cordialement

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

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

[Desktop-packages] [Bug 1714810] Re: gnome-terminal shrinks window to nothing

Output of "lshw"

** Attachment added: "lshw"

https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1714810/+attachment/4944297/+files/hw.txt

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

Title:
gnome-terminal shrinks window to nothing

Status in gnome-terminal package in Ubuntu:
New

Bug description:
Using Ubuntu 17.04, vim, in gnome-terminal. Default everythings from
the desktop install, default Theme. The only change is the default
window size in the settings -- I have it at 149x48. This bug happens
even with the default 80x24 window size. The font is the default (not
overridden) Monospace Regular 12.

When running vim in gnome-terminal, there is an ugly margin of
terminal-background color on the right/bottom of the terminal window.
My vim background is gray, my terminal background is green, vim
displays gray background but there is a green border just slightly
slimmer than one character cell on the right/bottom. This also happens
for other terminal programs (including the shell) if they set the
background color of output.

In an attempt to at least make this less ugly, I tried to add some
padding to the terminal to center the drawable area that vim paints
with the background. I added the following to my gtk.css:

$ cat .config/gtk-3.0/gtk.css
vte-terminal {
padding: 8px 8px 5px 1px;
}

Now, when I open gnome-terminal, it keeps resizing itself to be
shorter in the Y axis, one line at a time, until it is only one line
high. It's almost like an animation of the window height, collapsing
the window to be very short. After it stops there, I can manually snap
the terminal to top/bottom edges of the screen, and it will stay
there, but trying to resize it will just keep shrinking the height.

This bug is about the resizing behavior. My totally uneducated guess
is that there's some off-by-one error when allocating space for the
terminal window contents. Terminal calculates contents, sets the
window, measures contents, decides to attempt to "snap" to size of
character cell, rounds down, window gets shorter, terminal measures
contents, decides to attempt to "snap" to size of character cell,
rounds down, window gets shorter, ...

If that is, indeed, the case, then the other bug (the ugly border) may
be caused by the same problem, but I will file a separate bug for
that.

$ lsb_release -rd
Description: Ubuntu 17.04
Release: 17.04

$ apt-cache policy gnome-terminal
gnome-terminal:
Installed: 3.20.2-1ubuntu8
Candidate: 3.20.2-1ubuntu8

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

[Desktop-packages] [Bug 1714810] Re: gnome-terminal shrinks window to nothing

output of "dpkg -l"

** Attachment added: "dpkg -l"

https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1714810/+attachment/4944298/+files/dpkg.txt

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

Title:
gnome-terminal shrinks window to nothing

Status in gnome-terminal package in Ubuntu:
New

In an attempt to at least make this less ugly, I tried to add some
padding to the terminal to center the drawable area that vim paints
with the background. I added the following to my gtk.css:

$ cat .config/gtk-3.0/gtk.css
vte-terminal {
padding: 8px 8px 5px 1px;
}

If that is, indeed, the case, then the other bug (the ugly border) may
be caused by the same problem, but I will file a separate bug for
that.

$ lsb_release -rd
Description: Ubuntu 17.04
Release: 17.04

$ apt-cache policy gnome-terminal
gnome-terminal:
Installed: 3.20.2-1ubuntu8
Candidate: 3.20.2-1ubuntu8

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

[Desktop-packages] [Bug 1714810] Re: gnome-terminal shrinks window to nothing

Thanks for your answer!

Yes, the ugly margin is there even when not maximizing the terminal and even
when not using a css override file. (I removed the css override so I can keep
working.)
I'm attaching a screen shot (the ugly border is only on the right side,
probably scroll bar related?)

Also worthy of note (sorry, spaced on this last time): I installed this as
Ubuntu Server, and then added the desktop by doing sudo apt install
ubuntu-desktop. I have also installed the NVIDIA CUDA tools, which installs the
NVIDIA 375 driver.
Interestingly, my control panels don't have any option to select default window
chrome sizes or font sizes, although the Terminal application itself does. I
wonder if ubuntu-desktop doesn't actually include *everything* it needs. (I
also noted that gnome-screenshot wasn't installed by default; I had to install
it manually.)

The version of ubuntu-desktop is 1.379 and the version of unity is
7.5.0+17.04.20170407.1-0ubuntu1

Regarding "symmetric" margins, the following padding does NOT cause the problem:
padding: 1px 1px 1px 1px;
The following padding DOES cause the problem:
padding: 2px 1px 1px 1px;

** Attachment added: "screen shot of ugly margin and versions"

https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1714810/+attachment/4944285/+files/Screenshot%20from%202017-09-04%2010-34-02.png

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

Title:
gnome-terminal shrinks window to nothing

Status in gnome-terminal package in Ubuntu:
New

In an attempt to at least make this less ugly, I tried to add some
padding to the terminal to center the drawable area that vim paints
with the background. I added the following to my gtk.css:

$ cat .config/gtk-3.0/gtk.css
vte-terminal {
padding: 8px 8px 5px 1px;
}

If that is, indeed, the case, then the other bug (the ugly border) may
be caused by the same problem, but I will file a separate bug for
that.

$ lsb_release -rd
Description: Ubuntu 17.04
Release: 17.04

$ apt-cache policy gnome-terminal
gnome-terminal:
Installed: 3.20.2-1ubuntu8
Candidate: 3.20.2-1ubuntu8

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

[Desktop-packages] [Bug 1703690] Re: Add support for Budgie Desktop using GNOME Screensaver

2017-09-04 Thread Iain Lane

Sponsored, thanks. For gnome-desktop3, I merged your patch into the
revert patch since I thought it made sense there. If that's too annoying
in future, someone can split it back out.

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

Title:
  Add support for Budgie Desktop using GNOME Screensaver

Status in gnome-desktop3 package in Ubuntu:
  Fix Released
Status in gnome-screensaver package in Ubuntu:
  In Progress

Bug description:
  Ubuntu Budgie and Budgie Desktop uses GNOME Screensaver for its lock-
  screen.

  It also uses gnome-control-center to control both the desktop
  background and the lock-screen background.

  GNOME Screensaver does not support gnome-control-center lock screen
  dialog - GNOME has changed to a gsettings path
  org.gnome.desktop.screensaver.  GNOME Screensaver is expecting the
  path org.gnome.desktop.background.

  To resolve this requires patches in two packages - gnome-screensaver
  and gnome-desktop3.

  1. GNOME Screensaver has been patched to support Budgie Desktop and 
gnome-control-center.
  Note - I've taken the opportunity to reuse the existing "Unity" patchwork 
which is now defunct (I believe) since Unity uses an alternative locking 
mechanism.  The lock-screen is styled as per the old "Unity" implementation 
before Unity 16.04 moved to the new lock screen.

  2. The consequence of making the requisite changes to GNOME
  Screensaver has unfortunately impacted gnome-desktop3.  gnome-desktop3
  has a Ubuntu specific patch to revert a GNOME upstream decision to
  remove a key called draw-background.  GNOME Screensaver calls a public
  function in gnome-desktop3 - the gsettings path causes a segmentation
  fault since draw-background does not exist in
  org.gnome.desktop.screensaver.  I have worked around this to check the
  path being called before pulling the draw-background key.

  All of this is explained in the dep3 headers of the two debdiff
  patches attached

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

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

[Desktop-packages] [Bug 1703690] Re: Add support for Budgie Desktop using GNOME Screensaver

This bug was fixed in the package gnome-desktop3 - 3.25.91.1-0ubuntu2

---
gnome-desktop3 (3.25.91.1-0ubuntu2) artful; urgency=medium

  * debian/patches/git_revert_draw_background.patch: Check
org.gnome.desktop.background explicitly, not via the passed-in GSettings.
We're passed different schemas, but DRAW_BACKGROUND is always there. Patch
from David Mohammed (LP: #1703690)

 -- Iain Lane   Mon, 04 Sep 2017 17:46:55
+0100

** Changed in: gnome-desktop3 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Add support for Budgie Desktop using GNOME Screensaver

Status in gnome-desktop3 package in Ubuntu:
  Fix Released
Status in gnome-screensaver package in Ubuntu:
  In Progress

Bug description:
  Ubuntu Budgie and Budgie Desktop uses GNOME Screensaver for its lock-
  screen.

  It also uses gnome-control-center to control both the desktop
  background and the lock-screen background.

  GNOME Screensaver does not support gnome-control-center lock screen
  dialog - GNOME has changed to a gsettings path
  org.gnome.desktop.screensaver.  GNOME Screensaver is expecting the
  path org.gnome.desktop.background.

  To resolve this requires patches in two packages - gnome-screensaver
  and gnome-desktop3.

  1. GNOME Screensaver has been patched to support Budgie Desktop and 
gnome-control-center.
  Note - I've taken the opportunity to reuse the existing "Unity" patchwork 
which is now defunct (I believe) since Unity uses an alternative locking 
mechanism.  The lock-screen is styled as per the old "Unity" implementation 
before Unity 16.04 moved to the new lock screen.

  2. The consequence of making the requisite changes to GNOME
  Screensaver has unfortunately impacted gnome-desktop3.  gnome-desktop3
  has a Ubuntu specific patch to revert a GNOME upstream decision to
  remove a key called draw-background.  GNOME Screensaver calls a public
  function in gnome-desktop3 - the gsettings path causes a segmentation
  fault since draw-background does not exist in
  org.gnome.desktop.screensaver.  I have worked around this to check the
  path being called before pulling the draw-background key.

  All of this is explained in the dep3 headers of the two debdiff
  patches attached

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

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

[Desktop-packages] [Bug 310053] Re: Devanagari text rendered incorrectly in VTE apps

2017-09-04 Thread arunj

It seems this is still not fixed! I am on Ubuntu 16.04 facing exactly
the same problem!

http://askubuntu.com/questions/8437/is-there-a-good-mono-spaced-font-
for-devanagari-script-in-the-terminal

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

Title:
  Devanagari text rendered incorrectly in VTE apps

Status in Gnome Virtual Terminal Emulator:
  New
Status in vte package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: libvte-common

  Under Ubuntu 8.10 Gnome-terminal and xfce-terminal incorrectly render
  devanagari script. Gedit (with the same font) renders the same text
  correctly. See example in screenshot. Using libvte 0.17.4-0ubuntu1.

  (Font is Liberation Mono in both applications).
  http://acm.jhu.edu/~me/devanagari-err.png

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

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

[Desktop-packages] [Bug 1715000] [NEW] No sound from internal spakers.

2017-09-04 Thread alberto.bicego

Public bug reported:

Hello,
I bought a Yashi all-in-one 64-bit pc 'Pioneer IPS AIO'  with Intel® Core™ 
i5-6400T CPU @ 2.20GHz × 4 and Intel® HD Graphics 530 (Skylake GT2). The 
machine had FreeDos and I installed Ubuntu 16.04 LTS.  

The sound works fine with headphones and external speakers, but I can
get no sound from internal speakers. The retailer could not help: he
says it is a problem of Linux with new hardware.

I looked for help here https://answers.launchpad.net/ubuntu/+source
/alsa-driver/+question/654230, but I could not solve my problem. The
internal speakers work fine with Windows 10 drivers, as I described
there, but I could not have them working with several versions of
Ubuntu, Mint, Arch.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  No sound from internal spakers.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello,
  I bought a Yashi all-in-one 64-bit pc 'Pioneer IPS AIO'  with Intel® Core™ 
i5-6400T CPU @ 2.20GHz × 4 and Intel® HD Graphics 530 (Skylake GT2). The 
machine had FreeDos and I installed Ubuntu 16.04 LTS.  

  The sound works fine with headphones and external speakers, but I can
  get no sound from internal speakers. The retailer could not help: he
  says it is a problem of Linux with new hardware.

  I looked for help here https://answers.launchpad.net/ubuntu/+source
  /alsa-driver/+question/654230, but I could not solve my problem. The
  internal speakers work fine with Windows 10 drivers, as I described
  there, but I could not have them working with several versions of
  Ubuntu, Mint, Arch.

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

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

[Desktop-packages] [Bug 1714766] Re: Software center apt failure at 15% when loading programs

2017-09-04 Thread Matthew Paul Thomas

** Package changed: software-center (Ubuntu) => apt (Ubuntu)

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

Title:
  Software center apt failure at 15% when loading programs

Status in apt package in Ubuntu:
  New

Bug description:
  I have just loaded the Ubuntu from LINUX format July 2017 edition,
  onto my wifes computer. I tried to load a DVD player onto the computer
  (a Lenovo ideapad 305) and every program that I try fails at 15% with
  an error "apt exception failure", I have since gone to the room above
  the room I was in (where the router is) and have managed to load VLC
  player without a problem. Any ideas why and how I can make it easier
  to use WiFi in all rooms in my semi-detached 3 bed house. I wondered
  if it was the software or the computer (which has just been bought,
  pre-installed with Windows 10. Widows 10 has been totally removed as
  it refused to allow dual boot.

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

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

[Desktop-packages] [Bug 960096] Re: Live session started with wrong layout

2017-09-04 Thread Colin Watson

** Attachment removed: "C5C731355480F854.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/libxklavier/+bug/960096/+attachment/4943864/+files/C5C731355480F854.jpg

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

Title:
  Live session started with wrong layout

Status in libxklavier:
  Confirmed
Status in libxklavier package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released

Bug description:
  Hello

  TESTCASE

  - Boot a usb with persistence live session
  - Select italian and set the network manager, everythings is OK.
  - Select -Prova Ubuntu- let it load
  - The session will be started with the english layout.

  **WORKAROUND**
  -System Settings -> keyboard layout -> click reset to defaults

  see attached screenshot, the language is italian (installa ubuntu) but
  the layout is wrong

  ProblemType: BugDistroRelease: Ubuntu 12.04
  Package: casper 1.312
  ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
  Uname: Linux 3.2.0-19-generic x86_64
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.312
  Date: Tue Mar 20 11:00:47 2012LiveMediaBuild: Ubuntu 12.04 LTS "Precise 
Pangolin" - Alpha amd64 (20120320)
  ProcEnviron:
   TERM=xterm
   LANG=it_IT.UTF-8
   SHELL=/bin/bashSourcePackage: casper
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1538333] Re: AssertionError in manifest.py: assert filecount == len(self.files_changed)

2017-09-04 Thread Niklas Sombert

I've just experienced this bug on Zesty with duplicity 0.7.06-2ubuntu3.

I was doing a full backup when the underlying filesystem disappeared (partly my 
fault).
I remounted it and trying to resume the backup, but duplicity won't start with
Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1532, in 
with_tempdir(main)
  File "/usr/bin/duplicity", line 1526, in with_tempdir
fn()
  File "/usr/bin/duplicity", line 1380, in main
do_backup(action)
  File "/usr/bin/duplicity", line 1405, in do_backup
globals.archive_dir).set_values()
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 710, 
in set_values
self.get_backup_chains(partials + backend_filename_list)
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 835, 
in get_backup_chains
add_to_sets(f)
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 829, 
in add_to_sets
if new_set.add_filename(filename):
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 101, 
in add_filename
self.set_manifest(filename)
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 149, 
in set_manifest
self.set_files_changed()
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 128, 
in set_files_changed
mf = self.get_manifest()
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, 
in get_manifest
return self.get_local_manifest()
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 225, 
in get_local_manifest
return manifest.Manifest().from_string(manifest_buffer)
  File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 207, in 
from_string
assert filecount == len(self.files_changed)
AssertionError

This bug is marked as fixed but I haven't seen an update for Zesty. Did
I miss something?

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

Title:
  AssertionError in manifest.py: assert filecount ==
  len(self.files_changed)

Status in Duplicity:
  Fix Released
Status in duplicity package in Ubuntu:
  Confirmed
Status in duplicity source package in Zesty:
  Fix Released

Bug description:
  Duplicity was almost finishing a full backup to a FTP server. When I
  restarted the backup, the following error occured:

  root@MyMachine:~# duply MyProfile backup
  Start duply v1.11, time is 2016-01-26 23:38:21.
  Using profile '/root/.duply/MyProfile'.
  Using installed duplicity version 0.7.06, python 2.7.3, gpg 1.4.12 (Home: 
~/.gnupg), awk 'mawk 1.3.3 Nov 1996, Copyright (C) Michael D. Brennan', grep 
'grep (GNU grep) 2.12', bash 'GNU bash, Version 4.2.37(1)-release 
(i486-pc-linux-gnu)'.
  Autoset found secret key of first GPG_KEY entry '' for signing.
  Checking TEMP_DIR '/tmp' is a folder and writable (OK)
  Test - Encrypt to '' & Sign with '' (OK)
  Test - Decrypt (OK)
  Test - Compare (OK)
  Cleanup - Delete '/tmp/duply.16938.1453847902_*'(OK)

  --- Start running command PRE at 23:38:24.349 ---
  Skipping n/a script '/root/.duply/MyProfile/pre'.
  --- Finished state OK at 23:38:24.400 - Runtime 00:00:00.051 ---

  --- Start running command BKP at 23:38:24.447 ---
  LFTP version is 4.3.6
  Reading globbing filelist /root/.duply/MyProfile/exclude
  Local and Remote metadata are synchronized, no sync needed.
  Traceback (most recent call last):
File "/usr/local/bin/duplicity", line 1532, in 
  with_tempdir(main)
File "/usr/local/bin/duplicity", line 1526, in with_tempdir
  fn()
File "/usr/local/bin/duplicity", line 1380, in main
  do_backup(action)
File "/usr/local/bin/duplicity", line 1405, in do_backup
  globals.archive_dir).set_values()
File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", 
line 710, in set_values
  self.get_backup_chains(partials + backend_filename_list)
File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", 
line 835, in get_backup_chains
  add_to_sets(f)
File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", 
line 829, in add_to_sets
  if new_set.add_filename(filename):
File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", 
line 101, in add_filename
  self.set_manifest(filename)
File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", 
line 149, in set_manifest
  self.set_files_changed()
File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", 
line 128, in set_files_changed
  mf = self.get_manifest()
File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", 
line 250, in get_manifest
  return self.get_local_manifest()
File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", 
line 225, in get_local_manifest
  return

[Desktop-packages] [Bug 1694565] Re: llvm-toolchain-3.8 FTBFS in Artful due to gcc-6 ICE

2017-09-04 Thread Balint Reczey

All llvm packages seem to build since then (or fail to build due to
other reasons).

** Also affects: llvm-toolchain-4.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: llvm-toolchain-4.0 (Ubuntu)
   Status: New => Fix Released

** Changed in: llvm-toolchain-3.8 (Ubuntu)
   Status: New => Fix Released

** Changed in: gcc-7 (Ubuntu)
   Status: New => Fix Released

** Changed in: llvm-toolchain-3.8 (Ubuntu)
   Status: Fix Released => Invalid

** Changed in: llvm-toolchain-4.0 (Ubuntu)
   Status: Fix Released => Invalid

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

Title:
  llvm-toolchain-3.8 FTBFS in Artful due to gcc-6 ICE

Status in gcc-7 package in Ubuntu:
  Fix Released
Status in llvm-toolchain-3.8 package in Ubuntu:
  Invalid
Status in llvm-toolchain-4.0 package in Ubuntu:
  Invalid

Bug description:
  Rebuilding llvm-toolchain-3.8 1:3.8.1-23ubuntu3 failed on i386:

  ...
  [ 54%] Building CXX object 
tools/clang/lib/Sema/CMakeFiles/clangSema.dir/SemaEx
  prCXX.cpp.o
  cd /<>/build-llvm/tools/clang/lib/Sema && /usr/bin/g++-6   
-DCLANG
  _ENABLE_ARCMT -DCLANG_ENABLE_OBJC_REWRITER -DCLANG_ENABLE_STATIC_ANALYZER 
-D_GN
  U_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS 
-D__STDC_LIMIT_MACROS 
  -I/<>/build-llvm/tools/clang/lib/Sema 
-I/<>/tools/cla
  ng/lib/Sema -I/<>/tools/clang/include 
-I/<>/build-llv
  m/tools/clang/include -I/<>/build-llvm/include 
-I/<>/
  include  -std=c++0x -gsplit-dwarf -Wl,-fuse-ld=gold -fPIC 
-fvisibility-inlines-
  hidden -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual 
-Wno-missing-
  field-initializers -pedantic -Wno-long-long -Wno-maybe-uninitialized 
-Wdelete-n
  on-virtual-dtor -Wno-comment -std=c++11 -ffunction-sections -fdata-sections 
-fn
  o-common -Woverloaded-virtual -fno-strict-aliasing -O2 -g -DNDEBUG
-fno-exce
  ptions -o CMakeFiles/clangSema.dir/SemaExprCXX.cpp.o -c 
/<>/tools/
  clang/lib/Sema/SemaExprCXX.cpp
  ...
  g++-6: internal compiler error: Killed (program cc1plus)
  Please submit a full bug report,
  with preprocessed source if appropriate.
  See  for instructions.
  tools/clang/lib/Sema/CMakeFiles/clangSema.dir/build.make:689: recipe for 
target
   'tools/clang/lib/Sema/CMakeFiles/clangSema.dir/SemaExprCXX.cpp.o' failed
  make[4]: *** 
[tools/clang/lib/Sema/CMakeFiles/clangSema.dir/SemaExprCXX.cpp.o] 
  Error 4
  make[4]: *** Waiting for unfinished jobs
  make[4]: Leaving directory '/<>/build-llvm'
  CMakeFiles/Makefile2:24600: recipe for target 
'tools/clang/lib/Sema/CMakeFiles/
  clangSema.dir/all' failed
  make[3]: *** [tools/clang/lib/Sema/CMakeFiles/clangSema.dir/all] Error 2
  make[3]: Leaving directory '/<>/build-llvm'
  Makefile:152: recipe for target 'all' failed
  make[2]: *** [all] Error 2
  make[2]: Leaving directory '/<>/build-llvm'
  debian/rules:269: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 2
  make[1]: Leaving directory '/<>'
  debian/rules:150: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

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

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

[Desktop-packages] [Bug 1714810] Re: gnome-terminal shrinks window to nothing

You're using Unity7 as far as I tell from the video, is that correct?

I couldn't yet reproduce your problem, but I'll keep trying with some
different settings.

Could you please try with something "symmetrical" such as "8px 8px 5px
px" as well as "8px 8px 1px 1px"? This could help us locate whether the
horizontal and vertical paddings are mixed up somewhere in the source,
causing the problem.

"there is an ugly margin of terminal-background color on the
right/bottom of the terminal window" - Do you even have it without
adding a custom padding, and with non-fullscreen non-maximized terminal?
If so, that's probably related to the bug.

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

Title:
  gnome-terminal shrinks window to nothing

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Using Ubuntu 17.04, vim, in gnome-terminal. Default everythings from
  the desktop install, default Theme. The only change is the default
  window size in the settings -- I have it at 149x48. This bug happens
  even with the default 80x24 window size. The font is the default (not
  overridden) Monospace Regular 12.

  When running vim in gnome-terminal, there is an ugly margin of
  terminal-background color on the right/bottom of the terminal window.
  My vim background is gray, my terminal background is green, vim
  displays gray background but there is a green border just slightly
  slimmer than one character cell on the right/bottom. This also happens
  for other terminal programs (including the shell) if they set the
  background color of output.

  In an attempt to at least make this less ugly, I tried to add some
  padding to the terminal to center the drawable area that vim paints
  with the background. I added the following to my gtk.css:

  $ cat .config/gtk-3.0/gtk.css 
  vte-terminal {
  padding: 8px 8px 5px 1px;
  }

  Now, when I open gnome-terminal, it keeps resizing itself to be
  shorter in the Y axis, one line at a time, until it is only one line
  high. It's almost like an animation of the window height, collapsing
  the window to be very short. After it stops there, I can manually snap
  the terminal to top/bottom edges of the screen, and it will stay
  there, but trying to resize it will just keep shrinking the height.

  This bug is about the resizing behavior. My totally uneducated guess
  is that there's some off-by-one error when allocating space for the
  terminal window contents. Terminal calculates contents, sets the
  window, measures contents, decides to attempt to "snap" to size of
  character cell, rounds down, window gets shorter, terminal measures
  contents, decides to attempt to "snap" to size of character cell,
  rounds down, window gets shorter, ...

  If that is, indeed, the case, then the other bug (the ugly border) may
  be caused by the same problem, but I will file a separate bug for
  that.

  $ lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  $ apt-cache policy gnome-terminal
  gnome-terminal:
Installed: 3.20.2-1ubuntu8
Candidate: 3.20.2-1ubuntu8

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

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

[Desktop-packages] [Bug 1714920] Re: gnome-terminal.wrapper missing argument -x

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

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

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

Title:
  gnome-terminal.wrapper missing argument -x

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  When executing the wrapper with the -x option this is ignored and not
  forwarded to gnome-terminal. If you run directly gnome-terminal with
  the -x argument it works as expected.

  Just changing the line 58 at /usr/bin/gnome-terminal.wrapper
  from:
  elsif ($opt eq '-e')
  to:
  elsif ($opt eq '-e' or $opt eq '-x')
  fixes the problem without changing the '-e' argument behaviour.

  Ubuntu 17.04
  Gnome-terminal 3.20.2

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

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

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

2017-09-04 Thread cement_head

Public bug reported:

After last kernel upgrade, machine freezes running any kind of video,
doesn't always happen but is random.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-34.38~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-34-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
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: Mon Sep  4 11:58:31 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:2425]
InstallationDate: Installed on 2016-04-28 (493 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 045e:007d Microsoft Corp. Notebook Optical Mouse
 Bus 001 Device 003: ID 5986:068f Acer, Inc 
 Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System76, Inc. Lemur
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-34-generic 
root=UUID=52cc6985-56fb-43f9-8439-967a49db65bb ro quiet splash 
elevator=deadline vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/29/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.06RS76
dmi.board.asset.tag: Tag 12345
dmi.board.name: Lemur
dmi.board.vendor: System76, Inc.
dmi.board.version: lemu6
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06RS76:bd11/29/2015:svnSystem76,Inc.:pnLemur:pvrlemu6:rvnSystem76,Inc.:rnLemur:rvrlemu6:cvnSystem76,Inc.:ct10:cvrN/A:
dmi.product.name: Lemur
dmi.product.version: lemu6
dmi.sys.vendor: System76, Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Mon Sep  4 11:57:12 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1~16.04.2
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 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/1714990

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  After last kernel upgrade, machine freezes running any kind of video,
  doesn't always happen but is random.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-34.38~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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: Mon Sep  4 11:58:31 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK

[Desktop-packages] [Bug 1555569] Update Released

The verification of the Stable Release Update for gnome-software has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Use 'title' field for snap apps

Status in Snapcraft:
  New
Status in Software Center Agent:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Won't Fix
Status in gnome-software source package in Zesty:
  Fix Released
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Snaps show using the snap 'name', which has a limited character set and is 
not translatable (e.g. 'moon-buggy'). The store contained a 'title' which is 
more appropriate (e.g. 'Moon Buggy') which was not exposed via snapd. Now snapd 
supports this field we should use it in GNOME Software.

  [Test Case]
  1. Start GNOME Software
  2. Search for 'moon'

  Expected result:
  A snap called 'Moon Buggy' is shown.

  Observed result:
  A snap called 'moon-buggy' is shown.

  [Regression Potential]
  The fix is to use the new field if it is present.

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

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

[Desktop-packages] [Bug 761478] Re: Enhancement: Prompt to check a busy file system on next reboot

** Changed in: gnome-disk-utility
   Status: In Progress => Fix Released

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

Title:
  Enhancement: Prompt to check a busy file system on next reboot

Status in GNOME Disks:
  Fix Released
Status in gnome-disk-utility package in Ubuntu:
  Confirmed
Status in Baltix:
  Confirmed

Bug description:
  Binary package hint: gnome-disk-utility

  When selecting "Check File System" on a file system which is is use,
  you currently get an error stating the device is busy.

  If a disk was busy, Disk Utility could prompt the user and ask if the
  file system should be scheduled for a check on the next reboot.

  I have just found out about the special file "/forcefsck"
  (http://www.cyberciti.biz/faq/linux-force-fsck-on-the-next-reboot-or-
  boot-sequence/) which forces the file system to be checked on the next
  reboot, and due to this I think this is a potentially simple
  implementation.  Disk Utility would just have to prompt and create
  that file.

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

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

[Desktop-packages] [Bug 1479710] Re: /usr/bin/gnome-disks:11:g_dbus_object_get_interface:udisks_object_peek_drive:gdu_window_select_object:create_partition_cb:g_task_return_now

** Changed in: gnome-disk-utility
   Status: Confirmed => Incomplete

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

Title:
  /usr/bin/gnome-
  
disks:11:g_dbus_object_get_interface:udisks_object_peek_drive:gdu_window_select_object:create_partition_cb:g_task_return_now

Status in GNOME Disks:
  Incomplete
Status in udisks:
  Confirmed
Status in gnome-disk-utility package in Ubuntu:
  Triaged
Status in udisks2 package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding gnome-disk-utility.  This problem was most recently seen
  with version 3.16.2-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/9ec0e4eaf2490589696da7e6514c5fc0507946b0
  contains more details.

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

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

[Desktop-packages] [Bug 519928] Re: Firefox incorrectly renders table borders when zooming

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

Title:
  Firefox incorrectly renders table borders when zooming

Status in Mozilla Firefox:
  In Progress
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: mozilla-firefox

  Steps to reproduce:
  1. Open Firefox
  2. Go to http://kossick.de/test.htm
  3. Zoom in and out (either using View -> Zoom, or Ctrl + Scroll)

  Expected Result:
  The table would retain its properties and still be rendered correctly, just 
larger or smaller in overall size.

  Observed Behavior:
  The borders of the table change thickness, sometimes disappearing because 
they get so thin.

  Confirmed on:
  Ubuntu 9.10 (64-bit), NVidia, Firefox 3.7
  Ubuntu 9.10 (64-bit), Intel, Firefox 3.6
  Ubuntu 9.10 (32-bit)
  Ubuntu 10.04 (alpha 2)

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

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

[Desktop-packages] [Bug 1555569] Re: Use 'title' field for snap apps

This bug was fixed in the package gnome-software -
3.22.7-0ubuntu3.17.04.7

---
gnome-software (3.22.7-0ubuntu3.17.04.7) zesty; urgency=medium

  * debian/patches/0001-snap-Use-title-field-if-available.patch:
- Use new title field from snapd (LP: #169)
  * debian/patches/0001-snap-Remove-size-limit-on-snap-responses.patch:
  * debian/patches/0002-snap-Fix-failures-to-read-from-snapd.patch:
- Fix icons larger than 65kB not loading (LP: #1704888)
  * debian/patches/0001-snap-Mark-non-app-snaps-as-runtimes.patch:
- Stop 'core' snap showing as an app (LP: #1704904)
  * debian/patches/0001-snap-Fix-crash-when-fail-to-use-icon-from-cache.patch:
- Add to debian/patches/series - was not enabled in last release
  * 
debian/patches/0001-snap-Replace-libsoup-icon-loading-code-with-AsIcon.patch:
- Fix crash loading cached icons (LP: #1708140)
  * debian/patches/0001-snap-Run-before-hardcoded-popular-plugin.patch:
  * 
debian/patches/0018-Make-gs_app_list_filter_duplicates-not-change-app-or.patch:
  * debian/patches/0019-snap-Use-first-featured-snap-as-featured-app.patch:
  * debian/patches/0020-snap-Only-feature-snaps.patch:
  * debian/patches/0021-Don-t-randomize-editors-picks.patch:
- Only show snaps in "Editor's picks" (LP: #1705953)
- Show snap in "Featured" section (LP: #1706478)

gnome-software (3.22.7-0ubuntu3.17.04.6) zesty; urgency=medium

  * 0001-snap-Fix-crash-when-fail-to-use-icon-from-cache.patch:
- Fix crash when failing to load icons from cache (LP: #1702122)

 -- Robert Ancell   Thu, 24 Aug 2017
13:46:31 +1200

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

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

Title:
  Use 'title' field for snap apps

Status in Snapcraft:
  New
Status in Software Center Agent:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Won't Fix
Status in gnome-software source package in Zesty:
  Fix Released
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Snaps show using the snap 'name', which has a limited character set and is 
not translatable (e.g. 'moon-buggy'). The store contained a 'title' which is 
more appropriate (e.g. 'Moon Buggy') which was not exposed via snapd. Now snapd 
supports this field we should use it in GNOME Software.

  [Test Case]
  1. Start GNOME Software
  2. Search for 'moon'

  Expected result:
  A snap called 'Moon Buggy' is shown.

  Observed result:
  A snap called 'moon-buggy' is shown.

  [Regression Potential]
  The fix is to use the new field if it is present.

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

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

[Desktop-packages] [Bug 1704888] Update Released

The verification of the Stable Release Update for gnome-software has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Doesn't download snap icons greater than 65kB

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Won't Fix
Status in gnome-software source package in Zesty:
  Fix Released
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Due to a hard-coded limitation in the gnome-software snap support it is 
unable to download icons greater than 65kB in size (e.g. pin-town).

  [Test Case]
  1. Install pin-town from the command line (sudo snap install pin-town
  2. Open GNOME Software
  3. Go to installed apps

  Expected result:
  pin-town is shown

  Observed result:
  pin-town is not shown (due to failure to download icon).

  [Regression Potential]
  Solution is to backport snapd code from gnome-software 3.24. This has a risk 
of introducing new bugs. The code has been used in 17.10.

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

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

[Desktop-packages] [Bug 1704904] Update Released

The verification of the Stable Release Update for gnome-software has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Shows 'core' snap as an application

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Won't Fix
Status in gnome-software source package in Zesty:
  Fix Released
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  GNOME Software shows the 'core' snap as an application. It should be 
correctly marked as a runtime so GNOME Software will display it more 
appropriately.

  [Test Case]
  1. Ensure at least one snap is installed so the core snap has been installed.
  2. Open GNOME Software.
  3. Browse to installed apps.

  Expected result:
  'core' is shown as an add-on.

  Observed result:
  'core' is shown in the app list.

  [Regression Potential]
  Fix is to tag the app object as a 'runtime' in GNOME Software based on the 
snap 'type' field. This could expose new bugs in the runtime code.

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

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

[Desktop-packages] [Bug 1708140] Update Released

The verification of the Stable Release Update for gnome-software has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  /usr/bin/gnome-
  
software:11:gs_plugin_snap_set_app_pixbuf_from_data:load_icon:gs_plugin_refine_app:gs_plugin_loader_run_refine:gs_plugin_loader_search_thread_cb

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Released
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  errors.ubuntu.com [1] is showing crashes in the icon caching code. Inspection 
and testing of this code doesn't show any reason why this code path can occur.

  [Test Case]
  1. Check errors.ubuntu.com for crash reports in the icon cache code

  Expected result:
  Errors do not occur.

  Observed result:
  Errors occur.

  [Regression Potential]
  Some risk of introducing new bugs in the icon handling code. The code is 
similar to what has been released into Artful, but needed to be modified to 
work with the older version of gnome-software in Xenial (the Zesty change is 
the same as Artful).

  [1]
  https://errors.ubuntu.com/problem/3a1f24323eae90094dc223360e9f0e56deb5e56d

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

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

[Desktop-packages] [Bug 1702122] Re: /usr/bin/gnome-software:11:load_icon:gs_plugin_refine_app:gs_plugin_loader_run_refine_app:gs_plugin_loader_run_refine_internal:gs_plugin_loader_run_refine

This bug was fixed in the package gnome-software -
3.22.7-0ubuntu3.17.04.7

---
gnome-software (3.22.7-0ubuntu3.17.04.7) zesty; urgency=medium

  * debian/patches/0001-snap-Use-title-field-if-available.patch:
- Use new title field from snapd (LP: #169)
  * debian/patches/0001-snap-Remove-size-limit-on-snap-responses.patch:
  * debian/patches/0002-snap-Fix-failures-to-read-from-snapd.patch:
- Fix icons larger than 65kB not loading (LP: #1704888)
  * debian/patches/0001-snap-Mark-non-app-snaps-as-runtimes.patch:
- Stop 'core' snap showing as an app (LP: #1704904)
  * debian/patches/0001-snap-Fix-crash-when-fail-to-use-icon-from-cache.patch:
- Add to debian/patches/series - was not enabled in last release
  * 
debian/patches/0001-snap-Replace-libsoup-icon-loading-code-with-AsIcon.patch:
- Fix crash loading cached icons (LP: #1708140)
  * debian/patches/0001-snap-Run-before-hardcoded-popular-plugin.patch:
  * 
debian/patches/0018-Make-gs_app_list_filter_duplicates-not-change-app-or.patch:
  * debian/patches/0019-snap-Use-first-featured-snap-as-featured-app.patch:
  * debian/patches/0020-snap-Only-feature-snaps.patch:
  * debian/patches/0021-Don-t-randomize-editors-picks.patch:
- Only show snaps in "Editor's picks" (LP: #1705953)
- Show snap in "Featured" section (LP: #1706478)

gnome-software (3.22.7-0ubuntu3.17.04.6) zesty; urgency=medium

  * 0001-snap-Fix-crash-when-fail-to-use-icon-from-cache.patch:
- Fix crash when failing to load icons from cache (LP: #1702122)

 -- Robert Ancell   Thu, 24 Aug 2017
13:46:31 +1200

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

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

Title:
  /usr/bin/gnome-
  
software:11:load_icon:gs_plugin_refine_app:gs_plugin_loader_run_refine_app:gs_plugin_loader_run_refine_internal:gs_plugin_loader_run_refine

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Zesty:
  Fix Released
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  The new icon cache code has a bug where it doesn't correctly handle errors 
loading from the cache. This was picked up in the error tracker [1].

  [1]
  https://errors.ubuntu.com/problem/bc8baf24512d0c46f341376c9134e4f04ec284d0

  [Test Case]
  1. Run GNOME Software

  Expected result:
  Crash doesn't show on errors.ubuntu.com

  Observed result:
  Crash shows on errors.ubuntu.com

  [Regression Potential]
  Fix was to use correct variable (typo). Seems unlikely to be able to cause 
new issues (though may unmask other issues by now working correctly).

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

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

[Desktop-packages] [Bug 1705953] Update Released

The verification of the Stable Release Update for gnome-software has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Show only snaps in "Editor's Picks"

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Released
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  The "Editor's Picks" section currently contains a mix of hard-coded values, 
values based on Ubuntu reviews and snaps from the "featured" snap store 
section. As snaps are the newest and preferred method of installing things in 
Ubuntu it should show only these in the order provided by snapd, falling back 
to the default behaviour if no snaps are found.

  [Test Case]
  1. Open GNOME Software
  2. Look at "Editor's Picks" section

  Expected result:
  This section contains the snaps from the "featured" snap store section in the 
correct order.

  Observed result:
  This section contains a mix of .deb and snaps. Some snaps may not be shown 
due to not being able to fit them all in. The order is random (changes daily).

  [Regression Potential]
  Solution is to add featured snaps last after clearing the existing featured 
apps. GNOME Software was modified to not randomize this list. Some risk of 
breaking related code.

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

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

[Desktop-packages] [Bug 1704888] Re: Doesn't download snap icons greater than 65kB

This bug was fixed in the package gnome-software -
3.22.7-0ubuntu3.17.04.7

---
gnome-software (3.22.7-0ubuntu3.17.04.7) zesty; urgency=medium

  * debian/patches/0001-snap-Use-title-field-if-available.patch:
- Use new title field from snapd (LP: #169)
  * debian/patches/0001-snap-Remove-size-limit-on-snap-responses.patch:
  * debian/patches/0002-snap-Fix-failures-to-read-from-snapd.patch:
- Fix icons larger than 65kB not loading (LP: #1704888)
  * debian/patches/0001-snap-Mark-non-app-snaps-as-runtimes.patch:
- Stop 'core' snap showing as an app (LP: #1704904)
  * debian/patches/0001-snap-Fix-crash-when-fail-to-use-icon-from-cache.patch:
- Add to debian/patches/series - was not enabled in last release
  * 
debian/patches/0001-snap-Replace-libsoup-icon-loading-code-with-AsIcon.patch:
- Fix crash loading cached icons (LP: #1708140)
  * debian/patches/0001-snap-Run-before-hardcoded-popular-plugin.patch:
  * 
debian/patches/0018-Make-gs_app_list_filter_duplicates-not-change-app-or.patch:
  * debian/patches/0019-snap-Use-first-featured-snap-as-featured-app.patch:
  * debian/patches/0020-snap-Only-feature-snaps.patch:
  * debian/patches/0021-Don-t-randomize-editors-picks.patch:
- Only show snaps in "Editor's picks" (LP: #1705953)
- Show snap in "Featured" section (LP: #1706478)

gnome-software (3.22.7-0ubuntu3.17.04.6) zesty; urgency=medium

  * 0001-snap-Fix-crash-when-fail-to-use-icon-from-cache.patch:
- Fix crash when failing to load icons from cache (LP: #1702122)

 -- Robert Ancell   Thu, 24 Aug 2017
13:46:31 +1200

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

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

Title:
  Doesn't download snap icons greater than 65kB

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Won't Fix
Status in gnome-software source package in Zesty:
  Fix Released
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Due to a hard-coded limitation in the gnome-software snap support it is 
unable to download icons greater than 65kB in size (e.g. pin-town).

  [Test Case]
  1. Install pin-town from the command line (sudo snap install pin-town
  2. Open GNOME Software
  3. Go to installed apps

  Expected result:
  pin-town is shown

  Observed result:
  pin-town is not shown (due to failure to download icon).

  [Regression Potential]
  Solution is to backport snapd code from gnome-software 3.24. This has a risk 
of introducing new bugs. The code has been used in 17.10.

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

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

[Desktop-packages] [Bug 1704904] Re: Shows 'core' snap as an application

This bug was fixed in the package gnome-software -
3.22.7-0ubuntu3.17.04.7

---
gnome-software (3.22.7-0ubuntu3.17.04.7) zesty; urgency=medium

  * debian/patches/0001-snap-Use-title-field-if-available.patch:
- Use new title field from snapd (LP: #169)
  * debian/patches/0001-snap-Remove-size-limit-on-snap-responses.patch:
  * debian/patches/0002-snap-Fix-failures-to-read-from-snapd.patch:
- Fix icons larger than 65kB not loading (LP: #1704888)
  * debian/patches/0001-snap-Mark-non-app-snaps-as-runtimes.patch:
- Stop 'core' snap showing as an app (LP: #1704904)
  * debian/patches/0001-snap-Fix-crash-when-fail-to-use-icon-from-cache.patch:
- Add to debian/patches/series - was not enabled in last release
  * 
debian/patches/0001-snap-Replace-libsoup-icon-loading-code-with-AsIcon.patch:
- Fix crash loading cached icons (LP: #1708140)
  * debian/patches/0001-snap-Run-before-hardcoded-popular-plugin.patch:
  * 
debian/patches/0018-Make-gs_app_list_filter_duplicates-not-change-app-or.patch:
  * debian/patches/0019-snap-Use-first-featured-snap-as-featured-app.patch:
  * debian/patches/0020-snap-Only-feature-snaps.patch:
  * debian/patches/0021-Don-t-randomize-editors-picks.patch:
- Only show snaps in "Editor's picks" (LP: #1705953)
- Show snap in "Featured" section (LP: #1706478)

gnome-software (3.22.7-0ubuntu3.17.04.6) zesty; urgency=medium

  * 0001-snap-Fix-crash-when-fail-to-use-icon-from-cache.patch:
- Fix crash when failing to load icons from cache (LP: #1702122)

 -- Robert Ancell   Thu, 24 Aug 2017
13:46:31 +1200

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

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

Title:
  Shows 'core' snap as an application

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Won't Fix
Status in gnome-software source package in Zesty:
  Fix Released
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  GNOME Software shows the 'core' snap as an application. It should be 
correctly marked as a runtime so GNOME Software will display it more 
appropriately.

  [Test Case]
  1. Ensure at least one snap is installed so the core snap has been installed.
  2. Open GNOME Software.
  3. Browse to installed apps.

  Expected result:
  'core' is shown as an add-on.

  Observed result:
  'core' is shown in the app list.

  [Regression Potential]
  Fix is to tag the app object as a 'runtime' in GNOME Software based on the 
snap 'type' field. This could expose new bugs in the runtime code.

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

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

[Desktop-packages] [Bug 1705953] Re: Show only snaps in "Editor's Picks"

This bug was fixed in the package gnome-software -
3.22.7-0ubuntu3.17.04.7

---
gnome-software (3.22.7-0ubuntu3.17.04.7) zesty; urgency=medium

  * debian/patches/0001-snap-Use-title-field-if-available.patch:
- Use new title field from snapd (LP: #169)
  * debian/patches/0001-snap-Remove-size-limit-on-snap-responses.patch:
  * debian/patches/0002-snap-Fix-failures-to-read-from-snapd.patch:
- Fix icons larger than 65kB not loading (LP: #1704888)
  * debian/patches/0001-snap-Mark-non-app-snaps-as-runtimes.patch:
- Stop 'core' snap showing as an app (LP: #1704904)
  * debian/patches/0001-snap-Fix-crash-when-fail-to-use-icon-from-cache.patch:
- Add to debian/patches/series - was not enabled in last release
  * 
debian/patches/0001-snap-Replace-libsoup-icon-loading-code-with-AsIcon.patch:
- Fix crash loading cached icons (LP: #1708140)
  * debian/patches/0001-snap-Run-before-hardcoded-popular-plugin.patch:
  * 
debian/patches/0018-Make-gs_app_list_filter_duplicates-not-change-app-or.patch:
  * debian/patches/0019-snap-Use-first-featured-snap-as-featured-app.patch:
  * debian/patches/0020-snap-Only-feature-snaps.patch:
  * debian/patches/0021-Don-t-randomize-editors-picks.patch:
- Only show snaps in "Editor's picks" (LP: #1705953)
- Show snap in "Featured" section (LP: #1706478)

gnome-software (3.22.7-0ubuntu3.17.04.6) zesty; urgency=medium

  * 0001-snap-Fix-crash-when-fail-to-use-icon-from-cache.patch:
- Fix crash when failing to load icons from cache (LP: #1702122)

 -- Robert Ancell   Thu, 24 Aug 2017
13:46:31 +1200

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

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

Title:
  Show only snaps in "Editor's Picks"

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Released
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  The "Editor's Picks" section currently contains a mix of hard-coded values, 
values based on Ubuntu reviews and snaps from the "featured" snap store 
section. As snaps are the newest and preferred method of installing things in 
Ubuntu it should show only these in the order provided by snapd, falling back 
to the default behaviour if no snaps are found.

  [Test Case]
  1. Open GNOME Software
  2. Look at "Editor's Picks" section

  Expected result:
  This section contains the snaps from the "featured" snap store section in the 
correct order.

  Observed result:
  This section contains a mix of .deb and snaps. Some snaps may not be shown 
due to not being able to fit them all in. The order is random (changes daily).

  [Regression Potential]
  Solution is to add featured snaps last after clearing the existing featured 
apps. GNOME Software was modified to not randomize this list. Some risk of 
breaking related code.

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

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

[Desktop-packages] [Bug 1706478] Re: Show promoted snap in "Featured" section

This bug was fixed in the package gnome-software -
3.22.7-0ubuntu3.17.04.7

---
gnome-software (3.22.7-0ubuntu3.17.04.7) zesty; urgency=medium

  * debian/patches/0001-snap-Use-title-field-if-available.patch:
- Use new title field from snapd (LP: #169)
  * debian/patches/0001-snap-Remove-size-limit-on-snap-responses.patch:
  * debian/patches/0002-snap-Fix-failures-to-read-from-snapd.patch:
- Fix icons larger than 65kB not loading (LP: #1704888)
  * debian/patches/0001-snap-Mark-non-app-snaps-as-runtimes.patch:
- Stop 'core' snap showing as an app (LP: #1704904)
  * debian/patches/0001-snap-Fix-crash-when-fail-to-use-icon-from-cache.patch:
- Add to debian/patches/series - was not enabled in last release
  * 
debian/patches/0001-snap-Replace-libsoup-icon-loading-code-with-AsIcon.patch:
- Fix crash loading cached icons (LP: #1708140)
  * debian/patches/0001-snap-Run-before-hardcoded-popular-plugin.patch:
  * 
debian/patches/0018-Make-gs_app_list_filter_duplicates-not-change-app-or.patch:
  * debian/patches/0019-snap-Use-first-featured-snap-as-featured-app.patch:
  * debian/patches/0020-snap-Only-feature-snaps.patch:
  * debian/patches/0021-Don-t-randomize-editors-picks.patch:
- Only show snaps in "Editor's picks" (LP: #1705953)
- Show snap in "Featured" section (LP: #1706478)

gnome-software (3.22.7-0ubuntu3.17.04.6) zesty; urgency=medium

  * 0001-snap-Fix-crash-when-fail-to-use-icon-from-cache.patch:
- Fix crash when failing to load icons from cache (LP: #1702122)

 -- Robert Ancell   Thu, 24 Aug 2017
13:46:31 +1200

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

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

Title:
  Show promoted snap in "Featured" section

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Released
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  The "Featured" banner only shows hard-coded .debs that are available. This 
should show the currently promoted snap.

  [Test Case]
  1. Open GNOME Software
  2. Look at featured section

  Expected result:
  The currently promoted snap is shown.

  Observed result:
  A hard-coded .deb is shown.

  [Regression Potential]
  The change is to use the first snap from the "featured" store section and 
show it here. If there is a screenshot with the name "banner" then this is used 
as the promotion image (and not shown in screenshots).

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

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

[Desktop-packages] [Bug 1706478] Update Released

The verification of the Stable Release Update for gnome-software has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Show promoted snap in "Featured" section

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Released
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  The "Featured" banner only shows hard-coded .debs that are available. This 
should show the currently promoted snap.

  [Test Case]
  1. Open GNOME Software
  2. Look at featured section

  Expected result:
  The currently promoted snap is shown.

  Observed result:
  A hard-coded .deb is shown.

  [Regression Potential]
  The change is to use the first snap from the "featured" store section and 
show it here. If there is a screenshot with the name "banner" then this is used 
as the promotion image (and not shown in screenshots).

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

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

[Desktop-packages] [Bug 1708140] Re: /usr/bin/gnome-software:11:gs_plugin_snap_set_app_pixbuf_from_data:load_icon:gs_plugin_refine_app:gs_plugin_loader_run_refine:gs_plugin_loader_search_thread_cb

This bug was fixed in the package gnome-software -
3.22.7-0ubuntu3.17.04.7

---
gnome-software (3.22.7-0ubuntu3.17.04.7) zesty; urgency=medium

  * debian/patches/0001-snap-Use-title-field-if-available.patch:
- Use new title field from snapd (LP: #169)
  * debian/patches/0001-snap-Remove-size-limit-on-snap-responses.patch:
  * debian/patches/0002-snap-Fix-failures-to-read-from-snapd.patch:
- Fix icons larger than 65kB not loading (LP: #1704888)
  * debian/patches/0001-snap-Mark-non-app-snaps-as-runtimes.patch:
- Stop 'core' snap showing as an app (LP: #1704904)
  * debian/patches/0001-snap-Fix-crash-when-fail-to-use-icon-from-cache.patch:
- Add to debian/patches/series - was not enabled in last release
  * 
debian/patches/0001-snap-Replace-libsoup-icon-loading-code-with-AsIcon.patch:
- Fix crash loading cached icons (LP: #1708140)
  * debian/patches/0001-snap-Run-before-hardcoded-popular-plugin.patch:
  * 
debian/patches/0018-Make-gs_app_list_filter_duplicates-not-change-app-or.patch:
  * debian/patches/0019-snap-Use-first-featured-snap-as-featured-app.patch:
  * debian/patches/0020-snap-Only-feature-snaps.patch:
  * debian/patches/0021-Don-t-randomize-editors-picks.patch:
- Only show snaps in "Editor's picks" (LP: #1705953)
- Show snap in "Featured" section (LP: #1706478)

gnome-software (3.22.7-0ubuntu3.17.04.6) zesty; urgency=medium

  * 0001-snap-Fix-crash-when-fail-to-use-icon-from-cache.patch:
- Fix crash when failing to load icons from cache (LP: #1702122)

 -- Robert Ancell   Thu, 24 Aug 2017
13:46:31 +1200

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

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

Title:
  /usr/bin/gnome-
  
software:11:gs_plugin_snap_set_app_pixbuf_from_data:load_icon:gs_plugin_refine_app:gs_plugin_loader_run_refine:gs_plugin_loader_search_thread_cb

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Released
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  errors.ubuntu.com [1] is showing crashes in the icon caching code. Inspection 
and testing of this code doesn't show any reason why this code path can occur.

  [Test Case]
  1. Check errors.ubuntu.com for crash reports in the icon cache code

  Expected result:
  Errors do not occur.

  Observed result:
  Errors occur.

  [Regression Potential]
  Some risk of introducing new bugs in the icon handling code. The code is 
similar to what has been released into Artful, but needed to be modified to 
work with the older version of gnome-software in Xenial (the Zesty change is 
the same as Artful).

  [1]
  https://errors.ubuntu.com/problem/3a1f24323eae90094dc223360e9f0e56deb5e56d

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

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

[Desktop-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

2017-09-04 Thread LocutusOfBorg

the question is more tricky

ettercap has the pkexec file
#!/bin/sh
pkexec --disable-internal-agent "ettercap" "$@"


but it is using a polkit file

http://www.freedesktop.org/standards/PolicyKit/1/policyconfig.dtd;>


  
Authentication is required to run Ettercap
ettercap

  auth_admin
  auth_admin
  auth_admin

@INSTALL_BINDIR@/ettercap
true
  




so, as upstream, I don't know what to do :(

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  New
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gufw package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  New
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  New
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  New
Status in ubuntustudio-default-settings package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  New
Status in zulucrypt package in Ubuntu:
  New

Bug description:
  Posting here what gnome says about porting to wayland, and their
  tests:

  GNOME Applications under Wayland
  GTK+ has a Wayland backend. If it was enabled at compile-time, you can run a 
GTK+ application under Wayland simply by:

  GDK_BACKEND=wayland gnome-calculator
  Applications that use Clutter or clutter-gtk also need the Clutter Wayland 
backend enabled:

  GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese

  https://wiki.gnome.org/Initiatives/Wayland/Applications

  ==> so hope the settings are well set at compile time; maybe a
  rebuilt to get sure all apps are ok.

  
  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful

[Desktop-packages] [Bug 1714312] Re: 'Ubuntu' starts an x11 session instead of wayland

2017-09-04 Thread Jean-Baptiste Lallement

I mean, if, after boot, I select wayland, then on next logins, the wayland 
session always starts whether I select X or Wayland. 
The same happens the other way around, if, after boot, I select xorg, then on 
next logins, the xorg session always starts whether I select X or Wayland. 

It is reproducible on real hardware, regularly upgraded, and in a
freshly installed VM.

I'll check if stopping pulseaudio makes a different.

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

Title:
  'Ubuntu' starts an x11 session instead of wayland

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  artful desktop up to date on real hardware

  Test Case
  1. In gdm select a user
  2. Click on the cog
    -> Verify the list of sessions available
  4. Select "Ubuntu" and log in
    -> Verify that wayland is running ($WAYLAND_DISPLAY is set)

  Expected Result
  At least "Ubuntu" and "Ubuntu on Xorg" are available
  Wayland is running

  Actual result
  Both entries start xorg instead of wayland. Sometimes it's the opposite, both 
entries start wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-session (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 31 18:59:31 2017
  InstallationDate: Installed on 2013-09-03 (1457 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by

2017-09-04 Thread Jon Stumpf

This affects me as well.  I have trace information in the attached syslog.  
Below are the outputs from:
   * lsb_release -a
   * apt-cache policy network-manager
   * hwinfo --netcard

- jss



$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename:   xenial

$ apt-cache policy network-manager
network-manager:
  Installed: 1.2.6-0ubuntu0.16.04.1
  Candidate: 1.2.6-0ubuntu0.16.04.1
  Version table:
 *** 1.2.6-0ubuntu0.16.04.1 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
100 /var/lib/dpkg/status
 1.2.2-0ubuntu0.16.04.4 500
500 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages
 1.1.93-0ubuntu4 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages

$ hwinfo --netcard
24: PCI 200.0: 0200 Ethernet controller 
  [Created at pci.366]
  Unique ID: rBUF.DLcddtZ5wl3
  Parent ID: z8Q3.lhbiXmvIKtB
  SysFS ID: /devices/pci:00/:00:1c.0/:02:00.0
  SysFS BusID: :02:00.0
  Hardware Class: network
  Model: "Lenovo ThinkPad X60/X60s"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x109a "82573L Gigabit Ethernet Controller"
  SubVendor: pci 0x17aa "Lenovo"
  SubDevice: pci 0x207e "ThinkPad X60/X60s"
  Driver: "e1000e"
  Driver Modules: "e1000e"
  Device File: eth0
  Memory Range: 0xee00-0xee01 (rw,non-prefetchable)
  I/O Ports: 0x2000-0x201f (rw)
  IRQ: 28 (1760 events)
  HW Address: 00:16:d3:31:a0:90
  Link detected: no
  Module Alias: "pci:v8086d109Asv17AAsd207Ebc02sc00i00"
  Driver Info #0:
Driver Status: e1000e is active
Driver Activation Cmd: "modprobe e1000e"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #10 (PCI bridge)

25: PCI 300.0: 0282 WLAN controller
  [Created at pci.366]
  Unique ID: y9sn.FZoxbnX_PE2
  Parent ID: qTvu.nWUCVv8jNeC
  SysFS ID: /devices/pci:00/:00:1c.1/:03:00.0
  SysFS BusID: :03:00.0
  Hardware Class: network
  Model: "Intel PRO/Wireless 3945ABG [Golan] Network Connection"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x4227 "PRO/Wireless 3945ABG [Golan] Network Connection"
  SubVendor: pci 0x8086 "Intel Corporation"
  SubDevice: pci 0x1010 
  Revision: 0x02
  Driver: "iwl3945"
  Driver Modules: "iwl3945"
  Device File: wlan0
  Features: WLAN
  Memory Range: 0xedf0-0xedf00fff (rw,non-prefetchable)
  IRQ: 31 (120102 events)
  HW Address: 00:18:de:66:4b:57
  Link detected: yes
  WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 149 153 157 
161 165
  WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 
2.462 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.745 5.765 5.785 5.805 5.825
  WLAN encryption modes: WEP40 WEP104 TKIP CCMP
  WLAN authentication modes: open sharedkey wpa-psk wpa-eap
  Module Alias: "pci:v8086d4227sv8086sd1010bc02sc80i00"
  Driver Info #0:
Driver Status: iwl3945 is active
Driver Activation Cmd: "modprobe iwl3945"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #11 (PCI bridge)


** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1408963/+attachment/4944203/+files/syslog

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

Title:
  [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945
  :03:00.0: BSM uCode verification failed at addr ...; wlan0:
  deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING),

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  From time to time, the system loses all wireles networks and kubuntu
  network manager applet goes blank - not even one network is shown. All
  wifi connections are broken. Rebooting fixes the issue, switching to
  WICD on-the-fly enables to continue browsing without rebooting, so it
  seems to be no hardware issue or iwl3945 issue.

  What to expect: stable connections and flawless network managing.
  What happens: so above.

  Further informations about the system, the network configuration, the
  package version can be found in the attachment, also parts of rsyslog
  and dmesg.

  Interesting, according to some helpers, are the following lines:
  dmesg:   wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice 
(Reason: 3=DEAUTH_LEAVING)

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

  apt-cache policy network-manager
  network-manager:
    Installiert:   0.9.8.8-0ubuntu28
    Installationskandidat: 0.9.8.8-0ubuntu28
    Versionstabelle:
   *** 0.9.8.8-0ubuntu28 0
  500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages

[Desktop-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while

2017-09-04 Thread João Marcos S . Scaramal

Bart van Deenen (bvdeenen)'s solution perfectly worked for me! Thank
you!

Dell Inspiron 7000 (7460)
Arch Linux
Linux 4.12.8-2-ARCH #1 SMP PREEMPT

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

Title:
[XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a
while

Status in alsa-driver package in Ubuntu:
Confirmed

Bug description:
I'm experiencing a strange behavior with a headphone jack on my
laptop.

I have an external audio speaker connected to it. When I disconnect the
speaker and reconnect it again it stops working.
Even more, laptop audio stops working too. And after the reboot, I don't even
see any of the audio devices.

I've googled a lot and tried different fixes from forums with no luck.
After a while, I've accidentally discovered that putting the laptop to
the sleep mode and rebooting system after brings audio back to live.
Even more, if speakers were attached during this sleep-reboot
procedure, they are starting to work as well.

However, after the next reboot speakers are not working again. And if
I will plug them out and in - problem with completely missing audio
returns.

P.S. I'm using laptop-mode-tools package on my laptop. Recovery after
hibernation made me believe that it's somehow related. But after
uninstalling this package nothing really changed.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: kop3224 F...m pulseaudio
/dev/snd/controlC0: kop3224 F pulseaudio
CurrentDesktop: Unity
Date: Tue Apr 26 12:17:03 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-04-22 (3 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Встроенное аудио - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Left
Symptom_Type: Sound works for a while, then breaks
Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after
a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/07/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.02.00
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.

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

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

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1714330
   gnome-shell crashed with SIGSEGV in on_crtc_flipped() from 
g_closure_invoke() from invoke_flip_closure() from page_flip_handler() from 
drmHandleEvent()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I don't know if this is related to why I still see issues from
  #1714295 or not.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Sep  4 09:39:52 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-07-23 (42 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7fbff1c15836:mov0x1a0(%rax),%rax
   PC (0x7fbff1c15836) ok
   source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   drmHandleEvent () from /usr/lib/x86_64-linux-gnu/libdrm.so.2
   meta_monitor_manager_kms_wait_for_flip () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1714979] [NEW] Dual screen via VGA crashes

2017-09-04 Thread alessio

Public bug reported:

Running Ubuntu 17.04, AMD HD 7420G.
I have difficulties in trying to configure an external monitor via VGA (HDMI 
works perfectly), the system crashes whenever I switch to extended mode. 
Sometimes I get one monitor switched on while the other off but never duplicate 
mode working perfectly nor extended mode. In the end the function never works.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: lightdm 1.22.0-0ubuntu2.1
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Mon Sep  4 16:25:17 2017
InstallationDate: Installed on 2017-04-08 (148 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Dual screen via VGA crashes

Status in lightdm package in Ubuntu:
  New

Bug description:
  Running Ubuntu 17.04, AMD HD 7420G.
  I have difficulties in trying to configure an external monitor via VGA (HDMI 
works perfectly), the system crashes whenever I switch to extended mode. 
Sometimes I get one monitor switched on while the other off but never duplicate 
mode working perfectly nor extended mode. In the end the function never works.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: lightdm 1.22.0-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Sep  4 16:25:17 2017
  InstallationDate: Installed on 2017-04-08 (148 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1713513] Re: notification for extensions keep reapearing

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

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

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

Title:
  notification for extensions keep reapearing

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  after installing lightdm and login in the guest session, all
  extensions with notifications restart a few times (at least two, most
  I've seen is 6) this only started happening after logging off and on
  again in the guest session. I couldn't find a way to solve this other
  than turning off the notifications of those extensions, I tested and
  even the standard extensions that come with Ubuntu Gnome 16.04 show
  the same issue

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

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

[Desktop-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

2017-09-04 Thread dino99

@LOB

as #2 explain, many gui apps fail to open under wayland (this is expected by 
wayland design, not working with pkexec)
So the transition to polkit is needed for these apps.

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  New
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gufw package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  New
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  New
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  New
Status in ubuntustudio-default-settings package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  New
Status in zulucrypt package in Ubuntu:
  New

Bug description:
  Posting here what gnome says about porting to wayland, and their
  tests:

  GNOME Applications under Wayland
  GTK+ has a Wayland backend. If it was enabled at compile-time, you can run a 
GTK+ application under Wayland simply by:

  GDK_BACKEND=wayland gnome-calculator
  Applications that use Clutter or clutter-gtk also need the Clutter Wayland 
backend enabled:

  GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese

  https://wiki.gnome.org/Initiatives/Wayland/Applications

  ==> so hope the settings are well set at compile time; maybe a
  rebuilt to get sure all apps are ok.

  
  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  PackageArchitecture: all
  SourcePackage: backintime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1714330] Re: gnome-shell crashed with SIGSEGV in on_crtc_flipped() from g_closure_invoke() from invoke_flip_closure() from page_flip_handler() from drmHandleEvent()

2017-09-04 Thread Julian Andres Klode

AFAICT, the bug really is still happening, it just happens a lot less,
see:

https://bugzilla.gnome.org/show_bug.cgi?id=787240

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

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

Title:
  gnome-shell crashed with SIGSEGV in on_crtc_flipped() from
  g_closure_invoke() from invoke_flip_closure() from page_flip_handler()
  from drmHandleEvent()

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

Bug description:
  https://errors.ubuntu.com/problem/196617236bfd49c847a208a8eda38e2bd701ca99

  ---

  Gnome shell crashes when trying to log in to the wayland ubuntu
  session. It works fine on Xorg.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Aug 31 11:39:23 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2017-07-27 (35 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170723)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fdee0bf9296:mov0x1a0(%rax),%rax
   PC (0x7fdee0bf9296) ok
   source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   drmHandleEvent () at /usr/lib/x86_64-linux-gnu/libdrm.so.2
   meta_monitor_manager_kms_wait_for_flip () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1710656] Re: Allow user to select power off button functionality

** Changed in: gnome-session (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Allow user to select power off button functionality

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  The power button suspends the computer. I read the developers deemed it 'too 
destructive'. That is a very questionable assumption.
   
  Is the user also considered incapable of deciding what s/he wants if the 
dialog to power off, restart, suspend or hibernate the system is displayed? 
Don't they think that some users might like to at least have the chance to 
configure the behavior in the configuration? What is the point of having a 
suspend and power off buttons in a computer if both do the same?

  Please configure the power button to display the dialog to restart,
  suspend, shutdown the computer, or at least make it easy to users to
  select that by using the dconf-editor tool.

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

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

[Desktop-packages] [Bug 1714312] Re: 'Ubuntu' starts an x11 session instead of wayland

I don't see the issue described in comment #3 here, the previous comment
is always confusing since it states "then this session will be used for
any subsequent logout/login whichever entry is selected in gdm." but in

"1. Boot your system
2. Select Xorg
  -> Xorg session starts
3. Logout and select Wayland
  -> Wayland session starts"

so the first session is not used for subsequent logins, or is that the
second one?

I wonder if it could have to do with
https://bugzilla.gnome.org/show_bug.cgi?id=785918 ... could you go to a
vt and stop the pulseaudio processes before logging in an see if that
makes a difference?

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

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

Title:
  'Ubuntu' starts an x11 session instead of wayland

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  artful desktop up to date on real hardware

  Test Case
  1. In gdm select a user
  2. Click on the cog
    -> Verify the list of sessions available
  4. Select "Ubuntu" and log in
    -> Verify that wayland is running ($WAYLAND_DISPLAY is set)

  Expected Result
  At least "Ubuntu" and "Ubuntu on Xorg" are available
  Wayland is running

  Actual result
  Both entries start xorg instead of wayland. Sometimes it's the opposite, both 
entries start wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-session (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 31 18:59:31 2017
  InstallationDate: Installed on 2013-09-03 (1457 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1713323] Re: HiDPI support partially broken after upgrade