[Desktop-packages] [Bug 1720510] [NEW] No results after search

2017-09-30 Thread Per-Inge
Public bug reported:

Test case:
Open a new version of gnome-software/Ubuntu Software
Search for soft
No results are shown
Do something outside the gnome-software window, e.g mouse click or focus on 
another window, and the results are shown.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-software 3.26.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 30 09:28:37 2017
InstallationDate: Installed on 2017-09-15 (14 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170915)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.26.0-0ubuntu3
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  No results after search

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Test case:
  Open a new version of gnome-software/Ubuntu Software
  Search for soft
  No results are shown
  Do something outside the gnome-software window, e.g mouse click or focus on 
another window, and the results are shown.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 30 09:28:37 2017
  InstallationDate: Installed on 2017-09-15 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170915)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.0-0ubuntu3
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

2017-09-30 Thread Nir Yeffet
Graham,

Unfortunately I'm not an expert with Network Manager, until now it
remains a mystery to me how it works, where is the configuration stored
and where there heck are the log files?!?. Nevertheless, if the "Network
Manager" icon disappeared, you can run that "Network Connections" tool
directly from "search your computer" (click on the ubuntu logo on the
top left or press the "windows" key) and type "Network Connections".
Alternatively you can run nm-connection-editor from the terminal. On
ubuntu, it is part of package network-manager-gnome.

Nir

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

Title:
  Avahi-daemon withdraws address record

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

Bug description:
  For some reason, if I leave my Ubuntu VM up for a prolonged period of
  time the machine will lose connection to the network.  ip addr shows
  that the nic port no longer has an address and an examination of the
  syslog shows this:

  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast 
group on interface enp0s3.IPv4 with address 10.0.2.15.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.

  
  for no known reason.

  The only reliable way to get the network to come back (that I have
  found) is a full reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 27 15:11:34 2016
  InstallationDate: Installed on 2015-10-22 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

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

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


[Desktop-packages] [Bug 1720395] Re: variable name conflict in french leads to invalid expression errors

2017-09-30 Thread Amr Ibrahim
In the changelog, you mentioned the bugzilla bug number instead of the
LP bug number.

gnome-calculator (1:3.25.91-0ubuntu2) artful; urgency=medium

  * debian/patches/git_fix_calculator_additional_parameter.patch:
