date:20170915

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

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

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

Title:
  gpu-manager Error: can't open /lib/modules/

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  At least once a day there is an unexpected desktop freeze incl. mouse
  and keyboard. Even magic-sys-rq isn't possible, only hard switch-off.
  From smartmontools I can exclude a hardware failure.

  I've found that gpu-manager and systemd fail to load kernel modules.
  This is among the output of journalctl | grep modules
  Jan 10 13:12:34  systemd[1]: systemd-modules-load.service: Unit entered 
failed state.
  Jan 10 13:12:34  systemd[1]: systemd-modules-load.service: Failed with result 
'exit-code'.
  Jan 10 13:12:49  gpu-manager[791]: Error: can't open 
/lib/modules/4.4.0-57-generic/updates/dkms
  Jan 10 13:12:49  gpu-manager[791]: Error: can't open 
/lib/modules/4.4.0-57-generic/updates/dkms
  (terminal-output attached)

  dito with latest kernel

  Jan 11 07:53:04 gpu-manager[786]: Error: can't open 
/lib/modules/4.4.0-59-generic/updates/dkms
  Jan 11 07:53:04 gpu-manager[786]: Error: can't open 
/lib/modules/4.4.0-59-generic/updates/dkms

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-drivers-common 1:0.4.17.2
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 10 14:37:00 2017
  InstallationDate: Installed on 2012-02-05 (1801 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120204)
  SourcePackage: ubuntu-drivers-common
  UpgradeStatus: Upgraded to xenial on 2016-08-01 (162 days ago)

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

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

[Desktop-packages] [Bug 1705691] Re: sane-backends 1.0.27 has several RC bugs

2017-09-15 Thread Bug Watch Updater

** Changed in: sane-backends (Debian)
   Status: Fix Released => New

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

Title:
  sane-backends 1.0.27 has several RC bugs

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends package in Debian:
  New

Bug description:
  See these Debian bugs

  https://bugs.debian.org/868307 library package ships libtools .la files
  https://bugs.debian.org/868308 file conflict with libsane
  https://bugs.debian.org/868312 libsane1 package no longer ships a 
60-libsane.rules file

  This one has already been worked around in Ubuntu:
  https://bugs.debian.org/868309 src:sane-backends] FTBFS on various 
architectures due to missing symbols 9wo

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

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

[Desktop-packages] [Bug 1717634] [NEW] Logging in regular Gnome displays classical

2017-09-15 Thread Carlos Eduardo Moreira dos Santos

Public bug reported:

I'm running Ubuntu 17.04. I changed to Gnome classic in the login
screen, then logged in, logged out and chose regular Gnome, but I keep
logging in Gnome classic every time. A workaround is to run "gnome-shell
--mode=user -r" after every login.

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

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

Title:
  Logging in regular Gnome displays classical

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 17.04. I changed to Gnome classic in the login
  screen, then logged in, logged out and chose regular Gnome, but I keep
  logging in Gnome classic every time. A workaround is to run "gnome-
  shell --mode=user -r" after every login.

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

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

[Desktop-packages] [Bug 1704572] Re: package libnl-route-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: package libnl-route-3-200:amd64 is not ready for configuration cannot configure

[Expired for libnl3 (Ubuntu) because there has been no activity for 60
days.]

** Changed in: libnl3 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package libnl-route-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to
  install/upgrade: package libnl-route-3-200:amd64 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in libnl3 package in Ubuntu:
  Expired

Bug description:
  System update failed because this package could not be removed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libnl-route-3-200:amd64 3.2.27-1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  Date: Sat Jul 15 18:24:00 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
   libnl-3-200 3.2.27-1ubuntu0.16.04.1
  DuplicateSignature:
   package:libnl-route-3-200:amd64:3.2.27-1ubuntu0.16.04.1
   Processing triggers for gconf2 (3.2.6-3ubuntu6) ...
   dpkg: error processing package libnl-route-3-200:amd64 (--configure):
package libnl-route-3-200:amd64 is not ready for configuration
  ErrorMessage: package libnl-route-3-200:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2016-10-20 (267 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: libnl3
  Title: package libnl-route-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to 
install/upgrade: package libnl-route-3-200:amd64 is not ready for configuration 
 cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1210280] Re: libgtop2 used by system monitor reporting incorrect number of processors for Ubuntu 13.10 vms on Hyper-V

libgtop2 2.32.0 included in Ubuntu 16.04 LTS has bumped the CPU number
limit to 1024.

Therefore, I'm closing this bug since that is more than this bug
originally asked for and I'm skeptical whether tools using libgtop2 can
adequately work with more than 1024 CPUs anyway.

** Changed in: libgtop2 (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  libgtop2 used by system monitor reporting incorrect number of
  processors for Ubuntu 13.10 vms on Hyper-V

Status in libgtop:
  Confirmed
Status in libgtop2 package in Ubuntu:
  Fix Released
Status in libgtop2 source package in Saucy:
  Won't Fix

Bug description:
  We have noticed that when a Ubuntu 13.10 VM is configured with 64CPUs
  on Hyper-V, system monitor only shows 32 CPUs. This bug is also
  observed on Ubuntu 12.04. So it seems like an old issue. Please
  provide a fix.

  Attached are two files - One of the files is the output from system
  monitor and the other one contains the output from lscpu. System
  monitor output shows 32 CPUs whereas lscpu output shows the 64 CPUs
  correctly.

  Please let me know if you need more info.

  Thanks,
  Abhishek

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

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

[Desktop-packages] [Bug 1264368] Re: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c

2017-09-15 Thread chris pollock

I see the same in my Ubuntu 16.04.3

(gnome-shell:3000): GLib-CRITICAL **: Source ID 3572546 was not found
when attempting to remove it

Kernel 4.10.0-33-generic

apt-cache policy gnome-shell
gnome-shell:
  Installed: 3.18.5-0ubuntu0.3
  Candidate: 3.18.5-0ubuntu0.3

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

Title:
  GLib-CRITICAL **: Source ID was not found when attempting to remove it
  - warning when leaving Network menu of g-c-c

Status in AndroidSDK:
  New
Status in Banshee:
  New
Status in gnome-control-center:
  Incomplete
Status in GParted:
  Unknown
Status in notification-daemon:
  New
Status in anjuta package in Ubuntu:
  Confirmed
Status in consolekit package in Ubuntu:
  Confirmed
Status in f-spot package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in putty package in Ubuntu:
  Confirmed

Bug description:
  Steps to recreate:
  1. Open gnome-control-center in terminal.
  2. Go to Network.
  3. Go back to All preferences.
  4. Notice that in terminal there is a warning:

  $ gnome-control-center

  (gnome-control-center:13519): GLib-CRITICAL **: Source ID 166 was not
  found when attempting to remove it

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu49
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Dec 26 21:03:52 2013
  InstallationDate: Installed on 2013-10-15 (71 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131015)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to trusty on 2013-11-05 (51 days ago)

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

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

[Desktop-packages] [Bug 29355] Re: Can not sign on as su

2017-09-15 Thread dino99

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

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

Title:
  Can not sign on as su

Status in gnome-terminal package in Ubuntu:
  Invalid

Bug description:
  When log in as su at the terminal. the password in alway
  authornication failure. Is this a bug?

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

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

[Desktop-packages] [Bug 29355] Re: Can not sign on as su

2017-09-15 Thread john wickliffe

in the GNOME apt updaye manager:

this happened on 2 different machines when updating in ubuntu 17.10 daily 
install
one was:
HP Pavillion G series 4 gb ram Intel® Pentium(R) CPU P6300 @ 2.27GHz × 2
gnome 3.26.0 (desktop)
Ubuntu 17.10 due in October is nicknamed the “Artful Aardvark
the other laptop is:
Asus model X541SA 4gb ram Intell Pentium cpu N3710 1.60ghz x 4

after update I tried to do su in the GNOME Terminal (3.24.2) to run a 
filemanager
 as root and got a message :
 
"marcia@marcia-HP-Pavilion-g7-Notebook-PC:~$ su
Password:
su: Authentication failure"

got the same Authentication failure message after the update today
9/15/20017.

sudo works fine.
sudo worked fine before the update on both machines. I am going to get todays 
daily build nd reinstall Ubuntu 17.10 daily and see if it still has this 
problem.


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

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

Title:
  Can not sign on as su

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  When log in as su at the terminal. the password in alway
  authornication failure. Is this a bug?

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

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

[Desktop-packages] [Bug 1698198] Re: WARNING: CPU: 3 PID: 1367 at /build/linux-nOqmtv/linux-4.10.0/drivers/gpu/drm/nouveau/nouveau_bo.c:137 nouveau_bo_del_ttm+0x7f/0x90 [nouveau]

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

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

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

Title:
  WARNING: CPU: 3 PID: 1367 at /build/linux-
  nOqmtv/linux-4.10.0/drivers/gpu/drm/nouveau/nouveau_bo.c:137
  nouveau_bo_del_ttm+0x7f/0x90 [nouveau]

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

Bug description:
  Consider reading related bug here
  https://bugzilla.redhat.com/show_bug.cgi?id=1449961

  Bug 1449961 - nouveau: WARNING at drivers/gpu/drm/nouveau/nouveau_bo.c:137 
nouveau_bo_del_ttm+0x7f/0x90 
  This topic suggests to install version 1.0.14 or more recent 1.0.15

  --
  
https://cgit.freedesktop.org/nouveau/xf86-video-nouveau/commit/?id=924083938c8f209d8f6ff472caf8692a644f7e78

  The patch was in 1.0.14, but F24 never got that.  If you don't see
  1.0.15 in updates already, you can download it from koji[1].

  Ben.

  [1] https://koji.fedoraproject.org/koji/buildinfo?buildID=885031
  --
  The current version is 1.0.14 and the bug is still there

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7
  Date: Thu Jun 15 20:59:31 2017
  DistUpgraded: 2017-04-15 11:29:06,806 DEBUG icon theme changed, re-reading
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-20-generic, x86_64: installed
   bbswitch, 0.8, 4.10.0-21-generic, x86_64: installed
   bbswitch, 0.8, 4.10.0-22-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK208 [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell GK208 [GeForce GT 730] [1028:1083]
  InstallationDate: Installed on 2016-10-25 (233 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Inspiron 3650
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed 
root=UUID=e94af33a-7753-4118-9b90-7f5bb42dc49f ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to zesty on 2017-04-15 (61 days ago)
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.3.6
  dmi.board.name: 0C2XKD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.3.6:bd09/30/2016:svnDellInc.:pnInspiron3650:pvrX00:rvnDellInc.:rn0C2XKD:rvrA01:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.name: Inspiron 3650
  dmi.product.version: X00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Thu Jun 15 19:13:06 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1698198/+subscriptions

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

[Desktop-packages] [Bug 1717626] Re: gnome-control-center crashed with SIGSEGV

2017-09-15 Thread Seth Arnold

** Information type changed from Private Security to Public

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

Title:
  gnome-control-center crashed with SIGSEGV

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

Bug description:
  gnome-control-center crashed with SIGSEGV

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.0-0ubuntu1
  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: Fri Sep 15 22:08:33 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-09-14 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: gnome-control-center wifi
  SegvAnalysis:
   Segfault happened at: 0x7fd2b0a4b1d4:mov0x0(%rbp),%rdi
   PC (0x7fd2b0a4b1d4) ok
   source "0x0(%rbp)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libnm.so.0
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: Upgraded to artful on 2017-09-15 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1717623] Re: gimp-2.8 crashed with SIGSEGV in pango_ot_info_list_scripts()

2017-09-15 Thread Apport retracing service

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

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 #1694977, 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/1717623/+attachment/4950949/+files/CoreDump.gz

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

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

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

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

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

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

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

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

Title:
  gimp-2.8 crashed with SIGSEGV in pango_ot_info_list_scripts()

Status in gimp package in Ubuntu:
  New

Bug description:
  GIMP crash when we select font in the fonts tab.
  ubuntu 17.10 in wayland mode.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gimp 2.8.20-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
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 15 21:15:14 2017
  ExecutablePath: /usr/bin/gimp-2.8
  InstallationDate: Installed on 2017-06-08 (99 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170608)
  ProcCmdline: gimp-2.8
  SegvAnalysis:
   Segfault happened at: 0x7fd5b3ad934f :
mov0x20(%r12),%rdi
   PC (0x7fd5b3ad934f) ok
   source "0x20(%r12)" (0x0020) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gimp
  StacktraceTop:
   pango_ot_info_list_scripts () from 
/usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0
   ?? ()
   gimp_viewable_get_preview ()
   ?? ()
   gimp_viewable_get_pixbuf ()
  Title: gimp-2.8 crashed with SIGSEGV in pango_ot_info_list_scripts()
  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/gimp/+bug/1717623/+subscriptions

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

[Desktop-packages] [Bug 1717499] Re: gnome-software crashed with SIGSEGV in gs_app_kv_printf()

2017-09-15 Thread Seth Arnold

** Information type changed from Private Security to Public

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

Title:
  gnome-software crashed with SIGSEGV in gs_app_kv_printf()

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Error:org.freedesktop.DBus. "org.gnome.shell.Extensions" is absent to
  the path /org/gnome/shell

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.25.91-1ubuntu5
  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: Unity:Unity7:ubuntu
  Date: Thu Sep 14 21:07:40 2017
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2017-05-27 (110 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.25.91-1ubuntu5
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   LANGUAGE=el_GR
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: gnome-software
  StacktraceTop:
   ?? ()
   gs_app_to_string_append ()
   gs_app_to_string ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-software crashed with SIGSEGV in gs_app_to_string_append()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1717617] [NEW] [Inspiron 13-7359, Conexant CX20722, Speaker, Internal] No sound at all

2017-09-15 Thread Manikanta Bhagavatula

Public bug reported:

I am not able to listen to the sound on bootup and when I login I cannot
hear any sound on browser, not even the bubble pop sound that we
typically hear when the volume increase button is pressed. Kindly fix
this at the earliest. Thank you.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  manikanta   1980 F pulseaudio
CurrentDesktop: Unity
Date: Fri Sep 15 19:01:38 2017
InstallationDate: Installed on 2017-09-01 (14 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  manikanta   1980 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [Inspiron 13-7359, Conexant CX20722, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/25/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.06.00
dmi.board.name: 0WJF7F
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr01.06.00:bd02/25/2016:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0WJF7F:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 13-7359
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  [Inspiron 13-7359, Conexant CX20722, Speaker, Internal] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I am not able to listen to the sound on bootup and when I login I
  cannot hear any sound on browser, not even the bubble pop sound that
  we typically hear when the volume increase button is pressed. Kindly
  fix this at the earliest. Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  manikanta   1980 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 15 19:01:38 2017
  InstallationDate: Installed on 2017-09-01 (14 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  manikanta   1980 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Inspiron 13-7359, Conexant CX20722, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.06.00
  dmi.board.name: 0WJF7F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.06.00:bd02/25/2016:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0WJF7F:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1429535] Re: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed

2017-09-15 Thread Andrew Holmes

Please see the upstream bug:

https://bugzilla.gnome.org/show_bug.cgi?id=784278

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

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

Title:
  nautilus_menu_provider_get_background_items: assertion
  'NAUTILUS_IS_MENU_PROVIDER (provider)' failed

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Get that error from journalctl

  org.gnome.Nautilus[1518]: ** (nautilus:3572): CRITICAL **:
  nautilus_menu_provider_get_background_items: assertion
  'NAUTILUS_IS_MENU_PROVIDER (provider)' failed

  https://developer.gnome.org/libnautilus-extension/stable/libnautilus-
  extension-nautilus-menu-provider.html

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: nautilus 1:3.14.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Mar  8 09:35:05 2015
  GsettingsChanges:
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1676547] Re: No network connectivity after upgrade from 16.04 to 16.10

I've verified this is fixed with the version of network-manager in
zesty-proposed, using both the testcases (with and without nplan
installed).

** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty

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

Title:
  No network connectivity after upgrade from 16.04 to 16.10

Status in network-manager package in Ubuntu:
  In Progress
Status in network-manager source package in Yakkety:
  Fix Released
Status in network-manager source package in Zesty:
  Fix Committed

Bug description:
  Impact
  --
  When upgrading from Xenial (with all updates installed) to Yakkety/Zesty you 
will boot to a system without networking - sad!

  Test Case
  -
  1) Boot a xenial desktop system
  2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed
  3) Upgrade to yakkety or zesty
  3.5) Enable -proposed and download the new version of n-m "apt-get download 
