date:20170421

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [13Y-GNB1562A2I3, Realtek ALC269VC, Speaker, Internal] volume slider
  problem

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound on / off buttons do not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-44.47~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-44-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  erkanunluturk   1451 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Mar 28 15:14:30 2017
  InstallationDate: Installed on 2017-03-25 (2 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Dahili Ses - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Volume slider, or mixer problems
  Title: [13Y-GNB1562A2I3, Realtek ALC269VC, Speaker, Internal] volume slider 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/03/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: P023
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: PEGATRON Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr203:bd04/03/2012:svnARCELIK:pn13Y-GNB1562A2I3:pvrV107:rvnPEGATRONCORPORATION:rnP023:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0:
  dmi.product.name: 13Y-GNB1562A2I3
  dmi.product.version: V107
  dmi.sys.vendor: ARCELIK

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

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

[Desktop-packages] [Bug 1612380] Re: Huge unrealistic amount of hours to go shown after successfully moving file/folder

2017-04-21 Thread Bug Watch Updater

** Changed in: nautilus
   Status: Confirmed => Fix Released

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

Title:
  Huge unrealistic amount of hours to go shown after successfully moving
  file/folder

Status in Nautilus:
  Fix Released
Status in Ubuntu GNOME:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  For instance I was moving a folder today using Nautilus which told me
  it would take 5 minutes to move, and it did, the time to completion
  was actually very accurate, until it finished, at which point it
  suddenly jumped to this even though it had already succeed in moving
  the folder in the time it had promised. I see this happen reasonably
  often. I am running Ubuntu GNOME 16.04 with GNOME 3.20.

  I have attached a screenshot of what I mean.

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

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

[Desktop-packages] [Bug 1685419] [NEW] Just i want graphic drivers for my HP Compaq LE2002xi monitor

2017-04-21 Thread Shareque Mohammad

Public bug reported:

Just I want graphic drivers for my HP Compaq LE2002xi monitor
I have Intel Core I3 2nd Generation based processor

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8.2
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 Apr 22 10:31:38 2017
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:1495]
InstallationDate: Installed on 2017-03-13 (39 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
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.
MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic 
root=UUID=7f32f64d-9a8b-4437-8db3-bdb8a4a63265 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/10/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: J01 v02.15
dmi.board.asset.tag: 2UA2121YQH
dmi.board.name: 1495
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: 2UA2121YQH
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ01v02.15:bd11/10/2011:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP Compaq 8200 Elite SFF PC
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.74-1
version.libgl1-mesa-dri: libgl1-mesa-dri 13.0.2-1ubuntu1co1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 13.0.2-1ubuntu1co1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Sat Apr 22 10:21:00 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: OutputDP-1  HDMI-1 
  VGA-1
xserver.version: 2:1.18.4-1ubuntu6.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu yakkety

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

Title:
  Just i want graphic drivers for my HP Compaq LE2002xi monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  Just I want graphic drivers for my HP Compaq LE2002xi monitor
  I have Intel Core I3 2nd Generation based processor

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  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 Apr 22 10:31:38 2017
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:1495]
  InstallationDate: Installed on 2017-03-13 (39 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (201610

[Desktop-packages] [Bug 1645116] Re: [Brother DCP-J715W] core dumped executing scanimage -L

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

** Changed in: sane-backends (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [Brother DCP-J715W] core dumped executing scanimage -L

Status in sane-backends package in Ubuntu:
  Expired

Bug description:
  In Xubuntu 16.10 I get a core dump executing via a terminal:
  scanimage -L
  Erreur de segmentation (core dumped)

  Errors report:
  https://errors.ubuntu.com/oops/f494063a-bdc2-11e6-ad54-fa163e30221b

  With Xubuntu 16.04 I don't have this problem:
  scanimage -L
  device `brother3:net1;dev0' is a Brother DCP-J715W DCP-J715W

  The Brother DCP-J715W device is WiFi connected to my router. All the
  clients access the device via the network.

  I installed the latest Brother software on the client from their website:
  
http://support.brother.com/g/b/downloadlist.aspx?c=fr&lang=fr&prod=dcpj715w_eu_as&os=128&flang=English

  sudo dpkg -i  brscan3-0.2.13-1.amd64.deb
  sudo brsaneconfig3 -a name=scanner model=DCP-J715W ip=192.168.1.27
  sudo brsaneconfig3 -p
  cd /usr/lib64/
  sudo cp -r . /usr/lib

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: sane-utils 1.0.25+git20150528-1ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Nov 27 18:13:36 2016
  InstallationDate: Installed on 2016-11-22 (4 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1685414] [NEW] [MIR] gnome-settings-daemon

Public bug reported:

This is an abbreviated MIR since gnome-settings-daemon was in Ubuntu
since the beginning (therefore there was no MIR before) until it was
replaced by unity-settings-daemon, a fork of gnome-settings-daemon 3.6
(?). The intent now is to replace unity-settings-daemon in main with
gnome-settings-daemon.

At least for now, I expect unity-settings-daemon to remain in universe
in case it's useful for attempts to keep Unity going. On the other hand,
that's a pain since the gsettings schemas can't be forked, so there is a
lot of patching to keep schemas around since unity-control-center has
not kept up with gnome-settings-daemon at all.

Ubuntu Desktop Bugs is still subscribed to bugs for this package.

The last time gnome-settings-daemon was merged with Debian was 3.22:

+ Split out schemas into gnome-settings-daemon-schemas so
  unity-settings-daemon can use them
+ debian/control.in:
  - Build-depend on accountsservice
  - Bump breaks/replaces for moving files to the -schemas pkg
+ debian/patches:
   - 05_disable_corner_tapping.patch:
  Disable corner tapping when disabling tap to click
   - 45_suppress-printer-may-not-be-connected-notification.patch
   - 53_sync_input_sources_to_accountsservice.patch
   - 64_restore_terminal_keyboard_shortcut_schema.patch
   - correct_logout_action.patch
  display the logout action on ctrl-alt-del
   - ubuntu-lid-close-suspend.patch
  Reimplement support for setting lid close suspend actions
   - revert_background_dropping.patch
  Keep gsettings keys background u-s-d needs them
   - revert-gsettings-removals.patch
  Revert gsettings keys that were dropped since 3.8, for u-s-d
+ debian/gnome-settings-daemon-schemas.install:
  - Install schemas, translations and the rfkill rule
+ Don't install gnome-settings-daemon.gsettings-override
+ debian/rules: 
  - Dont link with "-Wl,-Bsymbolic-functions",
this was causing GType mismatches between plugins using
gsd-device-manager (LP: #1427877)

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

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

Title:
  [MIR] gnome-settings-daemon

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

Bug description:
  This is an abbreviated MIR since gnome-settings-daemon was in Ubuntu
  since the beginning (therefore there was no MIR before) until it was
  replaced by unity-settings-daemon, a fork of gnome-settings-daemon 3.6
  (?). The intent now is to replace unity-settings-daemon in main with
  gnome-settings-daemon.

  At least for now, I expect unity-settings-daemon to remain in universe
  in case it's useful for attempts to keep Unity going. On the other
  hand, that's a pain since the gsettings schemas can't be forked, so
  there is a lot of patching to keep schemas around since unity-control-
  center has not kept up with gnome-settings-daemon at all.

  Ubuntu Desktop Bugs is still subscribed to bugs for this package.

  The last time gnome-settings-daemon was merged with Debian was 3.22:

  + Split out schemas into gnome-settings-daemon-schemas so
unity-settings-daemon can use them
  + debian/control.in:
- Build-depend on accountsservice
- Bump breaks/replaces for moving files to the -schemas pkg
  + debian/patches:
 - 05_disable_corner_tapping.patch:
Disable corner tapping when disabling tap to click
 - 45_suppress-printer-may-not-be-connected-notification.patch
 - 53_sync_input_sources_to_accountsservice.patch
 - 64_restore_terminal_keyboard_shortcut_schema.patch
 - correct_logout_action.patch
display the logout action on ctrl-alt-del
 - ubuntu-lid-close-suspend.patch
Reimplement support for setting lid close suspend actions
 - revert_background_dropping.patch
Keep gsettings keys background u-s-d needs them
 - revert-gsettings-removals.patch
Revert gsettings keys that were dropped since 3.8, for u-s-d
  + debian/gnome-settings-daemon-schemas.install:
- Install schemas, translations and the rfkill rule
  + Don't install gnome-settings-daemon.gsettings-override
  + debian/rules: 
- Dont link with "-Wl,-Bsymbolic-functions",
  this was causing GType mismatches between plugins using
  gsd-device-manager (LP: #1427877)

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

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

[Desktop-packages] [Bug 1282372] Re: [MIR] colord-gtk

New MIR filed as LP: #1685411 since this package fell out of main but is
needed again.

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

Title:
  [MIR] colord-gtk

Status in colord-gtk package in Ubuntu:
  Fix Released

Bug description:
  Availability: Currently available in Universe, building on all
  currently supported architectures, see
  https://launchpad.net/ubuntu/+source/colord-gtk

  Rationale: The Unity Control Center Color panel uses colord-gtk to
  provide color management. The library is around 92k.

  Security: No known problems.

  Quality assurance: Maintained with colord.

  UI standards: Follows GNOME UI standards.

  Dependencies: All dependencies in main.

  Maintenance: Will be maintained in the same way colord is. (i.e.
  mostly by taking packages from Debian).

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

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

[Desktop-packages] [Bug 1685411] [NEW] [MIR] colord-gtk

Public bug reported:

Rationale
-
colord-gtk is a required build-dependency for gnome-control-center which is 
needed for gnome-shell

colord-gtk was in main before and the code hasn't really changed much
since then. Therefore, this is an abbreviated MIR. (I didn't look too
deeply but it looks like unity-control-center was forked before the
colord-gtk dependency was added and the commit was never backported into
unity-control-center.)

Old MIR: LP: #1282372

https://github.com/hughsie/colord-gtk/blob/master/NEWS
https://github.com/hughsie/colord-gtk/commits/master

The package is in sync with Debian.

** Affects: colord-gtk (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Rationale
  -
  colord-gtk is a required build-dependency for gnome-control-center which is 
needed for gnome-shell
  
- colord-gtk was in main before and the code hasn't really changed since
- then. Therefore, this is an abbreviated MIR. (I didn't look too deeply
- but it looks like unity-control-center was forked before the colord-gtk
- dependency was added and the commit was never backported into unity-
- control-center.)
+ colord-gtk was in main before and the code hasn't really changed much
+ since then. Therefore, this is an abbreviated MIR. (I didn't look too
+ deeply but it looks like unity-control-center was forked before the
+ colord-gtk dependency was added and the commit was never backported into
+ unity-control-center.)
  
  Old MIR: LP: #1282372
  
  https://github.com/hughsie/colord-gtk/blob/master/NEWS
  https://github.com/hughsie/colord-gtk/commits/master
  
  The package is in sync with Debian.

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

Title:
  [MIR] colord-gtk

Status in colord-gtk package in Ubuntu:
  New

Bug description:
  Rationale
  -
  colord-gtk is a required build-dependency for gnome-control-center which is 
needed for gnome-shell

  colord-gtk was in main before and the code hasn't really changed much
  since then. Therefore, this is an abbreviated MIR. (I didn't look too
  deeply but it looks like unity-control-center was forked before the
  colord-gtk dependency was added and the commit was never backported
  into unity-control-center.)

  Old MIR: LP: #1282372

  https://github.com/hughsie/colord-gtk/blob/master/NEWS
  https://github.com/hughsie/colord-gtk/commits/master

  The package is in sync with Debian.

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

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

[Desktop-packages] [Bug 1678271] Re: Background color erase (bce) is broken

2017-04-21 Thread Boris Gjenero

I'm not able to reproduce this now in Zesty with gnome-terminal
3.20.2-1ubuntu8. Program that was causing problems before is DOSBox SVN
with ncursesw output added, https://github.com/dreamlayers/em-
dosbox/tree/contxt-only but that works fine now. infocmp $TERM shows I'm
using /lib/terminfo/x/xterm-256color and bce is present there, so it
seems bce now works.

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

Title:
  Background color erase (bce) is broken

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I'm running my ncursesw application, displaying a black background.
  When the screen or a region scrolls up by one line, empty areas of the
  screen in the newly visible line show the default white background of
  gnome-terminal.

  If I remove the bce capability from the Terminfo for that terminal type, the 
problem goes away. This workaround involves:
  "infocmp xterm-256color > xt.ti" to get the Terminfo data in text format.
  Editing xt.ti and removing "bce, " on the 3rd line
  "tic xt.ti" to compile this text to Terminfo again. Without sudo that ends up 
in ~/.terminfo, overriding the system's entry, and with sudo it would overwrite 
the system's Terminfo entry for that terminal type.

  Another workaround would be to use a different terminal type without
  bce, like TERM=screen, but removing bce is better because that leaves
  other capabilities intact.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-terminal 3.20.2-1ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
  Uname: Linux 4.8.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 31 13:49:01 2017
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (169 days ago)

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

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

[Desktop-packages] [Bug 1685397] [NEW] Profile Manager no longer works as documented

2017-04-21 Thread Paul Gear

Public bug reported:

The Firefox man page documents that -ProfileManager and -P with no
profile specified should both start Firefox with the Profile Manager
dialog.  As of a recent release (I'm not exactly sure which one, but has
been since the release of yakkety), this no longer works and both
options simply open a blank window in the running Firefox instance.  If
there's no Firefox running, Profile Manager will display as normal, but
this is no different to when Firefox is started without parameters.

Expected behaviour: -ProfileManager or -P without a profile specified
should open the Firefox Profile Manager regardless of whether a Firefox
instance is running.

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

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

Title:
  Profile Manager no longer works as documented

Status in firefox package in Ubuntu:
  New

Bug description:
  The Firefox man page documents that -ProfileManager and -P with no
  profile specified should both start Firefox with the Profile Manager
  dialog.  As of a recent release (I'm not exactly sure which one, but
  has been since the release of yakkety), this no longer works and both
  options simply open a blank window in the running Firefox instance.
  If there's no Firefox running, Profile Manager will display as normal,
  but this is no different to when Firefox is started without
  parameters.

  Expected behaviour: -ProfileManager or -P without a profile specified
  should open the Firefox Profile Manager regardless of whether a
  Firefox instance is running.

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

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

[Desktop-packages] [Bug 1670059] Re: [Latitude 3340, Realtek ALC3234] Headphones Not Detected if Plugged in before Boot

2017-04-21 Thread spm2011

Headphones also stop working after logging out and back in, until they
are unplugged and plugged in again.

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

Title:
  [Latitude 3340, Realtek ALC3234] Headphones Not Detected if Plugged in
  before Boot

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When (re)booting with headphones in, audio won't play. Once the headphones 
are unplugged, it will start to come through the speakers and will work with 
the headphones when they are plugged back in.
  Expected headphones to be detected automatically even if plugged in before 
boot.

  This is on latest Xenial HWE kernel (4.8.0-39-generic x86_64).
  ALSA Info attached.

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

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

[Desktop-packages] [Bug 1685394] [NEW] hp media center remote not responding

2017-04-21 Thread Michael Stockenhuber

Public bug reported:

The hp mce remote was working fine with kodi running on Ubuntu 16.10. After 
upgrade to 17.04, 
the remote does not respond anymore. Loads the driver, dmesg looks ok. I 
managed to get it to respond a couple of times after a reboot by unpluging an 
plugging back in. 
ir-keytable gives:

Found /sys/class/rc/rc0/ (/dev/input/event9) with:
Driver mceusb, table rc-rc6-mce
Supported protocols: unknown other lirc rc-5 rc-5-sz jvc sony nec sanyo 
mce_kbd rc-6 sharp xmp 
Enabled protocols: lirc rc-6 
Name: Media Center Ed. eHome Infrared 
bus: 3, vendor/product: 1934:5168, version: 0x0001
Repeat delay = 500 ms, repeat period = 125 ms
I suspect this is a bug because it happenee just after the upgrade
any help would be greatly appreciated
cheers
Michael

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: lirc 0.9.4c-9
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Sat Apr 22 10:28:49 2017
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: lirc
UpgradeStatus: Upgraded to zesty on 2017-04-17 (4 days ago)
mtime.conffile..etc.lirc.hardware.conf: 2017-04-18T19:07:44.10
mtime.conffile..etc.lirc.lircd.conf: 2017-04-18T18:58:35.039496

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

Title:
  hp media center remote not responding

Status in lirc package in Ubuntu:
  New

Bug description:
  The hp mce remote was working fine with kodi running on Ubuntu 16.10. After 
upgrade to 17.04, 
  the remote does not respond anymore. Loads the driver, dmesg looks ok. I 
managed to get it to respond a couple of times after a reboot by unpluging an 
plugging back in. 
  ir-keytable gives:

  Found /sys/class/rc/rc0/ (/dev/input/event9) with:
Driver mceusb, table rc-rc6-mce
Supported protocols: unknown other lirc rc-5 rc-5-sz jvc sony nec sanyo 
mce_kbd rc-6 sharp xmp 
Enabled protocols: lirc rc-6 
Name: Media Center Ed. eHome Infrared 
bus: 3, vendor/product: 1934:5168, version: 0x0001
Repeat delay = 500 ms, repeat period = 125 ms
  I suspect this is a bug because it happenee just after the upgrade
  any help would be greatly appreciated
  cheers
  Michael

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: lirc 0.9.4c-9
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sat Apr 22 10:28:49 2017
  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: lirc
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (4 days ago)
  mtime.conffile..etc.lirc.hardware.conf: 2017-04-18T19:07:44.10
  mtime.conffile..etc.lirc.lircd.conf: 2017-04-18T18:58:35.039496

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

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

[Desktop-packages] [Bug 1685387] Re: Suspending machine takes too long

2017-04-21 Thread kyjo

I just noticed this only happens in the MATE environment. When I suspend
from Gnome it suspends immediatelly.

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

Title:
  Suspending machine takes too long

Status in pm-utils package in Ubuntu:
  New

Bug description:
  1) Ubuntu 16.04 and Ubuntu 16.10

  2) pm-utils 1.4.1-16

  3) I expect the machine to suspend without delay. On Ubuntu 15.10 the
  my machine used to suspend in 1-2 seconds.

  4) It takes over 10 seconds before the machine is suspended.

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

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

[Desktop-packages] [Bug 1685387] [NEW] Suspending machine takes too long

2017-04-21 Thread kyjo

Public bug reported:

1) Ubuntu 16.04 and Ubuntu 16.10

2) pm-utils 1.4.1-16

3) I expect the machine to suspend without delay. On Ubuntu 15.10 the my
machine used to suspend in 1-2 seconds.

4) It takes over 10 seconds before the machine is suspended.

** Affects: pm-utils (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Suspending machine takes too long

Status in pm-utils package in Ubuntu:
  New

Bug description:
  1) Ubuntu 16.04 and Ubuntu 16.10

  2) pm-utils 1.4.1-16

  3) I expect the machine to suspend without delay. On Ubuntu 15.10 the
  my machine used to suspend in 1-2 seconds.

  4) It takes over 10 seconds before the machine is suspended.

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

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

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

2017-04-21 Thread GammaPoint

This bug fix corrected my VPN leaks in Ubuntu 16.10, but I've since
upgraded to 17.04 (fresh install) and I'm seeing DNS leaks again. Should
this issue be fixed in Zesty already, or is that coming later?

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

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

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

Bug description:
  [Impact]

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

  [Test Case]

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

  [Regression Potential]

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

  ---

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1181632] Re: gnome-shell doesn't give focus to fallback lock screen

** Changed in: ubuntu-gnome
   Status: New => Fix Released

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

Title:
  gnome-shell doesn't give focus to fallback lock screen

Status in GTK+:
  Fix Released
Status in Ubuntu GNOME:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  I tried running gnome-shell 3.8 with lightdm instead of gdm. I locked
  the screen with Ctrl+Alt+L. When I tried to enter my password to
  unlock, no characters showed up but it's still possible to blindly
  enter the password and unlock -- there just isn't any feedback that
  GNOME is accepting input.

  An alternate workaround is to click Switch User from the unlock screen
  and enter my password from the login screen which unlocked my screen.

  We should fix this bug before having gnome-shell depend solely on
  libgdm instead of gdm (LP: #1162849).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-shell 3.8.2-1ubuntu1
  ProcVersionSignature: Ubuntu 3.9.0-2.6-generic 3.9.2
  Uname: Linux 3.9.0-2-generic x86_64
  ApportVersion: 2.10.1-0ubuntu1
  Architecture: amd64
  CrashDB: ubuntu
  Date: Sat May 18 19:26:23 2013
  DisplayManager: lightdm
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  MarkForUpload: True
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to saucy on 2013-05-07 (11 days ago)

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

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

[Desktop-packages] [Bug 1566717] Re: No option to set up Gnome Terminal Notifications "Job done"

This feature has been available in Fedora for years.

Find the branch you need in the following two repos and then copy the commits 
for it.
https://github.com/debarshiray/vte
https://github.com/debarshiray/gnome-terminal

** Changed in: gnome-terminal (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: ubuntu-gnome
Milestone: yakkety => artful

** Changed in: ubuntu-gnome
   Status: New => Triaged

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

Title:
  No option to set up Gnome Terminal Notifications "Job done"

Status in GNOME Terminal:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gnome-terminal package in Ubuntu:
  Triaged

Bug description:
  Hi,

  Ubuntu Gnome 16.04 - 64 bits - Nvidia driver ON

  expected to happen : Could set up notification for Gnome Terminal to
  show thumbnail in notification area "job done"

  What happened : Nothing, there is no such option in gnome settings.
  Haven't seen in dconf-editor or kind of setting editor - so there is
  no gnome terminal notification

  wich this not my mistake, anyway

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-terminal 3.18.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Apr  6 10:22:12 2016
  InstallationDate: Installed on 2016-04-05 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160323.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1547127] Re: Guest account option - feature request

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

** Tags added: gnome-17.10

** Changed in: ubuntu-gnome
   Status: New => Triaged

** Changed in: ubuntu-gnome
Milestone: None => artful

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

Title:
  Guest account option - feature request

Status in gdm:
  Unknown
Status in Ubuntu GNOME:
  Triaged
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  Though I didn't have it enabled for security reasons when I was using
  Unity, I think that some may find it useful to have a 'guest account'
  option, though I think that it should be off by default and be
  reasonably easy to configure in the gnome-control-center.

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

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

[Desktop-packages] [Bug 1672424] Re: Cannot install Debian files outside of the repositories

2017-04-21 Thread Robert Ancell

I didn't push the last change to master because I'm not sure of the
correct solution there. The apt plugin is not upstream, so it doesn't
make sense to set the management plugin to apt (should probably be
packagekit?). I don't really get the point of management plugin so I
need to ask Richard what to do here.

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

Title:
  Cannot install Debian files outside of the repositories

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Confirmed
Status in gnome-software source package in Yakkety:
  Confirmed
Status in gnome-software source package in Zesty:
  Confirmed

Bug description:
  Impact
  --
  It is not possible to use the default Software app to install .debs for 
packages that are not already available in Ubuntu.

  Test Case
  -
  1.
  a. Download the .deb for a simple app for your version of Ubuntu directly 
from Launchpad.
  For 16.10, try 
https://launchpad.net/ubuntu/+source/gnome-clocks/3.22.1-0ubuntu1/
  Click amd64 then download the last .deb on that page.

  b. Open the .deb with gnome-software:
  gnome-software --local-filename=gnome-clocks_3.22.1-0ubuntu1_amd64.deb

  gnome-software should open to a page with an Install button for the
  package.

  This test case should already work.

  2.
  a. Download a .deb that is not already in Ubuntu.
  It is important that the package not be available in your local apt cache.
  For this, I made sure that I was not using the GNOME3 Staging PPA. As of 
today, switcheroo-control is not accepted into Ubuntu 17.04.

  So I downloaded
  https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+files
  /switcheroo-control_1.1-0ubuntu0~zesty1_amd64.deb

  b. Open the .deb with gnome-software
  gnome-software 
--local-filename=switcheroo-control_1.1-0ubuntu0~zesty1_amd64.deb

  I only suggested using switcheroo-control because I know it's not because the 
package isn't packaged correctly. Alternatively, this test case should also 
work with one of these:
  https://www.google.com/chrome/
  https://itch.io/app

  gnome-software should open to a page with an Install button for the
  package.

  What Happens
  
  The second test fails. On Ubuntu 17.04, I get a popup
  "Sorry this did not work The file is not supported"

  On Ubuntu 16.04 LTS or 16.10, I get "Sorry this did not work No
  file_to_app results to show"

  Regression Potential
  

  Original Bug Report
  ---
  .deb files fail to install from non repository locations i.e. The file 
manager gnome-software claims "this file type is not supported".

  Using dpkg from the command line works as expected so the files aren't
  corrupt. This happened last distribution as well when it was first
  released. Might be a regression caused by adding snap package
  capabilities to the software-center?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-software 3.22.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar 13 10:02:00 2017
  InstallationDate: Installed on 2017-02-20 (20 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to zesty on 2017-02-28 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1672424/+subscriptions

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

[Desktop-packages] [Bug 1671612] Re: Software app only shows explicitly compatible GNOME Shell extensions

This is fixed now. I believe this issue only affected Ubuntu GNOME
17.04.

** Changed in: ubuntu-gnome
   Status: Triaged => Fix Released

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

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

Title:
  Software app only shows explicitly compatible GNOME Shell extensions

Status in GNOME Software:
  In Progress
Status in Ubuntu GNOME:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released

Bug description:
  Only gnome-shell extensions explicitly marked as compatible with the
  running gnome-shell version are shown in the Addons category in gnome-
  software.

  This is a problem when a beta version of gnome- shell is packaged.

  It's a problem when a new gnome-shell version is first released
  because it takes time for developers to test the extension and mark it
  as compatible. It's also a problem because gnome-software only checks
  for extension updates every 7 days.

  Some extensions still work but haven't been updated in a very long
  time.

  More discussion on the attached GNOME bug, particularly comment 7 and
  at GNOME bug 776460

  
  Original Bug Report
  ---
  Update: This behavior was because gnome-shell was a 3.23 development snapshot 
and no extensions at extensions.gnome.org were marked as being explicitly 
compatible with that version.

  GNOME Software 3.22 includes a plugin to show GNOME Shell extensions
  when GNOME Shell is running.

  On the home page, click Add-Ons.

  Except that the Add-Ons button is not showing up here.

  gnome-software 3.22.6-0ubuntu1
  Ubuntu GNOME 17.04 Beta

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

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

[Desktop-packages] [Bug 1628179] Re: gnome-session does not show version info

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: ubuntu-gnome
Milestone: yakkety => None

** Changed in: ubuntu-gnome
   Importance: Medium => Low

** Project changed: ubuntu-gnome => gnome-session (Ubuntu)

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

Title:
  gnome-session does not show version info

Status in gnome-session package in Ubuntu:
  Triaged

Bug description:
  Following command has no output.
  $ gnome-session --version
  However, help says,
  $ gnome-session --help
  Usage:
gnome-session-binary [OPTION...]  - the GNOME session manager

  Help Options:
-h, --helpShow help options

  Application Options:
-a, --autostart=AUTOSTART_DIR Override standard autostart directories
--session=SESSION_NAMESession to use
--debug   Enable debugging code
-f, --failsafeDo not load user-specified applications
--version Version of this application
--whale   Show the fail whale dialog for testing
--disable-acceleration-check  Disable hardware acceleration check

  Also, in man, there in no entry for gnome-session.

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

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

[Desktop-packages] [Bug 1610944] Re: GNOME Online Accounts breaks if you log out (until you reboot)

** Tags removed: package-from-proposed
** Tags added: gnome-17.10

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

Title:
  GNOME Online Accounts breaks if you log out (until you reboot)

Status in gnome-online-accounts:
  Unknown
Status in Ubuntu GNOME:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  Can't add any online accounts in after opened Online accounts + mark is 
faded, can't click.
  After reinstalled gnome-online-accounts still has same problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-online-accounts 3.20.3-1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Mon Aug  8 15:33:45 2016
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1610944/+subscriptions

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

[Desktop-packages] [Bug 1628179] [NEW] gnome-session does not show version info

You have been subscribed to a public bug:

Following command has no output.
$ gnome-session --version
However, help says,
$ gnome-session --help
Usage:
  gnome-session-binary [OPTION...]  - the GNOME session manager

Help Options:
  -h, --helpShow help options

Application Options:
  -a, --autostart=AUTOSTART_DIR Override standard autostart directories
  --session=SESSION_NAMESession to use
  --debug   Enable debugging code
  -f, --failsafeDo not load user-specified applications
  --version Version of this application
  --whale   Show the fail whale dialog for testing
  --disable-acceleration-check  Disable hardware acceleration check

Also, in man, there in no entry for gnome-session.

** Affects: gnome-session (Ubuntu)
 Importance: Low
 Status: Triaged


** Tags: gnome-3.20 yakkety
-- 
gnome-session does not show version info
https://bugs.launchpad.net/bugs/1628179
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-session 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 1678271] Re: Background color erase (bce) is broken

Boris,

I've added a patch to the linked VTE bug. Could you please let me know
if it fixes your problem?

The simplest way of testing: download VTE, patch and compile it, and run
"./src/testvte".

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

Title:
  Background color erase (bce) is broken

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I'm running my ncursesw application, displaying a black background.
  When the screen or a region scrolls up by one line, empty areas of the
  screen in the newly visible line show the default white background of
  gnome-terminal.

  If I remove the bce capability from the Terminfo for that terminal type, the 
problem goes away. This workaround involves:
  "infocmp xterm-256color > xt.ti" to get the Terminfo data in text format.
  Editing xt.ti and removing "bce, " on the 3rd line
  "tic xt.ti" to compile this text to Terminfo again. Without sudo that ends up 
in ~/.terminfo, overriding the system's entry, and with sudo it would overwrite 
the system's Terminfo entry for that terminal type.

  Another workaround would be to use a different terminal type without
  bce, like TERM=screen, but removing bce is better because that leaves
  other capabilities intact.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-terminal 3.20.2-1ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
  Uname: Linux 4.8.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 31 13:49:01 2017
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (169 days ago)

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

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

[Desktop-packages] [Bug 1685353] [NEW] new

2017-04-21 Thread Joseph Bondi

Public bug reported:

sorry

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Apr 21 16:07:22 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GM107 [GeForce GTX 750 Ti] [3842:3753]
InstallationDate: Installed on 2017-04-15 (6 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Gigabyte Technology Co., Ltd. Z270X-UD3
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=8e613cba-dc9a-418e-a419-a466c3efa01d ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/24/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2
dmi.board.asset.tag: Default string
dmi.board.name: Z270X-UD3-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd11/24/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ270X-UD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270X-UD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.name: Z270X-UD3
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Fri Apr 21 13:42:27 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1
xserver.video_driver: nouveau

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


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

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

Title:
  new

Status in xorg package in Ubuntu:
  New

Bug description:
  sorry

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Apr 21 16:07:22 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: eVga.com. Corp. GM107 [GeForce GTX 750 Ti] [3842:3753]
  InstallationDate: Installed on 2017-04-15 (6 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Gigabyte Technology Co., Ltd. Z270X-UD3
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=8e613cba-dc9a-418e-a419-a466c3efa01d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: Default string
  dmi.board.name: Z270X-UD3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd11/24/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ270X-UD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270X-UD3-CF:rvrx.x:cvnDefaultstring:ct3:cv

[Desktop-packages] [Bug 1672465] Re: Onboard doesn't work in Wayland

2017-04-21 Thread Francesco Fumanti

** Changed in: onboard
   Status: Confirmed => In Progress

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

Title:
  Onboard doesn't work in Wayland

Status in Onboard:
  In Progress
Status in onboard package in Ubuntu:
  Confirmed

Bug description:
  Onboard 1.4.1 on Ubuntu GNOME 17.04

  Onboard at least shows the keyboard now in GNOME on Wayland. But it
  doesn't send key presses to gedit or other native Wayland apps.

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

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

[Desktop-packages] [Bug 1683037] Re: touchpad mouse not moves hoizontally in kubuntu 17.04.

2017-04-21 Thread Gnu

I think this is a bug with Synaptics driver, rather than xinput.

I added a xorg.conf and changed to Driver "libinput"
With libinput the mouse pointer is moving in all directions. 

** Also affects: xserver-xorg-input-synaptics (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
   touchpad mouse not moves hoizontally in kubuntu 17.04.

Status in xinput package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-synaptics package in Ubuntu:
  New

Bug description:
  In Kubuntu 17.04. my touchpad (Lenovo ideapad 500S-13ISK) is
  recognized as "AlpsPS/2 ALPS GlidePoint".

  All clicks are recognized. Two finger scrolling is working, but the mouse 
pointer is only moving vertically not horizontally.
  I tried several boot options (i8042.nomux, i8042.reset) but nothing changed 
the behavior.

  I figured out it occurs the same behavior (no horizontal mouse pointer
  movement) not only after update from Kubuntu 16.10, but also in the
  Live version when starting kubuntu / ubuntu 17.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xinput 1.6.2-1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr 15 16:05:12 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-14 (1 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: xinput
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1644830] Re: gnome-software process does not quit after closing application window

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

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

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

Title:
  gnome-software process does not quit after closing application window

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Gnome-system-monitor shows a process "gnome-software" that continues
  running after the application window has been closed. The process
  constantly takes 100–200MB RAM and was not there after boot/login.

  Observed behavior:
  Process does not quit after quitting the application window, although it is 
neither used nor does it seem to give any other noticeable benefit from the 
reserved memory.

  Expected behavior:
  After closing the application window, it's process ends.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-software 3.20.1+git20161003.0.7ac7d1b-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Nov 25 14:05:31 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-05 (20 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  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/1644830/+subscriptions

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

[Desktop-packages] [Bug 1685347] [NEW] /dev/sr0

2017-04-21 Thread Ulrich Gros

Public bug reported:

i have installed Ubuntu 16.10 on my Sony vario
VGN-NW210AE without serious problems. Now I started with go around on the system
First I had tried to check the DVD drive same Cd i was possible to mount and 
open but a lot was not possible.
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
# / was on /dev/sda2 during installation
UUID=9b81a2a9-ae7c-44ea-80e4-818fe4344a45 /   ext4
errors=remount-ro 0   1
# /boot was on /dev/sda1 during installation
UUID=28937039-ce17-4714-8282-22e86004091d /boot   ext3defaults  
  0   2
# /home was on /dev/sda5 during installation
UUID=3d475f29-5177-4e0d-aa1a-cf0e0c19a8c5 /home   ext4defaults  
  0   2
# /opt was on /dev/sda9 during installation
UUID=f0207789-c415-4f72-a0e8-d8486303c123 /optext4defaults  
  0   2
# /reserve was on /dev/sda13 during installation
UUID=66ce238a-63bb-4356-9ac2-d240cca08a2d /reserveext4defaults  
  0   2
# /reserve1 was on /dev/sda15 during installation
UUID=e66f737d-94a0-4e47-ae5f-ef2f66942076 /reserve1   ext4defaults  
  0   2
# /root was on /dev/sda11 during installation
UUID=29f4b1da-9df8-4a57-9f1d-9eef0dbdb54c /root   ext4defaults  
  0   2
# /srv was on /dev/sda10 during installation
UUID=f3b5a6f4-9dc4-4a29-9d01-6e9a5b835121 /srvext4defaults  
  0   2
# /tmp was on /dev/sda6 during installation
UUID=2f47c1ca-7d3a-4f35-ab52-b2a879c95753 /tmpext4defaults  
  0   2
# /usr was on /dev/sda7 during installation
UUID=a430eb8a-e7d1-4ae5-812b-06dd40e05d9a /usrext4defaults  
  0   2
# /usr/local was on /dev/sda12 during installation
UUID=17b3854f-54d5-4f9b-a9a6-96ebebaf4b07 /usr/local  ext4defaults  
  0   2
# /var was on /dev/sda8 during installation
UUID=5f851ee2-6fd6-4e62-ba7f-962151d8fc3c /varext4defaults  
  0   2
# /windows was on /dev/sda14 during installation
UUID=2535-4B06  /windowsvfatutf8,umask=007,gid=46 0   1
# swap was on /dev/sda3 during installation
UUID=5541e93e-604d-4f8f-9157-5abadfba86da noneswapsw
  0   0
/dev/disk/by-id/ata-MATSHITADVD-RAM_UJ880AS_UG33_135382 
/mnt/ata-MATSHITADVD-RAM_UJ880AS_UG33_135382 auto nosuid,nodev,nofail 0 0

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8.2
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
Date: Fri Apr 21 16:08:12 2017
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Sony Corporation Mobile 4 Series Chipset Integrated Graphics 
Controller [104d:906b]
   Subsystem: Sony Corporation Mobile 4 Series Chipset Integrated Graphics 
Controller [104d:906b]
InstallationDate: Installed on 2017-04-21 (0 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: Sony Corporation VGN-NW210AE
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-46-generic 
root=UUID=9b81a2a9-ae7c-44ea-80e4-818fe4344a45 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/20/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R1120Y4
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR1120Y4:bd08/20/2009:svnSonyCorporation:pnVGN-NW210AE:pvrC7003NB9:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VGN-NW210AE
dmi.product.version: C7003NB9
dmi.sys.vendor: Sony Corporation
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2

[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.

2017-04-21 Thread Anton

I just ran headlong into this same issue on Ubuntu 16.04 LTS using
Audacity 2.1.2 on my Dell XPS15. When inserting a jack, I get a dialogue
box asking whether I have a headphone, headset, or mic inserted
(apparently an external amp with speakers should be considered
'headphones', but that's a different issue). It all works fine, until I
start audacity. Also, when closing audacity, it still doesn't work.

The same workaround still works: switch the mic source to something else
but the headphone. Which IMHO isn't a fix, it is a cludgy, confusing
workaround.

Judging by the dialogue box, this is really more of an Audacity issue,
and not so much alsa-driver, but I thought to mention it here as well.

$ dpkg -l audacity
ii  audacity   2.1.2-1  amd64fast, cross-platform audio editor
$ uname -a
Linux AF-XPS-15-9550 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Headphones stopped working after use of Audacity. They are detected,
  but no sound is produced.

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  I'm running 13.10 and the latest GNOME. I've just fresh installed
  everything and the problem has occured again the same way. I would
  like to be able to use audacity, but I suppose in the mean time I will
  just reinstall everything.

  Steps to reproduce : 
  1) Install audacity 2.0.3 from official Ubuntu repositories
  2) Open Audacity and play something with it
  3) That's it : no more headphones sound.

  
  - alsa log created with 'alsa-info.sh' 
(https://wiki.ubuntu.com/Audio/AlsaInfo) : http://paste.ubuntu.com/7131709/

  - pulse log when I plug in my headphones, I run a MP3 file with VLC,
  close VLC then unplug headphones
  (https://wiki.ubuntu.com/PulseAudio/Log) :
  http://paste.ubuntu.com/7131713/

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

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

[Desktop-packages] [Bug 1684213] Re: Intel Wireless 7260 often crashes

2017-04-21 Thread Ben

** Attachment added: "Output dmesg crash on resume"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684213/+attachment/4866130/+files/ucode-error-crash.txt

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

Title:
  Intel Wireless 7260 often crashes

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS 
enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses 
Intel 7260 wifi, rev. bb:
  01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently,
  everything (kernel, firmware, etc.) is stock. Issue has persisted
  across multiple installations.

  Bug: Wifi/Bluetooth crashes and refuses to come back up, even after
  multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.)

  When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, 
upon boot, it is not uncommon for the wireless to stop working within two 
minutes of login time. Curiously, the GUI usually still shows being 
"connected", though trying to change anything with the wifi shows otherwise. 
Other times, upon system resume when wireless was previously working, the GUI 
will show "device not ready" and refuse to continue. Dmesg shows the following:
  [  423.814823] Bluetooth: hci0 command 0x1403 tx timeout
  [  424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  424.173067] iwlwifi :01:00.0: Scan failed! ret -5
  [  425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  425.194593] iwlwifi :01:00.0: Scan failed! ret -5

  Solution: Rebooting doesn't fix the problem. Perhaps a different
  firmware version will work better? Configuration settings? etc.?
  Unknown.

  Thanks ahead of time for the help. Let me know if there's anything you
  need/commands I should run/solutions I can attempt.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bmueller   1669 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Apr 19 10:34:11 2017
  InstallationDate: Installed on 2017-04-13 (6 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp.
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Gnawty
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=45b1dd3f-10df-4a28-904c-74c694ef75a5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago)
  dmi.bios.date: 08/16/2015
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

[Desktop-packages] [Bug 1684213] Re: Intel Wireless 7260 often crashes

2017-04-21 Thread Ben

** Attachment added: "Output of modinfo iwlwifi"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684213/+attachment/4866129/+files/modinfo-iwlwifi.txt

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

Title:
  Intel Wireless 7260 often crashes

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS 
enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses 
Intel 7260 wifi, rev. bb:
  01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently,
  everything (kernel, firmware, etc.) is stock. Issue has persisted
  across multiple installations.

  Bug: Wifi/Bluetooth crashes and refuses to come back up, even after
  multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.)

  When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, 
upon boot, it is not uncommon for the wireless to stop working within two 
minutes of login time. Curiously, the GUI usually still shows being 
"connected", though trying to change anything with the wifi shows otherwise. 
Other times, upon system resume when wireless was previously working, the GUI 
will show "device not ready" and refuse to continue. Dmesg shows the following:
  [  423.814823] Bluetooth: hci0 command 0x1403 tx timeout
  [  424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  424.173067] iwlwifi :01:00.0: Scan failed! ret -5
  [  425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  425.194593] iwlwifi :01:00.0: Scan failed! ret -5

  Solution: Rebooting doesn't fix the problem. Perhaps a different
  firmware version will work better? Configuration settings? etc.?
  Unknown.

  Thanks ahead of time for the help. Let me know if there's anything you
  need/commands I should run/solutions I can attempt.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bmueller   1669 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Apr 19 10:34:11 2017
  InstallationDate: Installed on 2017-04-13 (6 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp.
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Gnawty
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=45b1dd3f-10df-4a28-904c-74c694ef75a5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago)
  dmi.bios.date: 08/16/2015
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

[Desktop-packages] [Bug 1684213] Re: Intel Wireless 7260 often crashes

2017-04-21 Thread Ben

Some additional notes after testing for a while...

The crashing behavior doesn't occur consistently in the same way.
Sometimes the Bluetooth crashes with the Wifi, while sometimes it
recovers fine and continues to work while the Wifi doesn't. In addition,
it seems that the Wifi crash breaks NetworkManager as well- when I try
to plug in a USB WiFi card, the networks show up but give me the
following error in dmesg whenever the usb adapter tries to connect:

[21857.875157] wlx002129e30688: authenticate with 8e:15:44:a9:86:22
[21857.924545] wlx002129e30688: send auth to 8e:15:44:a9:86:22 (try 1/3)
[21857.926882] wlx002129e30688: authenticated
[21863.316129] wlx002129e30688: authenticate with 8e:15:44:a9:85:f8
[21863.371861] wlx002129e30688: send auth to 8e:15:44:a9:85:f8 (try 1/3)
[21863.374438] wlx002129e30688: authenticated
[21868.376165] wlx002129e30688: aborting authentication with 8e:15:44:a9:85:f8 
by local choice (Reason: 3=DEAUTH_LEAVING)
[21868.740813] wlx002129e30688: authenticate with 8e:15:44:a9:82:fa
[21868.788615] wlx002129e30688: send auth to 8e:15:44:a9:82:fa (try 1/3)
[21868.790444] wlx002129e30688: authenticated
[21873.795552] wlx002129e30688: aborting authentication with 8e:15:44:a9:82:fa 
by local choice (Reason: 3=DEAUTH_LEAVING)

This repeats until it gives up trying to connect. Yet, tethering to my
Android phone over USB DOES usually work. Restarting the NetworkManager
service has no effect on the wifi issue.

@jsalisbury: This issue has persisted across kernel versions and Ubuntu
versions. I had the same issue on 16.10, as well as Arch when I used it,
upgrade or not. I'm not ruling out a regression however, but frankly I
have no qualifications to say what the issue is caused by. If I have
time (and I get desperate enough) I'll try 16.04 and 14.04 and let you
know if it's still present there.

I'll test the 4.11 kernel this weekend, in the meantime, I'll upload
some more dmesg outputs.

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

Title:
  Intel Wireless 7260 often crashes

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS 
enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses 
Intel 7260 wifi, rev. bb:
  01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently,
  everything (kernel, firmware, etc.) is stock. Issue has persisted
  across multiple installations.

  Bug: Wifi/Bluetooth crashes and refuses to come back up, even after
  multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.)

  When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, 
upon boot, it is not uncommon for the wireless to stop working within two 
minutes of login time. Curiously, the GUI usually still shows being 
"connected", though trying to change anything with the wifi shows otherwise. 
Other times, upon system resume when wireless was previously working, the GUI 
will show "device not ready" and refuse to continue. Dmesg shows the following:
  [  423.814823] Bluetooth: hci0 command 0x1403 tx timeout
  [  424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  424.173067] iwlwifi :01:00.0: Scan failed! ret -5
  [  425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  425.194593] iwlwifi :01:00.0: Scan failed! ret -5

  Solution: Rebooting doesn't fix the problem. Perhaps a different
  firmware version will work better? Configuration settings? etc.?
  Unknown.

  Thanks ahead of time for the help. Let me know if there's anything you
  need/commands I should run/solutions I can attempt.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bmueller   1669 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Apr 19 10:34:11 2017
  InstallationDate: Installed on 2017-04-13 (6 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp.
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Gnawty
  Pr

[Desktop-packages] [Bug 1678271] Re: Background color erase (bce) is broken

This was broken intentionally in order to fix another bug which is not
fixable and not even workaroundable otherwise. See
https://bugzilla.gnome.org/show_bug.cgi?id=754596. Although, as
discussed there, we are aware of problems that we introduced and we have
a few ideas how to improve (that is, partially revert) the behavior.

In order to help move forward, could you please share your app (or
better, a tiny proof of concept, just the necessary steps extracted that
demo the problematic behavior)?

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

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

Title:
  Background color erase (bce) is broken

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I'm running my ncursesw application, displaying a black background.
  When the screen or a region scrolls up by one line, empty areas of the
  screen in the newly visible line show the default white background of
  gnome-terminal.

  If I remove the bce capability from the Terminfo for that terminal type, the 
problem goes away. This workaround involves:
  "infocmp xterm-256color > xt.ti" to get the Terminfo data in text format.
  Editing xt.ti and removing "bce, " on the 3rd line
  "tic xt.ti" to compile this text to Terminfo again. Without sudo that ends up 
in ~/.terminfo, overriding the system's entry, and with sudo it would overwrite 
the system's Terminfo entry for that terminal type.

  Another workaround would be to use a different terminal type without
  bce, like TERM=screen, but removing bce is better because that leaves
  other capabilities intact.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-terminal 3.20.2-1ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
  Uname: Linux 4.8.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 31 13:49:01 2017
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (169 days ago)

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

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

[Desktop-packages] [Bug 1684678] Re: NVIDIA Driver Crashes the System

2017-04-21 Thread Kai-Heng Feng

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

** No longer affects: unity (Ubuntu)

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

Title:
  NVIDIA Driver Crashes the System

Status in bbswitch package in Ubuntu:
  New

Bug description:
  When I install the proprietary driver from NVIDIA the system doesn't
  log on.In return it repeatedly shows the error.

  bbswitch:No suitable _dsm call found

  
  Driver shown Additional Drivers Page:

  Using NVIDIA binary driver-version 375.29 from
  nvidia-375(proprietary,tested).

  The NVIDIA Driver was working fine in Ubuntu 16.10 in my laptop. 
  When I upgraded to Ubuntu 17.04 I got this error. So I completely removed 
that and made a clean installation of Ubuntu 17.04 but still I got the error.
   
  My Laptop Specs:

  OS:Ubuntu 17.04

  Processor:i5-5200u

  Graphics: NVIDIA 920M 2GB

  RAM: 8GB

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

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

[Desktop-packages] [Bug 1629251] Re: Some app-indicators not showing menus

2017-04-21 Thread Pat

@Mark Tidd, I had the same problem with pia indicator. I contacted pia's
help desk and they gave me the folowing instructions to fix it. You can
copy and past the instructions in the terminal. It is best to remove the
app and re-install it. The instructions below were sent to me by the
pia's support team:

To remove the app follow these instructions:

Please, I will encourage you to fully remove the PIA app, then download
a fresh copy of the app and re-install, then check if issue persist. To
uninstall our application you can simply run the following terminal
command:

NOTE: Please make sure this step is completed very carefully. All
symbols, and spacing are VERY important. Incorrect usage of this command
can lead to DATA LOSS. (It is best to simply copy and paste the command
below)


rm -rf ~/.pia_manager/

If the command is successful, there will be no confirmation, it will
simply go to a new line in the Terminal window.

Once you have done that, you can install the app from:
https://www.privateinternetaccess.com/installer/download_installer_linux
,

Then, from the terminal in the directory you downloaded to:

1) Extract file: tar -xzf pia-v68-installer-linux.tar.gz

2) Tell OS to proceed: chmod +x pia-v68-installer-linux.sh

3) Run installer: ./pia-v68-installer-linux.sh

Please enter your login details and click save. Make sure not to select
Start application at login and Auto-connect on launch.


To fix the pia app not showing on the indicator, pia's support team suggested 
the following:

>From the terminal type the following instructions:

1. Open terminal and type:

cd ~/.pia_manager/pia_manager/

Next run the following (this is case sensitive, so it may be best to
copy and paste),

env XDG_CURRENT_DESKTOP=Unity ./run.sh


After trying the above, does the icon appear in the tray(it may take 15 seconds 
or so)? If not, is there any errors in the terminal?

If the above worked, please proceed to the next step:

2.  Next you need to edit pia_manager.desktop in
/.local/share/applications and add the following line after Exec=:

env XDG_CURRENT_DESKTOP=Unity

To do so, please enter the following commands in terminal:

cd ~/.local /share/applications

Next, type the following:

nano pia_manager.desktop


The final result should look something like the following (additional 
information in bold; YourUserName will of course be different, e.g Arthur):

Type=Application Name=Private Internet Access   
  
Exec=env XDG_CURRENT_DESKTOP=Unity 
/home/YourUserName/.pia_manager/pia_manager/run.sh
Icon=/home/YourUserName/.pia_manager/pia_tray_files/img/default_app_logo.png 


(there is a space between Unity and /home)

To exit and save, hit ctrl-x on your keyboard and hit y

I also copied the edited pia_manager.desktop in
/.local/share/applications to /user/share/applications folder. This is
so that I can search for the app in the dash. All you need to do in dash
is start type priv it sholud show two green icons for Private Internet
Access. Select the bigger one of the two (it is slightly brighter than
the other). Once the app started, you should see the icon on the
launcher. Right click on it and select lock to launcher. This enables
you to run the app from the launcher from now on.

Hope fully you should the red icon on the app indicator.

Good luck

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

Title:
  Some app-indicators not showing menus

Status in appmenu-qt package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Impact
  ==
  In Ubuntu 16.10 the menus of the Dropbox and hplip app-indicators are not 
working. I attach a video of the problem.

  Test Case
  =
  sudo apt install hplip-gui
  Log out
  Log in (to Unity)
  Click the hp indicator in the top left of the screen.
  Does it show items or is it blank?

  appmenu-qt 0.2.7+14.04.20140305-0ubuntu2  is installed

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity 7.5.0+16.10.20160906.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7
  Date: Fri Sep 30 11:44:26 2016
  DistUpgraded: 2016-09-01 11:00:51,009 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: yakkety
  DistroVariant: ubun

[Desktop-packages] [Bug 1683898] Re: Compose key can't be set in Settings>Keyboard with GNOME 3.24

2017-04-21 Thread Gunnar Hjalmarsson

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

** Changed in: gnome-control-center
   Importance: Medium => Unknown

** Changed in: gnome-control-center
   Status: Confirmed => Unknown

** Changed in: gnome-control-center
 Remote watch: GNOME Bug Tracker #781478 => GNOME Bug Tracker #771009

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

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

Title:
  Compose key can't be set in Settings>Keyboard with GNOME 3.24

Status in gnome-control-center:
  Unknown
Status in Gnome Documentation:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-user-docs package in Ubuntu:
  Confirmed

Bug description:
  The changes implemented with https://bugs.launchpad.net/ubuntu/+source
  /ubuntu-docs/+bug/1624778 in https://help.gnome.org/users/gnome-
  help/stable/tips-specialchars.html.en#compose do not reflect the
  current settings dialog for Ubuntu-Gnome 17.04.

  Going from "All Settings" to "Keyboard" switches to "Keyboard Shortcuts" 
immediately.
  The new "Keyboard Shortcuts" dialog does not seem to contain settings for 
'compose key' (the group "Typing" only contains "Switch to {next,previous} 
input source").

  PS: In the meantime, where do I find the settings for 'compose key' in
  Ubuntu-Gnome 17.04? :(

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

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

[Desktop-packages] [Bug 1564067] Re: gvfsd-dnssd crashed with SIGSEGV in avahi_service_resolver_event()

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

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

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

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

Title:
  gvfsd-dnssd crashed with SIGSEGV in avahi_service_resolver_event()

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  Automatically started report of bug, have no other information

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gvfs-backends 1.27.92-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 31 08:58:50 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gvfs/gvfsd-dnssd
  InstallationDate: Installed on 2016-03-12 (18 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/lib/gvfs/gvfsd-dnssd --spawner :1.5 
/org/gtk/gvfs/exec_spaw/7
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_NZ:en
   PATH=(custom, no user)
   LANG=en_NZ.UTF-8
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? ()
   ?? ()
   avahi_service_resolver_event () from 
/usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  Title: gvfsd-dnssd crashed with SIGSEGV in avahi_service_resolver_event()
  UpgradeStatus: Upgraded to xenial on 2016-03-16 (13 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1564259] Re: gvfsd-dnssd crashed with SIGSEGV in avahi_service_resolver_event()

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

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

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

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

Title:
  gvfsd-dnssd crashed with SIGSEGV in avahi_service_resolver_event()

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  unknow

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gvfs-backends 1.27.92-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 31 08:46:58 2016
  ExecutablePath: /usr/lib/gvfs/gvfsd-dnssd
  InstallationDate: Installed on 2016-03-17 (13 days ago)
  InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160127)
  ProcCmdline: /usr/lib/gvfs/gvfsd-dnssd --spawner :1.6 
/org/gtk/gvfs/exec_spaw/32
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? ()
   ?? ()
   avahi_service_resolver_event () from 
/usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  Title: gvfsd-dnssd crashed with SIGSEGV in avahi_service_resolver_event()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1684506] Re: QT4 Trolltech.conf settings lost after reboot

2017-04-21 Thread eugenez

Same. 
After saving the qtconfig settings and reboot, there are two lines "fonts=" 
appears in ~/.config/Trolltech.conf

#after reboot
$ cat ~/.config/Trolltech.conf | grep font=
font="Ubuntu,8,-1,5,50,0,0,0,0,0"
font="Sans Serif,9,-1,5,50,0,0,0,0,0"

#after manual qtconfig saving
$ cat ~/.config/Trolltech.conf | grep font=
font="Ubuntu,8,-1,5,50,0,0,0,0,0"

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

Title:
  QT4 Trolltech.conf settings lost after reboot

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Since the update to Kubuntu 17.04 / plasma 5.9.4 all qt4 based
  applications (e.g. KeePassX) render using wrong font instead of my
  personal configured font. When I run qtconfig-qt4 (4.8.7), change font
  and click 'save', a fresh .config/Trolltech.conf is saved, contains
  the correct font config and all qt4 applications now show correct
  font. These settings however do not survive a reboot although
  Trolltech.conf exists and contains correct settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  Uname: Linux 4.10.11 x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Apr 20 10:33:21 2017
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to zesty on 2017-04-11 (8 days ago)

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

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

[Desktop-packages] [Bug 1574347] Re: WiFi networks list disappears (device type not reloaded)

2017-04-21 Thread Khoi

Bug still occurs with network-manager 1.2.6-0ubuntu0.16.04.1

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

Title:
  WiFi networks list disappears (device type not reloaded)

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  
  💥 WARNING 💥
  
  If you are still experiencing this bug please don't comment here, but look at 
these: (https://goo.gl/LdPpYG)

  **
   HOW TO REPRODUCE
  **
  Boot the system.

  
   RESULT
  
  From time to time, some of these happen:
  - The applet doesn't list any wireless network.
  - The applet doesn't show the name of the current network.
  - The icon shows the wired connection symbol, instead of the wifi one.

  *
   WORK AROUND
  *
  (http://askubuntu.com/questions/762198/16-04-lts-wifi-connection-issues)

  *
   FIX
  *
  The applet needs to re-read the DEVTYPE after the device name changed.

  ***
   HOW TO TEST A FIX
  ***
  In the Terminal application enter:
  nmcli dev

  If it works, in the line for the wireless device, the TYPE column
  should be "wifi". If it doesn't it will be "ethernet".

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

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

[Desktop-packages] [Bug 1684506] Re: QT4 Trolltech.conf settings lost after reboot

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

Title:
  QT4 Trolltech.conf settings lost after reboot

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Since the update to Kubuntu 17.04 / plasma 5.9.4 all qt4 based
  applications (e.g. KeePassX) render using wrong font instead of my
  personal configured font. When I run qtconfig-qt4 (4.8.7), change font
  and click 'save', a fresh .config/Trolltech.conf is saved, contains
  the correct font config and all qt4 applications now show correct
  font. These settings however do not survive a reboot although
  Trolltech.conf exists and contains correct settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  Uname: Linux 4.10.11 x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Apr 20 10:33:21 2017
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to zesty on 2017-04-11 (8 days ago)

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

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

[Desktop-packages] [Bug 1685317] [NEW] Cannot build CUPS 2.2.3 with cups-filters 1.13.4

2017-04-21 Thread Alex Korobkin

Public bug reported:

When CUPS 2.2.3 is being built, one of the steps is testing: test/run-
stp-tests.sh.

CUPS passes the tests OK with cups-filters-1.0.54, but fails with cups-
filters-1.13.4 due to some changes in how classified.pdf banner is
handled, which is done when test Job 14 is printed.


cups-filters 1.0.54:
[Job 14] Started filter /tmp/cups-pbuser/bin/filter/bannertopdf (PID 38207)
[Job 14] Started filter /tmp/cups-pbuser/bin/filter/pdftopdf (PID 38208)
[Job 14] Started filter /tmp/cups-pbuser/bin/filter/pdftops (PID 38209)
[Job 14] pdftops - copying to temp print file 
\"/tmp/cups-pbuser/spool/temp/0954158fd0dc0\"
[Job 14] PDF template file doesn\'t have form. It\'s okay.
[Job 14] PID 38207 (/tmp/cups-pbuser/bin/filter/bannertopdf) exited with no 
errors.
[Job 14] PID 38208 (/tmp/cups-pbuser/bin/filter/pdftopdf) exited with no errors.

cups-filters 1.13.4:
[Job 14] Started filter /tmp/cups-pbuser/bin/filter/bannertopdf (PID 76934)
[Job 14] Started filter /tmp/cups-pbuser/bin/filter/pdftopdf (PID 76935)
[Job 14] Started filter /tmp/cups-pbuser/bin/filter/pdftops (PID 76936)
[Job 14] pdftops - copying to temp print file 
\"/tmp/cups-pbuser/spool/temp/12c8858f972ae\"
[Job 14] pdftopdf: Last filter determined by the PPD: None; FINAL_CONTENT_TYPE: 
printer/Test1 => pdftopdf will not log pages in page_log.
[Job 14] PID 76934 (/tmp/cups-pbuser/bin/filter/bannertopdf) stopped with 
status 1.
[Job 14] PID 76935 (/tmp/cups-pbuser/bin/filter/pdftopdf) stopped with status 1.
[Job 14] I/O Error: Couldn\'t open file 
\'/tmp/cups-pbuser/share/data/classified.pdf\': No such file or directory.
[Job 14] Error: unable to open template document 
\'/tmp/cups-pbuser/share/data/classified.pdf\'
[Job 14] loadFile failed: temp file: not a PDF file


I see that previous debian releases used to link banners from 
/usr/share/cups/banner to /tmp/cups-$user, but there's no linking to 
/usr/share/cups/data/*.pdf that now exist for cups-filters-1.13. 

I guess something like this is needed for the patch:

--- a/test/run-stp-tests.sh
+++ b/test/run-stp-tests.sh
@@ -482,6 +483,17 @@
ln -sf /usr/share/cups/banners/topsecret /tmp/cups-$user/share/banners/
ln -sf /usr/share/cups/banners/unclassified 
/tmp/cups-$user/share/banners/
 
+  ln -sf /usr/share/cups/data/classified.pdf /tmp/cups-$user/share/data
+  ln -sf /usr/share/cups/data/confidential.pdf /tmp/cups-$user/share/data
+  ln -sf /usr/share/cups/data/default.pdf /tmp/cups-$user/share/data
+  ln -sf /usr/share/cups/data/default-testpage.pdf /tmp/cups-$user/share/data
+  ln -sf /usr/share/cups/data/form_english.pdf /tmp/cups-$user/share/data
+  ln -sf /usr/share/cups/data/form_russian.pdf /tmp/cups-$user/share/data
+  ln -sf /usr/share/cups/data/secret.pdf /tmp/cups-$user/share/data
+  ln -sf /usr/share/cups/data/standard.pdf /tmp/cups-$user/share/data
+  ln -sf /usr/share/cups/data/topsecret.pdf /tmp/cups-$user/share/data
+  ln -sf /usr/share/cups/data/unclassified.pdf /tmp/cups-$user/share/data
+
if test -d /usr/share/cups/charsets; then
ln -s /usr/share/cups/charsets $BASE/share
fi

** Affects: cups-filters (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Cannot build CUPS 2.2.3 with cups-filters 1.13.4

Status in cups-filters package in Ubuntu:
  New

Bug description:
  When CUPS 2.2.3 is being built, one of the steps is testing: test/run-
  stp-tests.sh.

  CUPS passes the tests OK with cups-filters-1.0.54, but fails with
  cups-filters-1.13.4 due to some changes in how classified.pdf banner
  is handled, which is done when test Job 14 is printed.

  
  cups-filters 1.0.54:
  [Job 14] Started filter /tmp/cups-pbuser/bin/filter/bannertopdf (PID 38207)
  [Job 14] Started filter /tmp/cups-pbuser/bin/filter/pdftopdf (PID 38208)
  [Job 14] Started filter /tmp/cups-pbuser/bin/filter/pdftops (PID 38209)
  [Job 14] pdftops - copying to temp print file 
\"/tmp/cups-pbuser/spool/temp/0954158fd0dc0\"
  [Job 14] PDF template file doesn\'t have form. It\'s okay.
  [Job 14] PID 38207 (/tmp/cups-pbuser/bin/filter/bannertopdf) exited with no 
errors.
  [Job 14] PID 38208 (/tmp/cups-pbuser/bin/filter/pdftopdf) exited with no 
errors.

  cups-filters 1.13.4:
  [Job 14] Started filter /tmp/cups-pbuser/bin/filter/bannertopdf (PID 76934)
  [Job 14] Started filter /tmp/cups-pbuser/bin/filter/pdftopdf (PID 76935)
  [Job 14] Started filter /tmp/cups-pbuser/bin/filter/pdftops (PID 76936)
  [Job 14] pdftops - copying to temp print file 
\"/tmp/cups-pbuser/spool/temp/12c8858f972ae\"
  [Job 14] pdftopdf: Last filter determined by the PPD: None; 
FINAL_CONTENT_TYPE: printer/Test1 => pdftopdf will not log pages in page_log.
  [Job 14] PID 76934 (/tmp/cups-pbuser/bin/filter/bannertopdf) stopped with 
status 1.
  [Job 14] PID 76935 (/tmp/cups-pbuser/bin/filter/pdft

[Desktop-packages] [Bug 1685272] Re: gnome-shell: no window border

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

** Changed in: light-themes (Ubuntu)
   Status: New => Confirmed

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

Title:
  gnome-shell: no window border

Status in light-themes package in Ubuntu:
  Confirmed
Status in light-themes source package in Artful:
  Confirmed

Bug description:
  Under gnome-shell, there are no window borders.  See attached
  screenshot.

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

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

[Desktop-packages] [Bug 1685273] Re: gnome-shell: notebook tabs hard to distinguish

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

** Changed in: light-themes (Ubuntu)
   Status: New => Confirmed

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

Title:
  gnome-shell: notebook tabs hard to distinguish

Status in light-themes package in Ubuntu:
  Confirmed
Status in light-themes source package in Artful:
  Confirmed

Bug description:
  Under gnome-shell, it's difficult to distinguish which tab is focused.
  See the attached screenshot.

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

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

[Desktop-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout

2017-04-21 Thread Simos Xenitellis 

@dror-sign: I just tried the Alt+F shortcut on LibreOffice, on Ubuntu
16.04, having enabled the Hebrew keyboard layout. It worked for me.

You are supposed to have as primary keyboard layout the English (En)
keyboard layout.

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

Title:
  Hotkeys not functional in non-latin keyboard layout

Status in aptana-studio-installer:
  New
Status in Default settings and artwork for Baltix OS:
  New
Status in LibreOffice:
  Fix Released
Status in ibus:
  New
Status in Indicator keyboard:
  Fix Released
Status in Inkscape:
  New
Status in Intellij Idea:
  New
Status in monodevelop:
  New
Status in Mutter:
  Fix Released
Status in okular:
  New
Status in OpenOffice:
  New
Status in sigram:
  New
Status in Unity:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-terminal package in Ubuntu:
  Triaged
Status in kdevelop package in Ubuntu:
  Confirmed
Status in openjdk-7 package in Ubuntu:
  Incomplete
Status in unity package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  In Progress
Status in gnome-settings-daemon source package in Xenial:
  Triaged
Status in gnome-terminal source package in Xenial:
  Triaged
Status in kdevelop source package in Xenial:
  Confirmed
Status in openjdk-7 source package in Xenial:
  Incomplete
Status in unity source package in Xenial:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  In Progress
Status in gnome-shell package in Fedora:
  Unknown
Status in openoffice package in Fedora:
  Unknown

Bug description:
  New keyboard layout changer in Ubuntu 13.10 introduce  old-new bug. Any 
system or application hotkey witch use char (for example: ctrl+alt+t for 
terminal or ctrl+t for new tab in browser) become unfunctional when selected 
non-latin keyboard layout.
  Hotkeys with F1-12, numbers and other non-character buttons works perfectly.

  Window manager hotkeys not affected by this bug. All hotkeys in system
  parameters->keyboard->hotkeys->windows works perfect with any keyboard
  layout.

  Workaround for some system hotkeys and two layouts (english and non-
  latin): rebind all hotkeys in your local layout. For example instead
  of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with
  english layout.  If you use english and two different non-latin
  layouts this workaround helps only with one of them.


  Dear Ubuntu users and developers! 
  Please include the following information to your comment about non-latin 
shortcuts problems:
  1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 
14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean 
installed
  2. What keyboard layout do you have
  3. What shortcut for keyboard layout switching do you use 
  4. On which session you have problems - that is one from Unity, GNOME Shell, 
GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz)
  5. With which program and its version and origin (Ubuntu repositories, PPA, 
non-deb binary package from some website) you have problems.

  By providing this information you can make bug-fixing much simpler and
  may be faster.

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions

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

[Desktop-packages] [Bug 1685294] [NEW] Deja-dup won't run backup in Xubuntu 17.04

2017-04-21 Thread Victor Marin

Public bug reported:

Deja-dup backup won't run in Xubuntu 17.04; It works OK in Ubuntu MATE
and Kubuntu (both 17.04 version), though.

I attach you the error message it spawns when trying to make a backup.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: deja-dup 34.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Apr 21 17:50:14 2017
InstallationDate: Installed on 2017-04-19 (1 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: deja-dup
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: deja-dup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

** Attachment added: "Captura de pantalla_2017-04-21_17-49-02.png"
   
https://bugs.launchpad.net/bugs/1685294/+attachment/4866089/+files/Captura%20de%20pantalla_2017-04-21_17-49-02.png

** Summary changed:

- Deja-dup won't start in Xubuntu 17.04
+ Deja-dup won't run in Xubuntu 17.04

** Summary changed:

- Deja-dup won't run in Xubuntu 17.04
+ Deja-dup won't run backup in Xubuntu 17.04

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

Title:
  Deja-dup won't run backup in Xubuntu 17.04

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Deja-dup backup won't run in Xubuntu 17.04; It works OK in Ubuntu MATE
  and Kubuntu (both 17.04 version), though.

  I attach you the error message it spawns when trying to make a backup.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: deja-dup 34.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Apr 21 17:50:14 2017
  InstallationDate: Installed on 2017-04-19 (1 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1685292] [NEW] Zesty: network-manager-applet VPN 17.04 Cisco AnyConnect fails with Duo Authentication

2017-04-21 Thread pureblood

Public bug reported:

Since I have updated to Ubuntu Zesty 17.04 I have had problems with
connecting through VPN. I did not understand at first what was causing
the issue. Now I think I have figured it out and explaining the issue
might help other people with the same problem understanding what is
going on.

I login to my work VPN network using Cisco AnyConnect (available through
package openconnect) and Duo Authentication. Because of Duo
Authentication, there are always two passwords to fill in, one is my
regular password and the other one is a 6 numeric password generated
every few seconds that I need to ascertain from my smartphone. If I
click on the option dialogue box "Save passwords", I think the applet
manager will save both passwords and the next time I try to connect
through VPN it will use both passwords (one of which will be expired)
multiple times until my work account will be locked out. By the time the
dialogue appears allowing me to include the correct passwords, it seems
to be already too late. The login will fail no matter what because now I
have been locked out and I could understand what was going on because
there was no way for me to know that at that point I had been
irrevocably locked out of the ability to VPN.

I do not know if this is a network-manager issue, a network-manager-
applet issue, or an openconnect issue, but this is definitely a
completely new annoying behaviour resulting from the update to Ubuntu
Zesty 17.04.

Also, of notice buy maybe unrelated, if I select in the network-manager-
applet "VPN Connections", the option "Configure VPN..." is greyed out
and cannot be selected anymore. This is also a new behaviour of Ubuntu
Zesty 17.04.

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

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

Title:
Zesty: network-manager-applet VPN 17.04 Cisco AnyConnect fails with
Duo Authentication

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

Bug description:
Since I have updated to Ubuntu Zesty 17.04 I have had problems with
connecting through VPN. I did not understand at first what was causing
the issue. Now I think I have figured it out and explaining the issue
might help other people with the same problem understanding what is
going on.

I login to my work VPN network using Cisco AnyConnect (available
through package openconnect) and Duo Authentication. Because of Duo
Authentication, there are always two passwords to fill in, one is my
regular password and the other one is a 6 numeric password generated
every few seconds that I need to ascertain from my smartphone. If I
click on the option dialogue box "Save passwords", I think the applet
manager will save both passwords and the next time I try to connect
through VPN it will use both passwords (one of which will be expired)
multiple times until my work account will be locked out. By the time
the dialogue appears allowing me to include the correct passwords, it
seems to be already too late. The login will fail no matter what
because now I have been locked out and I could understand what was
going on because there was no way for me to know that at that point I
had been irrevocably locked out of the ability to VPN.

Also, of notice buy maybe unrelated, if I select in the network-
manager-applet "VPN Connections", the option "Configure VPN..." is
greyed out and cannot be selected anymore. This is also a new
behaviour of Ubuntu Zesty 17.04.

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

--
Mailing list: https://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 1226962] Re: Hotkeys not functional in non-latin keyboard layout

2017-04-21 Thread drorlev

LibreOffice shortcuts don't work in Hebrew on Ubuntu 16.04

On Fri, Apr 21, 2017 at 12:19 PM, Simos Xenitellis  <
1226...@bugs.launchpad.net> wrote:

> @xeron-oskom: Indeed, Super+A/F/M/C/V are not adapted and do not currently
> work with Greek either.
> However, what is working, are those shortcuts that I show in my screenshot
> (Super+W, Super+S).
>
> Here is a screenshot that shows that when you switch to Russian keyboard
> layout, the Unity shortcuts for Super+W and Super+S are adapted
> automatically for Russian.
>
> The way that Super+W and Super+S work, makes me believe that these are not
> hard-coded but dynamic.
> Here is relevant code http://bazaar.launchpad.net/~
> unity-team/unity/trunk/files/head:/shortcuts/
>
>
> ** Attachment added: "unity-shortcuts-russian.png"
>https://bugs.launchpad.net/unity/+bug/1226962/+
> attachment/4865983/+files/unity-shortcuts-russian.png
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1246583).
> https://bugs.launchpad.net/bugs/1226962
>
> Title:
>   Hotkeys not functional in non-latin keyboard layout
>
> Status in aptana-studio-installer:
>   New
> Status in Default settings and artwork for Baltix OS:
>   New
> Status in LibreOffice:
>   Fix Released
> Status in ibus:
>   New
> Status in Indicator keyboard:
>   Fix Released
> Status in Inkscape:
>   New
> Status in Intellij Idea:
>   New
> Status in monodevelop:
>   New
> Status in Mutter:
>   Fix Released
> Status in okular:
>   New
> Status in OpenOffice:
>   New
> Status in sigram:
>   New
> Status in Unity:
>   Fix Released
> Status in gnome-settings-daemon package in Ubuntu:
>   Triaged
> Status in gnome-terminal package in Ubuntu:
>   Triaged
> Status in kdevelop package in Ubuntu:
>   Confirmed
> Status in openjdk-7 package in Ubuntu:
>   Incomplete
> Status in unity package in Ubuntu:
>   Fix Released
> Status in unity-settings-daemon package in Ubuntu:
>   In Progress
> Status in gnome-settings-daemon source package in Xenial:
>   Triaged
> Status in gnome-terminal source package in Xenial:
>   Triaged
> Status in kdevelop source package in Xenial:
>   Confirmed
> Status in openjdk-7 source package in Xenial:
>   Incomplete
> Status in unity source package in Xenial:
>   Fix Released
> Status in unity-settings-daemon source package in Xenial:
>   In Progress
> Status in gnome-shell package in Fedora:
>   Unknown
> Status in openoffice package in Fedora:
>   Unknown
>
> Bug description:
>   New keyboard layout changer in Ubuntu 13.10 introduce  old-new bug. Any
> system or application hotkey witch use char (for example: ctrl+alt+t for
> terminal or ctrl+t for new tab in browser) become unfunctional when
> selected non-latin keyboard layout.
>   Hotkeys with F1-12, numbers and other non-character buttons works
> perfectly.
>
>   Window manager hotkeys not affected by this bug. All hotkeys in system
>   parameters->keyboard->hotkeys->windows works perfect with any keyboard
>   layout.
>
>   Workaround for some system hotkeys and two layouts (english and non-
>   latin): rebind all hotkeys in your local layout. For example instead
>   of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with
>   english layout.  If you use english and two different non-latin
>   layouts this workaround helps only with one of them.
>
>
>   Dear Ubuntu users and developers!
>   Please include the following information to your comment about non-latin
> shortcuts problems:
>   1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME,
> Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or
> clean installed
>   2. What keyboard layout do you have
>   3. What shortcut for keyboard layout switching do you use
>   4. On which session you have problems - that is one from Unity, GNOME
> Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback
> (Compiz)
>   5. With which program and its version and origin (Ubuntu repositories,
> PPA, non-deb binary package from some website) you have problems.
>
>   By providing this information you can make bug-fixing much simpler and
>   may be faster.
>
>   --
>   For other layout switching problems introduced in Ubuntu 13.10 you can
> see bug 1218322.
>   --
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/aptana-studio-installer/+bug/
> 1226962/+subscriptions
>

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

Title:
  Hotkeys not functional in non-latin keyboard layout

Status in aptana-studio-installer:
  New
Status in Default settings and artwork for Baltix OS:
  New
Status in LibreOffice:
  Fix Released
Status in ibus:
  New
Status in Indicator keyboard:
  Fix Released
Status in Inkscape:
  New
Status in Intellij Idea:
  New
Status in monodevelop:
  New
Status in Mutter:
  Fix Released
Status in okular:
  New
S

Re: [Desktop-packages] [Bug 1681228] Re: LightDM Unityt-Gretter is wrong resolution

2017-04-21 Thread Robert Jackson

Sorry ... this bug was against a MacBook Pro 15 inch. But the scenario
is the same. Look screen looks great. Login screen looks kind of
cartoonish in size. I'll send pictures tonight.

Sent from my iPhone

> On Apr 21, 2017, at 6:46 AM, Sebastien Bacher  wrote:
> 
> Thank you for your bug report, your screen is hidpi so the scaling is
> normal, is that your issue, would you prefer to have tiny UI elements?
> 
> ** Package changed: lightdm (Ubuntu) => unity-greeter (Ubuntu)
> 
> ** Changed in: unity-greeter (Ubuntu)
>   Importance: Undecided => Low
> 
> ** Changed in: unity-greeter (Ubuntu)
>   Status: Confirmed => Incomplete
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1681228
> 
> Title:
>  LightDM Unityt-Gretter is wrong resolution
> 
> Status in unity-greeter package in Ubuntu:
>  Incomplete
> 
> Bug description:
>  Running on a macbook pro 15" at 2880 x 1800.
> 
>  At 16.04 the greeter starts at the correct resolution and then after a
>  couple of secs changes to what looks like 2X scaling.
> 
>  I updated to 16.10 and now the greeter boots directly into the 2z
>  scaling.
> 
>  It almost seems like the bug was fixed backwards.
> 
>  ProblemType: Bug
>  DistroRelease: Ubuntu 16.10
>  Package: lightdm 1.19.5-0ubuntu1.1
>  ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
>  Uname: Linux 4.8.0-46-generic x86_64
>  ApportVersion: 2.20.3-0ubuntu8.2
>  Architecture: amd64
>  CurrentDesktop: Unity
>  Date: Sun Apr  9 10:27:54 2017
>  InstallationDate: Installed on 2017-04-01 (8 days ago)
>  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
> (20160719)
>  SourcePackage: lightdm
>  UpgradeStatus: Upgraded to yakkety on 2017-04-07 (2 days ago)
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1681228/+subscriptions

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

Title:
  LightDM Unityt-Gretter is wrong resolution

Status in unity-greeter package in Ubuntu:
  Incomplete

Bug description:
  Running on a macbook pro 15" at 2880 x 1800.

  At 16.04 the greeter starts at the correct resolution and then after a
  couple of secs changes to what looks like 2X scaling.

  I updated to 16.10 and now the greeter boots directly into the 2z
  scaling.

  It almost seems like the bug was fixed backwards.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.5-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr  9 10:27:54 2017
  InstallationDate: Installed on 2017-04-01 (8 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to yakkety on 2017-04-07 (2 days ago)

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

-- 
Mailing list: https://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 1681228] Re: LightDM Unityt-Gretter is wrong resolution

2017-04-21 Thread Robert Jackson

The screen is 4K and I get where you are coming from on a 15 or 13 inch
monitor...but the Razer Blade Pro has a 17.3 inch monitor.

I'll send a photo of the unity greater login screen which looks almost
cartoonish compared to the unity screen lock which looks amazing.

> On Apr 21, 2017, at 6:46 AM, Sebastien Bacher  wrote:
> 
> Thank you for your bug report, your screen is hidpi so the scaling is
> normal, is that your issue, would you prefer to have tiny UI elements?
> 
> ** Package changed: lightdm (Ubuntu) => unity-greeter (Ubuntu)
> 
> ** Changed in: unity-greeter (Ubuntu)
>   Importance: Undecided => Low
> 
> ** Changed in: unity-greeter (Ubuntu)
>   Status: Confirmed => Incomplete
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1681228
> 
> Title:
>  LightDM Unityt-Gretter is wrong resolution
> 
> Status in unity-greeter package in Ubuntu:
>  Incomplete
> 
> Bug description:
>  Running on a macbook pro 15" at 2880 x 1800.
> 
>  At 16.04 the greeter starts at the correct resolution and then after a
>  couple of secs changes to what looks like 2X scaling.
> 
>  I updated to 16.10 and now the greeter boots directly into the 2z
>  scaling.
> 
>  It almost seems like the bug was fixed backwards.
> 
>  ProblemType: Bug
>  DistroRelease: Ubuntu 16.10
>  Package: lightdm 1.19.5-0ubuntu1.1
>  ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
>  Uname: Linux 4.8.0-46-generic x86_64
>  ApportVersion: 2.20.3-0ubuntu8.2
>  Architecture: amd64
>  CurrentDesktop: Unity
>  Date: Sun Apr  9 10:27:54 2017
>  InstallationDate: Installed on 2017-04-01 (8 days ago)
>  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
> (20160719)
>  SourcePackage: lightdm
>  UpgradeStatus: Upgraded to yakkety on 2017-04-07 (2 days ago)
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1681228/+subscriptions

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

Title:
  LightDM Unityt-Gretter is wrong resolution

Status in unity-greeter package in Ubuntu:
  Incomplete

Bug description:
  Running on a macbook pro 15" at 2880 x 1800.

  At 16.04 the greeter starts at the correct resolution and then after a
  couple of secs changes to what looks like 2X scaling.

  I updated to 16.10 and now the greeter boots directly into the 2z
  scaling.

  It almost seems like the bug was fixed backwards.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.5-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr  9 10:27:54 2017
  InstallationDate: Installed on 2017-04-01 (8 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to yakkety on 2017-04-07 (2 days ago)

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

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

[Desktop-packages] [Bug 1685271] Re: gnome-shell: corners are not rounded

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

** Changed in: light-themes (Ubuntu)
   Status: New => Confirmed

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

Title:
  gnome-shell: corners are not rounded

Status in light-themes package in Ubuntu:
  Confirmed
Status in light-themes source package in Artful:
  Confirmed

Bug description:
  Under gnome-shell apps have dark black squared top corners when they
  should be rounded.  See attached screenshot.

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

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

[Desktop-packages] [Bug 1682238] Re: Update mutter and gnome-shell to 3.24.1

** Branch linked: lp:~ken-vandine/gnome-shell/ubuntu

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

Title:
  Update mutter and gnome-shell to 3.24.1

Status in gnome-desktop3 package in Ubuntu:
  In Progress
Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Zesty:
  Fix Committed

Bug description:
  Impact
  --
  3.24.1 is a new bugfix release in the stable 3.24 series. Although mutter and 
gnome-shell could be handled separately, it makes sense to handle them together 
since they're so closely tied together.

  This has several fixes for GNOME Shell 3.24's new Weather feature
  built-in to the clock menu. There are quite a few other bugfixes too.

  https://git.gnome.org/browse/gnome-shell/tree/NEWS?h=gnome-3-24
  https://git.gnome.org/browse/mutter/tree/NEWS?h=gnome-3-24

  https://git.gnome.org/browse/gnome-shell/log?h=gnome-3-24
  https://git.gnome.org/browse/mutter/log?h=gnome-3-24

  Test Case
  -
  In Ubuntu GNOME, install the update then reboot. Log in.

  Do the same with Ubuntu Budgie (or you can install budgie-desktop on
  top of Ubuntu GNOME and then log in to Budgie afterwards.)

  Regression Potential
  
  The biggest risk is that something in the update causes Budgie or GNOME Shell 
to no longer work. If GNOME Shell is broken, it could break gdm which is very 
bad for Ubuntu GNOME users.

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

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

[Desktop-packages] [Bug 1685288] [NEW] Unity freeze by hotkeysequence - be warned

2017-04-21 Thread Michael Kuster

Public bug reported:

Before trying this I suggest you to close all your important things!
After this test you can reach (with a bit of luck) the terminal by pressing 
Ctrl+Alt+F1 to reboot your System!

For me this affects Ubuntu 14.04.5 with the Unity Desktop...

The freezing hotkeysequence is:
Ctrl+Alt+F8
Ctrl+Alt+F1
Ctrl+Alt+F7 (returns to GUI, but now is freezed)

** Affects: at-spi2-core (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Unity freeze by hotkeysequence - be warned

Status in at-spi2-core package in Ubuntu:
  New

Bug description:
  Before trying this I suggest you to close all your important things!
  After this test you can reach (with a bit of luck) the terminal by pressing 
Ctrl+Alt+F1 to reboot your System!

  For me this affects Ubuntu 14.04.5 with the Unity Desktop...

  The freezing hotkeysequence is:
  Ctrl+Alt+F8
  Ctrl+Alt+F1
  Ctrl+Alt+F7 (returns to GUI, but now is freezed)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1685288/+subscriptions

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

[Desktop-packages] [Bug 1685271] Re: gnome-shell: corners are not rounded

** Also affects: light-themes (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Tags added: gnome-17.10

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

Title:
  gnome-shell: corners are not rounded

Status in light-themes package in Ubuntu:
  New
Status in light-themes source package in Artful:
  New

Bug description:
  Under gnome-shell apps have dark black squared top corners when they
  should be rounded.  See attached screenshot.

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

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

[Desktop-packages] [Bug 1685272] [NEW] gnome-shell: no window border

Public bug reported:

Under gnome-shell, there are no window borders.  See attached
screenshot.

** Affects: light-themes (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: light-themes (Ubuntu Artful)
 Importance: Undecided
 Status: New


** Tags: gnome-17.10

** Attachment added: "Ambiance_window_border.png"
   
https://bugs.launchpad.net/bugs/1685272/+attachment/4866061/+files/Ambiance_window_border.png

** Also affects: light-themes (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Tags added: gnome-17.10

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

Title:
  gnome-shell: no window border

Status in light-themes package in Ubuntu:
  New
Status in light-themes source package in Artful:
  New

Bug description:
  Under gnome-shell, there are no window borders.  See attached
  screenshot.

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

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

[Desktop-packages] [Bug 1685273] [NEW] gnome-shell: notebook tabs hard to distinguish

Public bug reported:

Under gnome-shell, it's difficult to distinguish which tab is focused.
See the attached screenshot.

** Affects: light-themes (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: light-themes (Ubuntu Artful)
 Importance: Undecided
 Status: New


** Tags: gnome-17.10

** Attachment added: "Ambiance_notebook_tab.png"
   
https://bugs.launchpad.net/bugs/1685273/+attachment/4866062/+files/Ambiance_notebook_tab.png

** Also affects: light-themes (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Tags added: gnome-17.10

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

Title:
  gnome-shell: notebook tabs hard to distinguish

Status in light-themes package in Ubuntu:
  New
Status in light-themes source package in Artful:
  New

Bug description:
  Under gnome-shell, it's difficult to distinguish which tab is focused.
  See the attached screenshot.

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

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

[Desktop-packages] [Bug 1685271] [NEW] gnome-shell: corners are not rounded

Public bug reported:

Under gnome-shell apps have dark black squared top corners when they
should be rounded.  See attached screenshot.

** Affects: light-themes (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Ambiance_corners.png"
   
https://bugs.launchpad.net/bugs/1685271/+attachment/4866060/+files/Ambiance_corners.png

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

Title:
  gnome-shell: corners are not rounded

Status in light-themes package in Ubuntu:
  New

Bug description:
  Under gnome-shell apps have dark black squared top corners when they
  should be rounded.  See attached screenshot.

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

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

[Desktop-packages] [Bug 1682238] Please test proposed package

Hello Jeremy, or anyone else affected,

Accepted mutter into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/3.24.1-0ubuntu1
in a few hours, and then in the -proposed repository.

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

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

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

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

Title:
  Update mutter and gnome-shell to 3.24.1

Status in gnome-desktop3 package in Ubuntu:
  In Progress
Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Zesty:
  Fix Committed

Bug description:
  Impact
  --
  3.24.1 is a new bugfix release in the stable 3.24 series. Although mutter and 
gnome-shell could be handled separately, it makes sense to handle them together 
since they're so closely tied together.

  This has several fixes for GNOME Shell 3.24's new Weather feature
  built-in to the clock menu. There are quite a few other bugfixes too.

  https://git.gnome.org/browse/gnome-shell/tree/NEWS?h=gnome-3-24
  https://git.gnome.org/browse/mutter/tree/NEWS?h=gnome-3-24

  https://git.gnome.org/browse/gnome-shell/log?h=gnome-3-24
  https://git.gnome.org/browse/mutter/log?h=gnome-3-24

  Test Case
  -
  In Ubuntu GNOME, install the update then reboot. Log in.

  Do the same with Ubuntu Budgie (or you can install budgie-desktop on
  top of Ubuntu GNOME and then log in to Budgie afterwards.)

  Regression Potential
  
  The biggest risk is that something in the update causes Budgie or GNOME Shell 
to no longer work. If GNOME Shell is broken, it could break gdm which is very 
bad for Ubuntu GNOME users.

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

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

[Desktop-packages] [Bug 1682238] Re: Update mutter and gnome-shell to 3.24.1

Hello Jeremy, or anyone else affected,

Accepted gnome-shell into zesty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.24.1-0ubuntu1 in a few hours, and then in the -proposed
repository.

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

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

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

** Tags added: verification-needed

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

** Changed in: mutter (Ubuntu Zesty)
   Status: New => Fix Committed

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

Title:
  Update mutter and gnome-shell to 3.24.1

Status in gnome-desktop3 package in Ubuntu:
  In Progress
Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Zesty:
  Fix Committed

Bug description:
  Impact
  --
  3.24.1 is a new bugfix release in the stable 3.24 series. Although mutter and 
gnome-shell could be handled separately, it makes sense to handle them together 
since they're so closely tied together.

  This has several fixes for GNOME Shell 3.24's new Weather feature
  built-in to the clock menu. There are quite a few other bugfixes too.

  https://git.gnome.org/browse/gnome-shell/tree/NEWS?h=gnome-3-24
  https://git.gnome.org/browse/mutter/tree/NEWS?h=gnome-3-24

  https://git.gnome.org/browse/gnome-shell/log?h=gnome-3-24
  https://git.gnome.org/browse/mutter/log?h=gnome-3-24

  Test Case
  -
  In Ubuntu GNOME, install the update then reboot. Log in.

  Do the same with Ubuntu Budgie (or you can install budgie-desktop on
  top of Ubuntu GNOME and then log in to Budgie afterwards.)

  Regression Potential
  
  The biggest risk is that something in the update causes Budgie or GNOME Shell 
to no longer work. If GNOME Shell is broken, it could break gdm which is very 
bad for Ubuntu GNOME users.

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

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

[Desktop-packages] [Bug 1682236] Re: Update gnome-desktop3 to 3.24.1

Hello Jeremy, or anyone else affected,

Accepted gnome-desktop3 into zesty-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
desktop3/3.24.1-0ubuntu1 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Tags added: verification-needed

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

Title:
  Update gnome-desktop3 to 3.24.1

Status in gnome-desktop3 package in Ubuntu:
  In Progress
Status in gnome-desktop3 source package in Zesty:
  Fix Committed

Bug description:
  Impact
  --
  Since we do our own translations, the only impact is that some tools use the 
version reported by this package as the version of GNOME. Since we're updating 
most of the other GNOME packages to 3.24.1, it's appropriate to do this one too.

  Test Case
  -
  Install gnome-recipes (this version is a very large download; it will be a 
smaller download in 17.10)
  Open the Recipes app. In the top bar, click the Recipes app menu and select 
About.
  Switch to the System tab. The Desktop should say "GNOME 3.24.1".

  Regression Potential
  
  There shouldn't really be a regression here. Two languages got translation 
updates but those aren't really used.

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

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

[Desktop-packages] [Bug 1682913] Re: Missing libgles1 in Ubuntu 17.04 repos triggers issues with some games

2017-04-21 Thread Brice Terzaghi

Just made another test: I installed Steam and Faeria on my old laptop
which has a nVidia GPU. I haven't installed the proprietary driver yet,
so I'm on Mesa with Nouveau. Faeria works. I haven't tried Payday 2, as
the required config is far too high for this PC.

Specs:
- desktop: Ubuntu MATE 17.04 with AMD RadeonHD 7770 GPU and Mesa 17.0.4 from
Padoka's PPA
- laptop: Ubuntu GNOME 17.04 with nVidia 8400M GS GPU and Mesa 17.0.3 from the
Ubuntu repos

So, I'm even more confused than before. What could explain that some
games are broken without libgles1 on my desktop and work fine on my
laptop?

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

Title:
Missing libgles1 in Ubuntu 17.04 repos triggers issues with some games

Status in mesa package in Ubuntu:
Won't Fix

Bug description:
I've just upgraded Ubuntu from 16.10 to 17.04. Afterwards, I noticed
graphical issues in some games, that render partially black. E.g.:
- menu of Payday 2:
https://steamuserimages-a.akamaihd.net/ugc/156906385546364727/C1182DAE4DA1A6CB638A2D42FA33541629F2/
- menu of Faeria:
https://steamuserimages-a.akamaihd.net/ugc/156906385546272628/52E8E6F366A54299597774C22D78771EA0F074ED/

I've traced the issue to a missing lib, libgles1, which for some
reason has been removed from the 17.04 repos, as using Oibaf's PPA and
manually installing the lib from it fixes the issues on these games.

So, please build a version for Mesa 17.0.3 and put it in the repos,
it's needed by some games.

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

[Desktop-packages] [Bug 1683898] Re: Compose key can't be set in Settings>Keyboard with GNOME 3.24

2017-04-21 Thread Armin Grodon

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

** Also affects: gnome-user-docs via
   https://bugzilla.gnome.org/show_bug.cgi?id=781593
   Importance: Unknown
   Status: Unknown

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

Title:
  Compose key can't be set in Settings>Keyboard with GNOME 3.24

Status in gnome-control-center:
  Confirmed
Status in Gnome Documentation:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-user-docs package in Ubuntu:
  Confirmed

Bug description:
  The changes implemented with https://bugs.launchpad.net/ubuntu/+source
  /ubuntu-docs/+bug/1624778 in https://help.gnome.org/users/gnome-
  help/stable/tips-specialchars.html.en#compose do not reflect the
  current settings dialog for Ubuntu-Gnome 17.04.

  Going from "All Settings" to "Keyboard" switches to "Keyboard Shortcuts" 
immediately.
  The new "Keyboard Shortcuts" dialog does not seem to contain settings for 
'compose key' (the group "Typing" only contains "Switch to {next,previous} 
input source").

  PS: In the meantime, where do I find the settings for 'compose key' in
  Ubuntu-Gnome 17.04? :(

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

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

[Desktop-packages] [Bug 1682132] Re: Update gnome-settings-daemon to 3.24.1

Hello Jeremy, or anyone else affected,

Accepted gnome-settings-daemon into zesty-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-settings-daemon/3.24.1-0ubuntu1 in a few hours, and then in the
-proposed repository.

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

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

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

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

** Tags added: verification-needed

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

Title:
  Update gnome-settings-daemon to 3.24.1

Status in gnome-settings-daemon package in Ubuntu:
  In Progress
Status in gnome-settings-daemon source package in Zesty:
  Fix Committed

Bug description:
  Impact
  --
  gnome-settings-daemon 3.24.1 is a bugfix release in the stable 3.24 series.

  https://git.gnome.org/browse/gnome-settings-daemon/log?h=gnome-3-24
  https://git.gnome.org/browse/gnome-settings-daemon/tree/NEWS?h=gnome-3-24
  https://git.gnome.org/browse/libgnome-volume-control/commit/?id=d52194f
  https://git.gnome.org/browse/libgnome-volume-control/commit/?id=ce8e488

  gnome-settings-daemon itself is used by Ubuntu Budgie and Ubuntu GNOME.
  The schemas are also used by Ubuntu, Ubuntu Kylin and Ubuntu MATE. And Ubuntu 
Touch.

  Test Case
  -
  After installing the update, reboot and log into GNOME

  Regression Potential
  
  The changes look like minimal bugfixes. Affected are Bluetooth audio, GNOME's 
Night Light feature, and the clipboard. Schemas shouldn't be affected in this 
update.

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

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

[Desktop-packages] [Bug 1407712] Re: Add option to disable /var/lib/lightdm-data/ directories

2017-04-21 Thread Michael Terry

** Changed in: lightdm
 Assignee: Michael Terry (mterry) => (unassigned)

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

Title:
  Add option to disable /var/lib/lightdm-data/ directories

Status in Light Display Manager:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  There is no way to disable the creation of directories under /var/lib
  /lightdm-data/ for users.

  In environments where[, there is a single user and] all the user's
  data should be controlled under solely /home directories, this is
  undesirable.

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

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

[Desktop-packages] [Bug 1682913] Re: Missing libgles1 in Ubuntu 17.04 repos triggers issues with some games

2017-04-21 Thread Brice Terzaghi

After adding Oibaf's (Mesa devel 17.1.x) and/or Padoka's (Mesa stable
17.0.4) PPA, I still had to manually install libgles1-mesa (which they
package) to fix the issues in both games.

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

Title:
  Missing libgles1 in Ubuntu 17.04 repos triggers issues with some games

Status in mesa package in Ubuntu:
  Won't Fix

Bug description:
  I've just upgraded Ubuntu from 16.10 to 17.04. Afterwards, I noticed 
graphical issues in some games, that render partially black. E.g.:
  - menu of Payday 2: 
https://steamuserimages-a.akamaihd.net/ugc/156906385546364727/C1182DAE4DA1A6CB638A2D42FA33541629F2/
  - menu of Faeria: 
https://steamuserimages-a.akamaihd.net/ugc/156906385546272628/52E8E6F366A54299597774C22D78771EA0F074ED/

  I've traced the issue to a missing lib, libgles1, which for some
  reason has been removed from the 17.04 repos, as using Oibaf's PPA and
  manually installing the lib from it fixes the issues on these games.

  So, please build a version for Mesa 17.0.3 and put it in the repos,
  it's needed by some games.

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

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

[Desktop-packages] [Bug 1614233] Re: timezone search causing autopilot failures

2017-04-21 Thread Michael Terry

** Changed in: geonames (Ubuntu)
 Assignee: Michael Terry (mterry) => (unassigned)

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

Title:
  timezone search causing autopilot failures

Status in geonames package in Ubuntu:
  In Progress

Bug description:
  Our autopilot tests are failing from the datetime panel.  The tests
  use "London, United Kingdom" as a string to search, which returns no
  matches.  If you type this manually, the suggestions are correct until
  after entering the comma.

  A more obvious example of the issue is searching for "San Antonio,
  Texas".  As you're typing the "San Antonio, Texas" is the top result,
  once you enter the ", " all the suggestions are cleared except "San
  Antonio, Tecomitl, Mexico City, Mexico".  This makes it impossible to
  select Texas.

  It works fine as long as you pick a result from the selection before
  the results change, however it's impossible to select very specific
  searches.

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

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

[Desktop-packages] [Bug 1281588] Re: Disk standby timer is broken

2017-04-21 Thread Paul Cullum

This behaviour still seems to be present in 17.04. I have a secondary
drive (ST3500418AS) that is isn't mounted and should remain asleep. It
doesn't go to sleep unless I force it with "hdparm -Y /dev/sdb". There
is something that happens every 10 minutes that will wake up the drive.

I think there is something wrong with libatasmart because just checking
the state seems to change the state (Heisenberg?). Running "hdparm -C
/dev/sdb" will actually wake the drive up.

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

Title:
  Disk standby timer is broken

Status in udisks:
  Fix Released
Status in udisks2 package in Ubuntu:
  Fix Released
Status in udisks2 source package in Trusty:
  Confirmed

Bug description:
  udisks' / gnome-disk-utility's support for the drive standby timer is
  broken.  If the standby timer is set to at least 10 minutes ( which is
  the minimum on many drives ), every 10 minutes udisks tries to update
  the smart status of the drive, which resets the standby timer.

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

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

[Desktop-packages] [Bug 1683170] Re: No permission to write files on storage device

2017-04-21 Thread Phillip Susi

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks! 

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

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

Title:
  No permission to write files on storage device

Status in udisks2 package in Ubuntu:
  Incomplete

Bug description:
  It is always the same problem. It affects Ubuntu 16 and 17. I can not
  write anything on my pendrive one I have formatted with Ubuntu. I
  already tryed all the solutions in the comments of this question.

  https://askubuntu.com/questions/905303/all-my-pendrives-in-read-only-
  mode?noredirect=1#comment1421136_905303

  Don't know what to do. Writing files in your pendrive should be
  somethinh user friendly... :(

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udisks2 2.1.7-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  CustomUdevRuleFiles: 60-vboxdrv.rules
  Date: Sun Apr 16 15:10:31 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-02 (349 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Hewlett-Packard HP Pavilion dm4 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic 
root=UUID=f79a4aad-8806-4e03-aee3-7abd5990a847 ro quiet splash vt.handoff=7
  SourcePackage: udisks2
  Symptom: storage
  Title: No permission to access files on storage device
  UpgradeStatus: Upgraded to xenial on 2016-09-24 (203 days ago)
  dmi.bios.date: 11/10/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.05
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1793
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 41.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.05:bd11/10/2011:svnHewlett-Packard:pnHPPaviliondm4NotebookPC:pvr069410001120401623100:rvnHewlett-Packard:rn1793:rvr41.19:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dm4 Notebook PC
  dmi.product.version: 069410001120401623100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1672465] Re: Onboard doesn't work in Wayland

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

** Tags added: wayland

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

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

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

Title:
  Onboard doesn't work in Wayland

Status in Onboard:
  Confirmed
Status in onboard package in Ubuntu:
  Confirmed

Bug description:
  Onboard 1.4.1 on Ubuntu GNOME 17.04

  Onboard at least shows the keyboard now in GNOME on Wayland. But it
  doesn't send key presses to gedit or other native Wayland apps.

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

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

[Desktop-packages] [Bug 1640970] Re: 16.10: VPN Connections -> Configure VPN grayed out

2017-04-21 Thread jaybo

So is this issue (Configure VPN grayed out and the "Disconnect
VPN")considered a bug or a planned change?  Or maybe an unplanned change
that has a very low priority to correct?

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

Title:
  16.10: VPN Connections -> Configure VPN grayed out

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10, in the nm applet menu, VPN
  Connections -> Configure VPN is grayed out.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov 10 16:04:49 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-04-04 (951 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  IpRoute:
   default via 172.28.77.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   172.28.77.0/24 dev wlan0  proto kernel  scope link  src 172.28.77.23  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2016-11-07 (3 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2016-03-07T11:36:55.286063
  nmcli-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   wlan0   wifi  connected /org/freedesktop/NetworkManager/Devices/0  
BlueCedar-GUEST  f7b79954-9427-47eb-adba-875b5b152f37  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   eth0ethernet  disconnected  /org/freedesktop/NetworkManager/Devices/1  
--   ----   
  
   lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/2  
--   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1685035] Re: GDM login doesn't scale on Hi-DPI display

2017-04-21 Thread Bug Watch Updater

** Changed in: gnome-settings-daemon
   Status: Unknown => Confirmed

** Changed in: gnome-settings-daemon
   Importance: Unknown => Medium

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

Title:
  GDM login doesn't scale on Hi-DPI display

Status in gnome-settings-daemon:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gnome-settings-daemon package in Ubuntu:
  Triaged

Bug description:
  Ubuntu gnome 17.04, gnome 3.24. On high resolution display, 3200x1800,
  login screen is too tiny to read. GDM login screen doesn't reflect
  changes to org.gnome.desktop.interface scaling-factor or text-scaling-
  factor.

  Eg:
  xhost +SI:localuser:gdm
  sudo su gdm -s /bin/bash
  gsettings set org.gnome.desktop.interface scaling-factor 2
  gsettings set org.gnome.desktop.interface text-scaling-factor 2.0

  no effect.

  Creating a gdm user under /etc/dconf and running dconf update has no
  effect either. Scaling-factor seems to scale the mouse cursor, but
  nothing else.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1685035/+subscriptions

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

[Desktop-packages] [Bug 1675892] Re: pulseaudio crashed with SIGABRT

pulseaudio keeps crashing for me too on Zesty, maybe about once a day.
It didn't happen in earlier releases.

When it crashes, volume controls (Fn+F2/F3 hotkeys on my laptop, and in
Unity's upper panel) no longer work. Manually launching "pulseaudio
--start" fixes the Unity panel's control, but does not fix the more
convenient keyboard shortcuts. Logging out and back in fixes everything.

Seems to me that existing Firefox processes (or tabs? not sure) can
still play sound when there's no pulseaudio running (no clue how), but
newly opened ones cannot.

Let me know if there's anything I can help.

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

Title:
  pulseaudio crashed with SIGABRT

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  A random pulseaudio crash

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  Uname: Linux 4.10.4-041004-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   1902 F pulseaudio
  CurrentDesktop: MATE
  Date: Thu Mar 23 07:51:00 2017
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  Stacktrace:
   #0  
   No locals.
   #1  0x in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x0
  StacktraceTop: ?? ()
  Title: pulseaudio crashed with SIGABRT
  UpgradeStatus: Upgraded to zesty on 2017-03-12 (12 days ago)
  UserGroups: adm admin cdrom dialout lpadmin lxd plugdev sambashare staff
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: HM77-HT
  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.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT: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/pulseaudio/+bug/1675892/+subscriptions

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

[Desktop-packages] [Bug 1675892] Re: pulseaudio crashed with SIGABRT

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

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

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

Title:
  pulseaudio crashed with SIGABRT

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  A random pulseaudio crash

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  Uname: Linux 4.10.4-041004-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   1902 F pulseaudio
  CurrentDesktop: MATE
  Date: Thu Mar 23 07:51:00 2017
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  Stacktrace:
   #0  
   No locals.
   #1  0x in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x0
  StacktraceTop: ?? ()
  Title: pulseaudio crashed with SIGABRT
  UpgradeStatus: Upgraded to zesty on 2017-03-12 (12 days ago)
  UserGroups: adm admin cdrom dialout lpadmin lxd plugdev sambashare staff
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: HM77-HT
  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.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT: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/pulseaudio/+bug/1675892/+subscriptions

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

[Desktop-packages] [Bug 1684401] Re: There is no sound on my laptop asus today. Yesterday I had sound!

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

This is sure not a gnome-terminal bug. Redirecting to hopefully the
right one.

** This bug has been marked a duplicate of bug 1675892
   pulseaudio crashed with SIGABRT

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

Title:
  There is no sound on my laptop asus today. Yesterday I had sound!

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  There is no sound on my laptop asus today. Yesterday I had sound!

  Ubumtu 17.04

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-terminal 3.20.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Apr 20 09:14:03 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2016-11-07 (164 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  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-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1684280] Re: Running espeak with mbrola voices results in error

2017-04-21 Thread Paul Gevers

For what it is worth it, I can't reproduce this in Debian Stretch,
neither with espeak, nor with espeak-ng.

paul@testavoira ~ $ /usr/bin/espeak -v mb-us3 "Hello world"
paul@testavoira ~ $ /usr/bin/espeak-ng -v mb-us3 "Hello world"
paul@testavoira ~ $

Note, espeak-ng doesn't actually speak the words, I'll file a bug about
that.

And shouldn't this bug be assigned to mbrola? The error is:
*** Error in `mbrola': free(): invalid pointer: 0x09472da0 ***

Paul

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

Title:
  Running espeak with mbrola voices results in error

Status in espeak package in Ubuntu:
  New

Bug description:
  1. RELEASE

  amy@ThinkPad-T510:~$ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  2. PACKAGE INFO

  amy@ThinkPad-T510:~$ apt-cache policy espeak
  espeak:
Installed: 1.48.04+dfsg-2
Candidate: 1.48.04+dfsg-2
Version table:
   *** 1.48.04+dfsg-2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  amy@ThinkPad-T510:~$ apt-cache policy mbrola
  mbrola:
Installed: 3.01h+1-3
Candidate: 3.01h+1-3
Version table:
   *** 3.01h+1-3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/multiverse amd64 
Packages
  100 /var/lib/dpkg/status
  amy@ThinkPad-T510:~$ apt-cache policy mbrola-us1
  mbrola-us1:
Installed: 0.3-2
Candidate: 0.3-2
Version table:
   *** 0.3-2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/multiverse amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu xenial/multiverse i386 
Packages
  100 /var/lib/dpkg/status
  amy@ThinkPad-T510:~$ apt-cache policy mbrola-us2
  mbrola-us2:
Installed: 0.1-2
Candidate: 0.1-2
Version table:
   *** 0.1-2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/multiverse amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu xenial/multiverse i386 
Packages
  100 /var/lib/dpkg/status
  amy@ThinkPad-T510:~$ apt-cache policy mbrola-us3
  mbrola-us3:
Installed: 0.1-1
Candidate: 0.1-1
Version table:
   *** 0.1-1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/multiverse amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu xenial/multiverse i386 
Packages
  100 /var/lib/dpkg/status

  
  3. EXPECTED

  When running `espeak -v mb-us3 "Hello world"`, expected espeak to
  speak "Hello world" using designated mbrola voice without error.

  4. ACTUAL

  When running `espeak -v mb-us3 "Hello world"`, espeak speaks "Hello
  world" using designated mbrola voice, but terminal reports memory leak
  stacktrace. See below:

  
  amy@ThinkPad-T510:/usr/share/mbrola/voices$ espeak -v mb-us3 "Hello world"
  *** Error in `mbrola': free(): invalid pointer: 0x09472da0 ***
  === Backtrace: =
  /lib/i386-linux-gnu/libc.so.6(+0x67377)[0xf753b377]
  /lib/i386-linux-gnu/libc.so.6(+0x6d2f7)[0xf75412f7]
  /lib/i386-linux-gnu/libc.so.6(+0x6dbb1)[0xf7541bb1]
  /lib/i386-linux-gnu/libc.so.6(_IO_wsetb+0x69)[0xf75360e9]
  /lib/i386-linux-gnu/libc.so.6(+0x6bc02)[0xf753fc02]
  /lib/i386-linux-gnu/libc.so.6(+0x2e93a)[0xf750293a]
  /lib/i386-linux-gnu/libc.so.6(+0x2e9ef)[0xf75029ef]
  mbrola(free+0x60)[0x8048c0c]
  === Memory map: 
  08048000-0805 r-xp  08:01 23465356   
/usr/bin/mbrola
  0805-08051000 rwxp 7000 08:01 23465356   
/usr/bin/mbrola
  09437000-09479000 rwxp  00:00 0  
[heap]
  f730-f7321000 rwxp  00:00 0 
  f7321000-f740 ---p  00:00 0 
  f74d3000-f74d4000 rwxp  00:00 0 
  f74d4000-f7683000 r-xp  08:01 28321694   
/lib/i386-linux-gnu/libc-2.23.so
  f7683000-f7684000 ---p 001af000 08:01 28321694   
/lib/i386-linux-gnu/libc-2.23.so
  f7684000-f7686000 r-xp 001af000 08:01 28321694   
/lib/i386-linux-gnu/libc-2.23.so
  f7686000-f7687000 rwxp 001b1000 08:01 28321694   
/lib/i386-linux-gnu/libc-2.23.so
  f7687000-f768a000 rwxp  00:00 0 
  f768a000-f76dd000 r-xp  08:01 28321686   
/lib/i386-linux-gnu/libm-2.23.so
  f76dd000-f76de000 r-xp 00052000 08:01 28321686   
/lib/i386-linux-gnu/libm-2.23.so
  f76de000-f76df000 rwxp 00053000 08:01 28321686   
/lib/i386-linux-gnu/libm-2.23.so
  f76e9000-f7705000 r-xp  08:01 28319113   
/lib/i386-linux-gnu/libgcc_s.so.1
  f7705000-f7706000 rwxp 0001b000 08:01 28319113   
/lib/i386-linux-gnu/libgcc_s.so.1
  f7706000-f7709000 rwxp  00:00 0 
  f7709000-f770b000 r--p  00:00 0  
[vvar]
  f770b000-f770c000 r-xp  00:

[Desktop-packages] [Bug 1684854] Re: The default behaviour for search domains changed from 16.10 to 17.04

2017-04-21 Thread ThyMythos

I did some more tests. Using "dns-search=my.domain" and "ignore-auto-
dns=true" actually works for wifi connections. For VPN (vpnc) is does
not work.

The tool "systemd-resolve --status" still shows a tilda before the
domain name ("DNS Domain: ~my.domain" instead of "DNS Domain:
my.domain") and the name lookup for computers in my.domain does not work
without giving the FQDN.

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

Title:
  The default behaviour for search domains changed from 16.10 to 17.04

Status in network-manager package in Ubuntu:
  New

Bug description:
  Since Ubuntu 17.04 uses systemd-resolved for DNS lookups the default
  behaviour for search domains changed. By default systemd-resolved does
  not use the domain supplied by DHCP as a search domain.

  So network-manager should at least have an option to tell systemd-
  networkd to change it's behaviour. In systemd-networkd the
  corresponding option is named "UseDomains".

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

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

[Desktop-packages] [Bug 1590844] Re: Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition]

2017-04-21 Thread Alexandre Payet

Hello Stephan,

Is there a simple / not risky way to update the kernel on ubuntu ? 
Alexandre,

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

Title:
  Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition]

Status in Canonical System Image:
  Confirmed
Status in turbo:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  My bluetooth headset perfectly connects to my Meizu Pro 5. However,
  the sound quality is so poor (a lot of noise) such that you don't
  understand your communication partner. Note that the headset works
  perfectly together with Ubuntu on my Nexus 4.

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

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

[Desktop-packages] [Bug 120971] Re: what do you think?

2017-04-21 Thread Bartolomeo Nicolotti

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

Greetings,


Do you know what I've just found on the internet? You're going to be  
surprised, just check it  out here http://www.musorkalauz.hu/challenge.php?e1e3

Bartolomeo Nicolotti

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

Title:
  [EDGY] firefox crashed [@nsTextControlFrame::SetValue]
  [@nsTextControlFrame::SetProperty]
  [@nsHTMLInputElement::SetValueInternal]

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: firefox

  ... Crash during firefox use

  
  Following a link firefox crashed

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

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

[Desktop-packages] [Bug 1685035] Re: GDM login doesn't scale on Hi-DPI display

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

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

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

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

** Also affects: ubuntu-gnome
   Importance: Undecided
   Status: New

** Changed in: ubuntu-gnome
   Importance: Undecided => Medium

** Changed in: ubuntu-gnome
   Status: New => Triaged

** Package changed: gdm3 (Ubuntu) => gnome-settings-daemon (Ubuntu)

** Project changed: gdm => gnome-settings-daemon

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

Title:
  GDM login doesn't scale on Hi-DPI display

Status in gnome-settings-daemon:
  Unknown
Status in Ubuntu GNOME:
  Triaged
Status in gnome-settings-daemon package in Ubuntu:
  Triaged

Bug description:
  Ubuntu gnome 17.04, gnome 3.24. On high resolution display, 3200x1800,
  login screen is too tiny to read. GDM login screen doesn't reflect
  changes to org.gnome.desktop.interface scaling-factor or text-scaling-
  factor.

  Eg:
  xhost +SI:localuser:gdm
  sudo su gdm -s /bin/bash
  gsettings set org.gnome.desktop.interface scaling-factor 2
  gsettings set org.gnome.desktop.interface text-scaling-factor 2.0

  no effect.

  Creating a gdm user under /etc/dconf and running dconf update has no
  effect either. Scaling-factor seems to scale the mouse cursor, but
  nothing else.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1685035/+subscriptions

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

[Desktop-packages] [Bug 1241986] Re: Cannot connect to WPA/WPA2, EAP-PEAP, MSCHAPV2 network

2017-04-21 Thread Merlijn Sebrechts

This was fixed a long time ago

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

** Changed in: network-manager (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: indicator-network (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Cannot connect to WPA/WPA2, EAP-PEAP, MSCHAPV2 network

Status in Canonical System Image:
  Fix Released
Status in indicator-network package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  On Ubuntu for Phones final image on mako I can see a network but
  cannot connect because I never get prompted for the username/password.

  :
  "In both the ‘Connect to “{network name}”’ and “Connect to Hidden
  Network” dialogs, the contents of the dialog, and the behavior of the
  “Connect” button, should vary depending on the security and
  authentication methods..."

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

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

[Desktop-packages] [Bug 1685035] [NEW] GDM login doesn't scale on Hi-DPI display

You have been subscribed to a public bug:

Ubuntu gnome 17.04, gnome 3.24. On high resolution display, 3200x1800,
login screen is too tiny to read. GDM login screen doesn't reflect
changes to org.gnome.desktop.interface scaling-factor or text-scaling-
factor.

Eg:
xhost +SI:localuser:gdm
sudo su gdm -s /bin/bash
gsettings set org.gnome.desktop.interface scaling-factor 2
gsettings set org.gnome.desktop.interface text-scaling-factor 2.0

no effect.

Creating a gdm user under /etc/dconf and running dconf update has no
effect either. Scaling-factor seems to scale the mouse cursor, but
nothing else.

** Affects: gdm
 Importance: Unknown
 Status: Unknown

** Affects: ubuntu-gnome
 Importance: Medium
 Status: Triaged

** Affects: gnome-settings-daemon (Ubuntu)
 Importance: Medium
 Status: Triaged

-- 
GDM login doesn't scale on Hi-DPI display
https://bugs.launchpad.net/bugs/1685035
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-settings-daemon 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 1683162] Re: Nautilus: Double click on folder is not working in list view with touchscreen

thanks

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

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

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

Title:
  Nautilus: Double click on folder is not working in list view with
  touchscreen

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

Bug description:
  I have a similar problem to one with touchpad.
  https://bugzilla.gnome.org/show_bug.cgi?id=748501

  I have mouse, touchpad and touchscreen.
  I can always do double click on folder to enter it with mouse and with 
touchpad.
  But I can't enter into folder with double click with touchscreen whem 
nautilus is in list view.
  I can do it in icon view.

  My laptop is Dell Latitude 7350, and when I'm detaching screen,
  touchscreen is my only pointing device. It is annoying because I like
  list view, and I don't like icons view.

  Please, help.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Apr 16 18:21:54 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-28 (170 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=pl_PL.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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

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

[Desktop-packages] [Bug 1684967] Re: [17.04 ]network-connection-editor won't edit old wifi entries

2017-04-21 Thread flux242

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

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

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

Title:
  [17.04 ]network-connection-editor won't edit old wifi entries

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

Bug description:
  after upgrading to 17.04 from 16.10 I cannot save changes I make in
  the wi-fi settings because the save button is greyed out. If I create
  a new wi-fi entry then it works but it doesn't for all my old wi-fi
  entries. Changing the settings is only possible using 'nm-cli con
  modify'

  And for all my old vpn entries the passwords aren't show at all. They
  are present because I can connect to a vpn server but the password
  isn't shown in the text field

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

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

[Desktop-packages] [Bug 1610944] Re: GNOME Online Accounts breaks if you log out (until you reboot)

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

** Changed in: gnome-online-accounts
   Importance: Critical => Unknown

** Changed in: gnome-online-accounts
   Status: Confirmed => Unknown

** Changed in: gnome-online-accounts
 Remote watch: GNOME Bug Tracker #781564 => GNOME Bug Tracker #764029

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

Title:
  GNOME Online Accounts breaks if you log out (until you reboot)

Status in gnome-online-accounts:
  Unknown
Status in Ubuntu GNOME:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  Can't add any online accounts in after opened Online accounts + mark is 
faded, can't click.
  After reinstalled gnome-online-accounts still has same problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-online-accounts 3.20.3-1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Mon Aug  8 15:33:45 2016
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1610944/+subscriptions

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

[Desktop-packages] [Bug 1685184] [NEW] /usr/sbin/cups-browsed:11:__strcasecmp_l_avx:generate_local_queue:resolve_callback:avahi_service_resolver_event:filter_func

2017-04-21 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
cups-filters.  This problem was most recently seen with package version 
1.13.4-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/6f2469dfbcaa527d85b5c05039957e377260d457 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

** Affects: cups-filters (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: xenial yakkety zesty

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

Title:
  /usr/sbin/cups-
  
browsed:11:__strcasecmp_l_avx:generate_local_queue:resolve_callback:avahi_service_resolver_event:filter_func

Status in cups-filters package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1677198] Re: OpenVPN not Working in 17.04 via "Import a saved VPN configuration"

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: network-manager-openvpn (Ubuntu)
   Importance: Undecided => High

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

Title:
  OpenVPN not Working in 17.04 via "Import a saved VPN configuration"

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

Bug description:
  I can definitely confirm that Network Manager's OpenVPN is not working
  yet in Ubuntu 17.04.

  I set up my configuration via import:
  http://neartalk.com/ss/2017-03-29_001_633x332.png

  On all earlier versions of Ubuntu, after importing the configuration,
  I'm able to connect to the VPN. However, in 17.04, connection attempts
  always give this error immediately:

  "The VPN Connection disconnected because the VPN Service has stopped"

  Clearly the VPN Service has NOT stopped. I've confirmed that this
  error is false by taking the exact same import-file and I imported it
  into an Ubuntu 16.04 computer and then the VPN connected without
  issue. Also, with this same import-file I've had no issues in Ubuntu
  16.10.

  So I've thoroughly confirmed that there is no issue with the VPN
  service. The issue is with the client in Ubuntu 17.04.

  I cannot upgrade to 17.04 until this is fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager-openvpn-gnome 1.2.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Mar 29 05:25:14 2017
  InstallationDate: Installed on 2017-01-30 (58 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: Upgraded to zesty on 2017-03-27 (2 days ago)

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

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

[Desktop-packages] [Bug 1685182] [NEW] /usr/sbin/cups-browsed:11:__strcasecmp_l_avx:browse_callback:avahi_service_browser_event:filter_func:dbus_connection_dispatch

2017-04-21 Thread errors.ubuntu.com bug bridge

Public bug reported:

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

** Affects: cups-filters (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: wily xenial yakkety zesty

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

Title:
  /usr/sbin/cups-
  
browsed:11:__strcasecmp_l_avx:browse_callback:avahi_service_browser_event:filter_func:dbus_connection_dispatch

Status in cups-filters package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1685178] Re: /usr/bin/gnome-software:11:as_format_get_kind:as_store_add_app:as_store_load_yaml_file:as_store_from_file_internal:as_store_watch_source_added

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

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

Title:
  /usr/bin/gnome-
  
software:11:as_format_get_kind:as_store_add_app:as_store_load_yaml_file:as_store_from_file_internal:as_store_watch_source_added

Status in gnome-software package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1685178] [NEW] /usr/bin/gnome-software:11:as_format_get_kind:as_store_add_app:as_store_load_yaml_file:as_store_from_file_internal:as_store_watch_source_added

2017-04-21 Thread errors.ubuntu.com bug bridge

Public bug reported:

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

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


** Tags: zesty

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

Title:
  /usr/bin/gnome-
  
software:11:as_format_get_kind:as_store_add_app:as_store_load_yaml_file:as_store_from_file_internal:as_store_watch_source_added

Status in gnome-software package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1681228] Re: LightDM Unityt-Gretter is wrong resolution

Thank you for your bug report, your screen is hidpi so the scaling is
normal, is that your issue, would you prefer to have tiny UI elements?

** Package changed: lightdm (Ubuntu) => unity-greeter (Ubuntu)

** Changed in: unity-greeter (Ubuntu)
   Importance: Undecided => Low

** Changed in: unity-greeter (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  LightDM Unityt-Gretter is wrong resolution

Status in unity-greeter package in Ubuntu:
  Incomplete

Bug description:
  Running on a macbook pro 15" at 2880 x 1800.

  At 16.04 the greeter starts at the correct resolution and then after a
  couple of secs changes to what looks like 2X scaling.

  I updated to 16.10 and now the greeter boots directly into the 2z
  scaling.

  It almost seems like the bug was fixed backwards.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.5-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr  9 10:27:54 2017
  InstallationDate: Installed on 2017-04-01 (8 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to yakkety on 2017-04-07 (2 days ago)

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

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

[Desktop-packages] [Bug 1633874] Re: VPN - "Additional DNS servers" Settings are being Ignored

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.

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

Title:
  VPN - "Additional DNS servers" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify additional DNS servers that are located on the virtual private
  network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  additional DNS that I've specified at the dialog I've linked above.

  Normally, after connecting to a VPN (where additional DNS servers are
  specified), the command (below) will show (in addition to your local
  DNS servers) the remote DNS servers (located on the VPN):

  nmcli dev show | grep DNS

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name, which is very
  inconvenient considering that I have over 100 Remmina connections set
  to resolve by name. Right now, I have to manually discover the IP
  addresses of the remote computer-names before connecting to the
  computers with Remmina.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional DNS server are not making it here:

  nmcli dev show | grep DNS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 09:31:31 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1633877] Re: VPN - "Additional Search Domains" Settings are being Ignored

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.

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

Title:
  VPN - "Additional Search Domains" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify "additional Search Domains" that are located on the virtual
  private network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  "additional Search Domains" that I've specified at the dialog I've
  linked above.

  Normally, after connecting to a VPN (where additional Search Domains
  are specified), the command (below) will show (in addition to your
  local Search Domains) the remote Search Domains (located on the VPN):

  nmcli dev show | grep DOMAIN

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name because the
  "Search Domains" I've specified are not getting appended to the
  computer-names I'm pinging.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional Search Domains are not making it here:

  nmcli dev show | grep DOMAIN

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 10:16:04 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW   
WIFI  WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled disabled  
disabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1684774] Re: the app won't start via GUI at all, only via command line. also it crashes at random very often

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-calendar (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  the app won't start via GUI at all, only via command line. also it
  crashes at random very often

Status in gnome-calendar package in Ubuntu:
  Incomplete

Bug description:
  the app won't start via GUI at all, only via command line. 
  also it crashes at random very often.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-calendar 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr 20 16:33:04 2017
  InstallationDate: Installed on 2017-04-13 (6 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1684967] Re: [17.04 ]network-connection-editor won't edit old wifi entries