- Fix additional operand giving invalid expression for the frenchies
  (LP: #785107)

 -- Didier Roche   Fri, 29 Sep 2017 15:06:16 -0400

** Changed in: gnome-calculator (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  variable name conflict in french leads to invalid expression errors

Status in GNOME Calculator:
  Confirmed
Status in gnome-calculator package in Ubuntu:
  Fix Released

Bug description:
  The code uses an "ans" variable for results but that's a translated
  string in french which creates issues

  step to trigger
  type "1", "enter" then "+1" enter

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

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


[Desktop-packages] [Bug 1716341] Re: Settings for external monitor are deleted after reboot, suspension, log out

2017-09-30 Thread Bug Watch Updater
** Changed in: gnome-control-center
   Status: Incomplete => Confirmed

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

Title:
  Settings for external monitor are deleted after reboot, suspension,
  log out

Status in gnome-control-center:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell source package in Artful:
  Triaged

Bug description:
  New Gnome Settings on Ubuntu 17.10

  Settings for external monitor are working but after reboot/suspension
  /log-out log-in, the system will not remember the setup.

  Example:
  1- open Gnome Settings and select "Devices → Displays"
  2- set the external monitor as "Single Display" and click on "Apply"
  3- log-out

  After log-in the laptop monitor will be set as default instead of the
  external monitor.

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

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


[Desktop-packages] [Bug 1719106] Re: Notification message colour unreadable after upgrade to artful

2017-09-30 Thread Janne Snabb
This bug appears only with "GNOME Classic" session.

How to repeat:

1. Install Ubuntu 17.10
2. apt install gnome-shell-extensions
3. reboot
4. login choosing "GNOME Classic" session
5. open terminal
6. do "notify-send foobar"
7. unreadable notification box appears

Thus, I was able to get rid of this problem by choosing "GNOME on Xorg"
session.

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

** Summary changed:

- Notification message colour unreadable after upgrade to artful
+ Notification message colour unreadable with "GNOME Classic" session

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

Title:
  Notification message colour unreadable with "GNOME Classic" session

Status in gnome-shell-extensions package in Ubuntu:
  New

Bug description:
  After upgrading my Ubuntu GNOME 17.04 system to Ubuntu 17.10 the
  notification message window colour is unreadable.

  It is black text on very dark grey background. See attached
  screenshot.

  To make sure that it does not come from my settings, I created a new
  user account with empty home directory and logged in using that user
  account. The issue still remains.

  I am not sure if the notification messages are produced by the gnome-
  shell package.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Sat Sep 23 19:31:17 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2015-06-06 (839 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
     Users in the 'systemd-journal' group can see all messages. Pass -q to
     turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-09-20 (2 days ago)

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

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


[Desktop-packages] [Bug 1720519] [NEW] Module "module-switch-on-connect" should be loaded once at most. Refusing to load.

2017-09-30 Thread ben van 't ende
Public bug reported:

Pulseaudio daemon does not start after the update to Kubuntu 17.10
beta2, because the module fails to load although it is there.

>From 'pulseaudio -vv'

E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded 
once at most. Refusing to load.
E: [pulseaudio] main.c: Module load failed.
E: [pulseaudio] main.c: Failed to initialize daemon.

PS sorry I am not a seasoned bug reporter. Let me know if I can provide
more info.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   ben2809 F...m chrome
 /dev/snd/controlC0:  ben2809 F chrome
 /dev/snd/timer:  ben2809 f chrome
CurrentDesktop: KDE
Date: Sat Sep 30 11:20:55 2017
InstallationDate: Installed on 2017-04-07 (175 days ago)
InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago)
dmi.bios.date: 10/29/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.10
dmi.board.name: B150M-ITX
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug artful

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

Title:
  Module "module-switch-on-connect" should be loaded once at most.
  Refusing to load.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Pulseaudio daemon does not start after the update to Kubuntu 17.10
  beta2, because the module fails to load although it is there.

  From 'pulseaudio -vv'

  E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded 
once at most. Refusing to load.
  E: [pulseaudio] main.c: Module load failed.
  E: [pulseaudio] main.c: Failed to initialize daemon.

  PS sorry I am not a seasoned bug reporter. Let me know if I can
  provide more info.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ben2809 F...m chrome
   /dev/snd/controlC0:  ben2809 F chrome
   /dev/snd/timer:  ben2809 f chrome
  CurrentDesktop: KDE
  Date: Sat Sep 30 11:20:55 2017
  InstallationDate: Installed on 2017-04-07 (175 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: B150M-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Desktop-packages] [Bug 1720528] [NEW] package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 3

2017-09-30 Thread Xuan Hung
Public bug reported:

It crashed on ubuntu 16.04.03 LTS with Python 2.7

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libglib2.0-dev 2.48.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Sat Sep 30 18:18:36 2017
DpkgTerminalLog:
 Setting up libglib2.0-dev (2.48.2-0ubuntu1) ...
 E: pycompile:233: Requested versions are not installed
 dpkg: error processing package libglib2.0-dev (--configure):
  subprocess installed post-installation script returned error exit status 3
DuplicateSignature:
 package:libglib2.0-dev:2.48.2-0ubuntu1
 Setting up libglib2.0-dev (2.48.2-0ubuntu1) ...
 E: pycompile:233: Requested versions are not installed
 dpkg: error processing package libglib2.0-dev (--configure):
  subprocess installed post-installation script returned error exit status 3
ErrorMessage: subprocess installed post-installation script returned error exit 
status 3
InstallationDate: Installed on 2017-08-26 (35 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: glib2.0
Title: package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 3
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check xenial

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

Title:
  package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 3

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  It crashed on ubuntu 16.04.03 LTS with Python 2.7

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libglib2.0-dev 2.48.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sat Sep 30 18:18:36 2017
  DpkgTerminalLog:
   Setting up libglib2.0-dev (2.48.2-0ubuntu1) ...
   E: pycompile:233: Requested versions are not installed
   dpkg: error processing package libglib2.0-dev (--configure):
subprocess installed post-installation script returned error exit status 3
  DuplicateSignature:
   package:libglib2.0-dev:2.48.2-0ubuntu1
   Setting up libglib2.0-dev (2.48.2-0ubuntu1) ...
   E: pycompile:233: Requested versions are not installed
   dpkg: error processing package libglib2.0-dev (--configure):
subprocess installed post-installation script returned error exit status 3
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 3
  InstallationDate: Installed on 2017-08-26 (35 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: glib2.0
  Title: package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1720527] [NEW] GUFW gui no longer appears in System Settings or menus

2017-09-30 Thread René Lender
Public bug reported:

I've been testing Ubuntu GNOME 17.10 beta2 and I notice that Firewall
Configuration no longer appears in the System Settings gui, nor in any
menu.

The gui can be launched by using the terminal.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Sep 30 13:14:49 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2017-09-29 (0 days ago)
InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  GUFW gui no longer appears in System Settings or menus

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

Bug description:
  I've been testing Ubuntu GNOME 17.10 beta2 and I notice that Firewall
  Configuration no longer appears in the System Settings gui, nor in any
  menu.

  The gui can be launched by using the terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Sep 30 13:14:49 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-09-29 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170919)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1720529] [NEW] ~/dmesg and your /var/log/Xorg.0.log.

2017-09-30 Thread sunkaranam sai sri hari
Public bug reported:

i am unable to use my wireless mouse

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
Uname: Linux 4.4.0-96-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
BootLog:
 Scanning for Btrfs filesystems
 UBUNTU: clean, 275992/60309504 files, 5656499/241220352 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat Sep 30 16:46:23 2017
DistUpgraded: Fresh install
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0792]
InstallationDate: Installed on 2017-08-08 (53 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 138a:0010 Validity Sensors, Inc. VFS Fingerprint sensor
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Vostro 14-3468
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic.efi.signed 
root=UUID=de326c40-9285-4350-b59e-15e9b09834cb ro acpi_rev_override quiet 
splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/23/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.08.00
dmi.board.name: 0T1X3V
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:svnDellInc.:pnVostro14-3468:pvr:rvnDellInc.:rn0T1X3V:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Vostro 14-3468
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sat Sep 30 16:33:28 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1767 
 vendor BOE
xserver.version: 2:1.18.4-0ubuntu0.4

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


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

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

Title:
  ~/dmesg and your /var/log/Xorg.0.log.

Status in xorg package in Ubuntu:
  New

Bug description:
  i am unable to use my wireless mouse

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems
   UBUNTU: clean, 275992/60309504 files, 5656499/241220352 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Sep 30 16:46:23 2017
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0792]
  InstallationDate: Installed on 2017-08-08 (53 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:000

[Desktop-packages] [Bug 1720528] Re: package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 3

2017-09-30 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 glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1720528

Title:
  package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 3

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  It crashed on ubuntu 16.04.03 LTS with Python 2.7

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libglib2.0-dev 2.48.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sat Sep 30 18:18:36 2017
  DpkgTerminalLog:
   Setting up libglib2.0-dev (2.48.2-0ubuntu1) ...
   E: pycompile:233: Requested versions are not installed
   dpkg: error processing package libglib2.0-dev (--configure):
subprocess installed post-installation script returned error exit status 3
  DuplicateSignature:
   package:libglib2.0-dev:2.48.2-0ubuntu1
   Setting up libglib2.0-dev (2.48.2-0ubuntu1) ...
   E: pycompile:233: Requested versions are not installed
   dpkg: error processing package libglib2.0-dev (--configure):
subprocess installed post-installation script returned error exit status 3
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 3
  InstallationDate: Installed on 2017-08-26 (35 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: glib2.0
  Title: package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1720149] Re: gnome-shell segv on wake from display or system sleep

2017-09-30 Thread Rachel Greenham
It may be the Arc shell theme, in interaction with nVidia:

I was unable to reproduce the problem on the Macbook Pro using Xorg
gnome session, and that still with the Arc shell theme. Both a short
(few minutes) and long (greater than one hour) display sleeps tested.

I was also unable to reproduce it on the nVidia-equipped desktop with
the Default shell theme selected, on either short or long display sleep.
needs-root-rights is still set to yes in this configuration (ie: the
same as tested yesterday evening except for switching back to default
themes.)

I don't know how a theme can cause a segfault, it's just image assets
and css. But I'll leave it on Default for now to see if the issue does
after all recur. I'll also go back to modeset=1 but needs-root-rights
left unset, and wait and see.

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

Title:
  gnome-shell segv on wake from display or system sleep

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The observable symptom is that if I go away and let the computer go
  either to display sleep or suspend, when I come back and try to wake
  it up again, I find myself, after sliding up the lock screen, at the
  gdm login screen. I'm logged out, and logging in gives me a fresh new
  session. Anything I had open in the previous session is lost. (I'm
  getting used to saving stuff before I step away from the computer!)

  The only trace I've been able to find is that in /var/log/syslog I see
  a line like:

  Sep 28 14:38:44 fleetfoot kernel: [10621.432586] gnome-shell[1863]:
  segfault at 2c ip 7f6200e82434 sp 7ffc46f981c8 error 4 in
  libmutter-1.so.0.0.0[7f6200de4000+14]

  This happens at the time of attempted wake, not the time of going to
  sleep. It's preceded by a lot of activity from gdm-x-session that I'm
  not sure is indicating any error, just the process of waking up. I
  will attach a portion of syslog surrounding the whole event in the
  hope it helps. (In fact attaching the whole current syslog file - it
  has two such events occuring in it, first display sleep/wake at 09:02
  this morning, and secondly (because I was experimenting) a suspend-
  wake at 14:38 this afternoon.

  This is only affecting Xorg sessions, and may possibly only be
  affecting where nvidia is in use, I'm not sure about that. But the
  fact it occurs on display wake alone, not needing the system itself to
  have suspended (I was trying suspend to see if it *avoided* the
  problem, which it doesn't), does point the finger in that direction I
  guess. But ultimately I'm guessing it's gnome-shell itself segfaulting
  that's causing the login session to end?

  Not observed on my Wayland system.

  This is not new as of the current version of gnome-shell but I think
  it is relatively recent. Now my hackintosh partition is wrecked by a
  failed upgrade to High Sierra I'm using my Linux system more in
  earnest than before, so I'm hitting this often enough for it to
  provoke a bug report (and much of the time, to just turn all auto
  suspend/display-sleep off and instead shut down the computer when I'm
  leaving it for any length of time).

  The ubuntu bug reporter is not picking this up by itself, so I presume
  a crash report of the sort that uses is not being saved.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 28 14:41:07 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-07-30 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-08-22 (37 days ago)

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

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


[Desktop-packages] [Bug 1720133] Re: USB 3.0 displays are black on Ubuntu after x.org update to 1.18.3 or newer

2017-09-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  USB 3.0 displays are black on Ubuntu after x.org update to 1.18.3 or
  newer

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * This impacts all Ubuntu releases which received an update of x.org
  to 1.18.3 or newer, i.e. Ubuntu 16.04, 16.10, 17.04 & 17.10

   * End users are unable to use their USB displays unless they
  workaround the problem which currently involves disabling pageflip for
  modesetting in x.org.conf file

   * The fix which has been submitted to x.org extends blacklisting
  mechanism so the EVDI kernel module which is essential for DisplayLink
  USB 3.0 devices to work is correctly recognised by x.org. Then the
  PRIME sync is disabled in such case; The patch can be found here:
  
https://cgit.freedesktop.org/xorg/xserver/commit/?id=fbd80b2c8ebe9fd41229dc5438524d107c071ff1

  [Test Case]

  1. On a PC device with Ubuntu install DisplayLink SW for Ubuntu v1.3.54 
downloaded from http://www.displaylink.com/downloads/ubuntu. Detailed 
requirements and instructions can be found here:  
  2. Plug in a DisplayLink USB 3.0 compatible device, e.g. Dell D3100 docking 
station
  3. Plug in an external monitor (HDMI or DisplayPort) to the docking station

  Expected result: 
  The external monitor should light up and show the desktop

  Actual result: 
  The monitor remains black or shows frozen desktop.

  [Regression Potential]

   * The patchset extends number of modules for which x.org changes its
  functionality. It checks if "evdi" string is in the syspath so it is
  quite unlikely there would be any impact on anything else then USB 3.0
  displays which use EVDI module.

  [Other Info]
   
   * The patch has been applied to Ubuntu x.org source code built and tested.

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

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


[Desktop-packages] [Bug 1720133] Re: USB 3.0 displays are black on Ubuntu after x.org update to 1.18.3 or newer

2017-09-30 Thread Christopher M. Rogers
Same result on Ubuntu 17.10 - black screen with cursor on USB monitor
running on displaylink driver as mentioned above.

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

Title:
  USB 3.0 displays are black on Ubuntu after x.org update to 1.18.3 or
  newer

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * This impacts all Ubuntu releases which received an update of x.org
  to 1.18.3 or newer, i.e. Ubuntu 16.04, 16.10, 17.04 & 17.10

   * End users are unable to use their USB displays unless they
  workaround the problem which currently involves disabling pageflip for
  modesetting in x.org.conf file

   * The fix which has been submitted to x.org extends blacklisting
  mechanism so the EVDI kernel module which is essential for DisplayLink
  USB 3.0 devices to work is correctly recognised by x.org. Then the
  PRIME sync is disabled in such case; The patch can be found here:
  
https://cgit.freedesktop.org/xorg/xserver/commit/?id=fbd80b2c8ebe9fd41229dc5438524d107c071ff1

  [Test Case]

  1. On a PC device with Ubuntu install DisplayLink SW for Ubuntu v1.3.54 
downloaded from http://www.displaylink.com/downloads/ubuntu. Detailed 
requirements and instructions can be found here:  
  2. Plug in a DisplayLink USB 3.0 compatible device, e.g. Dell D3100 docking 
station
  3. Plug in an external monitor (HDMI or DisplayPort) to the docking station

  Expected result: 
  The external monitor should light up and show the desktop

  Actual result: 
  The monitor remains black or shows frozen desktop.

  [Regression Potential]

   * The patchset extends number of modules for which x.org changes its
  functionality. It checks if "evdi" string is in the syspath so it is
  quite unlikely there would be any impact on anything else then USB 3.0
  displays which use EVDI module.

  [Other Info]
   
   * The patch has been applied to Ubuntu x.org source code built and tested.

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

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


[Desktop-packages] [Bug 1720519] Re: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.

2017-09-30 Thread ben van 't ende
Heyla,

After reading up some more I removed alsa and pulseaudio and reinstalled
like this:

sudo apt-get remove --purge alsa-base pulseaudio

Now install again Alsa and Pulse Audio:

sudo apt-get install alsa-base pulseaudio

Then, reload Alsa:

sudo alsa force-reload

That made audio up and running again!

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

Title:
  Module "module-switch-on-connect" should be loaded once at most.
  Refusing to load.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Pulseaudio daemon does not start after the update to Kubuntu 17.10
  beta2, because the module fails to load although it is there.

  From 'pulseaudio -vv'

  E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded 
once at most. Refusing to load.
  E: [pulseaudio] main.c: Module load failed.
  E: [pulseaudio] main.c: Failed to initialize daemon.

  PS sorry I am not a seasoned bug reporter. Let me know if I can
  provide more info.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ben2809 F...m chrome
   /dev/snd/controlC0:  ben2809 F chrome
   /dev/snd/timer:  ben2809 f chrome
  CurrentDesktop: KDE
  Date: Sat Sep 30 11:20:55 2017
  InstallationDate: Installed on 2017-04-07 (175 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: B150M-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Desktop-packages] [Bug 1720519] Re: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.

2017-09-30 Thread ben van 't ende
fixed myself by reinstalling pulseaudio

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => ben van 't ende (benvantende)

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

Title:
  Module "module-switch-on-connect" should be loaded once at most.
  Refusing to load.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Pulseaudio daemon does not start after the update to Kubuntu 17.10
  beta2, because the module fails to load although it is there.

  From 'pulseaudio -vv'

  E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded 
once at most. Refusing to load.
  E: [pulseaudio] main.c: Module load failed.
  E: [pulseaudio] main.c: Failed to initialize daemon.

  PS sorry I am not a seasoned bug reporter. Let me know if I can
  provide more info.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ben2809 F...m chrome
   /dev/snd/controlC0:  ben2809 F chrome
   /dev/snd/timer:  ben2809 f chrome
  CurrentDesktop: KDE
  Date: Sat Sep 30 11:20:55 2017
  InstallationDate: Installed on 2017-04-07 (175 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: B150M-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


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

2017-09-30 Thread Apport retracing service
*** This bug is a duplicate of bug 1505409 ***
https://bugs.launchpad.net/bugs/1505409

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Always bug  After update too 
  I don't see where is this bug Is there any test to do ?

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

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

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


[Desktop-packages] [Bug 1720106] [NEW] inkscape crashes when saving as pdf, no error shown

2017-09-30 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I created .svg in Inkscape on Windows, and after trying to open and save
it to PDF on Ubuntu (I trying on 16.04 and 17.04) Inkscape crashes
without any error shown.


Can you repeat this bug?

** Affects: inkscape
 Importance: Undecided
 Status: New

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

-- 
inkscape crashes when saving as pdf, no error shown
https://bugs.launchpad.net/bugs/1720106
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to inkscape 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 1720483] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-09-30 Thread Paul White
*** This bug is a duplicate of bug 1514474 ***
https://bugs.launchpad.net/bugs/1514474

** This bug has been marked a duplicate of bug 1514474
   package tex-common 6.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  do-release-upgrade from 14.04 to 16.04 today.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 3.13.0-129.178-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-129-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  Date: Fri Sep 29 21:35:53 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-09-30 (0 days ago)

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

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


[Desktop-packages] [Bug 1720149] Re: gnome-shell segv on wake from display or system sleep

2017-09-30 Thread Rachel Greenham
I think my modeset=1 test earlier was invalid; I don't think that change
was ever applied. It *did* get applied just now with a routine dist-
upgrade, which included an update to console-setup, which forced update-
initramfs. And then the system was unbootable except via the recovery
system. syslog is full of crashes like this in rapid succession:

Sep 30 13:33:38 fleetfoot kernel: [  117.641448] [ cut here 
]
Sep 30 13:33:38 fleetfoot kernel: [  117.641467] WARNING: CPU: 0 PID: 221 at 
/build/linux-s_bACt/linux-4.13.0/drivers/gpu/drm/drm_atomic_helper.c:1682 
drm_atomic_helper_commit_hw_done+0x99/0xa0 [drm_kms_helper]
Sep 30 13:33:38 fleetfoot kernel: [  117.641468] Modules linked in: rfcomm 
hid_magicmouse hidp cmac bnep nls_iso8859_1 nvidia_uvm(POE) hid_apple joydev 
input_leds hid_generic ath3k btusb btrtl btbcm btintel bluetooth snd_usb_audio 
snd_usbmidi_lib usbhid hid ecdh_generic snd_hda_codec_hdmi eeepc_wmi asus_wmi 
cmdlinepart intel_spi_platform intel_rapl intel_spi spi_nor wmi_bmof 
sparse_keymap mtd x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm 
snd_hda_codec_realtek snd_hda_codec_generic irqbypass crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec pcbc snd_hda_core 
snd_hwdep arc4 snd_pcm snd_seq_midi ath9k aesni_intel snd_seq_midi_event 
ath9k_common ath9k_hw snd_rawmidi aes_x86_64 crypto_simd snd_seq glue_helper 
cryptd ath intel_cstate snd_seq_device intel_rapl_perf mac80211 snd_timer 
cfg80211 snd soundcore
Sep 30 13:33:38 fleetfoot kernel: [  117.641496]  mei_me mei shpchp lpc_ich wmi 
mac_hid nct6775 hwmon_vid coretemp parport_pc ppdev lp parport ip_tables 
x_tables autofs4 nvidia_drm(POE) nvidia_modeset(POE) i915 nvidia(POE) 
i2c_algo_bit drm_kms_helper e1000e syscopyarea sysfillrect sysimgblt 
fb_sys_fops ahci ptp drm libahci pps_core video
Sep 30 13:33:38 fleetfoot kernel: [  117.641507] CPU: 0 PID: 221 Comm: 
kworker/u16:6 Tainted: PW  OE   4.13.0-12-generic #13-Ubuntu
Sep 30 13:33:38 fleetfoot kernel: [  117.641507] Hardware name: ASUS All 
Series/Z87I-PRO, BIOS 1005 11/26/2014
Sep 30 13:33:38 fleetfoot kernel: [  117.641511] Workqueue: events_unbound 
commit_work [drm_kms_helper]
Sep 30 13:33:38 fleetfoot kernel: [  117.641512] task: 970a91cec5c0 
task.stack: b72901e5c000
Sep 30 13:33:38 fleetfoot kernel: [  117.641515] RIP: 
0010:drm_atomic_helper_commit_hw_done+0x99/0xa0 [drm_kms_helper]
Sep 30 13:33:38 fleetfoot kernel: [  117.641515] RSP: 0018:b72901e5fdb8 
EFLAGS: 00010286
Sep 30 13:33:38 fleetfoot kernel: [  117.641516] RAX: 970a8ff8b008 RBX: 
0004 RCX: 970a9ca0c000
Sep 30 13:33:38 fleetfoot kernel: [  117.641516] RDX: 970a8dce1400 RSI: 
0001 RDI: 970a93a56c08
Sep 30 13:33:38 fleetfoot kernel: [  117.641517] RBP: b72901e5fdd8 R08: 
970aafa12398 R09: 0018
Sep 30 13:33:38 fleetfoot kernel: [  117.641517] R10: b72901e5fd88 R11: 
0372 R12: 0001
Sep 30 13:33:38 fleetfoot kernel: [  117.641518] R13: 970a97780b40 R14: 
970a93a56c08 R15: 970a93a56c08
Sep 30 13:33:38 fleetfoot kernel: [  117.641518] FS:  () 
GS:970aafa0() knlGS:
Sep 30 13:33:38 fleetfoot kernel: [  117.641519] CS:  0010 DS:  ES:  
CR0: 80050033
Sep 30 13:33:38 fleetfoot kernel: [  117.641519] CR2: 7fa55cd3a010 CR3: 
0003ff609000 CR4: 001406f0
Sep 30 13:33:38 fleetfoot kernel: [  117.641520] DR0:  DR1: 
 DR2: 
Sep 30 13:33:38 fleetfoot kernel: [  117.641520] DR3:  DR6: 
fffe0ff0 DR7: 0400
Sep 30 13:33:38 fleetfoot kernel: [  117.641521] Call Trace:
Sep 30 13:33:38 fleetfoot kernel: [  117.641524]  
nvidia_drm_atomic_helper_commit_tail+0x10e/0x170 [nvidia_drm]
Sep 30 13:33:38 fleetfoot kernel: [  117.641527]  commit_tail+0x3f/0x60 
[drm_kms_helper]
Sep 30 13:33:38 fleetfoot kernel: [  117.641530]  commit_work+0x12/0x20 
[drm_kms_helper]
Sep 30 13:33:38 fleetfoot kernel: [  117.641532]  process_one_work+0x1e7/0x410
Sep 30 13:33:38 fleetfoot kernel: [  117.641533]  worker_thread+0x4a/0x410
Sep 30 13:33:38 fleetfoot kernel: [  117.641534]  kthread+0x125/0x140
Sep 30 13:33:38 fleetfoot kernel: [  117.641535]  ? process_one_work+0x410/0x410
Sep 30 13:33:38 fleetfoot kernel: [  117.641536]  ? 
kthread_create_on_node+0x70/0x70
Sep 30 13:33:38 fleetfoot kernel: [  117.641538]  ret_from_fork+0x25/0x30
Sep 30 13:33:38 fleetfoot kernel: [  117.641538] Code: 7d 30 e8 db b8 2c fa 48 
89 df c6 07 00 0f 1f 40 00 49 8b 4e 08 41 83 c4 01 44 39 a1 38 03 00 00 7f 98 
5b 41 5c 41 5d 41 5e 5d c3 <0f> ff eb c0 f3 c3 90 0f 1f 44 00 00 48 8b 4f 08 8b 
81 38 03 00
Sep 30 13:33:38 fleetfoot kernel: [  117.641552] ---[ end trace 
ab364b2a1fae43bb ]---
Sep 30 13:33:39 fleetfoot kernel: [  117.974932] [ cut here 
]


However that's probably offtopic here, and just speaks to nvidia kms not

[Desktop-packages] [Bug 1720106] Re: inkscape crashes when saving as pdf, no error shown

2017-09-30 Thread Paul White
** Package changed: ubuntu => inkscape (Ubuntu)

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

Title:
  inkscape crashes when saving as pdf, no error shown

Status in Inkscape:
  New
Status in inkscape package in Ubuntu:
  New

Bug description:
  I created .svg in Inkscape on Windows, and after trying to open and
  save it to PDF on Ubuntu (I trying on 16.04 and 17.04) Inkscape
  crashes without any error shown.

  
  Can you repeat this bug?

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

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


[Desktop-packages] [Bug 1720539] [NEW] network-manager-openvpn-gnome cannot be installed using GNOME Software

2017-09-30 Thread AsciiWolf
Public bug reported:

The network-manager-openvpn-gnome package cannot be installed using
GNOME Software as GNOME Control Center add-on because it is missing the
necessary AppStream metadata.

Steps to reproduce:
1. Run GNOME Software.
2. Search for "Control Center" and select "GNOME Control Center".
3. See available add-ons at the bottom of the page.

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


** Tags: appstream artful

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

Title:
  network-manager-openvpn-gnome cannot be installed using GNOME Software

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

Bug description:
  The network-manager-openvpn-gnome package cannot be installed using
  GNOME Software as GNOME Control Center add-on because it is missing
  the necessary AppStream metadata.

  Steps to reproduce:
  1. Run GNOME Software.
  2. Search for "Control Center" and select "GNOME Control Center".
  3. See available add-ons at the bottom of the page.

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

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


[Desktop-packages] [Bug 1720438] Re: brightness control broken nvidia

2017-09-30 Thread Brinstar
I've managed to use a workaround to make the hotkeys work.

I added acpi_osi=Linux to the grub config file and did an update-grub
and it works. But I think it would be better if this was looked into as
it did work fine without the acpi addition on Ubuntu LTS.

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

Title:
  brightness control broken nvidia

Status in gnome-power-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10 beta 2 
  Nvidia 310M, 340.x official driver installed with Additional Drivers program

  The brightness control built into the laptop (Dell Vostro 3300) isn't 
changing the brightness. Normally I can use Fn + Up/Down arrow keys to change 
the brightness.
  The brightness control works fine in Ubuntu 16.04 with the same driver series.

  I don't know if this is a GNOME 3.26 bug but it's likely as I'm having
  the exact same problem with Fedora 26 on this laptop.

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

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


[Desktop-packages] [Bug 1719322] Re: Remove patch to remove headerbar

2017-09-30 Thread Jeremy Bicha
I agree. There isn't much point in not using CSD for Epiphany since the
visual difference is really minor and Firefox will be getting CSD soon
too.

** Changed in: epiphany-browser (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Remove patch to remove headerbar

Status in epiphany-browser package in Ubuntu:
  Fix Committed
Status in evince package in Ubuntu:
  Incomplete
Status in file-roller package in Ubuntu:
  Incomplete
Status in gnome-contacts package in Ubuntu:
  Incomplete

Bug description:
  As of Artful, it seems that there are still patches against various
  apps that remove/replace the Gtk.HeaderBar with a Gtk.Toolbar.

  Now that GNOME Shell is default in Ubuntu and there is better support
  for client-side decorations, these patches can probably go away

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

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


[Desktop-packages] [Bug 1720539] Re: network-manager-openvpn-gnome cannot be installed using GNOME Software

2017-09-30 Thread Jeremy Bicha
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

https://bugzilla.gnome.org/enter_bug.cgi?product=NetworkManager&component=VPN:%20openvpn

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

Title:
  network-manager-openvpn-gnome cannot be installed using GNOME Software

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

Bug description:
  The network-manager-openvpn-gnome package cannot be installed using
  GNOME Software as GNOME Control Center add-on because it is missing
  the necessary AppStream metadata.

  Steps to reproduce:
  1. Run GNOME Software.
  2. Search for "Control Center" and select "GNOME Control Center".
  3. See available add-ons at the bottom of the page.

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

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


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

2017-09-30 Thread HuaiDan
Still an issue; Ubuntu 17.04; 4.10.0-35-generic.

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

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

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

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

  It is not browser specific and not website specific.

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

  The issue exists on both ubuntu and kubuntu 16.04.

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

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

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

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

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


[Desktop-packages] [Bug 1409166] Re: Popup dialog "could not set the configuration for CRTC 65" steals keyboard, hinders login in 3-monitor configuration

2017-09-30 Thread WinEunuchs2Unix
I've been using LVDS + HDMI for a few years first under Ubuntu 14.04 and
currently under Ubuntu 16.04.

Today I setup an second external TV using the VGA port and an in-line
VGA to HDMI converter box that's worked before. The necessary xrandr
commands are given:

`xrandr --newmode "1920x1080_60.00"  173.00  1920 2048 2248 2576  1080 1083 
1088 1120 -hsync +vsync`
`xrandr --addmode VGA1 "1920x1080"`

However the CRTC 65 popup error message results.

Although I am long-term shopping for a new laptop with HDMI + one or two
DP's, it would be nice to have HDMI+VGA working now.

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

Title:
  Popup dialog "could not set the configuration for CRTC 65" steals
  keyboard, hinders login in 3-monitor configuration

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  Every time I boot, while I'm trying to enter my password in the
  initial login screen (from Unity?), a dialog box pops up saying "Could
  not switch the monitor configuration  could not set the configuration
  for CRTC 65".

  The dialog box also steals the keyboard focus, which is very confusing
  if for some reason you're entering the password on an external display
  while the normally unused laptop display is not visible.  For example,
  three times in a row this morning I rebooted and tried unsuccessfully
  to log in.  Since the dialog box is only displayed on the laptop
  display, which I never use when external monitors are available, I had
  no idea why my keyboard seemed broken.

  Background:

  My Lenovo Thinkpad X230 Tablet laptop has a VGA and a DVI connector.
  I have the VGA hooked up to a Viewsonic 1920x1080 monitor, positioned
  above the laptop display.  I have a Samsung monitor to the right of
  the Viewsonic.  Since my laptop seems to only support two displays
  (which also seems true in Windows), I normally disable and totally
  ignore my laptop display, and may have papers propped up in front of
  it etc.

  Note that when I initially configured the third display I saw the
  following highly confusing behavior.  From Settings I tried to add a
  Samsung monitor to the right of the Viewsonic, via a DVI-to-HDMI
  passive connector, and got this dialog box when I hit "Apply":

     The selected configuration for displays could not be applied
     could not set the configuration for CRTC 65

  I clicked "OK" and got another dialog box:
     Failed to apply configuration: %s
     Can't add monitor: 
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gnome_2drr_2derror_2dquark.Code2:
 could not set the configuration for CRTC 65

  It works if I disable my laptop monitor, so it looks like the problem
  is with adding a third display.  I would think it would be a pretty
  common use case to use two nice external displays and disable the
  laptop display.

  Even when the hardware can't handle a third display, the error
  messages should not be so confusing, and the login process shouldn't
  result in the keyboard being mysteriously stolen by a dialog box on a
  display which may never be visible.

  This is on Trusty 64-bit, up-to-date with upgrades.

  This bug seems similar to bug 1304627, but it seemed cleanest to get
  all the right information reported via ubuntu-bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jan  9 15:35:57 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:2203]
  InstallationDate: Installed on 2015-01-01 (8 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-43-generic 
root=UUID=6dce26c4-3d5b-4980-880e-06f249f77c57 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/22/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET96WW (2.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chass

[Desktop-packages] [Bug 1720549] Re: crash when pressing alt+f which was assigned to "hide and show toolbar" shortcut

2017-09-30 Thread Apport retracing service
*** This bug is a duplicate of bug 1438014 ***
https://bugs.launchpad.net/bugs/1438014

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 #1438014, 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/1720549/+attachment/4959347/+files/CoreDump.gz

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  crash when pressing alt+f which was assigned to "hide and show
  toolbar" shortcut

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  just assigned alt+f to the "hide and show toolbar" shortcut (dialog
  was still opened) and pressed alt+f (shortcut conflict with default?)

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Sep 30 17:04:45 2017
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2012-07-22 (1895 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago)
  UserGroups: adm cdrom dialout dip libvirt libvirtd lpadmin plugdev sambashare 
sudo vboxusers wireshark

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

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


[Desktop-packages] [Bug 1720551] [NEW] Evince show this text when I try to open a PDF: Failed to load backend for 'application/pdf': libtiff.so.5

2017-09-30 Thread Felipe Castillo
Public bug reported:

Recently I notice I can't open any PDF. I've tried with Okular, Evince
and Quick PDF View. All of them mark an error as I try to open any PDF.

Evince show this text when I try to open a PDF: Failed to load backend
for 'application/pdf': libtiff.so.5

I'm using Ubuntu 16.04 LTS in 32 bits

I've already checked that libtiff5 is installed.

f: /usr/lib/i386-linux-gnu/libtiff.so.5
Drwxr-xr-x root  root  / 
drwxr-xr-x root  root   usr 
drwxr-xr-x root  root   lib 
drwxr-xr-x root  root   i386-linux-gnu 
srwxrw-r-T 138742031 1300990212 libtiff.so.5

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: evince 3.18.2-1ubuntu4.1
ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
Uname: Linux 4.4.0-96-generic i686
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: i386
CurrentDesktop: Unity
Date: Sat Sep 30 10:26:10 2017
InstallationDate: Installed on 2015-05-26 (857 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
ProcEnviron:
 LANGUAGE=es_MX:es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_MX.UTF-8
 SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 xenial

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

Title:
  Evince show this text when I try to open a PDF: Failed to load backend
  for 'application/pdf': libtiff.so.5

Status in evince package in Ubuntu:
  New

Bug description:
  Recently I notice I can't open any PDF. I've tried with Okular, Evince
  and Quick PDF View. All of them mark an error as I try to open any
  PDF.

  Evince show this text when I try to open a PDF: Failed to load backend
  for 'application/pdf': libtiff.so.5

  I'm using Ubuntu 16.04 LTS in 32 bits

  I've already checked that libtiff5 is installed.

  f: /usr/lib/i386-linux-gnu/libtiff.so.5
  Drwxr-xr-x root  root  / 
  drwxr-xr-x root  root   usr 
  drwxr-xr-x root  root   lib 
  drwxr-xr-x root  root   i386-linux-gnu 
  srwxrw-r-T 138742031 1300990212 libtiff.so.5

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: evince 3.18.2-1ubuntu4.1
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 30 10:26:10 2017
  InstallationDate: Installed on 2015-05-26 (857 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  ProcEnviron:
   LANGUAGE=es_MX:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_MX.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1719322] Re: Remove patch to remove headerbar

2017-09-30 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-desktop/file-roller/ubuntu

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

Title:
  Remove patch to remove headerbar

Status in epiphany-browser package in Ubuntu:
  Fix Committed
Status in evince package in Ubuntu:
  Incomplete
Status in file-roller package in Ubuntu:
  Fix Committed
Status in gnome-contacts package in Ubuntu:
  Fix Committed

Bug description:
  As of Artful, it seems that there are still patches against various
  apps that remove/replace the Gtk.HeaderBar with a Gtk.Toolbar.

  Now that GNOME Shell is default in Ubuntu and there is better support
  for client-side decorations, these patches can probably go away

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

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


[Desktop-packages] [Bug 1719322] Re: Remove patch to remove headerbar

2017-09-30 Thread Jeremy Bicha
** Changed in: file-roller (Ubuntu)
   Status: Incomplete => Fix Committed

** Changed in: gnome-contacts (Ubuntu)
   Status: Incomplete => Fix Committed

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

Title:
  Remove patch to remove headerbar

Status in epiphany-browser package in Ubuntu:
  Fix Committed
Status in evince package in Ubuntu:
  Incomplete
Status in file-roller package in Ubuntu:
  Fix Committed
Status in gnome-contacts package in Ubuntu:
  Fix Committed

Bug description:
  As of Artful, it seems that there are still patches against various
  apps that remove/replace the Gtk.HeaderBar with a Gtk.Toolbar.

  Now that GNOME Shell is default in Ubuntu and there is better support
  for client-side decorations, these patches can probably go away

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

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


[Desktop-packages] [Bug 1720446] Re: Freefont is buggy and produce broken rendering for many indian languages

2017-09-30 Thread Anivar Aravind
** Changed in: fonts-freefont (Ubuntu)
   Status: New => Confirmed

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

Title:
  Freefont is buggy and produce broken rendering for many indian
  languages

Status in fonts-freefont package in Ubuntu:
  Confirmed

Bug description:
  Freefont is last updated in 2012& not maintained. It is buggy and not
  producing quality rendering in Most Indian Languages. This is the only
  font in Ubuntu as of now supported in indtaller. But this results in
  broken rendering. I suggest to remove this font from installer and
  make it optional. I also suggest to remove this from ubuntu-desktop &
  vlc dependency

  In past there was a package called ttf-indic-fonts-core as an installer 
dependency to support indian languages. But now that is also removed and 
producing Square boxes for many Indian languages. 
  Ref : 
https://bugs.launchpad.net/ubuntu/+source/ttf-indic-fonts/+bug/958345/comments/39
  There is a need of better addressing of Indian language support in Ubuntu 
prior to 17.10 . The support must come from seperate font package & not via 
broken ttf-freefont. 
  As of now Beta 2 of 17.10 produces rendering errors for many languages 
including Malayalam because of fonts-freefont.

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

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


[Desktop-packages] [Bug 1719322] Re: Remove patch to remove headerbar

2017-09-30 Thread Jeremy Bicha
The GNOME Contacts patches were broken: it wasn't possible to use the
app menu on Budgie or Xfce. Also, the patches no longer applied against

The headerbar patches look bad in Xfce (waste of vertical space) and
they are inconsistent. Most GNOME apps use headerbars so trying to avoid
them in a few apps isn't very helpful. Xfce doesn't include Epiphany,
GNOME Contacts, or file-roller by default anyway.

file-roller still uses a traditional menu bar on Unity.

There is one issue: it makes LP: #1720555 a bit worse.

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

Title:
  Remove patch to remove headerbar

Status in epiphany-browser package in Ubuntu:
  Fix Committed
Status in evince package in Ubuntu:
  Incomplete
Status in file-roller package in Ubuntu:
  Fix Committed
Status in gnome-contacts package in Ubuntu:
  Fix Committed

Bug description:
  As of Artful, it seems that there are still patches against various
  apps that remove/replace the Gtk.HeaderBar with a Gtk.Toolbar.

  Now that GNOME Shell is default in Ubuntu and there is better support
  for client-side decorations, these patches can probably go away

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

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


[Desktop-packages] [Bug 1719322] Re: Remove patch to remove headerbar

2017-09-30 Thread Jeremy Bicha
*the gnome-contacts patches no longer applied against 3.26

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

Title:
  Remove patch to remove headerbar

Status in epiphany-browser package in Ubuntu:
  Fix Committed
Status in evince package in Ubuntu:
  Incomplete
Status in file-roller package in Ubuntu:
  Fix Committed
Status in gnome-contacts package in Ubuntu:
  Fix Committed

Bug description:
  As of Artful, it seems that there are still patches against various
  apps that remove/replace the Gtk.HeaderBar with a Gtk.Toolbar.

  Now that GNOME Shell is default in Ubuntu and there is better support
  for client-side decorations, these patches can probably go away

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

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


[Desktop-packages] [Bug 1719322] Re: Remove patch to remove headerbar

2017-09-30 Thread Jeremy Bicha
** Also affects: eog (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: eog (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Remove patch to remove headerbar

Status in eog package in Ubuntu:
  Incomplete
Status in epiphany-browser package in Ubuntu:
  Fix Committed
Status in evince package in Ubuntu:
  Incomplete
Status in file-roller package in Ubuntu:
  Fix Committed
Status in gnome-contacts package in Ubuntu:
  Fix Committed

Bug description:
  As of Artful, it seems that there are still patches against various
  apps that remove/replace the Gtk.HeaderBar with a Gtk.Toolbar.

  Now that GNOME Shell is default in Ubuntu and there is better support
  for client-side decorations, these patches can probably go away

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

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


[Desktop-packages] [Bug 1718719] Re: qemu can't capture keys properly under wayland

2017-09-30 Thread Timo Aaltonen
Now the question is should the patch be dropped or wait for a fix from
upstream. I'm leaning towards the first option, since artful is about to
be released.

** Package changed: wayland (Ubuntu) => xorg-server (Ubuntu)

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

** Changed in: xorg-server (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  qemu can't capture keys properly under wayland

Status in QEMU:
  New
Status in XServer:
  Incomplete
Status in qemu package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  This appears to be different than the previous similar bugs; patches
  do look to be applied to use libinput in the wayland case. Still:

  unknown keycodes `(unnamed)', please report to qemu-de...@nongnu.org

  I am using qemu-system-x86   1:2.10+dfsg-0ubuntu1
  on artful.

  Many key inputs work correctly, but at boot the system will not
  properly catch the arrow keys, the above error shows up immediately
  after hitting Esc (for instance) to get to the boot menu. Booting from
  CD onto a daily Ubuntu desktop image, I can't navigate the splash
  menu.

  The same works correctly through virt-manager (which uses spice
  AFAICT, but wayland tends to crash when running virt-manager), and
  things work if I switch my session to Xorg rather than wayland.

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

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


[Desktop-packages] [Bug 1719462] Re: [Translation] "Left" and "Right" must be translated differently in different contexts

2017-09-30 Thread Jeremy Bicha
Could you provide more detail about this issue? Are you unable to use
the same translation for both places?

Do you have a suggestion for the context string we could add?

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Incomplete

** Changed in: ubuntu-translations
   Status: New => Incomplete

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

Title:
  [Translation] "Left" and "Right" must be translated differently in
  different contexts

Status in Ubuntu Translations:
  Incomplete
Status in gnome-control-center package in Ubuntu:
  Incomplete

Bug description:
  In 17.10 artful in GNOME Control Center, there are two places where
  words "Left" and "Right" are encountered: the Mouse settings and the
  Dock settings. Both of the words have only one item to translate in
  Rosetta with indication that they are located in two different places
  in the sources:

  "Located in ../panels/mouse/gnome-mouse-properties.ui.h:4 
../panels/ubuntu/cc-ubuntu-panel.c:417"
  "Located in ../panels/mouse/gnome-mouse-properties.ui.h:5 
../panels/ubuntu/cc-ubuntu-panel.c:419"

  When translating in Russian, the words "Left" and "Right" must be translated 
differently in these two places. One translation for both contexts leads to 
inconsistent and ridiculous result.
  I can guess that this is also valid for some other languages, not only 
Russian.

  Please make two independent translations in Rosetta for "Left" and
  "Right" in these two different contexts.

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

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


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

2017-09-30 Thread Wolfgang
I got this crash when after upgrade from 17.04, my Google calendars
where imported but as my Google Account is 2FA the normal password box
does not work. I got several password prompts, one for each of the
Google calendars I had subscribed, I typed in the password but the boxes
prompting for the password re-appeared after some time (which is
probably as I'm using 2FA). At some point the calendar crashed. Not sure
if this is connected, but at least the behaviour is strange...

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

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

Status in gnome-calendar package in Ubuntu:
  Incomplete

Bug description:
  crashed when editing preferences

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-calendar 3.26.0-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
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 16 12:13:39 2017
  ExecutablePath: /usr/bin/gnome-calendar
  InstallationDate: Installed on 2017-04-22 (147 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7f7e39a85f57 :   
mov0x30(%rdi,%rax,1),%edx
   PC (0x7f7e39a85f57) ok
   source "0x30(%rdi,%rax,1)" (0xfe80) not located in a known VMA 
region (needed readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-calendar
  StacktraceTop:
   gtk_stack_set_visible_child_name () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? ()
   ?? ()
   g_hash_table_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
  Title: gnome-calendar crashed with SIGSEGV in 
gtk_stack_set_visible_child_name()
  UpgradeStatus: Upgraded to artful on 2017-09-03 (12 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-calendar/+bug/1717673/+subscriptions

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


[Desktop-packages] [Bug 1720527] Re: GUFW gui no longer appears in System Settings or menus

2017-09-30 Thread Jeremy Bicha
gufw is still available in the list of installed apps as "Firewall
Configuration".

It is intentionally not available in the GNOME Settings app since that
is reserved for GNOME settings (and select integrated Ubuntu settings).

Note that currently you will need to use the "Ubuntu on Xorg" session
since this app doesn't currently support Wayland as required by the
default "Ubuntu" session in 17.10. (LP: #1713238)


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

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

Title:
  GUFW gui no longer appears in System Settings or menus

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

Bug description:
  I've been testing Ubuntu GNOME 17.10 beta2 and I notice that Firewall
  Configuration no longer appears in the System Settings gui, nor in any
  menu.

  The gui can be launched by using the terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Sep 30 13:14:49 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-09-29 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170919)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2017-09-30 Thread Jeremy Bicha
** No longer affects: gufw (Ubuntu)

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

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

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

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

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

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

  GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese

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

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

  
  


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

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

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  PackageArchitecture: all
  SourcePackage: backintime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1719043] Re: Gnome web urlbar very slow to show typed input

2017-09-30 Thread Bug Watch Updater
** Changed in: epiphany-browser
   Status: Confirmed => Invalid

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

Title:
  Gnome web urlbar very slow to show typed input

Status in Epiphany Browser:
  Invalid
Status in epiphany-browser package in Ubuntu:
  Triaged
Status in epiphany-browser package in Debian:
  Confirmed

Bug description:
  First two characters typed in urlbar show immediately, other
  characters take up to 30 seconds to appear, or url will appear in full
  once enter key is pressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: epiphany-browser 3.26.0-1ubuntu1
  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 22 18:42:19 2017
  InstallationDate: Installed on 2017-09-22 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: epiphany-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1719043] Re: Gnome web urlbar very slow to show typed input

2017-09-30 Thread Jeremy Bicha
** Package changed: epiphany-browser (Debian) => mutter (Debian)

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

** Project changed: epiphany-browser => mutter

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

** Changed in: mutter
   Status: Invalid => Unknown

** Changed in: mutter
 Remote watch: GNOME Bug Tracker #788140 => GNOME Bug Tracker #784314

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

** Changed in: mutter (Ubuntu)
   Status: New => Triaged

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

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

Title:
  Gnome web urlbar very slow to show typed input

Status in Mutter:
  Unknown
Status in epiphany-browser package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in mutter package in Debian:
  Confirmed

Bug description:
  First two characters typed in urlbar show immediately, other
  characters take up to 30 seconds to appear, or url will appear in full
  once enter key is pressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: epiphany-browser 3.26.0-1ubuntu1
  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 22 18:42:19 2017
  InstallationDate: Installed on 2017-09-22 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: epiphany-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2017-09-30 Thread fossfreedom
Budgie welcome in its current form will never be run on a Wayland
session. Marked as invalid

** Changed in: budgie-welcome (Ubuntu)
   Status: New => Invalid

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

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

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

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

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

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

  GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese

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

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

  
  


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

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

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  PackageArchitecture: all
  SourcePackage: backintime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing lis

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

2017-09-30 Thread Norbert
Gufw is really affected.
See below:

$ apt-cache policy gufw
gufw:
  Installed: 17.10.0-0ubuntu1
  Candidate: 17.10.0-0ubuntu1
  Version table:
 *** 17.10.0-0ubuntu1 500
500 http://ru.archive.ubuntu.com/ubuntu artful/universe i386 Packages
100 /var/lib/dpkg/status


artful@artful:~$ dpkg -L gufw | grep desktop
/etc/gufw/app_profiles/remote-desktop-protocol.jhansonxi
/usr/share/applications/gufw.desktop
artful@artful:~$ cat /usr/share/applications/gufw.desktop | grep Exec
Exec=gufw
artful@artful:~$ gufw
# !!! # enter password here # !!! #
No protocol specified
Unable to init server: Could not connect: Connection refused
No protocol specified
Unable to init server: Could not connect: Connection refused

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion
'GDK_IS_DISPLAY (display)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion
'GDK_IS_DISPLAY (display)' failed

(gufw.py:3873): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers:
assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion
'GDK_IS_DISPLAY (display)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion
'GDK_IS_DISPLAY (display)' failed

(gufw.py:3873): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers:
assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion
'GDK_IS_DISPLAY (display)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion
'GDK_IS_DISPLAY (display)' failed

(gufw.py:3873): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers:
assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion
'GDK_IS_DISPLAY (display)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion
'GDK_IS_DISPLAY (display)' failed

(gufw.py:3873): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers:
assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion
'GDK_IS_DISPLAY (display)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion
'GDK_IS_DISPLAY (display)' failed

(gufw.py:3873): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers:
assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion
'GDK_IS_DISPLAY (display)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion
'GDK_IS_DISPLAY (display)' failed

(gufw.py:3873): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers:
assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion
'GDK_IS_DISPLAY (display)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion
'GDK_IS_DISPLAY (display)' failed

(gufw.py:3873): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers:
assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion
'GDK_IS_DISPLAY (display)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion
'GDK_IS_DISPLAY (display)' failed

(gufw.py:3873): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers:
assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion
'GDK_IS_DISPLAY (display)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion
'GDK_IS_DISPLAY (display)' failed

(gufw.py:3873): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers:
assertion 'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion
'GDK_IS_DISPLAY (display)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion
'GDK_IS_KEYMAP (keymap)' failed

(gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion
'GDK_IS_DISPLAY (display)' failed

(gufw.py:3873): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 
'GDK_IS_KEYMAP (keymap)' failed
/usr/bin/guf

[Desktop-packages] [Bug 1707110] Re: fwupd is consuming 100% of CPU in an upto date Ubuntu 16.04

2017-09-30 Thread Dan
I also have the same issue. By killing fwupd I was able to temporarily
stop the CPU usage. Manually restarting does not cause CPU usage to
spike up again. Attached is the output of fwupd after manually
restarting with,

> sudo /usr/lib/x86_64-linux-gnu/fwupd/fwupd -v

Here's my system info,

> sudo dmidecode | grep 'System Information' --after-context=10
System Information
Manufacturer: LENOVO
Product Name: 20HRCTO1WW
Version: ThinkPad X1 Carbon 5th
Serial Number: PF0QD769
UUID: 5EE5824C-23BB-11B2-A85C-C97143E41984
Wake-up Type: Power Switch
SKU Number: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th
Family: ThinkPad X1 Carbon 5th


** Attachment added: "fwupd.log"
   
https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1707110/+attachment/4959436/+files/fwupd.log

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

Title:
  fwupd is consuming 100% of CPU in an upto date Ubuntu 16.04

Status in appstream-glib package in Ubuntu:
  Confirmed

Bug description:
  Even though this bug is reported
  [https://bugs.launchpad.net/ubuntu/+source/appstream-
  glib/+bug/1591868] and marked as fixed, I am having the same issue on
  a up to date Ubuntu 16.04 system (as you can see in the attachment).
  Rebooting doesn't fix the problem.

  Thanks.

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

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


[Desktop-packages] [Bug 1707110] Re: fwupd is consuming 100% of CPU in an upto date Ubuntu 16.04

2017-09-30 Thread Dan
I also have the same issue. By killing fwupd I was able to temporarily
stop the CPU usage. Manually restarting does not cause CPU usage to
spike up again. Attached is the output of fwupd after manually
restarting with,

> sudo /usr/lib/x86_64-linux-gnu/fwupd/fwupd -v

Here's my system info,

> sudo dmidecode | grep 'System Information' --after-context=10
System Information
Manufacturer: LENOVO
Product Name: __
Version: ThinkPad X1 Carbon 5th
Serial Number: ___
UUID: ___
Wake-up Type: Power Switch
SKU Number: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th
Family: ThinkPad X1 Carbon 5th

** Attachment added: "fwupd.log"
   
https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1707110/+attachment/4959438/+files/fwupd.log

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

Title:
  fwupd is consuming 100% of CPU in an upto date Ubuntu 16.04

Status in appstream-glib package in Ubuntu:
  Confirmed

Bug description:
  Even though this bug is reported
  [https://bugs.launchpad.net/ubuntu/+source/appstream-
  glib/+bug/1591868] and marked as fixed, I am having the same issue on
  a up to date Ubuntu 16.04 system (as you can see in the attachment).
  Rebooting doesn't fix the problem.

  Thanks.

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

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


[Desktop-packages] [Bug 1707110] Re: fwupd is consuming 100% of CPU in an upto date Ubuntu 16.04

2017-09-30 Thread Dan
I also have the same issue. By killing fwupd I was able to temporarily
stop the CPU usage. Manually restarting does not cause CPU usage to
spike up again. Attached is the output of fwupd after manually
restarting with,

> sudo /usr/lib/x86_64-linux-gnu/fwupd/fwupd -v

Here's my system info,

> sudo dmidecode | grep 'System Information' --after-context=10
System Information
Manufacturer: LENOVO
Product Name: __
Version: ThinkPad X1 Carbon 5th
Serial Number: ___
UUID: ___
Wake-up Type: Power Switch
SKU Number: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th
Family: ThinkPad X1 Carbon 5th

** Attachment added: "fwupd.log"
   
https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1707110/+attachment/4959437/+files/fwupd.log

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

Title:
  fwupd is consuming 100% of CPU in an upto date Ubuntu 16.04

Status in appstream-glib package in Ubuntu:
  Confirmed

Bug description:
  Even though this bug is reported
  [https://bugs.launchpad.net/ubuntu/+source/appstream-
  glib/+bug/1591868] and marked as fixed, I am having the same issue on
  a up to date Ubuntu 16.04 system (as you can see in the attachment).
  Rebooting doesn't fix the problem.

  Thanks.

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

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


[Desktop-packages] [Bug 207135] Re: pulseaudio uses too much CPU

2017-09-30 Thread Chris Osgood
My system was doing the same thing. It went from working properly one
minute then broken for no reason. Very high CPU usage for pulseaudio,
polkitd, dbus-daemon. PulseAudio sound was stuttering. Trying to edit
the sound settings in the volume control was impossible because it kept
losing the connection to PulseAudio. Syslog was full of thousands of
this message repeated:

[pulseaudio] alsa-mixer.c: Failed to set switch of IEC958: Operation not
permitted

I've had issues on this system where the sound output would randomly
switch from analog out to some other method or even another device like
HDMI which I don't use. I believe due to the plug auto-detection on the
audio connector.

So I unplugged, replugged, and jiggled the audio connector on the back
of the computer and that fixed everything. I guess the plug was loose or
the motherboard is buggy and doesn't properly detect when an analog plug
is in the audio connector. This was causing pulseaudio to go haywire and
hammer the system (not a surprise considering the history of that
software).

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

Title:
  pulseaudio uses too much CPU

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: pulseaudio

  Pulseaudio uses between 6 and 8% of my CPU (AMD Athlon(tm) 64
  Processor 3500+) when I'm just listening music using Rhythmbox. Seems
  too much IMHO.

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

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


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

2017-09-30 Thread Jeremy Bicha
Norbert, yes but the package name was wrong. There already is LP:
#1713238

It's difficult to manage a single bug affecting large number of packages
like this in Launchpad in my opinion.

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

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

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

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

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

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

  GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese

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

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

  
  


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

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

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  PackageArchitecture: all
  SourcePackage: backintime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun

[Desktop-packages] [Bug 1596200] Re: Ubuntu 16.04: unresponsive keyboard (15 sec) after grub

2017-09-30 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1599306 ***
https://bugs.launchpad.net/bugs/1599306

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

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

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

Title:
  Ubuntu 16.04: unresponsive keyboard (15 sec) after grub

Status in kbd package in Ubuntu:
  Confirmed
Status in udev package in Ubuntu:
  Confirmed
Status in xinput package in Ubuntu:
  Confirmed

Bug description:
  I've upgraded my notebook with an SSD. All works fine and I can reach
  the login in less than 10 seconds. Problem is I can't use the internal
  keyboard (perfectly working on grub) for at least 10-15 seconds, then
  it starts to working just fine. The touchpad and capacitive buttons
  are working without issues.

  Luckily I have a second HDD on my machine and I've made some tests
  with the old mechanical drive, with this unit I can input my password
  on LightDM without any delay.

  The issue is not (only) related to Xorg or LightDM, because starting in 
recovery mode shown the same issue with both disks: if I use an external 
keyboard (a Logitech k400r in my case) I have no issue at all on both login and 
recovery mode. 
  Seems kdb needs some time to be up and running.

  Here's a video showing a full cycle of boots:

  https://youtu.be/yseDPvqWNw4

  And here a video of the recovery mode:

  https://youtu.be/vbsD9tb-Dn8

  Fresh install of Ubuntu 16.04 LTS without any other packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Jun 25 12:01:50 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile GM965/GL960 Integrated Graphics 
Controller (primary) [103c:30cd]
 Subsystem: Hewlett-Packard Company Mobile GM965/GL960 Integrated Graphics 
Controller (secondary) [103c:30cd]
  InstallationDate: Installed on 2016-06-25 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Pavilion dv2700 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=56bb4994-c2b0-4ada-9f3d-493898e2ad39 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2008
  dmi.bios.vendor: Phoenix
  dmi.bios.version: F.2B
  dmi.board.name: 30CD
  dmi.board.vendor: Wistron
  dmi.board.version: 80.52
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrF.2B:bd05/07/2008:svnHewlett-Packard:pnHPPaviliondv2700NotebookPC:pvrF.2B:rvnWistron:rn30CD:rvr80.52:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv2700 Notebook PC
  dmi.product.version: F.2B
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Jun 25 12:00:23 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   19778 
   vendor SEC
  xserver.version: 2:1.18.3-1ubuntu2

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

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


[Desktop-packages] [Bug 1596200] Re: Ubuntu 16.04: unresponsive keyboard (15 sec) after grub

2017-09-30 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1599306 ***
https://bugs.launchpad.net/bugs/1599306

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

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

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

Title:
  Ubuntu 16.04: unresponsive keyboard (15 sec) after grub

Status in kbd package in Ubuntu:
  Confirmed
Status in udev package in Ubuntu:
  Confirmed
Status in xinput package in Ubuntu:
  Confirmed

Bug description:
  I've upgraded my notebook with an SSD. All works fine and I can reach
  the login in less than 10 seconds. Problem is I can't use the internal
  keyboard (perfectly working on grub) for at least 10-15 seconds, then
  it starts to working just fine. The touchpad and capacitive buttons
  are working without issues.

  Luckily I have a second HDD on my machine and I've made some tests
  with the old mechanical drive, with this unit I can input my password
  on LightDM without any delay.

  The issue is not (only) related to Xorg or LightDM, because starting in 
recovery mode shown the same issue with both disks: if I use an external 
keyboard (a Logitech k400r in my case) I have no issue at all on both login and 
recovery mode. 
  Seems kdb needs some time to be up and running.

  Here's a video showing a full cycle of boots:

  https://youtu.be/yseDPvqWNw4

  And here a video of the recovery mode:

  https://youtu.be/vbsD9tb-Dn8

  Fresh install of Ubuntu 16.04 LTS without any other packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Jun 25 12:01:50 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile GM965/GL960 Integrated Graphics 
Controller (primary) [103c:30cd]
 Subsystem: Hewlett-Packard Company Mobile GM965/GL960 Integrated Graphics 
Controller (secondary) [103c:30cd]
  InstallationDate: Installed on 2016-06-25 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Pavilion dv2700 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=56bb4994-c2b0-4ada-9f3d-493898e2ad39 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2008
  dmi.bios.vendor: Phoenix
  dmi.bios.version: F.2B
  dmi.board.name: 30CD
  dmi.board.vendor: Wistron
  dmi.board.version: 80.52
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrF.2B:bd05/07/2008:svnHewlett-Packard:pnHPPaviliondv2700NotebookPC:pvrF.2B:rvnWistron:rn30CD:rvr80.52:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv2700 Notebook PC
  dmi.product.version: F.2B
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Jun 25 12:00:23 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   19778 
   vendor SEC
  xserver.version: 2:1.18.3-1ubuntu2

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

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


[Desktop-packages] [Bug 1596200] Re: Ubuntu 16.04: unresponsive keyboard (15 sec) after grub

2017-09-30 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1599306 ***
https://bugs.launchpad.net/bugs/1599306

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

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

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

Title:
  Ubuntu 16.04: unresponsive keyboard (15 sec) after grub

Status in kbd package in Ubuntu:
  Confirmed
Status in udev package in Ubuntu:
  Confirmed
Status in xinput package in Ubuntu:
  Confirmed

Bug description:
  I've upgraded my notebook with an SSD. All works fine and I can reach
  the login in less than 10 seconds. Problem is I can't use the internal
  keyboard (perfectly working on grub) for at least 10-15 seconds, then
  it starts to working just fine. The touchpad and capacitive buttons
  are working without issues.

  Luckily I have a second HDD on my machine and I've made some tests
  with the old mechanical drive, with this unit I can input my password
  on LightDM without any delay.

  The issue is not (only) related to Xorg or LightDM, because starting in 
recovery mode shown the same issue with both disks: if I use an external 
keyboard (a Logitech k400r in my case) I have no issue at all on both login and 
recovery mode. 
  Seems kdb needs some time to be up and running.

  Here's a video showing a full cycle of boots:

  https://youtu.be/yseDPvqWNw4

  And here a video of the recovery mode:

  https://youtu.be/vbsD9tb-Dn8

  Fresh install of Ubuntu 16.04 LTS without any other packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Jun 25 12:01:50 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile GM965/GL960 Integrated Graphics 
Controller (primary) [103c:30cd]
 Subsystem: Hewlett-Packard Company Mobile GM965/GL960 Integrated Graphics 
Controller (secondary) [103c:30cd]
  InstallationDate: Installed on 2016-06-25 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Pavilion dv2700 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=56bb4994-c2b0-4ada-9f3d-493898e2ad39 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2008
  dmi.bios.vendor: Phoenix
  dmi.bios.version: F.2B
  dmi.board.name: 30CD
  dmi.board.vendor: Wistron
  dmi.board.version: 80.52
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrF.2B:bd05/07/2008:svnHewlett-Packard:pnHPPaviliondv2700NotebookPC:pvrF.2B:rvnWistron:rn30CD:rvr80.52:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv2700 Notebook PC
  dmi.product.version: F.2B
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Jun 25 12:00:23 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   19778 
   vendor SEC
  xserver.version: 2:1.18.3-1ubuntu2

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

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


[Desktop-packages] [Bug 1720372] Re: deja-dup crashed with SIGSEGV in deja_dup_operation_start()

2017-09-30 Thread Michael Terry
** Information type changed from Private to Public

** Changed in: deja-dup (Ubuntu)
   Status: New => Confirmed

** Also affects: deja-dup
   Importance: Undecided
   Status: New

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

Title:
  deja-dup crashed with SIGSEGV in deja_dup_operation_start()

Status in Déjà Dup:
  New
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  
  Using Ubuntu 17.10 (Development Branch) with all latest package updates I am 
receiving an error with Deja Dup 36.1-0ubuntu1.

  What I expect to happen: Deja Dup will show me a list of missing files
  I can restore

  What happened: The application crashed

  Steps to reproduce:

  1. Right click when in a folder
  2. Click "Restore missing files..."

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 36.1-0ubuntu1
  Uname: Linux 4.13.4-041304-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Fri Sep 29 14:54:11 2017
  ExecutablePath: /usr/bin/deja-dup
  InstallationDate: Installed on 2017-08-31 (28 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: deja-dup --restore-missing file:///home/username
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fb2b86dbb90 : mov
(%rdi),%rax
   PC (0x7fb2b86dbb90) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   deja_dup_operation_start () from 
/usr/lib/x86_64-linux-gnu/deja-dup/libdeja.so
   assistant_restore_do_query ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: deja-dup crashed with SIGSEGV in deja_dup_operation_start()
  UpgradeStatus: Upgraded to artful on 2017-09-21 (8 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers

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

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


[Desktop-packages] [Bug 1719043] Re: Gnome web urlbar very slow to show typed input

2017-09-30 Thread Bug Watch Updater
** Changed in: mutter
   Status: Unknown => Confirmed

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

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

Title:
  Gnome web urlbar very slow to show typed input

Status in Mutter:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in mutter package in Debian:
  Confirmed

Bug description:
  First two characters typed in urlbar show immediately, other
  characters take up to 30 seconds to appear, or url will appear in full
  once enter key is pressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: epiphany-browser 3.26.0-1ubuntu1
  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 22 18:42:19 2017
  InstallationDate: Installed on 2017-09-22 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: epiphany-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2017-09-30 Thread Norbert
@Jeremy Bicha (jbicha) 
As you may know I created script for automation - see my comment #20 
https://bugs.launchpad.net/ubuntu/+source/gui-ufw/+bug/1713313/comments/20 ). 
And I collected all found problems here.

I added more affected packages here:
* `apport` because of /usr/share/apport/root_info_wrapper and 
/usr/share/apport/apport-gtk .
* `cinnamon` and `cinnamon-common` because of 
/usr/share/cinnamon/cinnamon-settings-users/cinnamon-settings-users.py .
* `caja-admin` because of /usr/bin/caja as root.
* `guidedog` because of "Authentication is required to run Guidedog script" 
/bin/sh.
* `update-notifier-common` because of /usr/lib/update-notifier/cddistupgrader 
and /usr/lib/update-notifier/package-system-locked .


It was too difficult to create separate bug reports for each application for 
me. I hope that community may help here. I hope that all we make Ubuntu better.

** Also affects: update-notifier (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: caja-admin (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

  GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese

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

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

  
  


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

  (gpartedbin:128

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

2017-09-30 Thread Jeremy Bicha
It doesn't make sense to run cinnamon inside GNOME on Wayland.

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

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

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

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

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

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

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

  GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese

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

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

  
  


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

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

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  PackageArchitectu

[Desktop-packages] [Bug 1720372] Re: deja-dup crashed with SIGSEGV in deja_dup_operation_start()

2017-09-30 Thread Michael Terry
** Changed in: deja-dup
   Status: New => Fix Committed

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

Title:
  deja-dup crashed with SIGSEGV in deja_dup_operation_start()

Status in Déjà Dup:
  Fix Committed
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  
  Using Ubuntu 17.10 (Development Branch) with all latest package updates I am 
receiving an error with Deja Dup 36.1-0ubuntu1.

  What I expect to happen: Deja Dup will show me a list of missing files
  I can restore

  What happened: The application crashed

  Steps to reproduce:

  1. Right click when in a folder
  2. Click "Restore missing files..."

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 36.1-0ubuntu1
  Uname: Linux 4.13.4-041304-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Fri Sep 29 14:54:11 2017
  ExecutablePath: /usr/bin/deja-dup
  InstallationDate: Installed on 2017-08-31 (28 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: deja-dup --restore-missing file:///home/username
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fb2b86dbb90 : mov
(%rdi),%rax
   PC (0x7fb2b86dbb90) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   deja_dup_operation_start () from 
/usr/lib/x86_64-linux-gnu/deja-dup/libdeja.so
   assistant_restore_do_query ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: deja-dup crashed with SIGSEGV in deja_dup_operation_start()
  UpgradeStatus: Upgraded to artful on 2017-09-21 (8 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers

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

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


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

2017-09-30 Thread Jeremy Bicha
This appears to be a false positive.

** Changed in: ubuntustudio-default-settings (Ubuntu)
   Status: New => Invalid

** Changed in: xubuntu-default-settings (Ubuntu)
   Status: New => Invalid

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

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

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

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

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

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

  GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese

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

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

  
  


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

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

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia:

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

2017-09-30 Thread Norbert
@Jeremy Bicha (jbicha)
FYI on other similar bug report dino99 was pleasant about one big bug report 
(see his comment - 
https://bugs.launchpad.net/ubuntu/+source/nmap/+bug/1713311/comments/4 ). So we 
can choose this bug-report style here too.

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

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

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

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

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

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

  GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese

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

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

  
  


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

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

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2

[Desktop-packages] [Bug 1719322] Re: Remove patch to remove headerbar

2017-09-30 Thread Launchpad Bug Tracker
This bug was fixed in the package file-roller - 3.26.0-0ubuntu2

---
file-roller (3.26.0-0ubuntu2) artful; urgency=medium

  * Drop bz_unity_header.patch: No longer needed for Unity (LP:
#1719322)

 -- Jeremy Bicha   Sat, 30 Sep 2017 11:43:39 -0400

** Changed in: file-roller (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Remove patch to remove headerbar

Status in eog package in Ubuntu:
  Incomplete
Status in epiphany-browser package in Ubuntu:
  Fix Committed
Status in evince package in Ubuntu:
  Incomplete
Status in file-roller package in Ubuntu:
  Fix Released
Status in gnome-contacts package in Ubuntu:
  Fix Committed

Bug description:
  As of Artful, it seems that there are still patches against various
  apps that remove/replace the Gtk.HeaderBar with a Gtk.Toolbar.

  Now that GNOME Shell is default in Ubuntu and there is better support
  for client-side decorations, these patches can probably go away

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

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


[Desktop-packages] [Bug 1719043] Re: Gnome web urlbar very slow to show typed input

2017-09-30 Thread Launchpad Bug Tracker
This bug was fixed in the package epiphany-browser - 3.26.1-1ubuntu1

---
epiphany-browser (3.26.1-1ubuntu1) artful; urgency=medium

  * Sync with Debian. Remaining change:
- Modify 07_bookmarks.patch:
  + Add Ubuntu-specific default bookmarks, borrowed from Firefox
  * Drop ubuntu_titlebars.patch (LP: #1719322)
+ Use traditional titlebars for non-GNOME sessions

epiphany-browser (3.26.1-1) unstable; urgency=medium

  * New upstream release
  * Drop git_fix-url-bar-lag.patch: Applied in new release
  * Bump Standards-Version to 4.1.1

 -- Jeremy Bicha   Sat, 30 Sep 2017 10:20:38 -0400

** Changed in: epiphany-browser (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Gnome web urlbar very slow to show typed input

Status in Mutter:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Triaged
Status in mutter package in Debian:
  Confirmed

Bug description:
  First two characters typed in urlbar show immediately, other
  characters take up to 30 seconds to appear, or url will appear in full
  once enter key is pressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: epiphany-browser 3.26.0-1ubuntu1
  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 22 18:42:19 2017
  InstallationDate: Installed on 2017-09-22 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: epiphany-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1719322] Re: Remove patch to remove headerbar

2017-09-30 Thread Launchpad Bug Tracker
This bug was fixed in the package epiphany-browser - 3.26.1-1ubuntu1

---
epiphany-browser (3.26.1-1ubuntu1) artful; urgency=medium

  * Sync with Debian. Remaining change:
- Modify 07_bookmarks.patch:
  + Add Ubuntu-specific default bookmarks, borrowed from Firefox
  * Drop ubuntu_titlebars.patch (LP: #1719322)
+ Use traditional titlebars for non-GNOME sessions

epiphany-browser (3.26.1-1) unstable; urgency=medium

  * New upstream release
  * Drop git_fix-url-bar-lag.patch: Applied in new release
  * Bump Standards-Version to 4.1.1

 -- Jeremy Bicha   Sat, 30 Sep 2017 10:20:38 -0400

** Changed in: epiphany-browser (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Remove patch to remove headerbar

Status in eog package in Ubuntu:
  Incomplete
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Incomplete
Status in file-roller package in Ubuntu:
  Fix Released
Status in gnome-contacts package in Ubuntu:
  Fix Committed

Bug description:
  As of Artful, it seems that there are still patches against various
  apps that remove/replace the Gtk.HeaderBar with a Gtk.Toolbar.

  Now that GNOME Shell is default in Ubuntu and there is better support
  for client-side decorations, these patches can probably go away

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

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


[Desktop-packages] [Bug 1719043] Re: Gnome web urlbar very slow to show typed input

2017-09-30 Thread Jeremy Bicha
** Changed in: epiphany-browser (Ubuntu)
   Status: Fix Released => Triaged

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

Title:
  Gnome web urlbar very slow to show typed input

Status in Mutter:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in mutter package in Debian:
  Confirmed

Bug description:
  First two characters typed in urlbar show immediately, other
  characters take up to 30 seconds to appear, or url will appear in full
  once enter key is pressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: epiphany-browser 3.26.0-1ubuntu1
  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 22 18:42:19 2017
  InstallationDate: Installed on 2017-09-22 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: epiphany-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1719322] Re: Remove patch to remove headerbar

2017-09-30 Thread Jeremy Bicha
** Changed in: gnome-contacts (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Remove patch to remove headerbar

Status in eog package in Ubuntu:
  Incomplete
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Incomplete
Status in file-roller package in Ubuntu:
  Fix Released
Status in gnome-contacts package in Ubuntu:
  Fix Released

Bug description:
  As of Artful, it seems that there are still patches against various
  apps that remove/replace the Gtk.HeaderBar with a Gtk.Toolbar.

  Now that GNOME Shell is default in Ubuntu and there is better support
  for client-side decorations, these patches can probably go away

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

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


[Desktop-packages] [Bug 1574278] Re: AbiWord text cursor starts to flicker after adding some text

2017-09-30 Thread Simon Quigley
** No longer affects: lubuntu-artwork (Ubuntu)

** No longer affects: gtk+3.0 (Ubuntu)

** No longer affects: gtk+3.0 (Ubuntu Xenial)

** No longer affects: lubuntu-artwork (Ubuntu Xenial)

** Also affects: abiword (Ubuntu Artful)
   Importance: High
   Status: Confirmed

** Also affects: abiword (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Changed in: abiword (Ubuntu Zesty)
   Importance: Undecided => High

** Changed in: abiword (Ubuntu Artful)
   Status: Confirmed => In Progress

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

** Changed in: abiword (Ubuntu Xenial)
   Status: In Progress => Confirmed

** Changed in: abiword (Ubuntu Artful)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: abiword (Ubuntu Zesty)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

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

Title:
  AbiWord text cursor starts to flicker after adding some text

Status in AbiWord:
  In Progress
Status in abiword package in Ubuntu:
  Fix Committed
Status in abiword source package in Xenial:
  Confirmed
Status in abiword source package in Zesty:
  Confirmed
Status in abiword source package in Artful:
  Fix Committed

Bug description:
  After adding some text in a new document, the entire document
  (including gray page background, text, text cursor) starts to flicker
  very fast. The UI above does not flicker. This happens too on a
  different system in VirtualBox. (Lubuntu 16.04 i386)

  Workaround for Ubuntu 16.04 LTS
  ===
  1. Open the Lubuntu menu.
  2. Open Preferences>Customize Look and Feel
  3. Change the theme to something other than Lubuntu-default or 
Lubuntu-dark-panel

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: abiword 3.0.1-6
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sun Apr 24 16:12:14 2016
  ExecutablePath: /usr/bin/abiword
  InstallationDate: Installed on 2016-04-22 (2 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: abiword
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago)

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

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


[Desktop-packages] [Bug 1720395] Re: variable name conflict in french leads to invalid expression errors

2017-09-30 Thread Didier Roche
OUpss, thanks for spotting this Amr :)

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

Title:
  variable name conflict in french leads to invalid expression errors

Status in GNOME Calculator:
  Confirmed
Status in gnome-calculator package in Ubuntu:
  Fix Released

Bug description:
  The code uses an "ans" variable for results but that's a translated
  string in french which creates issues

  step to trigger
  type "1", "enter" then "+1" enter

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

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


[Desktop-packages] [Bug 1720582] [NEW] gvfs-backends not installed with GIMP

2017-09-30 Thread Raúl Vidal
Public bug reported:

I am running Kubuntu 17.04.
I installed the GIMP.
I tried to use the menu item "Open from location", but it did not work.
After searching on the Internet, I found out that the GIMP needs a GVFS backend 
in order to fetch an image from the web. I installed gvfs-backends. Now the 
menu item "Open from location" works.

Problem: A feature from the GIMP does not work by default.
How to solve: install an additional package.
Ideal use case: user only needs to install the GIMP.

Could it be possible to add gvfs-backends as a hard dependency of the
GIMP?

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gimp 2.8.20-1
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Sep 30 23:21:25 2017
InstallationDate: Installed on 2015-07-31 (792 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
SourcePackage: gimp
UpgradeStatus: Upgraded to zesty on 2017-05-02 (151 days ago)

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


** Tags: amd64 apport-bug zesty

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

Title:
  gvfs-backends not installed with GIMP

Status in gimp package in Ubuntu:
  New

Bug description:
  I am running Kubuntu 17.04.
  I installed the GIMP.
  I tried to use the menu item "Open from location", but it did not work.
  After searching on the Internet, I found out that the GIMP needs a GVFS 
backend in order to fetch an image from the web. I installed gvfs-backends. Now 
the menu item "Open from location" works.

  Problem: A feature from the GIMP does not work by default.
  How to solve: install an additional package.
  Ideal use case: user only needs to install the GIMP.

  Could it be possible to add gvfs-backends as a hard dependency of the
  GIMP?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gimp 2.8.20-1
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 30 23:21:25 2017
  InstallationDate: Installed on 2015-07-31 (792 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: gimp
  UpgradeStatus: Upgraded to zesty on 2017-05-02 (151 days ago)

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

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


[Desktop-packages] [Bug 1720585] [NEW] GVFS backend gvfs-http can not use SSL protocol (HTTPS)

2017-09-30 Thread Raúl Vidal
Public bug reported:

While doing drag and drop of an image from Firefox to the GIMP, if the image 
has been accessed via HTTPS the GIMP reports that the file or directory does 
not exist.
In order to be able to do drag and drop, it has to be done on objects available 
via HTTP, without SSL.

Non-working image example:
https://images.anandtech.com/doci/11885/asrock_z270_supercarrier_03_678x452.jpg

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gvfs-backends 1.30.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Sep 30 23:28:29 2017
InstallationDate: Installed on 2015-07-31 (792 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
SourcePackage: gvfs
UpgradeStatus: Upgraded to zesty on 2017-05-02 (151 days ago)

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


** Tags: amd64 apport-bug zesty

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

Title:
  GVFS backend gvfs-http can not use SSL protocol (HTTPS)

Status in gvfs package in Ubuntu:
  New

Bug description:
  While doing drag and drop of an image from Firefox to the GIMP, if the image 
has been accessed via HTTPS the GIMP reports that the file or directory does 
not exist.
  In order to be able to do drag and drop, it has to be done on objects 
available via HTTP, without SSL.

  Non-working image example:
  
https://images.anandtech.com/doci/11885/asrock_z270_supercarrier_03_678x452.jpg

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gvfs-backends 1.30.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 30 23:28:29 2017
  InstallationDate: Installed on 2015-07-31 (792 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to zesty on 2017-05-02 (151 days ago)

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

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


[Desktop-packages] [Bug 1720587] [NEW] gnome-shell crashed with signal 5 in _XIOError()

2017-09-30 Thread Sosha
Public bug reported:

after login to session...

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.0-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sat Sep 30 15:26:49 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 
InstallationDate: Installed on 2017-09-02 (28 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/false
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: gnome-shell crashed with signal 5 in _XIOError()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

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


** Tags: amd64 apport-crash artful need-amd64-retrace

** Information type changed from Private to Public

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  after login to session...

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat Sep 30 15:26:49 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-09-02 (28 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5 in _XIOError()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Desktop-packages] [Bug 1720589] [NEW] gnome-shell crashed with signal 5 in g_settings_get_value()

2017-09-30 Thread Sosha
Public bug reported:

after login...

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.0-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Sep 29 22:09:02 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 
InstallationDate: Installed on 2017-09-02 (28 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_settings_get_value () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_settings_get_boolean () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
Title: gnome-shell crashed with signal 5 in g_settings_get_value()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

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


** Tags: amd64 apport-crash artful need-amd64-retrace

** Information type changed from Private to Public

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  after login...

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Sep 29 22:09:02 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-09-02 (28 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_value () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_boolean () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: gnome-shell crashed with signal 5 in g_settings_get_value()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


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

2017-09-30 Thread Apport retracing service
*** This bug is a duplicate of bug 1505409 ***
https://bugs.launchpad.net/bugs/1505409

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

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

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

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

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

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

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

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

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

** Tags removed: need-amd64-retrace

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  after login to session...

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat Sep 30 15:26:49 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-09-02 (28 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5 in _XIOError()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


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

2017-09-30 Thread Apport retracing service
*** This bug is a duplicate of bug 1719124 ***
https://bugs.launchpad.net/bugs/1719124

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 #1719124, 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/1720589/+attachment/4959558/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1719124
   gnome-shell crashed with signal 5 in g_settings_schema_get_value 
(..."opaque-background")

** Tags removed: need-amd64-retrace

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  after login...

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Sep 29 22:09:02 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-09-02 (28 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_value () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_boolean () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: gnome-shell crashed with signal 5 in g_settings_get_value()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Desktop-packages] [Bug 1720590] [NEW] fglrx 2:13.350.1-0ubuntu2: fglrx kernel module failed to build

2017-09-30 Thread Rodrigo Vega
Public bug reported:

After changing the driver to privative, my system crushed. Couldn't boot 
neither console or graphics.
I made a lot of changes through onsole. Update , upgrade , delete propietary 
devices , install lubuntu , cleared my password, etc.
I don't know what has happen that now it seems to be working well. Hope it 
continues like this


AMD A6-6400K APU with Radeon(tm) HD Graphics × 2 
Gallium 0.4 on AMD ARUBA (DRM 2.43.0, LLVM 3.8.0)
ubuntu 14.04 lts
Description:Ubuntu 14.04.5 LTS
Release:14.04

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: fglrx (not installed)
ProcVersionSignature: Ubuntu 4.4.0-96.119~14.04.1-generic 4.4.83
Uname: Linux 4.4.0-96-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.25
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
DKMSKernelVersion: 4.4.0-93-generic
Date: Thu Sep 28 16:18:49 2017
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 4.3.36, 3.16.0-45-generic, x86_64: installed
 virtualbox, 4.3.36, 3.16.0-77-generic, x86_64: installed
 virtualbox, 4.3.36, 4.4.0-93-generic, x86_64: installed
 virtualbox, 4.3.36, 4.4.0-96-generic, x86_64: installed
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8470D] [1002:9996] 
(prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation Device [1849:9996]
InstallationDate: Installed on 2015-05-17 (867 days ago)
InstallationMedia: It
LightdmGreeterLog:
 ** (lightdm-gtk-greeter:2421): WARNING **: Failed to load user background: 
Falló al abrir el archivo «/home/rodrigo/Documentos/1255808524707_f.jpg»: 
Permiso denegado
 
 ** (lightdm-gtk-greeter:2421): WARNING **: Failed to load user image: Falló al 
abrir el archivo «/home/rodrigo/.face»: No existe el archivo o el directorio
 
 (lightdm-gtk-greeter:2421): Gdk-WARNING **: lightdm-gtk-greeter: Fatal IO 
error 4 (Llamada al sistema interrumpida) on X server :0.
LightdmGreeterLogOld: 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.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
PackageVersion: 2:13.350.1-0ubuntu2
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-96-generic 
root=/dev/mapper/it--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.17
SourcePackage: fglrx-installer
Title: fglrx 2:13.350.1-0ubuntu2: fglrx kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/07/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.10
dmi.board.name: FM2A68M-DG3+
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd11/07/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-DG3+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sat Sep 30 19:28:02 2017
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2.9
xserver.video_driver: radeon

** Affects: fglrx-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package compiz-0.9 trusty ubuntu

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

Title:
  fglrx 2:13.350.1-0ubuntu2: fglrx kernel module failed to build

Status in fglrx-installer package in Ubuntu:
  New

Bug description:
  After changing the driver to privative, my system crushed. Couldn't boot 
neither console or graphics.
  I made a lot of changes through onsole. Update , upgrade , delete propietary 
devices , install lubuntu , cleared my password, etc.
  I don't know what has happen that now it seems to be working well. Hope it 
continues like this

  

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

2017-09-30 Thread Apport retracing service
*** This bug is a duplicate of bug 1719273 ***
https://bugs.launchpad.net/bugs/1719273

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 #1719273, 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/1720592/+attachment/4959593/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  The calendar app just crashed at random. It was open, but I was using
  another window (no focus or activity on application).

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-calendar 3.26.0-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 30 20:17:07 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-calendar
  InstallationDate: Installed on 2014-05-30 (1219 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x5619da51bdc1 :
mov0x18(%rdi),%rdi
   PC (0x5619da51bdc1) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-calendar
  StacktraceTop:
   gcal_manager_is_client_writable ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-calendar crashed with SIGSEGV in 
gcal_manager_is_client_writable()
  UpgradeStatus: Upgraded to artful on 2017-09-30 (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-calendar/+bug/1720592/+subscriptions

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


[Desktop-packages] [Bug 1719322] Re: Remove patch to remove headerbar

2017-09-30 Thread Sebastien Bacher
those changes modify the look of the softwares on some desktops right?
they require at least a UIFe...

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

Title:
  Remove patch to remove headerbar

Status in eog package in Ubuntu:
  Incomplete
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Incomplete
Status in file-roller package in Ubuntu:
  Fix Released
Status in gnome-contacts package in Ubuntu:
  Fix Released

Bug description:
  As of Artful, it seems that there are still patches against various
  apps that remove/replace the Gtk.HeaderBar with a Gtk.Toolbar.

  Now that GNOME Shell is default in Ubuntu and there is better support
  for client-side decorations, these patches can probably go away

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

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


[Desktop-packages] [Bug 1720585] Re: GVFS backend gvfs-http can not use SSL protocol (HTTPS)

2017-09-30 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

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

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

Title:
  GVFS backend gvfs-http can not use SSL protocol (HTTPS)

Status in gvfs package in Ubuntu:
  New

Bug description:
  While doing drag and drop of an image from Firefox to the GIMP, if the image 
has been accessed via HTTPS the GIMP reports that the file or directory does 
not exist.
  In order to be able to do drag and drop, it has to be done on objects 
available via HTTP, without SSL.

  Non-working image example:
  
https://images.anandtech.com/doci/11885/asrock_z270_supercarrier_03_678x452.jpg

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gvfs-backends 1.30.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 30 23:28:29 2017
  InstallationDate: Installed on 2015-07-31 (792 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to zesty on 2017-05-02 (151 days ago)

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

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


[Desktop-packages] [Bug 1718719] Re: qemu can't capture keys properly under wayland

2017-09-30 Thread Sebastien Bacher
is the patch providing any user visible improvement? if not it would
probably make sense to delay including it to next cycle

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

Title:
  qemu can't capture keys properly under wayland

Status in QEMU:
  New
Status in XServer:
  Incomplete
Status in qemu package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  This appears to be different than the previous similar bugs; patches
  do look to be applied to use libinput in the wayland case. Still:

  unknown keycodes `(unnamed)', please report to qemu-de...@nongnu.org

  I am using qemu-system-x86   1:2.10+dfsg-0ubuntu1
  on artful.

  Many key inputs work correctly, but at boot the system will not
  properly catch the arrow keys, the above error shows up immediately
  after hitting Esc (for instance) to get to the boot menu. Booting from
  CD onto a daily Ubuntu desktop image, I can't navigate the splash
  menu.

  The same works correctly through virt-manager (which uses spice
  AFAICT, but wayland tends to crash when running virt-manager), and
  things work if I switch my session to Xorg rather than wayland.

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

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


[Desktop-packages] [Bug 1708608] Re: [Nvidia GTX970M] Can't log in using default nouveau drivers, system freezes

2017-09-30 Thread SB
I installed latest beta 2 and this is no longer an issue, this bug can
be closed.

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

Title:
  [Nvidia GTX970M] Can't log in using default nouveau drivers, system
  freezes

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I just installed daily iso and I cant login to Gnome at all, when I enter my 
password after initial reboot the desktop hard locks and I must turn off my 
laptop, I cant get into virtual consoles or anything. My graphics card is 
Nvidia, there is no integrated Intel graphics card, only dedicated Nvidia 
graphics card. Logging into X.org or Wayland session makes no difference, both 
of them completely freeze the system. How can I debug this?
  --- 
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges: org.gnome.desktop.interface gtk-im-module 
'gtk-im-context-simple'
  InstallationDate: Installed on 2017-08-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170802)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.24.3-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Tags:  artful
  Uname: Linux 4.11.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1707110] Re: fwupd is consuming 100% of CPU in an upto date Ubuntu 16.04

2017-09-30 Thread Sebastien Bacher
** Changed in: appstream-glib (Ubuntu)
   Importance: Undecided => High

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

Title:
  fwupd is consuming 100% of CPU in an upto date Ubuntu 16.04

Status in appstream-glib package in Ubuntu:
  Confirmed

Bug description:
  Even though this bug is reported
  [https://bugs.launchpad.net/ubuntu/+source/appstream-
  glib/+bug/1591868] and marked as fixed, I am having the same issue on
  a up to date Ubuntu 16.04 system (as you can see in the attachment).
  Rebooting doesn't fix the problem.

  Thanks.

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

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


[Desktop-packages] [Bug 1720510] Re: No results after search

2017-09-30 Thread Sebastien Bacher
thank you for your bug report, do you get any error displayed in the ui?
trying here it works unless the snap query timeouts which blocks it to
return other results but that's indicated in a notification

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

Title:
  No results after search

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Test case:
  Open a new version of gnome-software/Ubuntu Software
  Search for soft
  No results are shown
  Do something outside the gnome-software window, e.g mouse click or focus on 
another window, and the results are shown.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 30 09:28:37 2017
  InstallationDate: Installed on 2017-09-15 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170915)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.0-0ubuntu3
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1720465] Re: HiDPI scaling does not hold across reboot

2017-09-30 Thread Sebastien Bacher
could be the same as bug #1716341

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  HiDPI scaling does not hold across reboot

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Running Ubuntu 17.10 Beta (updated as of 29 Sept 2017) on Parallels
  Desktop 13.  When changing the HiDPI scaling to 200% everything looks
  good, but on restart the settings are reset to 100%.

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

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


[Desktop-packages] [Bug 1720442] Re: Software (gnome-software) crashes after several seconds. Entirely unusable.

2017-09-30 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

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

** Changed in: gnome-software (Ubuntu)
   Status: New => Incomplete

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

Title:
  Software (gnome-software) crashes after several seconds. Entirely
  unusable.

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu version: Ubuntu Artful Aardvark (development branch), Release: 17.10
  gnome-software package version: 3.26.0-0ubuntu2

  Expected: To be able to use the application.

  What happened instead: The application crashes after several seconds.
  Bug replicated every time the application is opened, rending it
  entirely unusable.

  Journald shows a segfault, as per attached snippet.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 21:01:06 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-09-14 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170912)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.0-0ubuntu2
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1719322] Re: Remove patch to remove headerbar

2017-09-30 Thread Jeremy Bicha
Daniel, how important do you think this issue is? Can it wait until
18.04 LTS?

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

Title:
  Remove patch to remove headerbar

Status in eog package in Ubuntu:
  Incomplete
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Incomplete
Status in file-roller package in Ubuntu:
  Fix Released
Status in gnome-contacts package in Ubuntu:
  Fix Released

Bug description:
  As of Artful, it seems that there are still patches against various
  apps that remove/replace the Gtk.HeaderBar with a Gtk.Toolbar.

  Now that GNOME Shell is default in Ubuntu and there is better support
  for client-side decorations, these patches can probably go away

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

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


[Desktop-packages] [Bug 1720597] [NEW] package libfreerdp-utils1.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1 failed to install/upgrade: package libfreerdp-utils1.1:amd64 is not ready for config

2017-09-30 Thread khaniszcze
Public bug reported:

cannot update Thunderbird

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libfreerdp-utils1.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
Uname: Linux 4.4.0-87-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Sun Oct  1 01:18:53 2017
DpkgHistoryLog:
 Start-Date: 2017-10-01  01:18:38
 Commandline: aptdaemon role='role-upgrade-packages' sender=':1.62'
 Upgrade: thunderbird:amd64 (1:52.2.1+build1-0ubuntu0.16.04.1, 
1:52.3.0+build1-0ubuntu0.16.04.1), thunderbird-locale-en:amd64 
(1:52.2.1+build1-0ubuntu0.16.04.1, 1:52.3.0+build1-0ubuntu0.16.04.1), 
thunderbird-locale-pl:amd64 (1:52.2.1+build1-0ubuntu0.16.04.1, 
1:52.3.0+build1-0ubuntu0.16.04.1)
DuplicateSignature:
 package:libfreerdp-utils1.1:amd64:1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1
 Processing triggers for man-db (2.7.5-1) ...
 dpkg: error processing package libfreerdp-utils1.1:amd64 (--configure):
  package libfreerdp-utils1.1:amd64 is not ready for configuration
ErrorMessage: package libfreerdp-utils1.1:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
InstallationDate: Installed on 2016-03-22 (557 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: freerdp
Title: package libfreerdp-utils1.1:amd64 
1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1 failed to install/upgrade: package 
libfreerdp-utils1.1:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
UpgradeStatus: Upgraded to xenial on 2016-04-25 (523 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libfreerdp-utils1.1:amd64
  1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1 failed to install/upgrade:
  package libfreerdp-utils1.1:amd64 is not ready for configuration
  cannot configure (current status 'half-installed')

Status in freerdp package in Ubuntu:
  New

Bug description:
  cannot update Thunderbird

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libfreerdp-utils1.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sun Oct  1 01:18:53 2017
  DpkgHistoryLog:
   Start-Date: 2017-10-01  01:18:38
   Commandline: aptdaemon role='role-upgrade-packages' sender=':1.62'
   Upgrade: thunderbird:amd64 (1:52.2.1+build1-0ubuntu0.16.04.1, 
1:52.3.0+build1-0ubuntu0.16.04.1), thunderbird-locale-en:amd64 
(1:52.2.1+build1-0ubuntu0.16.04.1, 1:52.3.0+build1-0ubuntu0.16.04.1), 
thunderbird-locale-pl:amd64 (1:52.2.1+build1-0ubuntu0.16.04.1, 
1:52.3.0+build1-0ubuntu0.16.04.1)
  DuplicateSignature:
   package:libfreerdp-utils1.1:amd64:1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package libfreerdp-utils1.1:amd64 (--configure):
package libfreerdp-utils1.1:amd64 is not ready for configuration
  ErrorMessage: package libfreerdp-utils1.1:amd64 is not ready for 
configuration  cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2016-03-22 (557 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: freerdp
  Title: package libfreerdp-utils1.1:amd64 
1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1 failed to install/upgrade: package 
libfreerdp-utils1.1:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (523 days ago)

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

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


[Desktop-packages] [Bug 1720597] Re: package libfreerdp-utils1.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1 failed to install/upgrade: package libfreerdp-utils1.1:amd64 is not ready for configur

2017-09-30 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 freerdp in Ubuntu.
https://bugs.launchpad.net/bugs/1720597

Title:
  package libfreerdp-utils1.1:amd64
  1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1 failed to install/upgrade:
  package libfreerdp-utils1.1:amd64 is not ready for configuration
  cannot configure (current status 'half-installed')

Status in freerdp package in Ubuntu:
  New

Bug description:
  cannot update Thunderbird

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libfreerdp-utils1.1:amd64 1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sun Oct  1 01:18:53 2017
  DpkgHistoryLog:
   Start-Date: 2017-10-01  01:18:38
   Commandline: aptdaemon role='role-upgrade-packages' sender=':1.62'
   Upgrade: thunderbird:amd64 (1:52.2.1+build1-0ubuntu0.16.04.1, 
1:52.3.0+build1-0ubuntu0.16.04.1), thunderbird-locale-en:amd64 
(1:52.2.1+build1-0ubuntu0.16.04.1, 1:52.3.0+build1-0ubuntu0.16.04.1), 
thunderbird-locale-pl:amd64 (1:52.2.1+build1-0ubuntu0.16.04.1, 
1:52.3.0+build1-0ubuntu0.16.04.1)
  DuplicateSignature:
   package:libfreerdp-utils1.1:amd64:1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package libfreerdp-utils1.1:amd64 (--configure):
package libfreerdp-utils1.1:amd64 is not ready for configuration
  ErrorMessage: package libfreerdp-utils1.1:amd64 is not ready for 
configuration  cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2016-03-22 (557 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: freerdp
  Title: package libfreerdp-utils1.1:amd64 
1.1.0~git20140921.1.440916e+dfsg1-5ubuntu1 failed to install/upgrade: package 
libfreerdp-utils1.1:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (523 days ago)

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

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


Re: [Desktop-packages] [Bug 1720510] Re: No results after search

2017-09-30 Thread Per-Inge
No I don't get any errors.
Tested again.on two installations on the same hardware.
- Restarted the the computer.
 - Started Ubuntu Software from the doc
- Search for "soft" and the result was presented
- Closed Ubuntu Software
- Started Ubuntu Software from the doc
- Search for "soft" and the result wasn't presented
- Clicked outside the Ubuntu Software window and the result was shown.

Will check on a new installation with other hardware later.

2017-10-01 2:24 GMT+02:00 Sebastien Bacher :

> thank you for your bug report, do you get any error displayed in the ui?
> trying here it works unless the snap query timeouts which blocks it to
> return other results but that's indicated in a notification
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1720510
>
> Title:
>   No results after search
>
> Status in gnome-software package in Ubuntu:
>   New
>
> Bug description:
>   Test case:
>   Open a new version of gnome-software/Ubuntu Software
>   Search for soft
>   No results are shown
>   Do something outside the gnome-software window, e.g mouse click or focus
> on another window, and the results are shown.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: gnome-software 3.26.0-0ubuntu3
>   ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
>   Uname: Linux 4.13.0-12-generic x86_64
>   ApportVersion: 2.20.7-0ubuntu1
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Sep 30 09:28:37 2017
>   InstallationDate: Installed on 2017-09-15 (14 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170915)
>   InstalledPlugins:
>gnome-software-plugin-flatpak N/A
>gnome-software-plugin-limba   N/A
>gnome-software-plugin-snap3.26.0-0ubuntu3
>   SourcePackage: gnome-software
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-software/
> +bug/1720510/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  No results after search

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Test case:
  Open a new version of gnome-software/Ubuntu Software
  Search for soft
  No results are shown
  Do something outside the gnome-software window, e.g mouse click or focus on 
another window, and the results are shown.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 30 09:28:37 2017
  InstallationDate: Installed on 2017-09-15 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170915)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.0-0ubuntu3
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2017-09-30 Thread Niels Erik Jensen
?

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

Title:
  udisksd crashed with SIGSEGV in g_mutex_lock()

Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  Showed up after login

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

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

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


[Desktop-packages] [Bug 1720606] Re: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

2017-09-30 Thread Apport retracing service
*** This bug is a duplicate of bug 1714790 ***
https://bugs.launchpad.net/bugs/1714790

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 #1714790, 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/1720606/+attachment/4959626/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  Running from the root.
   A bad disk with troubles and write errors was formatted and created logical 
disks. He hung up and had to twiddle the power supply. On this, the gnome-disks 
flew.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-disk-utility 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Sun Oct  1 08:52:10 2017
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2017-09-25 (5 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: gnome-disks
  ProcEnviron:
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7f6090cc8f5f :   
mov(%rbx),%rdi
   PC (0x7f6090cc8f5f) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-disk-utility
  StacktraceTop:
   g_dbus_object_get_interface () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   udisks_object_get_partition_table () from 
/usr/lib/x86_64-linux-gnu/libudisks2.so.0
   gdu_utils_get_all_contained_objects ()
   gdu_application_has_running_job ()
   ?? ()
  Title: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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