network-manager"
  4) Reboot
  5) Observe you have no network

  If you install the version of network-manager from yakkety-proposed
  and then reboot you should have a network connection.

  1) Boot a xenial desktop system.
  2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed.
  3) Install nplan, configure to set up static network on an ethernet device 
using nplan.
  4) Upgrade to yakkety or zesty
  5) Reboot
  6) Observe that your system is still being managed by networkd rather than 
NetworkManager.

  Regression Potential
  

  Any failure to manage ethernet or wireless devices after upgrade, or
  issues with the use of netplan in conjunction with NetworkManager
  should be investigated as potential regressions. For example, if after
  upgrading, ethernet devices are no longer managed, or if devices that
  should be explicitly ignored by NetworkManager due to existing user
  configuration are now managed, these would indicate a possible
  regression caused by this update.

  Original Description
  

  nplan was installed during the upgrade process but I had no network
  connectivity after upgrading. Apparently, no package wanted to manage
  my ethernet connection.

  ProblemType: BugDistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.10
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Mar 27 11:34:04 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-16 (1531 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  PackageArchitecture: allSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago)
  VarLogDistupgradeTermlog:

  modified.conffile..etc.update-manager.meta-release: [modified]
  mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913

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

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

[Desktop-packages] [Bug 1698037] Re: Failed page loads sometimes redirect to about:blank instead of displaying errors

2017-09-15 Thread jeremy-list

Bug still present in 55.0.2+build1-0ubuntu0.17.04.1

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

Title:
  Failed page loads sometimes redirect to about:blank instead of
  displaying errors

Status in firefox package in Ubuntu:
  New

Bug description:
  To replicate:
  1: Use Firefox with an unstable internet connection
  2: Right-click a link and select "Open Link in New Tab" (the bug also occurs 
when navigating the current tab to a new page, but much less frequently)

  Expected results:
  The new tab should always contain one of the following:
  1: The new page, to the extent it has loaded
  2: An error message with a "retry" button

  Actual results:
  Sometimes instead of the error message: the tab will redirect to about:blank. 
This includes the address bar, so the only way to try again is to close the tab 
and try again from the initial page.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 53.0.3+build1-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.8.0-45.48~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-45-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeremy 1881 F pulseaudio
  BuildID: 20170524180630
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Thu Jun 15 14:15:15 2017
  EcryptfsInUse: Yes
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-03-04 (102 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0  proto static  metric 600 
   169.254.0.0/16 dev virbr0  scope link  metric 1000 linkdown 
   192.168.1.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.1.6  metric 
600 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
linkdown
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=53.0.3/20170524180630 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/07/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3JCN26WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K17763 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr3JCN26WW:bd03/07/2017:svnLENOVO:pn80TV:pvrLenovoideapad310-15IKB:rvnLENOVO:rnVIUU4:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrLenovoideapad310-15IKB:
  dmi.product.name: 80TV
  dmi.product.version: Lenovo ideapad 310-15IKB
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1676547] Re: No network connectivity after upgrade from 16.04 to 16.10

** Description changed:

  Impact
  --
  When upgrading from Xenial (with all updates installed) to Yakkety/Zesty you 
will boot to a system without networking - sad!
  
  Test Case
  -
  1) Boot a xenial desktop system
  2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed
  3) Upgrade to yakkety or zesty
  3.5) Enable -proposed and download the new version of n-m "apt-get download 
network-manager"
  4) Reboot
  5) Observe you have no network
  
  If you install the version of network-manager from yakkety-proposed and
  then reboot you should have a network connection.
  
  1) Boot a xenial desktop system.
  2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed.
- 3) Install netplan, configure to set up static network on an ethernet device 
using netplan.
+ 3) Install nplan, configure to set up static network on an ethernet device 
using nplan.
  4) Upgrade to yakkety or zesty
  5) Reboot
  6) Observe that your system is still being managed by networkd rather than 
NetworkManager.
  
  Regression Potential
  
  
  Any failure to manage ethernet or wireless devices after upgrade, or
  issues with the use of netplan in conjunction with NetworkManager should
  be investigated as potential regressions. For example, if after
  upgrading, ethernet devices are no longer managed, or if devices that
  should be explicitly ignored by NetworkManager due to existing user
  configuration are now managed, these would indicate a possible
  regression caused by this update.
  
  Original Description
  
  
  nplan was installed during the upgrade process but I had no network
  connectivity after upgrading. Apparently, no package wanted to manage my
  ethernet connection.
  
  ProblemType: BugDistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.10
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Mar 27 11:34:04 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-16 (1531 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  PackageArchitecture: allSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago)
  VarLogDistupgradeTermlog:
  
  modified.conffile..etc.update-manager.meta-release: [modified]
  mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913

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

Title:
  No network connectivity after upgrade from 16.04 to 16.10

Status in network-manager package in Ubuntu:
  In Progress
Status in network-manager source package in Yakkety:
  Fix Released
Status in network-manager source package in Zesty:
  Fix Committed

Bug description:
  Impact
  --
  When upgrading from Xenial (with all updates installed) to Yakkety/Zesty you 
will boot to a system without networking - sad!

  Test Case
  -
  1) Boot a xenial desktop system
  2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed
  3) Upgrade to yakkety or zesty
  3.5) Enable -proposed and download the new version of n-m "apt-get download 
network-manager"
  4) Reboot
  5) Observe you have no network

  If you install the version of network-manager from yakkety-proposed
  and then reboot you should have a network connection.

  1) Boot a xenial desktop system.
  2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed.
  3) Install nplan, configure to set up static network on an ethernet device 
using nplan.
  4) Upgrade to yakkety or zesty
  5) Reboot
  6) Observe that your system is still being managed by networkd rather than 
NetworkManager.

  Regression Potential
  

  Any failure to manage ethernet or wireless devices after upgrade, or
  issues with the use of netplan in conjunction with NetworkManager
  should be investigated as potential regressions. For example, if after
  upgrading, ethernet devices are no longer managed, or if devices that
  should be explicitly ignored by NetworkManager due to existing user
  configuration are now managed, these would indicate a possible
  regression caused by this update.

  Original Description
  

  nplan was installed during the upgrade process but I had no network
  connectivity after upgrading. Apparently, no package wanted to manage
  my ethernet connection.

  ProblemType: BugDistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.10
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux

[Desktop-packages] [Bug 1716068] Re: Gnome Shell crashes randomly

2017-09-15 Thread John Steeves

Thanks for the reply!

I'm not quite sure how to find the bug ID for the report sent in comment
#3. After running the "ubuntu-bug _usr_bin_gnome-shell.1000.crash"
command I saw a dialog asking to either "Examine Locally" or "Continue",
the latter of which I clicked (with the "Send error report" checkbox
marked). Nothing appeared on my screen after clicking "Continue" to give
me a report ID. Did I do something wrong when reporting the bug?

I ran "gnome-shell --replace" from the standard Gnome Terminal
(Ctrl+Alt+T) immediately before running the Software Updater, and the
"Segmentation Fault" error showed up in the Terminal window beside the
Software Updater window at the time of the crash. As the errors only
appeared in 16.04, 16.10 and 17.04 (which don't have Wayland) I was
using Xorg in these cases.

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

Title:
  Gnome Shell crashes randomly

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When using Ubuntu Gnome 16.04, it is common for gnome-shell to crash
  unexpectedly, especially when performing intensive tasks.

  
  I've found that I was able to replicate the error by following these steps:
  Download and install a copy of Ubuntu Gnome 16.04.2 in VirtualBox.
  Open a screen displaying App icons in a menu, such as the app grid in the 
Gnome Shell overlay or the Arc Menu Gnome Shell extension 
(https://extensions.gnome.org/extension/1228/arc-menu/).
  Install all the latest software updates from the Software Updater or Synaptic.
  Upgrading all the packages between 16.04.2 to 16.04.3 seems to over-load 
Gnome Shell and cause the crash in the middle of the installation process.
  This crash always seems to occur after opening a screen with app icons and 
I'm not sure why.

  
  I've attached my .crash file updated with a symbolic stack trace.I hope this 
info and my attachment proves helpful in fixing the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.5-0ubuntu0.3
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Sep  8 19:24:22 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['arc-m...@linxgem33.com']"
   b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 
'firefox.desktop', 'evolution.desktop', 'empathy.desktop', 'rhythmbox.desktop', 
'org.gnome.Photos.desktop', 'libreoffice-writer.desktop', 
'org.gnome.Nautilus.desktop', 'yelp.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-09-08 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  ProcEnviron:
   TERM=xterm-256color
   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/1716068/+subscriptions

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

[Desktop-packages] [Bug 1676547] Re: No network connectivity after upgrade from 16.04 to 16.10

** Description changed:

  Impact
  --
  When upgrading from Xenial (with all updates installed) to Yakkety/Zesty you 
will boot to a system without networking - sad!
  
  Test Case
  -
  1) Boot a xenial desktop system
  2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed
  3) Upgrade to yakkety or zesty
+ 3.5) Enable -proposed and download the new version of n-m "apt-get download 
network-manager"
  4) Reboot
  5) Observe you have no network
  
- If you install the version of network-manager from yakkety-proposed
- before rebooting you should have a network connection after you reboot.
+ If you install the version of network-manager from yakkety-proposed and
+ then reboot you should have a network connection.
  
  1) Boot a xenial desktop system.
  2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed.
  3) Install netplan, configure to set up static network on an ethernet device 
using netplan.
  4) Upgrade to yakkety or zesty
  5) Reboot
  6) Observe that your system is still being managed by networkd rather than 
NetworkManager.
  
  Regression Potential
  
  
  Any failure to manage ethernet or wireless devices after upgrade, or
  issues with the use of netplan in conjunction with NetworkManager should
  be investigated as potential regressions. For example, if after
  upgrading, ethernet devices are no longer managed, or if devices that
  should be explicitly ignored by NetworkManager due to existing user
  configuration are now managed, these would indicate a possible
  regression caused by this update.
  
  Original Description
  
  
  nplan was installed during the upgrade process but I had no network
  connectivity after upgrading. Apparently, no package wanted to manage my
  ethernet connection.
  
  ProblemType: BugDistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.10
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Mar 27 11:34:04 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-16 (1531 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  PackageArchitecture: allSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago)
  VarLogDistupgradeTermlog:
  
  modified.conffile..etc.update-manager.meta-release: [modified]
  mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913

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

Title:
  No network connectivity after upgrade from 16.04 to 16.10

Status in network-manager package in Ubuntu:
  In Progress
Status in network-manager source package in Yakkety:
  Fix Released
Status in network-manager source package in Zesty:
  Fix Committed

Bug description:
  Impact
  --
  When upgrading from Xenial (with all updates installed) to Yakkety/Zesty you 
will boot to a system without networking - sad!

  Test Case
  -
  1) Boot a xenial desktop system
  2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed
  3) Upgrade to yakkety or zesty
  3.5) Enable -proposed and download the new version of n-m "apt-get download 
network-manager"
  4) Reboot
  5) Observe you have no network

  If you install the version of network-manager from yakkety-proposed
  and then reboot you should have a network connection.

  1) Boot a xenial desktop system.
  2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed.
  3) Install netplan, configure to set up static network on an ethernet device 
using netplan.
  4) Upgrade to yakkety or zesty
  5) Reboot
  6) Observe that your system is still being managed by networkd rather than 
NetworkManager.

  Regression Potential
  

  Any failure to manage ethernet or wireless devices after upgrade, or
  issues with the use of netplan in conjunction with NetworkManager
  should be investigated as potential regressions. For example, if after
  upgrading, ethernet devices are no longer managed, or if devices that
  should be explicitly ignored by NetworkManager due to existing user
  configuration are now managed, these would indicate a possible
  regression caused by this update.

  Original Description
  

  nplan was installed during the upgrade process but I had no network
  connectivity after upgrading. Apparently, no package wanted to manage
  my ethernet connection.

  ProblemType: BugDistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.10
  ProcVersionSignature:

[Desktop-packages] [Bug 1687194] Re: Bluetooth file send stopped after 17.04

** Package changed: gnome-bluetooth (Ubuntu) => bluedevil (Ubuntu)

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

Title:
  Bluetooth file send stopped after 17.04

Status in bluedevil package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Bluetooth file send stopped after upgrade to Kubuntu 17.04. It was
  working fine with Kubuntu 16.10. "bluedevil-sendfile" hinted obex not
  running.

  $bluedevil-sendfile
  bluedevil.sendfile: Device ""
  bluedevil.sendfile: Files ()
  BluezQt: PendingCall Error: "Unit dbus-org.bluez.obex.service not found."
  bluedevil.sendfile: Manager initialized

  Then the following command solved the issue (but requires this extra
  step in every boot):

  $systemctl --user start obex

  Someone hinted "obexd should be dependency for bluedevil, you should
  file a bug against ubuntu packages." --
  https://bugs.kde.org/show_bug.cgi?id=379025#c3

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

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

[Desktop-packages] [Bug 1713347] Re: Firefox highligts textarea on mouse click (focus) in orange, it distracts user

This is already fixed in the current version of Firefox which will be
available as a security update before Ubuntu 17.10 is released.

There are a few workarounds for now to get the current version of
Firefox in Ubuntu 17.10 if you really need it.

One is to manually enable the zesty-security archive.

Another is to use the firefox-next PPA to try out the next (beta)
version of Firefox.

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

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

Title:
  Firefox highligts textarea on mouse click (focus) in orange, it
  distracts user

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 17.10.
  2. Launch Firefox
  3. Open website with textarea (for example launchpad).
  4. Click on textarea to start typing.
  5. Textarea fills with orange background color and it distracts user (see 
screenshot).

  Expected results:
  Textarea has white (or other defined background), which does not change on 
mouse click.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: firefox 50.1.0+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  artful 1762 F pulseaudio
  BuildID: 20161213224650
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 27 20:29:36 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  IpRoute:
   default via 192.168.3.1 dev wlp2s0 proto static metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.3.0/24 dev wlp2s0 proto kernel scope link src 192.168.3.15 metric 600
  Locales: extensions.sqlite corrupt or missing
  Plugins:
   GNOME Shell Integration - 
/usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so (gnome-shell)
   Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources:
   /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js
   prefs.js
  Profiles: Profile0 (Default) - LastVersion=50.1.0/20161213224650 (In use)
  RelatedPackageVersions: gnome-shell 3.24.3-0ubuntu4
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1709823] Re: Installation of libgles1-mesa (12.0.6-0ubuntu0.16.04.1) failed

2017-09-15 Thread Thomas

It seams to me not fixed or again broken:

root@vdr:~# LANG=C apt-get install libgles1-mesa
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libgles1-mesa : Depends: libglapi-mesa (= 12.0.6-0ubuntu0.16.04.1) but 
17.0.7-0ubuntu0.16.04.1 is to be installed
E: Unable to correct problems, you have held broken packages.

root@vdr:~# LANG=C apt-cache policy libgles1-mesa
libgles1-mesa:
  Installed: (none)
  Candidate: 12.0.6-0ubuntu0.16.04.1
  Version table:
 12.0.6-0ubuntu0.16.04.1 500
500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
 11.2.0-1ubuntu2 500
500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

root@vdr:~# LANG=C apt-cache policy libglapi-mesa
libglapi-mesa:
  Installed: 17.0.7-0ubuntu0.16.04.1
  Candidate: 17.0.7-0ubuntu0.16.04.1
  Version table:
 *** 17.0.7-0ubuntu0.16.04.1 500
500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 11.2.0-1ubuntu2 500
500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages


** Tags removed: verification-done-xenial
** Tags added: verification-needed-xenial

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

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

Title:
  Installation of libgles1-mesa (12.0.6-0ubuntu0.16.04.1) failed

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Xenial:
  Confirmed

Bug description:
  [Impact]
  Installation of libgles1-mesa (12.0.6-0ubuntu0.16.04.1) on Ubuntu 16.04 LTS 
failed - it needs the package libglapi-mesa (12.0.6-0buntu0.16.04.1), which 
does not exist. The current version of libglapi-mesa is 17.0.7-0ubuntu0.16.04.1 
(xenial-updates), which does not support the installation of libgles1-mesa.

  [Test case]
  Try to install the package from 
  
https://01.org/linuxgraphics/downloads/intel-graphics-update-tool-linux-os-v2.0.2

  [Regression potential]
  none, it just adds a dummy package to fix broken/unnecessary dependencies in 
3rd party packages

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

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

[Desktop-packages] [Bug 1717390] Re: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: problemas de dependencias - no se procesarán los disparadores

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

** This bug has been marked a duplicate of bug 1717085
   package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed

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

Title:
  package cracklib-runtime 2.9.2-5build1 failed to install/upgrade:
  problemas de dependencias - no se procesarán los disparadores

Status in cracklib2 package in Ubuntu:
  New

Bug description:
  It appears when I try to install language support

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: cracklib-runtime 2.9.2-5build1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Thu Sep 14 17:54:22 2017
  ErrorMessage: problemas de dependencias - no se procesarán los disparadores
  InstallationDate: Installed on 2017-09-14 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 
3.6.1-0ubuntu3
  PythonDetails: /usr/bin/python2.7, Python 2.7.14rc1, python-minimal, 2.7.13-2
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5~rc4
  SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: 
problemas de dependencias - no se procesarán los disparadores
  UpgradeStatus: Upgraded to artful on 2017-09-14 (0 days ago)

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

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

[Desktop-packages] [Bug 1717286] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: problemas de dependencias - no se procesarán los disparadores

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

** This bug has been marked a duplicate of bug 1717085
   package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed

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

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: problemas
  de dependencias - no se procesarán los disparadores

Status in cracklib2 package in Ubuntu:
  New

Bug description:
  It ocurred when a was installing Ubuntu Mate 17.10

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Thu Sep 14 10:56:01 2017
  ErrorMessage: problemas de dependencias - no se procesarán los disparadores
  InstallationDate: Installed on 2017-09-13 (1 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.4
  SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: problemas 
de dependencias - no se procesarán los disparadores
  UpgradeStatus: Upgraded to artful on 2017-09-14 (0 days ago)

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

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

[Desktop-packages] [Bug 1717573] [NEW] Bad query error when searching in GNOME Software

Public bug reported:

If a user types "=" into the search bar in GNOME Software when searching
for an application, he gets a "bad query" error instead of the actual
search results.

Steps to reproduce:
1. Open GNOME Software.
2. Type "someapp=".

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


** Tags: 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/1717573

Title:
  Bad query error when searching in GNOME Software

Status in gnome-software package in Ubuntu:
  New

Bug description:
  If a user types "=" into the search bar in GNOME Software when
  searching for an application, he gets a "bad query" error instead of
  the actual search results.

  Steps to reproduce:
  1. Open GNOME Software.
  2. Type "someapp=".

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

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

[Desktop-packages] [Bug 1717340] Re: [artful] Keyboard Logitech G15 doesn't work after logging in to gnome

Got it:

sep 15 19:39:45 mammut fwupd[2591]: failed to open: failed to ping G15 Gaming 
Keyboard: failed to receive: timeout
sep 15 19:39:45 mammut fwupd[2591]: failed to open: failed to ping G15 Gaming 
Keyboard: failed to send: failed to write: wrote -1 of 7
r

Uninstalling fwupd solves it.
Now let's see how to fix this properly...

** Package changed: gnome-shell (Ubuntu) => fwupd (Ubuntu)

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

Title:
  [artful] Keyboard Logitech G15 doesn't work after logging in to gnome

Status in fwupd package in Ubuntu:
  New

Bug description:
  After I type my password in GDM and come to the gnome desktop, no keys are 
working. Not even caps lock toggling.
  However, I found out that if I toggle "Slow keys" in the accessibility 
settings, it starts working again!
  To clarify, Slow keys and all other accessibility is disabled from start, but 
turning Slow keys on and off again makes my keyboard work.
  I seem to have to do this once after every _reboot_.

  This is on a system that has upgraded to Artful.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu5
  Uname: Linux 4.13.0-rc2+ x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 14 21:04:46 2017
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-08-29 (16 days ago)

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

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

[Desktop-packages] [Bug 1710373] Re: Desktop shortcut missing for Vino GUI in Ubuntu 17.10

This is an upstream issue: Vino VNC server does not support Wayland yet.

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

Title:
  Desktop shortcut missing for Vino GUI in Ubuntu 17.10

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

Bug description:
  There is not any possibility for an end user to configure screen
  sharing via VNC in Ubuntu 17.10. The "Desktop sharing" shortcut cannot
  be found in the GNOME Shell Overview and is also missing in the
  Sharing section of the GNOME Control Center.

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

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

[Desktop-packages] [Bug 1333700] Re: X locks after dragging file out of file-roller to pcmanfm

2017-09-15 Thread Mark

Another behaviour I tested: (see related bug
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1346984 )

* The freeze only occurs when I drag across the 'Places' side pane (the
one toggled by pressing F9). If I instead drag into the main area then
no freeze occurs.

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

Title:
  X locks after dragging file out of file-roller to pcmanfm

Status in file-roller package in Ubuntu:
  Invalid
Status in pcmanfm package in Ubuntu:
  Confirmed

Bug description:
  Looks to be a recurrence of https://bugs.launchpad.net/ubuntu/+source
  /file-roller/+bug/878993

  Dragging a file out of file-roller to pcmanfm sometimes results in the
  desktop locking up. Applications keep running but will not accept
  mouse input. Keyboard input mostly accepted, but not the space bar.

  Seen on Lubuntu 14.04 64 bit.

  -- Tim.

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

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

[Desktop-packages] [Bug 1702522] Re: "Software & Updates" string not marked for translation in Ubuntu 17.10

** Changed in: ubuntu-translations
   Status: New => 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/1702522

Title:
  "Software & Updates" string not marked for translation in Ubuntu 17.10

Status in GNOME Software:
  Confirmed
Status in Ubuntu Translations:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released

Bug description:
  The "Software & Updates" string is not marked for translation in
  Ubuntu 17.10.

  
https://translations.launchpad.net/ubuntu/zesty/+source/gnome-software/+pots/gnome-software/cs/+translate?search=Software+%26+Updates
  
https://translations.launchpad.net/ubuntu/artful/+source/gnome-software/+pots/gnome-software/cs/+translate?search=Software+%26+Updates

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

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

[Desktop-packages] [Bug 1717340] Re: [artful] Keyboard Logitech G15 doesn't work after logging in to gnome

xinput when it's broken:

⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ Razer Razer DeathAdder Chroma id=10   [slave  pointer  (2)]
⎜   ↳ Razer Razer DeathAdder Chroma id=11   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Power Button  id=7[slave  keyboard (3)]
↳ G15 Gaming Keyboard   id=8[slave  keyboard (3)]
↳ G15 Gaming Keyboard   id=9[slave  keyboard (3)]
↳ Razer Razer DeathAdder Chroma id=12   [slave  keyboard (3)]
↳ G15 GamePanel LCD id=13   [slave  keyboard (3)]
↳ Eee PC WMI hotkeysid=14   [slave  keyboard (3)]
↳ Razer Razer DeathAdder Chroma id=15   [slave  keyboard (3)]

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

Title:
  [artful] Keyboard Logitech G15 doesn't work after logging in to gnome

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After I type my password in GDM and come to the gnome desktop, no keys are 
working. Not even caps lock toggling.
  However, I found out that if I toggle "Slow keys" in the accessibility 
settings, it starts working again!
  To clarify, Slow keys and all other accessibility is disabled from start, but 
turning Slow keys on and off again makes my keyboard work.
  I seem to have to do this once after every _reboot_.

  This is on a system that has upgraded to Artful.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu5
  Uname: Linux 4.13.0-rc2+ x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 14 21:04:46 2017
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-08-29 (16 days ago)

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

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

[Desktop-packages] [Bug 1717340] Re: [artful] Keyboard Logitech G15 doesn't work after logging in to gnome

Ok more clues. My keyboard is a Logitech G15 Gaming keyboard. It has lots of 
features, which present themselves to Linux as various devices. The regression 
somewhere around that.
And it's a userspace regression, the same kernel with Ubuntu 17.04 works fine.

If I connect a very plain USB keyboard that works fine, it's only the
G15 that's giving problems.

So here's xinput from a Ubuntu where it works:
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ Razer Razer DeathAdder Chroma id=10   [slave  pointer  (2)]
⎜   ↳ Razer Razer DeathAdder Chroma id=11   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Power Button  id=7[slave  keyboard (3)]
↳ G15 Gaming Keyboard   id=8[slave  keyboard (3)]
↳ G15 Gaming Keyboard   id=9[slave  keyboard (3)]
↳ Razer Razer DeathAdder Chroma id=12   [slave  keyboard (3)]
↳ G15 GamePanel LCD id=13   [slave  keyboard (3)]
↳ Eee PC WMI hotkeysid=14   [slave  keyboard (3)]

** Summary changed:

- [artful] Keyboard doesn't work after logging in to gnome
+ [artful] Keyboard Logitech G15 doesn't work after logging in to gnome

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

Title:
  [artful] Keyboard Logitech G15 doesn't work after logging in to gnome

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After I type my password in GDM and come to the gnome desktop, no keys are 
working. Not even caps lock toggling.
  However, I found out that if I toggle "Slow keys" in the accessibility 
settings, it starts working again!
  To clarify, Slow keys and all other accessibility is disabled from start, but 
turning Slow keys on and off again makes my keyboard work.
  I seem to have to do this once after every _reboot_.

  This is on a system that has upgraded to Artful.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu5
  Uname: Linux 4.13.0-rc2+ x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 14 21:04:46 2017
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-08-29 (16 days ago)

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

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

[Desktop-packages] [Bug 1333700] Re: X locks after dragging file out of file-roller to pcmanfm

2017-09-15 Thread Mark

I am seeing this in a fresh install of Lubuntu 17.04 64-bit, also when
trying to unpack Tor browser 7.0.5 (
https://www.torproject.org/dist/torbrowser/7.0.5/tor-browser-linux64-7.0
.5_en-US.tar.xz ). I'm confirming the following characteristics
mentioned about this bug:

* Freeze triggers when mouse moves from file-roller to pcmanfm window.
* Mouse cursor movable but has locked icon, can't click on anything.
* Keyboard still works (can alt-tab between windows) but not spacebar or enter.
* Can do ctrl-alt-F1 to run 'killall file-roller' and unfreeze.

I downloaded the zip file from TimGS, above, and could drag-extract it
successfully the first time. But now on a second attempt it also causes
a freezing problem.

If it's relevant at all, this is on an Acer Aspire 5820TG laptop, with
encrypted disk.

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

Title:
  X locks after dragging file out of file-roller to pcmanfm

Status in file-roller package in Ubuntu:
  Invalid
Status in pcmanfm package in Ubuntu:
  Confirmed

Bug description:
  Looks to be a recurrence of https://bugs.launchpad.net/ubuntu/+source
  /file-roller/+bug/878993

  Dragging a file out of file-roller to pcmanfm sometimes results in the
  desktop locking up. Applications keep running but will not accept
  mouse input. Keyboard input mostly accepted, but not the space bar.

  Seen on Lubuntu 14.04 64 bit.

  -- Tim.

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

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

[Desktop-packages] [Bug 1717556] [NEW] Not installed itunes 12. Thank you.

2017-09-15 Thread Dmitry Levit

Public bug reported:

Not installed itunes 12. Thank you.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Sep 15 09:40:07 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:360b]
   Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:360b]
InstallationDate: Installed on 2017-05-28 (110 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
MachineType: Hewlett-Packard HP G60 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=/dev/mapper/ubuntu--vg-root ro splash quiet
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/15/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.65
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3612
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 09.67
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.65:bd12/15/2010:svnHewlett-Packard:pnHPG60NotebookPC:pvrPCID:rvnHewlett-Packard:rn3612:rvr09.67:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP G60 Notebook PC
dmi.product.version: PCID
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Fri Sep 15 08:32:53 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.1
xserver.video_driver: modeset

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


** Tags: apport-bug compiz-0.9 i386 ubuntu zesty

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

Title:
  Not installed itunes 12. Thank you.

Status in xorg package in Ubuntu:
  New

Bug description:
  Not installed itunes 12. Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Sep 15 09:40:07 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:360b]
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:360b]
  InstallationDate: Installed on 2017-05-28 (110 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  MachineType: Hewlett-Packard HP G60 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=/dev/mapper/ubuntu--vg-root ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/15/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.65
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3612
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 09.67
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias:

[Desktop-packages] [Bug 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low

2017-09-15 Thread Bug Watch Updater

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

** Changed in: gtk
   Importance: Unknown => Medium

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

Title:
  Totem pauses and stutters during video playback even when CPU usage is
  low

Status in GTK+:
  Confirmed
Status in Totem:
  Incomplete
Status in clutter-1.0 package in Ubuntu:
  Won't Fix
Status in clutter-gtk package in Ubuntu:
  In Progress
Status in gstreamer package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in totem package in Ubuntu:
  Fix Released

Bug description:
  Totem pauses and stutters during video playback even when CPU usage is
  low.

  After figuring out how to play videos with full hardware accelerated
  decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses
  and stutters during playback. Other apps like Mplayer, VLC and even
  gst-play-1.0 never have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:03:18 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 763894] Re: could not initialise Xv output

2017-09-15 Thread Vit

Have some problem and --xv switch not worked. It said: "Unknown option --xv"
but this worked: Go to Parole / Tools / Preferences / Video and change video 
output to other option.

Can anyone please fix this, i have 17.04 xubuntu, i selected Xubuntu
minimal, Xubuntu desktop during OS install. thx

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

Title:
  could not initialise Xv output

Status in gstreamer0.10 package in Ubuntu:
  Confirmed

Bug description:
  Parole  media player for the Xfce desktop environment not load  video
  files and send message:could not initialise Xv output

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: libgstreamer0.10-0 0.10.30-1build2
  ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11
  Uname: Linux 2.6.35-28-generic x86_64
  Architecture: amd64
  Date: Sun Apr 17 21:53:57 2011
  ExecutablePath: /usr/bin/totem
  InstallationMedia: Xubuntu 10.10 "Maverick Meerkat" - Release amd64 
(20101008.1)
  ProcEnviron:
   LANG=bg_BG.utf8
   SHELL=/bin/bash
  SourcePackage: gstreamer0.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/763894/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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()

2017-09-15 Thread Nicolás Abel Carbone

I still cannot login to ubuntu session using wayland. I have mutter 3.26.0-1. 
Is there a missing piece in the bug or should I report a new bug?
Thanks

-- 
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:
  Confirmed
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/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 1710370] Re: Cheese crashes on launch in Ubuntu 17.10 if no camera device is present

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

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

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

Status in cheese package in Ubuntu:
  Fix Released

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

2017-09-15 Thread Colin Law

@litinoveweedle this bug is marked fixed. If you are still seeing a
similar symptom then I suggest opening a new bug.

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

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

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

[Desktop-packages] [Bug 1717353] Re: dependancy problems with libgles1-mesa

2017-09-15 Thread Hans Joachim Desserud

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

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 1709823, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1709823
   Installation of libgles1-mesa (12.0.6-0ubuntu0.16.04.1) failed

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

Title:
  dependancy problems with libgles1-mesa

Status in mesa package in Ubuntu:
  New

Bug description:
  Hi,

  I wanted to install vlc from offical vlc ppa, but I cant install,
  because of a dependancy problems with libgles1-mesa.

  Hope it can be fixed.

  root@vdr:~# LANG=C apt-get install libgles1-mesa
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgles1-mesa : Depends: libglapi-mesa (= 12.0.6-0ubuntu0.16.04.1) but 
17.0.7-0ubuntu0.16.04.1 is to be installed
  E: Unable to correct problems, you have held broken packages.

  root@vdr:~# LANG=C apt-cache policy libgles1-mesa
  libgles1-mesa:
Installed: (none)
Candidate: 12.0.6-0ubuntu0.16.04.1
Version table:
   12.0.6-0ubuntu0.16.04.1 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   11.2.0-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  root@vdr:~# LANG=C apt-cache policy libglapi-mesa
  libglapi-mesa:
Installed: 17.0.7-0ubuntu0.16.04.1
Candidate: 17.0.7-0ubuntu0.16.04.1
Version table:
   *** 17.0.7-0ubuntu0.16.04.1 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   11.2.0-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgles1-mesa (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Sep 14 22:20:24 2017
  InstallationDate: Installed on 2017-09-09 (4 days ago)
  InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

2017-09-15 Thread litinoveweedle

Any updates for this one? After half year? on LTS? Are you serious?

Please note, that this bug #1672491 , ##1639776 and many other could be easily 
patched, just by applying patches:
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b
 
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=16800ea072dd0cdf14d951c4bb8d2808b3dfe53d

to dnsmasq package. If someone just could move the lazy ass and at least
follow other distros like Fedora
https://bugzilla.redhat.com/show_bug.cgi?id=1373485

I will post non constructive and frustrating post to all regarding bugs,
so hopefully someone will feel ashamed and finally fix it. Otherwise I
would like to ask you: step down as maintainers and orphan given package
so someone else who knows how to patch source could take over from you -
because you are doing no good by doing nothing!

** Bug watch added: Red Hat Bugzilla #1373485
   https://bugzilla.redhat.com/show_bug.cgi?id=1373485

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

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

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

[Desktop-packages] [Bug 1672491] Re: New NetworkManager breaks VPN DNS.

2017-09-15 Thread litinoveweedle

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

Any updates for this one? After half year? on LTS? Are you serious?

Please note, that this bug #1672491 , ##1639776 and many other could be easily
patched, just by applying patches:
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=16800ea072dd0cdf14d951c4bb8d2808b3dfe53d

to dnsmasq package. If someone just could move the lazy ass and at least
follow other distros like Fedora
https://bugzilla.redhat.com/show_bug.cgi?id=1373485

I will post non constructive and frustrating post to all regarding bugs,
so hopefully someone will feel ashamed and finally fix it. Otherwise I
would like to ask you: step down as maintainers and orphan given package
so someone else who knows how to patch source could take over from you -
because you are doing no good by doing nothing!

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

Title:
New NetworkManager breaks VPN DNS.

Status in network-manager package in Ubuntu:
Confirmed

Bug description:
Alright, this is going to be a frustrating bug for everyone involved I
expect, but here goes.

On Ubuntu 16.04, using a non-released VPN client (making this _much_
harder for anyone to reproduce), upgrading the network-manager
packages from 1.2.2-0ubuntu0.16.04.3 to 1.2.6-0ubuntu0.16.04.1 quite
handily broke DNS over the VPN.

And it broke it really oddly.

dnsmasq binds to socket 12 for the new interface, just fine.

strace shows that it does the sendto for the DNS request, and that the
poll calls are working, just fine.

tcpdump shows the response messages, they are coming back from the
correct host and port, going to my IP and the port that dnsmasq is
sending from.

There are no iptables rules involved, nothing is set to deny.

dnsmasq is never getting the response packet.

The request thus times out.

Doing a host or dig directly to the DNS server works just fine.

And this is completely reproducible, and goes away the moment I
downgrade back to 1.2.2-0ubuntu0.16.04.3.

Was there some change to how network-manager handles VPN
interfaces/tap0 in the new version?

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

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

[Desktop-packages] [Bug 1113420] Re: Alt+ window menu shortcuts cannot be disabled

2017-09-15 Thread Joshua Bearden

I just wanted to play games in Ubuntu. alt-e is a crucial keybind for me
in my favourite game. This little bug prevents me from playing.

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

Title:
  Alt+ window menu shortcuts cannot be disabled

Status in Unity:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  I find the  key ergonomically very useful (it can be pressed with
  a thumb without moving any of the "letter" fingers) and I would like
  to use it for many custom keyboard shortcuts (there is a reason why it
  plays such a big role in Emacs and the whole OS X for that matter).

  Currently, though,  is hardcoded to activate window menu entries
  (such as +F for the file menu, +E for the edit menu) and
  there is no way to surpass this functionality in all the applications.
  Personally, I find these shortcuts quite useless - they take you to
  "copy", "paste", and "open file" which have standard shortcuts anyway
  (with the exception of preferences, which for some reason don't have a
  standardized shortcut even though that's often the only thing a person
  looks for up there).

  Expected behaviour
  -

  What I would like to see is a global option to disable these alt+
  menu shortcuts to free up the  key for other uses (similar to the
  option already available in gnome-terminal, only global). Preferably,
  activating this option would also remove the first-letter underlining
  in the menu to indicate to users that they can't acess it through
  shortcuts.

  To reproduce:
  -

  - in Unity settings -> keyboard -> Shortcuts -> Launchers change the "Launch 
terminal" shortcut to ALT+T
  - hit -t, new terminial pops up
  - start Thunderbird or Okular, both of which have a "Tools" menu
  - note -t now opens the Tools menu
  - kill the application
  - hit -t, nothing happens

  (I marked nautilus for apport to collect my version numbers, but this
  affects most applications - didn't know what the right target is)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic x86_64
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  Date: Sat Feb  2 13:22:32 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'931x626+1+80'"
   b'org.gnome.nautilus.window-state' b'start-with-status-bar' b'true'
  InstallationDate: Installed on 2012-10-19 (106 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1717466] Re: Proxy settings are missing in apt.conf

I'm guessing you are using the gnome desktop environment, if not please
change the assigned package for this bug.

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

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

Title:
  Proxy settings are missing in apt.conf

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

Bug description:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  When proxies are set via network settings dialog this does not affect 
apt.conf.
  This results in software installation and upgrade problems.

  I had to specify proxies by adding "Acquire" in apt.conf.

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

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

[Desktop-packages] [Bug 1577879] Re: File save as dialog doesn't switch to keyed in path anymore when pressing enter

2017-09-15 Thread Walter Garcia-Fontes

I have tried this functionality in Ubuntu 17.10 with Unity and the
original behavior seems to be back. Can anybody confirm if this is still
an issue?

** Changed in: gtk
   Importance: Medium => Undecided

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

** Changed in: gtk
 Remote watch: GNOME Bug Tracker #766696 => None

** Changed in: gtk
   Status: New => Incomplete

** Changed in: gtk+3.0 (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  File save as dialog doesn't switch to keyed in path anymore when
  pressing enter

Status in GTK+:
  Incomplete
Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  Not sure if this is in Nautilus or a GTK package or something else..

  I run Unity as my desktop environment at the moment. With a recent
  update, the file save dialog presented to me by Firefox appears to
  have changed. I'm pretty sure it's an OS dialog and not a Firefox
  specific control, but please feel free to bounce this to whichever
  package is responsible for the File Save As dialog generated by
  Firefox 46.0 in Ubuntu now.

  In the past, when the save dialog came up, I was able to enter a path 
(absolute or relative) in the filename field:
  * If it was a directory path that existed, the directory contents would be 
shown inside the window, allowing me to then specify a name
  * If it was a directory path that didn't exist, it'd take me to the deepest 
part of the path that did match
  * If it was a directory that did exist, and a filename that didn't, it'd save 
as that filename in that folder

  The last is still true, but the others aren't anymore.. Say I have
  structure:

  home
  .../folder
  ../sub2
  ../sub3

  ... and I last saved into sub3 and I want to save into sub2, if I
  remove the filename from the name box, and I type ../sub2 and press
  enter, it doesn't navigate to the folder anymore.. The auto-complete
  function seems more reliable now, and it knows the folder exists, but
  the only way to actually show its contents now would be to click
  through the tree..

  This feels like a functionality downgrade. I should be able to type a
  pathname into the filename area of the dialog, press enter, and have
  it take me to that particular folder.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nautilus 1:3.14.2-0ubuntu13
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May  4 03:29:09 2016
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'group', 'where', 'mime_type', 
'owner', 'permissions', 'date_accessed']"
  InstallationDate: Installed on 2016-01-21 (103 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1717466] [NEW] Proxy settings are missing in apt.conf

You have been subscribed to a public bug:

Description:Ubuntu Artful Aardvark (development branch)
Release:17.10

When proxies are set via network settings dialog this does not affect apt.conf.
This results in software installation and upgrade problems.

I had to specify proxies by adding "Acquire" in apt.conf.

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


** Tags: artful bot-comment
-- 
Proxy settings are missing in apt.conf
https://bugs.launchpad.net/bugs/1717466
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-control-center in Ubuntu.

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

[Desktop-packages] [Bug 1715582] Re: deja-dup fails to backup

2017-09-15 Thread Michael Terry

Hrm.  Is it possible to share your /etc/samba/smb.conf?

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

Title:
  deja-dup fails to backup

Status in deja-dup package in Ubuntu:
  Fix Committed

Bug description:
  OS: Ubuntu 17.10 beta
  setting up deja-dup to backup to smb/ssh server fails

  With ssh: Permission denied
  syslog:
  Sep  7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from 
uid 1000 finished with success after 414ms

  
  with smb: Backup failed
  InvalidBackendURL: missing // - relative paths not supported for scheme 
gio+invalid: gio+invalid://
  syslog:
  Sep  7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from 
uid 1000 finished with success after 402ms

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 35.6-0ubuntu1
  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: Thu Sep  7 10:30:37 2017
  InstallationDate: Installed on 2017-09-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1715582] Re: deja-dup fails to backup

2017-09-15 Thread Michael Terry

(On the server of course)

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

Title:
  deja-dup fails to backup

Status in deja-dup package in Ubuntu:
  Fix Committed

Bug description:
  OS: Ubuntu 17.10 beta
  setting up deja-dup to backup to smb/ssh server fails

  With ssh: Permission denied
  syslog:
  Sep  7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from 
uid 1000 finished with success after 414ms

  
  with smb: Backup failed
  InvalidBackendURL: missing // - relative paths not supported for scheme 
gio+invalid: gio+invalid://
  syslog:
  Sep  7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from 
uid 1000 finished with success after 402ms

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 35.6-0ubuntu1
  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: Thu Sep  7 10:30:37 2017
  InstallationDate: Installed on 2017-09-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1715586] Re: Fix shrinking behavior in rrCheckPixmapBounding

Hello Kai-Heng, or anyone else affected,

Accepted xorg-server into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:1.18.4-0ubuntu0.5 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Also affects: xorg-server (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: xorg-server (Ubuntu Xenial)
   Status: New => In Progress

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

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

** Changed in: xorg-server (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-xenial

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

Title:
  Fix shrinking behavior in rrCheckPixmapBounding

Status in HWE Next:
  New
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  When using extended mode on an slave-output connected external monitor, 
RRSetCrtc calls rrCheckPixmapBounding, which shrinks the output area. It makes 
the slave-output configured to scan-out an area which completely falls outside 
of the screen-pixmap, and end up with
  a black display on the external monitor.

  We need these two commits:
  a46afee84d45fbff4e4dad9376afc95bbcc31d7c randr: rrCheckPixmapBounding: do not 
shrink the screen_pixmap
  3b624aa9a9df86dc7d48149e0f18ca223b4355f1 randr: rrCheckPixmapBounding: Do not 
substract crtc non 0 x,y from screen size

  [Test Case]
  Enable NVIDIA PRIME, plug an external monitor, and change to extended mode.

  [Regression Potential]
  There should be none, the shrinking behavior wasn't right at the first place.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1715586/+subscriptions

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

[Desktop-packages] [Bug 1710789] Re: chromium does not open downloaded files

2017-09-15 Thread wdoekes

Yeap, that fixes things. Thanks!

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

Title:
  chromium does not open downloaded files

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  I have up to date Ubuntu 17.04. Recently, Chromium stoped to open
  downloaded files.

  If i download and open doc file from chromium, in command line i see
  the following message:

  /usr/lib/libreoffice/program/soffice.bin: relocation error:
  /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: symbol
  mir_display_config_release, version MIR_CLIENT_0.21 not defined in
  file libmirclient.so.9 with link time reference

  If i download pdf file i see the same message with evince instead of
  libreoffice.

  It looks like more general problem, but I still can open files from
  these two applications or using xdg-open.

  I tried to work with new chromium profile, but i get the same message
  no matter what and files cannot be opened.

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

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

[Desktop-packages] [Bug 1717398] Re: incorrect file path in "/usr/share/apport/package-hooks/source_unity-settings-daemon.py"

2017-09-15 Thread Ubuntu Foundations Team Bug Bot

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

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

** Tags added: patch

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

Title:
  incorrect file path in "/usr/share/apport/package-hooks/source_unity-
  settings-daemon.py"

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

Bug description:
  I was poking around the files for the package "unity-settings-daemon"
  and found this bug:

  in the file "/usr/share/apport/package-hooks/source_unity-settings-
  daemon.py"

  line number 6 has this typo:
  if "Stacktrace" in report and "/usr/libg/nome-settings-daemon-3.0" in 
report["Stacktrace"]:

  I guess it should be:
  if "Stacktrace" in report and "/usr/lib/gnome-settings-daemon-3.0" in 
report["Stacktrace"]:

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

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

[Desktop-packages] [Bug 1663395] Re: Ubufox replacement/ discontinue?

2017-09-15 Thread Amr Ibrahim

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

** This bug has been marked a duplicate of bug 1711778
   Convert to web extension

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

Title:
  Ubufox replacement/ discontinue?

Status in ubufox package in Ubuntu:
  Confirmed

Bug description:
  Ubufox is an old style add-on that from my understanding will stop
  working in the Firefox 53/54 timeframe.

  Is there interest in making a new style add-on or should whatever
  changes we want be incorporated directly (see if we can add a blurb to
  the Firefox home page instead of making our own, etc).

  If we end up discontinuing it we, need to reset the users homepage (if
  it's the default) before we go.

  Also likely has an impact on bugs like:
  https://bugs.launchpad.net/ubuntu/+source/ubufox/+bug/1627808

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

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

[Desktop-packages] [Bug 1717503] [NEW] Support for installing Digital Certificates

2017-09-15 Thread Javier Antonio Nisa Avila

Public bug reported:

I am trying to enter in my university profile and in my bank and its
impossible, because this Gnome Web Browser "epihany", don't have
possibility to install my digital certificate in the browser.

without this option this browser is unsuitable for professionals,
businesses and individuals need the ability to import the browser our
digital certificates, to enter universities, banks, government pages.
Please develop this new option, this browser is precious, but useless
for ubuntu gnome desktop.

Thank you.

** Affects: epiphany-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: epiphany-browser gnome-17.10

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

Title:
  Support for installing Digital Certificates

Status in epiphany-browser package in Ubuntu:
  New

Bug description:
  I am trying to enter in my university profile and in my bank and its
  impossible, because this Gnome Web Browser "epihany", don't have
  possibility to install my digital certificate in the browser.

  without this option this browser is unsuitable for professionals,
  businesses and individuals need the ability to import the browser our
  digital certificates, to enter universities, banks, government pages.
  Please develop this new option, this browser is precious, but useless
  for ubuntu gnome desktop.

  Thank you.

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

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

[Desktop-packages] [Bug 1717498] Re: package liblouis-data 3.0.0-3ubuntu0.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura

2017-09-15 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package liblouis-data 3.0.0-3ubuntu0.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in liblouis package in Ubuntu:
  New

Bug description:
  There have been several recently where software has failed to
  download.

  This report is specifically about software that should have downloaded
  on Friday September 15.  Daily automatic check for zesty-security  and
  zesty-updates.

  It should, of course, have automatically downloaded but it finished
  with: 'The installation or removal of a software package failed.'  It
  seems that the package is "package liblouis-data 3.0.0-3ubuntu0.2
  failed to install/upgrad"

  Ubuntu 17.04

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: liblouis-data 3.0.0-3ubuntu0.2
  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
  Date: Fri Sep 15 12:24:08 2017
  Dependencies:
   
  DuplicateSignature:
   package:liblouis-data:3.0.0-3ubuntu0.2
   Setting up thunderbird (1:52.3.0+build1-0ubuntu0.17.04.1) ...
   dpkg: error processing package liblouis-data (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2013-10-25 (1420 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: liblouis
  Title: package liblouis-data 3.0.0-3ubuntu0.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: Upgraded to zesty on 2017-07-06 (70 days ago)

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

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

[Desktop-packages] [Bug 1717498] [NEW] package liblouis-data 3.0.0-3ubuntu0.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu

2017-09-15 Thread Alan Stopford

Public bug reported:

There have been several recently where software has failed to download.

This report is specifically about software that should have downloaded
on Friday September 15.  Daily automatic check for zesty-security  and
zesty-updates.

It should, of course, have automatically downloaded but it finished
with: 'The installation or removal of a software package failed.'  It
seems that the package is "package liblouis-data 3.0.0-3ubuntu0.2 failed
to install/upgrad"

Ubuntu 17.04

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: liblouis-data 3.0.0-3ubuntu0.2
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
Date: Fri Sep 15 12:24:08 2017
Dependencies:
 
DuplicateSignature:
 package:liblouis-data:3.0.0-3ubuntu0.2
 Setting up thunderbird (1:52.3.0+build1-0ubuntu0.17.04.1) ...
 dpkg: error processing package liblouis-data (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2013-10-25 (1420 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: liblouis
Title: package liblouis-data 3.0.0-3ubuntu0.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: Upgraded to zesty on 2017-07-06 (70 days ago)

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


** Tags: amd64 apport-package zesty

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

Title:
  package liblouis-data 3.0.0-3ubuntu0.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in liblouis package in Ubuntu:
  New

Bug description:
  There have been several recently where software has failed to
  download.

  This report is specifically about software that should have downloaded
  on Friday September 15.  Daily automatic check for zesty-security  and
  zesty-updates.

  It should, of course, have automatically downloaded but it finished
  with: 'The installation or removal of a software package failed.'  It
  seems that the package is "package liblouis-data 3.0.0-3ubuntu0.2
  failed to install/upgrad"

  Ubuntu 17.04

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: liblouis-data 3.0.0-3ubuntu0.2
  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
  Date: Fri Sep 15 12:24:08 2017
  Dependencies:
   
  DuplicateSignature:
   package:liblouis-data:3.0.0-3ubuntu0.2
   Setting up thunderbird (1:52.3.0+build1-0ubuntu0.17.04.1) ...
   dpkg: error processing package liblouis-data (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2013-10-25 (1420 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: liblouis
  Title: package liblouis-data 3.0.0-3ubuntu0.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: Upgraded to zesty on 2017-07-06 (70 days ago)

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

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

[Desktop-packages] [Bug 1273524] Re: LXDE guest session shows error message "no session for pid "

2017-09-15 Thread Carlos Renê

Lubuntu 16.04.3 have same problem! :/

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

Title:
  LXDE guest session shows error message "no session for pid "

Status in One Hundred Papercuts:
  Triaged
Status in Light Display Manager:
  Triaged
Status in Light Display Manager 1.18 series:
  Triaged
Status in lightdm package in Ubuntu:
  Confirmed
Status in lxsession package in Ubuntu:
  Triaged
Status in lightdm source package in Xenial:
  Confirmed
Status in lxsession source package in Xenial:
  Confirmed

Bug description:
  EXPECTED RESULTS:
  Log into guest session with no error messages.

  ACTUAL RESULTS:
  Upon log in to guest session, an error "no session for pid " is printed.

  STEPS TO REPRODUCE:
  1. Using Lubuntu in trusty, utopic, or vivid with either real or virtual 
hardware, log into guest session.
  2. After being logged in, see error message.

  AFFECTED VERSIONS:
  lightdm 1.10.0-0ubuntu3 to 1.12.1-0ubuntu1
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=lightdm-gtk-greeter
   user-session=Lubuntu
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1874): WARNING **: Failed to load user image: Failed 
to open file '/home/brendy/.face': No such file or directory
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2073): WARNING **: Failed to 
load user image: Failed to open file '/home/brendy/.face': No such file or 
directory
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1717398] Re: incorrect file path in "/usr/share/apport/package-hooks/source_unity-settings-daemon.py"

2017-09-15 Thread robin

** Attachment added: "patch.txt"
   
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1717398/+attachment/4950699/+files/patch.txt

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

Title:
  incorrect file path in "/usr/share/apport/package-hooks/source_unity-
  settings-daemon.py"

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

Bug description:
  I was poking around the files for the package "unity-settings-daemon"
  and found this bug:

  in the file "/usr/share/apport/package-hooks/source_unity-settings-
  daemon.py"

  line number 6 has this typo:
  if "Stacktrace" in report and "/usr/libg/nome-settings-daemon-3.0" in 
report["Stacktrace"]:

  I guess it should be:
  if "Stacktrace" in report and "/usr/lib/gnome-settings-daemon-3.0" in 
report["Stacktrace"]:

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

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

[Desktop-packages] [Bug 1713555] Re: System tray (notification area) icons are placed in strange non-intuitive place - left buttom corner of window!

Norbert, Ubuntu 17.10 provides indicator support by default:

https://didrocks.fr/2017/08/23/ubuntu-gnome-shell-in-artful-day-7/

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

Title:
  System tray (notification area) icons are placed in strange non-
  intuitive place - left buttom corner of window!

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 17.10.
  2. Launch Ubuntu GNOME session
  3. Install application which places its icon to the system tray (notification 
area) such as `hplip` or `transmission`
  3. Try to find application icon in the system tray (notification area) - 
right top corner of the screen

  Expected results:
  system tray (notification area) is easy to find and placed on right top 
corner of the screen, does not overlap screen elements and windows

  Actual results:
  system tray (notification area) is difficult to find, it is placed on left 
bottom corner of the screen and automatically hides on start or after 
inactivity, or overlaps left bottom corner of the screen (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-session-bin 3.25.90-0ubuntu2
  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: Mon Aug 28 21:25:51 2017
  InstallationDate: Installed on 2017-08-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  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/gnome-shell/+bug/1713555/+subscriptions

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

[Desktop-packages] [Bug 1717486] [NEW] gnome visual issues

2017-09-15 Thread Wolf Rogner

Public bug reported:

since the upgrade of gnome-session from 3.25.90 to 3.26.0 I observe
weird visual phenomena.

1. Icons in the task bar disappear (and only appear after logout/login)
2. Windows get drawn with black margins and sometimes with black canvas (gets 
away after a second or so)

Issue can be related to upgrade of libmutter (libmutter-1-0:amd64
3.25.91+20170902~ce515c5-1ubuntu1 -> 3.26.0-1)

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-session (not installed)
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 15 12:33:43 2017
InstallationDate: Installed on 2017-09-05 (9 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
SourcePackage: gnome-session
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-session (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 gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1717486

Title:
  gnome visual issues

Status in gnome-session package in Ubuntu:
  New

Bug description:
  since the upgrade of gnome-session from 3.25.90 to 3.26.0 I observe
  weird visual phenomena.

  1. Icons in the task bar disappear (and only appear after logout/login)
  2. Windows get drawn with black margins and sometimes with black canvas (gets 
away after a second or so)

  Issue can be related to upgrade of libmutter (libmutter-1-0:amd64
  3.25.91+20170902~ce515c5-1ubuntu1 -> 3.26.0-1)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-session (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 15 12:33:43 2017
  InstallationDate: Installed on 2017-09-05 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  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/gnome-session/+bug/1717486/+subscriptions

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

[Desktop-packages] [Bug 1715582] Re: deja-dup fails to backup

2017-09-15 Thread Wolf Rogner

upgraded to deja-dup 36.1. -> Backup failed
Operation not supported by backend

syslog:
Sep 15 12:27:23 mbpr13b deja-dup[1983]: BackendRemote.vala:83: The specified loc
ation is not mounted
Sep 15 12:27:23 mbpr13b gvfsd[1375]: mkdir failed on directory 
/var/cache/samba: Permission denied
Sep 15 12:27:25 mbpr13b gvfsd[1375]: message repeated 9 times: [ mkdir failed 
on directory /var/cache/samba: Permission denied]
Sep 15 12:27:25 mbpr13b deja-dup[1983]: BackendRemote.vala:83: Could not find 
enclosing mount
Sep 15 12:27:25 mbpr13b dbus-daemon[1335]: Activating via systemd: service 
name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service'
Sep 15 12:27:25 mbpr13b systemd[1321]: Starting Virtual filesystem metadata 
service...
Sep 15 12:27:25 mbpr13b dbus-daemon[1335]: Successfully activated service 
'org.gtk.vfs.Metadata'

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

Title:
  deja-dup fails to backup

Status in deja-dup package in Ubuntu:
  Fix Committed

Bug description:
  OS: Ubuntu 17.10 beta
  setting up deja-dup to backup to smb/ssh server fails

  With ssh: Permission denied
  syslog:
  Sep  7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from 
uid 1000 finished with success after 414ms

  
  with smb: Backup failed
  InvalidBackendURL: missing // - relative paths not supported for scheme 
gio+invalid: gio+invalid://
  syslog:
  Sep  7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from 
uid 1000 finished with success after 402ms

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 35.6-0ubuntu1
  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: Thu Sep  7 10:30:37 2017
  InstallationDate: Installed on 2017-09-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1716775] Re: Add option to disable gnome-shell animations

2017-09-15 Thread Doug McMahon

Yeah, it's in tweak tools though that won't be default provided. It's
probably somewhat similar to unity where some hardware benefited from
reduced effects. (- likely on a lesser scale..?

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

Title:
  Add option to disable gnome-shell animations

Status in ubuntu-settings package in Ubuntu:
  Invalid

Bug description:
  I believe doing so will provide the better experience for most users. Those 
that see use in it can enable if desired.
  Am filing this bug first rather than specific against gnome-shell because 
this is immediately  remedied in settings & there are reports of other poor 
behavior than the below test case.

  Test case 1:
  In current 'pseudo' default of xorg
  In any common video player (totem, vlc, mpv, ect.) open a video.
  Go from window to fullscreen, fullscreen to windowed, notice the distortion.

  May be even worse in wayland or when using hw decoding.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-settings 17.10.15
  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: Tue Sep 12 17:21:52 2017
  InstallationDate: Installed on 2017-09-10 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1713555] Re: System tray (notification area) icons are placed in strange non-intuitive place - left buttom corner of window!

2017-09-15 Thread Norbert

About TopIcons see https://help.gnome.org/misc/release-notes/3.26/ .

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

Title:
  System tray (notification area) icons are placed in strange non-
  intuitive place - left buttom corner of window!

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 17.10.
  2. Launch Ubuntu GNOME session
  3. Install application which places its icon to the system tray (notification 
area) such as `hplip` or `transmission`
  3. Try to find application icon in the system tray (notification area) - 
right top corner of the screen

  Expected results:
  system tray (notification area) is easy to find and placed on right top 
corner of the screen, does not overlap screen elements and windows

  Actual results:
  system tray (notification area) is difficult to find, it is placed on left 
bottom corner of the screen and automatically hides on start or after 
inactivity, or overlaps left bottom corner of the screen (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-session-bin 3.25.90-0ubuntu2
  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: Mon Aug 28 21:25:51 2017
  InstallationDate: Installed on 2017-08-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  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/gnome-shell/+bug/1713555/+subscriptions

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

[Desktop-packages] [Bug 1713555] Re: System tray (notification area) icons are placed in strange non-intuitive place - left buttom corner of window!

2017-09-15 Thread Norbert

Is it any chance to include TopIcons (
https://extensions.gnome.org/extension/495/topicons/ ) to 17.10 as in
GNOME 3.26 (see https://www.gnome.org/news/2017/09/gnome-3-26-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/1713555

Title:
  System tray (notification area) icons are placed in strange non-
  intuitive place - left buttom corner of window!

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 17.10.
  2. Launch Ubuntu GNOME session
  3. Install application which places its icon to the system tray (notification 
area) such as `hplip` or `transmission`
  3. Try to find application icon in the system tray (notification area) - 
right top corner of the screen

  Expected results:
  system tray (notification area) is easy to find and placed on right top 
corner of the screen, does not overlap screen elements and windows

  Actual results:
  system tray (notification area) is difficult to find, it is placed on left 
bottom corner of the screen and automatically hides on start or after 
inactivity, or overlaps left bottom corner of the screen (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-session-bin 3.25.90-0ubuntu2
  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: Mon Aug 28 21:25:51 2017
  InstallationDate: Installed on 2017-08-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  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/gnome-shell/+bug/1713555/+subscriptions

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

[Desktop-packages] [Bug 1208993] Re: Ubuntu slows down and hangs while copying file from/to USB

2017-09-15 Thread Thomas

What file system is involved?
I'm still investigating, but in my case it seems always btrfs related so far.

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

Title:
  Ubuntu slows down and hangs while copying file from/to USB

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Hi

  While copying many and large files to and from a USB drive, the system
  becomes incredibly slow and sometimes hangs. I watched the system
  monitor while it was running slowly but cpu was not above 50% at any
  time, the same for memory.

  I'm using the "WD my passport" HD with a USB3 port of my "ASUS K55VD"
  laptop.

  Description:  Ubuntu 13.04
  Release:  13.04

  nautilus:
Installed: 1:3.6.3-0ubuntu16
Candidate: 1:3.6.3-0ubuntu16
Version table:
   *** 1:3.6.3-0ubuntu16 0
  500 http://ubuntu-archive.mirror.nucleus.be/ raring/main amd64 
Packages
  100 /var/lib/dpkg/status

  
  Steps to reproduce:
  1) Aquire many large files (like your totally legit moviecollection)
  2) Copy files to external HD
  3) Open your browser and be sad when your system becomes incredibly slow 
after a few minutes


  This is my first bugreport so if I'm missing something, please tell
  me.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  Date: Tue Aug  6 22:56:34 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'656x715+154+151'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2013-05-31 (67 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on trusty/xenial/yakkety

2017-09-15 Thread tagMacher

I have just reported bug #1717473 with version
60.0.3112.113-0ubuntu0.16.04.1298, where the original bug reported here
is happening again except that I get "SEGV_MAPERR 0028" instead
of "SEGV_MAPERR 0010"

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on
  trusty/xenial/yakkety

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser package in Debian:
  Fix Released

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1717473] [NEW] Sign in to Chhromium causes "signal 11 SEGV_MAPERR 000000000028"

2017-09-15 Thread tagMacher

Public bug reported:

System info:

lsb_release -rd
Description:Ubuntu 16.04.3 LTS
Release:16.04

apt-cache policy chromium-browser
chromium-browser:
  Installed: 60.0.3112.113-0ubuntu0.16.04.1298
  Candidate: 60.0.3112.113-0ubuntu0.16.04.1298
  Version table:
 *** 60.0.3112.113-0ubuntu0.16.04.1298 500
500 http://download.nus.edu.sg/mirror/ubuntu xenial-updates/universe 
amd64 Packages
500 http://download.nus.edu.sg/mirror/ubuntu xenial-security/universe 
amd64 Packages
100 /var/lib/dpkg/status
 49.0.2623.108-0ubuntu1.1233 500
500 http://download.nus.edu.sg/mirror/ubuntu xenial/universe amd64 
Packages


Steps to demonstrate problem:
1. Installed chromium-browser from Ubuntu 16.04 64-bit LTS (xenial) standard 
repository using apt-get.
2. Chromium-browser starts up without issues and is usable.
EXPECTED: Google sign-in page
OBSERVED: Frame for new window (which should be Google sign-in page) 
flashes in momentarily and disappears, taking with it the chromium-browser 
window.



More info: Starting it in a Terminal, I was able to get the following:

user@ubuntu:~$ chromium-browser
Starting
Starting
Received signal 11 SEGV_MAPERR 0028
#0 0x7f33835373f7 base::debug::StackTrace::StackTrace()
#1 0x7f3383536f6f 
#2 0x7f3383cda390 
#3 0x009ec00b9f1e 
#4 0x009ebf944984 
#5 0x009ebf74132d 
#6 0x7f337d7fbc96 content::InterstitialPageImpl::OnDomOperationResponse()
#7 0x7f337d7fba96 
#8 0x7f337d7fb9a0 content::InterstitialPageImpl::OnMessageReceived()
#9 0x7f337d8194f7 content::RenderFrameHostImpl::OnMessageReceived()
#10 0x7f3381213d35 IPC::ChannelProxy::Context::OnDispatchMessage()
#11 0x7f3383537ed3 base::debug::TaskAnnotator::RunTask()
#12 0x7f338356092d base::MessageLoop::RunTask()
#13 0x7f338356118b base::MessageLoop::DoWork()
#14 0x7f3383562b7a 
#15 0x7f336c7f2197 g_main_context_dispatch
#16 0x7f336c7f23f0 
#17 0x7f336c7f249c g_main_context_iteration
#18 0x7f33835629e6 base::MessagePumpGlib::Run()
#19 0x7f338358e110 base::RunLoop::Run()
#20 0x009ebed26dd2 
#21 0x7f337d7128b3 content::BrowserMainLoop::RunMainMessageLoopParts()
#22 0x7f337d71545d 
#23 0x7f337d70e408 content::BrowserMain()
#24 0x7f337de5bc8f 
#25 0x7f3383a9419d service_manager::Main()
#26 0x7f337de5aa62 content::ContentMain()
#27 0x009ebe6c8bac 
#28 0x7f3369dc9830 __libc_start_main
#29 0x009ebe6c8a09 
  r8: 009ec2c63d80  r9: 000b r10:  r11: 
7f3369f3f110
 r12: 7ffdb51e5c20 r13: 009ec2cd5b80 r14: 7f32e428f1a8 r15: 
009ec2c09320
  di: 009ec2c09340  si: 009ec0f0a794  bp: 7ffdb51e5c10  bx: 
7f32e428ebe0
  dx:   ax:   cx: ffe0  sp: 
7ffdb51e56a0
  ip: 009ec00b9f1e efl: 00010246 cgf: 0033 erf: 
0004
 trp: 000e msk:  cr2: 0028
[end of stack trace]
Calling _exit(1). Core file will not be generated.
user@ubuntu:~$ Finishing
Finishing
Finishing



Further info: apport is not triggered by this crash

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: chromium-browser

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

Title:
  Sign in to Chhromium causes "signal 11 SEGV_MAPERR 0028"

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  System info:

  lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  apt-cache policy chromium-browser
  chromium-browser:
Installed: 60.0.3112.113-0ubuntu0.16.04.1298
Candidate: 60.0.3112.113-0ubuntu0.16.04.1298
Version table:
   *** 60.0.3112.113-0ubuntu0.16.04.1298 500
  500 http://download.nus.edu.sg/mirror/ubuntu xenial-updates/universe 
amd64 Packages
  500 http://download.nus.edu.sg/mirror/ubuntu xenial-security/universe 
amd64 Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://download.nus.edu.sg/mirror/ubuntu xenial/universe amd64 
Packages
  

  Steps to demonstrate problem:
  1. Installed chromium-browser from Ubuntu 16.04 64-bit LTS (xenial) standard 
repository using apt-get.
  2. Chromium-browser starts up without issues and is usable.
  EXPECTED: Google sign-in page
  OBSERVED: Frame for new window (which should be Google sign-in page) 
flashes in momentarily and disappears, taking with it the chromium-browser 
window.

  

  More info: Starting it in a Terminal, I was able to get the following:

  user@ubuntu:~$ chromium-browser
  Starting
  Starting
  Received signal 11 SEGV_MAPERR 0028
  #0 0x7f33835373f7 base::debug::StackTrace::StackTrace()
  #1 0x7f3383536f6f 
  #2 0x7f3383cda390 
  #3 0x009ec00b9f1e 
  #4 0x009ebf944984 
  #5 0x009ebf74132d 
  #6 0x7f337d7fbc96 content::InterstitialPageImpl::OnDomOperationResponse()
  #7

[Desktop-packages] [Bug 1717473] Re: Sign in to Chhromium causes "signal 11 SEGV_MAPERR 000000000028"

2017-09-15 Thread tagMacher

This seems specific to this system - I have been able to run chromium-
browser on my other laptop also with Ubuntu 16.04 64-bit LTS without any
issues. One difference between the two is that the computer on which it
crashes is behind a corporate firewall, though I feel this is not an
issue since internet access is available through a proxy server.

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

Title:
  Sign in to Chhromium causes "signal 11 SEGV_MAPERR 0028"

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  System info:

  lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  apt-cache policy chromium-browser
  chromium-browser:
Installed: 60.0.3112.113-0ubuntu0.16.04.1298
Candidate: 60.0.3112.113-0ubuntu0.16.04.1298
Version table:
   *** 60.0.3112.113-0ubuntu0.16.04.1298 500
  500 http://download.nus.edu.sg/mirror/ubuntu xenial-updates/universe 
amd64 Packages
  500 http://download.nus.edu.sg/mirror/ubuntu xenial-security/universe 
amd64 Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://download.nus.edu.sg/mirror/ubuntu xenial/universe amd64 
Packages
  

  Steps to demonstrate problem:
  1. Installed chromium-browser from Ubuntu 16.04 64-bit LTS (xenial) standard 
repository using apt-get.
  2. Chromium-browser starts up without issues and is usable.
  EXPECTED: Google sign-in page
  OBSERVED: Frame for new window (which should be Google sign-in page) 
flashes in momentarily and disappears, taking with it the chromium-browser 
window.

  

  More info: Starting it in a Terminal, I was able to get the following:

  user@ubuntu:~$ chromium-browser
  Starting
  Starting
  Received signal 11 SEGV_MAPERR 0028
  #0 0x7f33835373f7 base::debug::StackTrace::StackTrace()
  #1 0x7f3383536f6f 
  #2 0x7f3383cda390 
  #3 0x009ec00b9f1e 
  #4 0x009ebf944984 
  #5 0x009ebf74132d 
  #6 0x7f337d7fbc96 content::InterstitialPageImpl::OnDomOperationResponse()
  #7 0x7f337d7fba96 
  #8 0x7f337d7fb9a0 content::InterstitialPageImpl::OnMessageReceived()
  #9 0x7f337d8194f7 content::RenderFrameHostImpl::OnMessageReceived()
  #10 0x7f3381213d35 IPC::ChannelProxy::Context::OnDispatchMessage()
  #11 0x7f3383537ed3 base::debug::TaskAnnotator::RunTask()
  #12 0x7f338356092d base::MessageLoop::RunTask()
  #13 0x7f338356118b base::MessageLoop::DoWork()
  #14 0x7f3383562b7a 
  #15 0x7f336c7f2197 g_main_context_dispatch
  #16 0x7f336c7f23f0 
  #17 0x7f336c7f249c g_main_context_iteration
  #18 0x7f33835629e6 base::MessagePumpGlib::Run()
  #19 0x7f338358e110 base::RunLoop::Run()
  #20 0x009ebed26dd2 
  #21 0x7f337d7128b3 content::BrowserMainLoop::RunMainMessageLoopParts()
  #22 0x7f337d71545d 
  #23 0x7f337d70e408 content::BrowserMain()
  #24 0x7f337de5bc8f 
  #25 0x7f3383a9419d service_manager::Main()
  #26 0x7f337de5aa62 content::ContentMain()
  #27 0x009ebe6c8bac 
  #28 0x7f3369dc9830 __libc_start_main
  #29 0x009ebe6c8a09 
r8: 009ec2c63d80  r9: 000b r10:  r11: 
7f3369f3f110
   r12: 7ffdb51e5c20 r13: 009ec2cd5b80 r14: 7f32e428f1a8 r15: 
009ec2c09320
di: 009ec2c09340  si: 009ec0f0a794  bp: 7ffdb51e5c10  bx: 
7f32e428ebe0
dx:   ax:   cx: ffe0  sp: 
7ffdb51e56a0
ip: 009ec00b9f1e efl: 00010246 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0028
  [end of stack trace]
  Calling _exit(1). Core file will not be generated.
  user@ubuntu:~$ Finishing
  Finishing
  Finishing

  

  Further info: apport is not triggered by this crash

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

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

[Desktop-packages] [Bug 1717474] [NEW] Multi monitor config issues

2017-09-15 Thread lswn

Public bug reported:

Since wayland will be the default with 17.10 it might be important to
have it ready for multiple monitor support. I have the latest updates
installed and I am on the artful channel.

SETUP:
HiDPI internal screen running at 2160x1440 (Surface Pro 3)
External FullHD HDMI monitor running  at 1920x1080
Since the upgrade to the latest GNOME 3.26, wayland got activated again. I was 
running X before. 
Usually, I set my internal screen off and only work with the external monitor 
if plugged in.

ISSUE:
With wayland active for both GDM and GNOME there is actually two issues:

1. I am able to configure my desired settings in the display settings as
usual (=turn off internal screen and use only external monitor). But
since the latest update this setting is not remembered after a new
login. It can only remember the "mirror" or "join displays" options but
not the "single display" option. Very annoying to reconfigure this after
every login.

Before the update to the new GNOME settings look I was at least able to
have this setting remembered (even with wayland). However, even back
then it was not perfect since the internal screen was not completely
turned off (black but with light on). After manually setting the
displays again the screen was turned off but not after a login. This is
a wayland related issue since it is not reproducable with X.

2. GDM is always on the internal screen and simply does not match and
respect your GNOME config. I tried several ways to configure this:

sudo cp ~/.config/monitors.xml /var/lib/gdm3/.config - does not work
since wayland ignores this config file.

I tried to using shell scripts executed at startup with xrandr. But
xrandr does not work with wayland, too. So this is also not a solution.


FIX:
I don't know how to configure GDM with wayland. I am willing to test things out 
but have no further ideas and am relatively new to Linux/Ubuntu. Thanks for any 
help.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu2
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
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 15 10:57:43 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Microsoft Corporation Haswell-ULT Integrated Graphics Controller 
[1414:0005]
InstallationDate: Installed on 2017-08-24 (21 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170823)
MachineType: Microsoft Corporation Surface Pro 3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic.efi.signed 
root=UUID=f348de47-cb83-4d73-8de3-bdd738092165 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/26/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3.11.2150
dmi.board.asset.tag: 0
dmi.board.name: Surface Pro 3
dmi.board.vendor: Microsoft Corporation
dmi.board.version: 1
dmi.chassis.asset.tag: 0
dmi.chassis.type: 9
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: 1
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.11.2150:bd04/26/2017:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1:
dmi.product.family: Surface
dmi.product.name: Surface Pro 3
dmi.product.version: 1
dmi.sys.vendor: Microsoft Corporation
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.82-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

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


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

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

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

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

Title:
  Multi monitor config issues

Status in gdm3 package in Ubuntu:
  New
Status in wayland package in

[Desktop-packages] [Bug 1717398] Re: incorrect file path in "/usr/share/apport/package-hooks/source_unity-settings-daemon.py"

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

** Changed in: unity-settings-daemon (Ubuntu)
   Status: New => Confirmed

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

Title:
  incorrect file path in "/usr/share/apport/package-hooks/source_unity-
  settings-daemon.py"

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

Bug description:
  I was poking around the files for the package "unity-settings-daemon"
  and found this bug:

  in the file "/usr/share/apport/package-hooks/source_unity-settings-
  daemon.py"

  line number 6 has this typo:
  if "Stacktrace" in report and "/usr/libg/nome-settings-daemon-3.0" in 
report["Stacktrace"]:

  I guess it should be:
  if "Stacktrace" in report and "/usr/lib/gnome-settings-daemon-3.0" in 
report["Stacktrace"]:

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

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

[Desktop-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

2017-09-15 Thread Iain Lane

As I said, console-setup. I think cyphermox took the final changes in
the merge of 1.166.

It was some time ago, so you are probably not hitting this case.

Was it triggered by a package update for you? If so, then yes, please
have a look at what you upgraded and try to replay any suspicious things
to reproduce the failure.

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

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

Bug description:
  I'm used to using alt+left/right arrow to navigate back and forward in
  web browsers and elsewhere (nautilus)...  But on this fresh install of
  Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty
  consoles (the ctrl+alt+f1 ones).  But it's not listed as one of the
  shortcuts in the "keyboard" menu, so I don't know how to disable it...

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

-- 
Mailing list: https://launchpad.net/~desktop-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()

** Changed in: mutter (Ubuntu)
 Assignee: Jeremy Bicha (jbicha) => (unassigned)

-- 
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:
  Confirmed
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/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 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()

This bug was fixed in the package mutter - 3.26.0-1

---
mutter (3.26.0-1) experimental; urgency=medium

  * Team upload
  * debian/watch: Only watch stable branch again
  * New upstream release, functionally identical to the previous
snapshot

 -- Simon McVittie   Wed, 13 Sep 2017 09:22:55 +0100

** Changed in: mutter (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/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:
  Confirmed
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/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 1717398] Re: incorrect file path in "/usr/share/apport/package-hooks/source_unity-settings-daemon.py"

2017-09-15 Thread robin

Patch added above to fix the typo

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

Title:
  incorrect file path in "/usr/share/apport/package-hooks/source_unity-
  settings-daemon.py"

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

Bug description:
  I was poking around the files for the package "unity-settings-daemon"
  and found this bug:

  in the file "/usr/share/apport/package-hooks/source_unity-settings-
  daemon.py"

  line number 6 has this typo:
  if "Stacktrace" in report and "/usr/libg/nome-settings-daemon-3.0" in 
report["Stacktrace"]:

  I guess it should be:
  if "Stacktrace" in report and "/usr/lib/gnome-settings-daemon-3.0" in 
report["Stacktrace"]:

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

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

[Desktop-packages] [Bug 1717398] Re: incorrect file path in "/usr/share/apport/package-hooks/source_unity-settings-daemon.py"

2017-09-15 Thread robin

# Bazaar merge directive format 2 (Bazaar 0.90)
# revision_id: ro...@bumblepuppy.org-20170915075446-phxs6xye7sn0a4a7
# target_branch: http://bazaar.launchpad.net/~unity-settings-daemon-\
#   team/unity-settings-daemon/trunk/
# testament_sha1: 98208daf40f4bae50249e1b14e227521f9cad7b8
# timestamp: 2017-09-15 19:57:38 +1200
# base_revision_id: seb...@ubuntu.com-20170906144723-n9bskdpkhnh7ascr
# 
# Begin patch
=== modified file 'debian/source_unity-settings-daemon.py'
--- debian/source_unity-settings-daemon.py  2013-12-04 23:55:26 +
+++ debian/source_unity-settings-daemon.py  2017-09-15 07:54:46 +
@@ -3,7 +3,7 @@
 
 def add_info(report):
# the issue is not in the unity-settings-daemon code so reassign
-   if "Stacktrace" in report and "/usr/libg/nome-settings-daemon-3.0" in 
report["Stacktrace"]:
+   if "Stacktrace" in report and "/usr/lib/gnome-settings-daemon-3.0" in 
report["Stacktrace"]:
for words in report["Stacktrace"].split():
if 
words.startswith("/usr/lib/unity-settings-daemon-3.0"):
if apport.packaging.get_file_package(words) != 
'unity-settings-daemon':

# Begin bundle
IyBCYXphYXIgcmV2aXNpb24gYnVuZGxlIHY0CiMKQlpoOTFBWSZTWQVyYnUAAW9fgAAwUGP/91IA
WAq//99wUANj3QmZQBoaFPU0myaTRjUT0npMnppplGQzU0GNDQ0AGQ0AGU0pvSZMCSH6iMho
aDQA0BjQ0NABkNABJIIGkwaJphVP0JinqPU9I0PSeobdcBV2qEdaIKHxSgDoldawVJL8G6+c
Zgz7ZF3VjjRAZnGFy6+Zqpi7noIwPPCVz2mmsetxImUikIrPD8xmB3BKFgwmCKGBb2AptQWhWZ/p
MIpdOe2JXVbYXygsYku8eIME0wjy+c6bFpQ8VKcuiCHorFiKZ0qcURurYhnBLeFx278jaB9sF71m
Z546mFpL+Y9Vy3ri+tAXkDa2W/NwP1JklnKeqFVHKJA64SoW7HGA/eSwYO2IWvV6pcDMt4sOp7Sx
xYq0IcqVa1rbR9ArXLHreWioaLLSufZRKyjqLBU86XVAW3cdhVTu0uvGHSiNlAVcak9oD8+0JhLo
j8+QtDa0vfUxNA5s1bQsBIF73SkdxbHSDbPRApFLjZBcnFzhScC7kwL2A1kJV2xnqQprOuDxxzdo
GDKWbajFagVCxVmiFqjEDFTxG67Q+nSYSHa+MipcTHGRj8Sbg0PPlGImoQ4b1GS0qUDrgCMF/LzG
wPcG7A9gF19Eie0dTLnELSxCH45NmepisbHQgTHb/eLASSf9l/qXwvEPL2tt+tl7GVmIbK3gjBmO
Aw5Uc8X+CqisiKdxBe5n6dPEsn3PuoKvjDiLU2dJxTYsg6grRQL3fNlKJoE84CYbi48lrtn1HXbb
P5t+39uJdyw9UyJpX69Zz8O+wQCsKE+G+Nh3O7x/JQei+ePf1+uXjzBLVH80FASWWz02YV+qw6iu
VRxd23te3temp+ZGCeTsZMlcHSAfnTGGQdw/TC0hl8crUgtVoDzbsEQqcDcLNLejCjgp8w5T0nUM
Z2E31EYmtEWCDg6Jcp0Em3ing9kfqnRl7KiSKWUE5a6X/8wDtA2TX5VMy840mQfCUlYnrGxdFKqe
bMmeUTF4r3JltgFb0roJZ9IK4kG9azVKLyWzilKvhyjwfAzvHpRfCmpmYMlwH4FVleqagY0HM0uA
bNVEm9xdvDKZr0LUXb8s5nZH0TzX2hhsX2GuUQoE8gJHeGKw3qAhSN3n3N+B3V5yXMPE02k6Tvz6
4rIMh4nL8Czrm5yTBsJ5hUU/+LuSKcKEgCuTE6g=

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

Title:
  incorrect file path in "/usr/share/apport/package-hooks/source_unity-
  settings-daemon.py"

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

Bug description:
  I was poking around the files for the package "unity-settings-daemon"
  and found this bug:

  in the file "/usr/share/apport/package-hooks/source_unity-settings-
  daemon.py"

  line number 6 has this typo:
  if "Stacktrace" in report and "/usr/libg/nome-settings-daemon-3.0" in 
report["Stacktrace"]:

  I guess it should be:
  if "Stacktrace" in report and "/usr/lib/gnome-settings-daemon-3.0" in 
report["Stacktrace"]:

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

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

[Desktop-packages] [Bug 1717458] [NEW] Panel flickers when scrubbing across in-window menus

Public bug reported:

The Gnome panel flickers when scrubbing across old-style in-window
menus, such as those in Terminal or AisleRiot.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.25.91-0ubuntu5
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: Fri Sep 15 15:48:41 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-05-03 (135 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful gnome-17.10 visual-quality

** Changed in: gnome-shell (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/1717458

Title:
  Panel flickers when scrubbing across in-window menus

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Gnome panel flickers when scrubbing across old-style in-window
  menus, such as those in Terminal or AisleRiot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu5
  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: Fri Sep 15 15:48:41 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-03 (135 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  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/1717458/+subscriptions

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

[Desktop-packages] [Bug 1717453] Re: Shell menus (panel, dock, window) font size does not match configured interface font size

See also bug 1717456

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

Title:
  Shell menus (panel, dock, window) font size does not match configured
  interface font size

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Shell menus (panel, dock, window) font size does not match configured
  interface font size.

  Test case:
  gnome-tweak-tool > Fonts > Interface = (something different)

  Expected: Shell menus to use the same font size.
  Observed: Shell menu fonts never change.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu5
  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: Fri Sep 15 15:17:15 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-03 (135 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  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/1717453/+subscriptions

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

[Desktop-packages] [Bug 1717456] Re: Panel menus don't respond to theme changes

See also bug 1717453

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

Title:
  Panel menus don't respond to theme changes

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Panel menus don't respond to theme changes. If I change my theme to
  Adwaita, the panel menus are still Ambiance-themed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu5
  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: Fri Sep 15 15:31:30 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-03 (135 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  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/1717456/+subscriptions

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

[Desktop-packages] [Bug 1717456] [NEW] Panel menus don't respond to theme changes

Public bug reported:

Panel menus don't respond to theme changes. If I change my theme to
Adwaita, the panel menus are still Ambiance-themed.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.25.91-0ubuntu5
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: Fri Sep 15 15:31:30 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-05-03 (135 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful gnome-17.10 visual-quality

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

Title:
  Panel menus don't respond to theme changes

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Panel menus don't respond to theme changes. If I change my theme to
  Adwaita, the panel menus are still Ambiance-themed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu5
  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: Fri Sep 15 15:31:30 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-03 (135 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  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/1717456/+subscriptions

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

[Desktop-packages] [Bug 1667113] Re: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types)

2017-09-15 Thread ChristianEhrhardt

Thanks Tom, I agree that loosing the hidden-shells seems to be a regression.
And to make the state more clear that this in the current state is considered a 
an issue of accountservice or lightdm lets mark the other packages won't fix 
for now. Otherwise everybody assumes "the other will do it".

This give a better overview and in general it isn't feasible to fix
"all-those" and since there can be high-id system-users added manually
by users the issue would still persist even when all those other
packages would be fixed.

** Changed in: netqmail (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: libvirt (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: ifmail (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: ceph (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  System users appears in Ligthdm and user switcher (Accountsservice has
  no filter for shell types)

Status in accountsservice package in Ubuntu:
  Confirmed
Status in base-passwd package in Ubuntu:
  Invalid
Status in ceph package in Ubuntu:
  Won't Fix
Status in ifmail package in Ubuntu:
  Won't Fix
Status in libvirt package in Ubuntu:
  Won't Fix
Status in lightdm package in Ubuntu:
  Confirmed
Status in netqmail package in Ubuntu:
  Won't Fix
Status in sddm package in Ubuntu:
  Fix Released

Bug description:
  "Technical" user libvirt Qemu appears in the list of user in Ligthdm,
  among the real regular users. It probably shouldn't

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libvirt-bin 2.5.0-3ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Feb 22 22:09:24 2017
  InstallationDate: Installed on 2017-02-01 (21 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201)
  KernLog:
   
  SourcePackage: libvirt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1717453] [NEW] Shell menus (panel, dock, window) font size does not match configured interface font size

Public bug reported:

Shell menus (panel, dock, window) font size does not match configured
interface font size.

Test case:
gnome-tweak-tool > Fonts > Interface = (something different)

Expected: Shell menus to use the same font size.
Observed: Shell menu fonts never change.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.25.91-0ubuntu5
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: Fri Sep 15 15:17:15 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-05-03 (135 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful gnome-17.10 visual-quality

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

Title:
  Shell menus (panel, dock, window) font size does not match configured
  interface font size

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Shell menus (panel, dock, window) font size does not match configured
  interface font size.

  Test case:
  gnome-tweak-tool > Fonts > Interface = (something different)

  Expected: Shell menus to use the same font size.
  Observed: Shell menu fonts never change.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu5
  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: Fri Sep 15 15:17:15 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-03 (135 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  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/1717453/+subscriptions

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

[Desktop-packages] [Bug 1717340] Re: [artful] Keyboard doesn't work after logging in to gnome

Damn, I was certain that it was solved exactly when toggling Slow Keys, but 
next time that didn't work.
It's interesting that the problem remains after logging out, so I can't type my 
password anymore and log in a second time. Suggests it's outside the user 
session somehow...

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

Title:
  [artful] Keyboard doesn't work after logging in to gnome

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After I type my password in GDM and come to the gnome desktop, no keys are 
working. Not even caps lock toggling.
  However, I found out that if I toggle "Slow keys" in the accessibility 
settings, it starts working again!
  To clarify, Slow keys and all other accessibility is disabled from start, but 
turning Slow keys on and off again makes my keyboard work.
  I seem to have to do this once after every _reboot_.

  This is on a system that has upgraded to Artful.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu5
  Uname: Linux 4.13.0-rc2+ x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 14 21:04:46 2017
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-08-29 (16 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-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

Workaround:

gnome-tweak-tool > Windows > Window Action Key = Alt

-- 
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 1717408] Re: gnome-control-center crashed with SIGSEGV

2017-09-15 Thread Jean-Baptiste Lallement

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

Title:
  gnome-control-center crashed with SIGSEGV

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

Bug description:
  Not sure if this is going to be reproducible. I'm running in a
  virtualbox guest and after I installed virtualbox additions, gnome-
  control-center started crashing. Could be totally unrelated though.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.25.92.1-0ubuntu2
  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: Thu Sep 14 21:47:27 2017
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-04-20 (147 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ()
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   cogl_context_new () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: Upgraded to artful on 2017-09-15 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1716775] Re: Add option to disable gnome-shell animations

I just noticed that the option to disable animations already exists:

gnome-tweak-tool > Appearance > Animations = ON | OFF

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

Title:
  Add option to disable gnome-shell animations

Status in ubuntu-settings package in Ubuntu:
  Invalid

Bug description:
  I believe doing so will provide the better experience for most users. Those 
that see use in it can enable if desired.
  Am filing this bug first rather than specific against gnome-shell because 
this is immediately  remedied in settings & there are reports of other poor 
behavior than the below test case.

  Test case 1:
  In current 'pseudo' default of xorg
  In any common video player (totem, vlc, mpv, ect.) open a video.
  Go from window to fullscreen, fullscreen to windowed, notice the distortion.

  May be even worse in wayland or when using hw decoding.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-settings 17.10.15
  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: Tue Sep 12 17:21:52 2017
  InstallationDate: Installed on 2017-09-10 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1717446] [NEW] Window menus close as soon as they open

Public bug reported:

Window menus close as soon as they open, if you happen to be moving the
mouse upward very slightly at the same time.

Test case:
1. Move the cursor slowly upward over a window titlebar, and right click on the 
titlebar at the same time.

Expected: Window menu opens and stays open.
Observed: Window menu opens, but immediately closes again.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.25.91-0ubuntu5
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: Fri Sep 15 14:53:40 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-05-03 (135 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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

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


** Tags: amd64 apport-bug artful

** Description changed:

  Window menus close as soon as they open, if you happen to be moving the
  mouse upward very slightly at the same time.
  
  Test case:
- 1. Move the cursor slowly up over a window titlebar, and right click on the 
titlebar at the same time.
+ 1. Move the cursor slowly upward over a window titlebar, and right click on 
the titlebar at the same time.
  
  Expected: Window menu opens and stays open.
  Observed: Window menu opens, but immediately closes again.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu5
  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: Fri Sep 15 14:53:40 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-03 (135 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Title:
  Window menus close as soon as they open

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

Bug description:
  Window menus close as soon as they open, if you happen to be moving
  the mouse upward very slightly at the same time.

  Test case:
  1. Move the cursor slowly upward over a window titlebar, and right click on 
the titlebar at the same time.

  Expected: Window menu opens and stays open.
  Observed: Window menu opens, but immediately closes again.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu5
  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: Fri Sep 15 14:53:40 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-03 (135 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  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/1717446/+subscriptions

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

[Desktop-packages] [Bug 1693464] Re: Bluetooth Audio broken for Bose SoundLink Mini

** Changed in: pulseaudio (Ubuntu)
   Status: Expired => New

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

Title:
  Bluetooth Audio broken for Bose SoundLink Mini

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Bluetooth Audio stopped working when upgrading/clean install of Ubuntu
  17.04. The Bose SoundLink Mini Bluetooth Connection works fine in
  16.04.

  I have tried restarting and re configuring pulseaudio, but nothing seems to 
work.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D8p:   tangarora   2844 F...m pulseaudio
   /dev/snd/controlC1:  tangarora   2844 F pulseaudio
   /dev/snd/controlC2:  tangarora   2844 F pulseaudio
   /dev/snd/controlC0:  tangarora   2844 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-27 (140 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:10.0-1ubuntu2 [modified: usr/bin/start-pulseaudio-x11]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V8.1
  dmi.board.name: MS-78511
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: 3.1
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV8.1:bd07/20/2015:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-B08911:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-78511:rvr3.1:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-B08911
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

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

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

[Desktop-packages] [Bug 1693464] PulseList.txt

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1693464/+attachment/4950565/+files/PulseList.txt

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

Title:
  Bluetooth Audio broken for Bose SoundLink Mini

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Bluetooth Audio stopped working when upgrading/clean install of Ubuntu
  17.04. The Bose SoundLink Mini Bluetooth Connection works fine in
  16.04.

  I have tried restarting and re configuring pulseaudio, but nothing seems to 
work.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D8p:   tangarora   2844 F...m pulseaudio
   /dev/snd/controlC1:  tangarora   2844 F pulseaudio
   /dev/snd/controlC2:  tangarora   2844 F pulseaudio
   /dev/snd/controlC0:  tangarora   2844 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-27 (140 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:10.0-1ubuntu2 [modified: usr/bin/start-pulseaudio-x11]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V8.1
  dmi.board.name: MS-78511
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: 3.1
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV8.1:bd07/20/2015:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-B08911:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-78511:rvr3.1:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-B08911
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

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

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

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

apport information

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

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

Title:
  Bluetooth Audio broken for Bose SoundLink Mini

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Bluetooth Audio stopped working when upgrading/clean install of Ubuntu
  17.04. The Bose SoundLink Mini Bluetooth Connection works fine in
  16.04.

  I have tried restarting and re configuring pulseaudio, but nothing seems to 
work.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D8p:   tangarora   2844 F...m pulseaudio
   /dev/snd/controlC1:  tangarora   2844 F pulseaudio
   /dev/snd/controlC2:  tangarora   2844 F pulseaudio
   /dev/snd/controlC0:  tangarora   2844 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-27 (140 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:10.0-1ubuntu2 [modified: usr/bin/start-pulseaudio-x11]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V8.1
  dmi.board.name: MS-78511
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: 3.1
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV8.1:bd07/20/2015:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-B08911:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-78511:rvr3.1:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-B08911
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

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

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

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

apport information

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

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

Title:
  Bluetooth Audio broken for Bose SoundLink Mini

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Bluetooth Audio stopped working when upgrading/clean install of Ubuntu
  17.04. The Bose SoundLink Mini Bluetooth Connection works fine in
  16.04.

  I have tried restarting and re configuring pulseaudio, but nothing seems to 
work.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D8p:   tangarora   2844 F...m pulseaudio
   /dev/snd/controlC1:  tangarora   2844 F pulseaudio
   /dev/snd/controlC2:  tangarora   2844 F pulseaudio
   /dev/snd/controlC0:  tangarora   2844 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-27 (140 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:10.0-1ubuntu2 [modified: usr/bin/start-pulseaudio-x11]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V8.1
  dmi.board.name: MS-78511
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: 3.1
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV8.1:bd07/20/2015:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-B08911:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-78511:rvr3.1:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-B08911
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

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

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

[Desktop-packages] [Bug 1693464] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1693464/+attachment/4950560/+files/CurrentDmesg.txt

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

Title:
  Bluetooth Audio broken for Bose SoundLink Mini

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Bluetooth Audio stopped working when upgrading/clean install of Ubuntu
  17.04. The Bose SoundLink Mini Bluetooth Connection works fine in
  16.04.

  I have tried restarting and re configuring pulseaudio, but nothing seems to 
work.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D8p:   tangarora   2844 F...m pulseaudio
   /dev/snd/controlC1:  tangarora   2844 F pulseaudio
   /dev/snd/controlC2:  tangarora   2844 F pulseaudio
   /dev/snd/controlC0:  tangarora   2844 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-27 (140 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:10.0-1ubuntu2 [modified: usr/bin/start-pulseaudio-x11]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V8.1
  dmi.board.name: MS-78511
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: 3.1
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV8.1:bd07/20/2015:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-B08911:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-78511:rvr3.1:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-B08911
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

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

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

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

apport information

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

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

Title:
  Bluetooth Audio broken for Bose SoundLink Mini

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Bluetooth Audio stopped working when upgrading/clean install of Ubuntu
  17.04. The Bose SoundLink Mini Bluetooth Connection works fine in
  16.04.

  I have tried restarting and re configuring pulseaudio, but nothing seems to 
work.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D8p:   tangarora   2844 F...m pulseaudio
   /dev/snd/controlC1:  tangarora   2844 F pulseaudio
   /dev/snd/controlC2:  tangarora   2844 F pulseaudio
   /dev/snd/controlC0:  tangarora   2844 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-27 (140 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:10.0-1ubuntu2 [modified: usr/bin/start-pulseaudio-x11]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V8.1
  dmi.board.name: MS-78511
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: 3.1
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV8.1:bd07/20/2015:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-B08911:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-78511:rvr3.1:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-B08911
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

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

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

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

apport information

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

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

Title:
  Bluetooth Audio broken for Bose SoundLink Mini

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Bluetooth Audio stopped working when upgrading/clean install of Ubuntu
  17.04. The Bose SoundLink Mini Bluetooth Connection works fine in
  16.04.

  I have tried restarting and re configuring pulseaudio, but nothing seems to 
work.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D8p:   tangarora   2844 F...m pulseaudio
   /dev/snd/controlC1:  tangarora   2844 F pulseaudio
   /dev/snd/controlC2:  tangarora   2844 F pulseaudio
   /dev/snd/controlC0:  tangarora   2844 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-27 (140 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:10.0-1ubuntu2 [modified: usr/bin/start-pulseaudio-x11]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V8.1
  dmi.board.name: MS-78511
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: 3.1
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV8.1:bd07/20/2015:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-B08911:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-78511:rvr3.1:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-B08911
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

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

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

[Desktop-packages] [Bug 1693464] Re: Bluetooth Audio broken for Bose SoundLink Mini