[Desktop-packages] [Bug 1728143] Re: Screen freezes after waking from suspend with Gnome on Wayland

2017-10-31 Thread Nicholas Stommel
Okay, I will try this with a fresh install of Ubuntu 17.10 and provide
the necessary logs soon. I should be able to use the provided script
over ssh, thanks. The problem with GDM freezing on Wayland after system
resume/wakeup has been occurring ever since I ran the beta builds of
17.10, but it's clearly not fixed. I've been relatively busy lately, my
apologies.

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

Title:
  Screen freezes after waking from suspend with Gnome on Wayland

Status in gdm package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  It appears that using Xorg instead of Wayland is the only way to fix
  this problem on Ubuntu 17.10. For some odd reason, whenever I wake my
  computer from suspend (especially after an extended period of time
  asleep) using Gnome in a Wayland session (gnome-session and stock
  ubuntu-session alike), my screen freezes completely on whatever was
  last there before suspending and I can't get any IO response at all.
  Nothing, the screen is totally frozen. I am also unable to exit into a
  recovery shell or kill GDM or gnome-session/ubuntu-session locally. I
  also can't seem to find any traces or indications for the freeze in
  the syslog, or maybe I'm just not sure where to look. I believe this
  is a problem with GDM on Wayland, not kernel related, as it happens on
  a totally stock install and when I use an upgraded/downgraded kernel.
  It literally necessitates restarting my computer. This problem is
  nonexistent when using Xorg instead of Wayland with GDM. Anyone else
  have this issue on Ubuntu 17.10 or figure out a solution better than
  simply switching to Xorg? I should clarify that I am not using nvidia
  drivers, I'm using Intel integrated graphics on a core-i7 5500U.

  Ubuntu 17.10 uses gnome-session v3.26.1.
  Expected behavior: When waking computer from suspend, expect GDM lock prompt 
and log back in.
  What happened instead: When waking computer from suspend, screen and IO is 
completely frozen, necessitating a force-shutdown.

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

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


[Desktop-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-10-31 Thread Ricardo
#103 did fix it

Adding:

[ipv4]
dns-priority=-42

to system-connections config file
or runing 'sudo nmcli connection modify  ipv4.dns-priority 
-42'
and restarting networkmanager service
did fix dns leaking using ProtonVPN on openvpn for me, thanks.

But i didn't quite understand the problem! Is it the provided openvpn
config file misconfigured or a networkmanager bug? As i said, in others
distros doesn't happend!

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Zesty:
  Confirmed
Status in network-manager source package in Artful:
  Confirmed

Bug description:
  [Impact]

   * NetworkManager incorrectly handles dns-priority of the VPN-like
  connections, which leads to leaking DNS queries outside of the VPN
  into the general internet.

   * Upstream has resolved this issue in master and 1.8 to correctly
  configure any dns backends with negative dns-priority settings.

  [Test Case]

  #FIXME#

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  #FIXME#

  [Regression Potential]

   * If this issue is changed DNS resolution will change, for certain
  queries, to go via VPN rather than general internet. And therefore,
  one may get new/different results or even loose access to
  resolve/access certain parts of the interent depending on what the DNS
  server on VPN chooses to respond to.

  [Other Info]
   
   * Original bug report

  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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


[Desktop-packages] [Bug 1728791] Re: [SRU] pulseaudio-droid module crashes on start

2017-10-31 Thread bhushan
** Summary changed:

- pulseaudio-droid module crashes on start
+ [SRU] pulseaudio-droid module crashes on start

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

Title:
  [SRU] pulseaudio-droid module crashes on start

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04 Xenial, and pulseaudio version 8.0-0ubuntu3.4

  [Impact]

   * This bug prevents users (currently Project Halium, UBports, Plasma Mobile) 
from using the pulseaudio-modules-droid on android devices.
   * This behavior can be seen in Ubuntu Xenial 16.04 with xenial-updates 
enabled.
   * Last 3 releases of pulseaudio included multiple patches which modified 
behavior of pulsecore library but required changes were not made in 
pulseaudio-module-droid.
   * This results in crash in pulseaudio-modules-droid

  
  #0  init_profile (u=0x59528) at modules/droid/module-droid-card.c:370
  #1  module_droid_card_22_LTX_pa__init (m=0x3c3f8) at 
modules/droid/module-droid-card.c:923
  #2  0xf76feb88 in pa_module_load (c=c@entry=0x33a80, name=name@entry=0x58240 
"module-droid-card-22", argument=0x0) at pulsecore/module.c:180
  #3  0xf76f1d7e in pa_cli_command_load (c=0x33a80, t=0x49320, buf=0x44f28, 
fail=0x3c1f4) at pulsecore/cli-command.c:439
  #4  0xf76f6ad8 in pa_cli_command_execute_line_stateful (c=0x33a80, 
s=s@entry=0x59120 "load-module module-droid-card-22", buf=buf@entry=0x44f28, 
fail=fail@entry=0x3c1f4, ifstate=ifstate@entry=0x0) at 
pulsecore/cli-command.c:2134
  #5  0xf76f6fc8 in pa_cli_command_execute_line (c=, 
s=s@entry=0x59120 "load-module module-droid-card-22", buf=buf@entry=0x44f28, 
fail=fail@entry=0x3c1f4) at pulsecore/cli-command.c:2155
  #6  0xee32fc82 in line_callback (line=0x3c208, s=0x59120 "load-module 
module-droid-card-22", userdata=0x3c1e0) at pulsecore/cli.c:153
  #7  0xf76a1360 in scan_for_lines (skip=, l=0x3c208) at 
pulsecore/ioline.c:269
  #8  do_read (l=0x3c208) at pulsecore/ioline.c:337
  #9  do_work (l=0x3c208) at pulsecore/ioline.c:386
  #10 0xf7655fa6 in dispatch_pollfds (m=0x32bd0) at pulse/mainloop.c:655
  #11 pa_mainloop_dispatch (m=m@entry=0x32bd0) at pulse/mainloop.c:898
  #12 0xf765629a in pa_mainloop_iterate (m=0x32bd0, block=, 
retval=0xfffef1c4) at pulse/mainloop.c:929
  #13 0xf7656314 in pa_mainloop_run (m=m@entry=0x32bd0, 
retval=retval@entry=0xfffef1c4) at pulse/mainloop.c:944
  #14 0x000158ca in main (argc=, argv=) at 
daemon/main.c:1152

  
  [Test Case]

   * Start pulseaudio
   * From another session run pacmd
   * In prompt type load-module module-droid-discover
   * On ubuntu touch devices, it will crash at startup

  [Regression Potential]

   * There is no regression potential for other parts of pulseaudio
  components.

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

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


[Desktop-packages] [Bug 1729164] Re: there is no way to stop the clock under gnome

2017-10-31 Thread Jeremy Bicha
This looks like it is due to the stricter environment used by Wayland
which is the new default display server in Ubuntu 17.10.

As a workaround, log out. Click your name on the login screen then click
the gear button. Choose 'Ubuntu on Xorg' and then enter your password to
log into the traditional display server instead of Wayland.

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.

** Tags added: wayland

** Summary changed:

- there is no way to stop the clock under gnome
+ Minimizing Aisleriot does not pause the game under Wayland

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

Title:
  Minimizing Aisleriot does not pause the game under Wayland

Status in aisleriot package in Ubuntu:
  New

Bug description:
  under unity, "minimizing" the window stops the game clock.
  under gnome, its does NOT.
  there should be a way to stop the clock and continue later.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: aisleriot 1:3.22.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 22:35:39 2017
  SourcePackage: aisleriot
  UpgradeStatus: Upgraded to artful on 2017-10-22 (9 days ago)

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

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


[Desktop-packages] [Bug 1705864] Re: Nautilus no longer starts (again)

2017-10-31 Thread el_gallo_azul
No, I haven't yet reinstalled the operating system. It's VERY tempting,
due to the accumulation of bugs over time that happens on a computer,
but unfortunately I haven't had a chance to operate without my main
computer for the 2 weeks that it takes to reinstall the operating
system, applications, and configure everything again.

Yes, the last time I had this issue was yesterday. I don't know of any
way to make Nautilus start functioning again other than rebooting the
computer.

Note that this particular bug is not common. ie. It doesn't occur every
day. It happens every couple of weeks on average.

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

Title:
  Nautilus no longer starts (again)

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I have reported this bug several times (about 5 times) before.

  I have not had this error occur for some weeks.

  I was using nautilus during my current session about half an hour ago.

  I have tried to start nautilus by:

  1. Clicking "Show in folder" from Google Chromium browser; and
  2. Clicking the "Files" icon in the Unity Launcher; and
  3. Typing "nautilus" into a terminal.

  The best I get is the icon in the Launcher flashes as the application
  tries to start.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  el_gallo_azul@W2600CR-850Pro:~$ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  el_gallo_azul@W2600CR-850Pro:~$ apt-cache policy nautilus
  nautilus:
Installed: 1:3.18.4.is.3.14.3-0ubuntu6
Candidate: 1:3.18.4.is.3.14.3-0ubuntu6
Version table:
   *** 1:3.18.4.is.3.14.3-0ubuntu6 500
  500 http://mirror.optus.net/ubuntu xenial-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1:3.18.4.is.3.14.3-0ubuntu4 500
  500 http://mirror.optus.net/ubuntu xenial/main amd64 Packages

  3) What you expected to happen

  Nautilus starts

  4) What happened instead

  Nautilus doesn't start

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jul 23 09:03:00 2017
  InstallationDate: Installed on 2014-10-14 (1012 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to xenial on 2016-08-26 (330 days ago)

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

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


[Desktop-packages] [Bug 1491787] Re: Gnome's Activities Overview search is always in English, regardless of the system language

2017-10-31 Thread Daniel van Vugt
** Summary changed:

- System language isn't applied to gnome-control-center in Gnome-Shell
+ Gnome's Activities Overview search is always in English, regardless of the 
system language

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

Title:
  Gnome's Activities Overview search is always in English, regardless of
  the system language

Status in Ubuntu GNOME:
  New
Status in Ubuntu Translations:
  New
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Hey,

  I'm referring to this issue on AskUbuntu:
  http://askubuntu.com/questions/600656/change-language-of-the-gnome-
  shell-overview

  On my Ubuntu Gnome 15.04 system all entries from the gnome-control-
  center are shown in English in the Gnome-Shell overview (see
  screenshot in the above mentioned link), even though my system
  language is German. The entries in the gnome-control-center itself are
  however in German.

  Is this due to a bug or missing translations?

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

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


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

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

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

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

Title:
  Panel and panel menus don't respond to theme changes

Status in gnome-shell package in Ubuntu:
  Confirmed

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu5
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 15 15:31:30 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-03 (135 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2017-10-31 Thread Daniel van Vugt
** Summary changed:

- Panel menus don't respond to theme changes
+ Panel and panel menus don't respond to theme changes

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

Title:
  Panel and panel menus don't respond to theme changes

Status in gnome-shell package in Ubuntu:
  Confirmed

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu5
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 15 15:31:30 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-03 (135 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1729019] Re: Ambiance color affecting Gnome-Shell themes under Ubuntu Session

2017-10-31 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1717456 ***
https://bugs.launchpad.net/bugs/1717456

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


** This bug has been marked a duplicate of bug 1717456
   Panel and panel menus don't respond to theme changes

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

Title:
  Ambiance color affecting Gnome-Shell themes under Ubuntu Session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1717023
  
https://launchpad.net/ubuntu/+source/ubuntu-themes/16.10+17.10.20171012.1-0ubuntu1

  After this change other gnome-shell themes not looking well under
  ubuntu session

  See the screenshot

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

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


[Desktop-packages] [Bug 1729184] [NEW] audio output not showing in settings

2017-10-31 Thread Shuvadip Chattopadhyay
Public bug reported:

There is no audio output device in the settings. If i put on headphones
it automatically goes to mute and still no output showing in settings. I
don't know what went wrong I tried to use bluetooth headphones and
installed pulseaudio because of it and after a lot of trying couldn't
get it to work so uninstalled it and after that this issue popped up.
Thanks in advance for the help.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  1 08:33:49 2017
InstallationDate: Installed on 2017-06-11 (142 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: Upgraded to artful on 2017-10-20 (11 days ago)
dmi.bios.date: 05/17/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.21
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8136
dmi.board.vendor: HP
dmi.board.version: 31.38
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd05/17/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8136:rvr31.38:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP
dmi.product.name: HP Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


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

** Attachment added: "error.png"
   https://bugs.launchpad.net/bugs/1729184/+attachment/5001542/+files/error.png

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

Title:
  audio output not showing in settings

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  There is no audio output device in the settings. If i put on
  headphones it automatically goes to mute and still no output showing
  in settings. I don't know what went wrong I tried to use bluetooth
  headphones and installed pulseaudio because of it and after a lot of
  trying couldn't get it to work so uninstalled it and after that this
  issue popped up. Thanks in advance for the help.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  1 08:33:49 2017
  InstallationDate: Installed on 2017-06-11 (142 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: Upgraded to artful on 2017-10-20 (11 days ago)
  dmi.bios.date: 05/17/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8136
  dmi.board.vendor: HP
  dmi.board.version: 31.38
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd05/17/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8136:rvr31.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1566357] Re: Unable to type passwords with non-English/non-Latin input source

2017-10-31 Thread Daniel van Vugt
A possible solution (confirmed working in 17.04 at least):

1. On 17.04 and earlier: System Settings > Language Support
2. On 17.10 and later: Settings > Region & Language > Manage Installed Languages
3. Configure your preferred language
4. Click "Apply System-Wide (Use the same language choices for startup and the 
login screen.)"

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

Title:
  Unable to type passwords with non-English/non-Latin input source

Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I recently found that I am unable to type using the "Japanese (Anthy)"
  input source in password fields in gnome-shell. That is I am unable to
  type using it (I just get English) on the login screen in the password
  field (though I haven't tried the username field), I am unable to type
  using it in the graphical prompts for authentication, and I am unable
  to type using it when setting a new password through the gnome-
  control-center.

  I am running Ubuntu GNOME 15.10 with GNOME 3.18 but have also
  experienced this issue with Ubuntu GNOME 16.04 with GNOME 3.18 as well
  as with GNOME 3.20.

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

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


[Desktop-packages] [Bug 1706309] Re: Multi-monitor positioning lost on do-release-upgrade -d

2017-10-31 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1726538 ***
https://bugs.launchpad.net/bugs/1726538

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


** This bug has been marked a duplicate of bug 1726538
   Dual monitor configuration not saved across logout / login

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

Title:
  Multi-monitor positioning lost on do-release-upgrade -d

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Coming from a 17.04 install and typing do-release-upgrade -d on the
  command line results in multi-monitor positioning information being
  lost.

  I have two monitors, one is positioned below the other but on boot
  into 17.10, after the upgrade, the monitors are positioned side-by-
  side.

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

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


[Desktop-packages] [Bug 1652618] Re: Impossible to unlock the screen when using non-English language

2017-10-31 Thread Daniel van Vugt
A possible solution (confirmed working in 17.04 at least):

1. On 17.04 and earlier: System Settings > Language Support
2. On 17.10 and later: Settings > Region & Language > Manage Installed Languages
3. Configure your preferred language
4. Click "Apply System-Wide (Use the same language choices for startup and the 
login screen".

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

Title:
  Impossible to unlock the screen when using non-English language

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

Bug description:
  Steps to reproduce:
  1. Add another keyboard layout, e.g. Russian. Set key combination to switch 
languages to Capslock
  2. Change keyboard layout to Russian.
  3. Lock the screen with Ctrl-Alt-l
  4. Try to unlock the screen

  No matter what it's impossible now to unlock the screen. Changing keyboard 
layout with key combination or using mouse doesn't help. System always reports 
invalid password.
  It works absolutely fine if keyboard layout before locking the screen was 
English.

  I was able to reproduce it on clean 16.10 install in VM.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-shell 3.20.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec 26 16:43:30 2016
  DisplayManager: lightdm
  InstallationDate: Installed on 2016-09-16 (100 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to yakkety on 2016-12-09 (17 days ago)

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

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


[Desktop-packages] [Bug 1729181] [NEW] directory and file icons are same in "Files" app

2017-10-31 Thread Kunal Shah
Public bug reported:

while browsing File Manager with nautilus, it does not show different
icons for files and directory. Please see attached screenshot.

using Ubuntu Desktop 17.10 with wayland
GNOME nautilus 3.26.0

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


** Tags: 3.26.0 gnome gnome-17.10 nautilus ubuntu

** Attachment added: "Screenshot from 2017-11-01 08-27-06.png"
   
https://bugs.launchpad.net/bugs/1729181/+attachment/5001508/+files/Screenshot%20from%202017-11-01%2008-27-06.png

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

Title:
  directory and file icons are same in "Files" app

Status in nautilus package in Ubuntu:
  New

Bug description:
  while browsing File Manager with nautilus, it does not show different
  icons for files and directory. Please see attached screenshot.

  using Ubuntu Desktop 17.10 with wayland
  GNOME nautilus 3.26.0

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

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


[Desktop-packages] [Bug 1566357] Re: Unable to type passwords with non-English/non-Latin input source

2017-10-31 Thread Daniel van Vugt
See also bug 1652618

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

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

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

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

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

Title:
  Unable to type passwords with non-English/non-Latin input source

Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I recently found that I am unable to type using the "Japanese (Anthy)"
  input source in password fields in gnome-shell. That is I am unable to
  type using it (I just get English) on the login screen in the password
  field (though I haven't tried the username field), I am unable to type
  using it in the graphical prompts for authentication, and I am unable
  to type using it when setting a new password through the gnome-
  control-center.

  I am running Ubuntu GNOME 15.10 with GNOME 3.18 but have also
  experienced this issue with Ubuntu GNOME 16.04 with GNOME 3.18 as well
  as with GNOME 3.20.

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

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


[Desktop-packages] [Bug 1566357] Re: Unable to type passwords with non-English/non-Latin input source

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

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

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

Title:
  Unable to type passwords with non-English/non-Latin input source

Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I recently found that I am unable to type using the "Japanese (Anthy)"
  input source in password fields in gnome-shell. That is I am unable to
  type using it (I just get English) on the login screen in the password
  field (though I haven't tried the username field), I am unable to type
  using it in the graphical prompts for authentication, and I am unable
  to type using it when setting a new password through the gnome-
  control-center.

  I am running Ubuntu GNOME 15.10 with GNOME 3.18 but have also
  experienced this issue with Ubuntu GNOME 16.04 with GNOME 3.18 as well
  as with GNOME 3.20.

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

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


[Desktop-packages] [Bug 1566357] Re: Unable to type passwords with non-English/non-Latin input source

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

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

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

Title:
  Unable to type passwords with non-English/non-Latin input source

Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I recently found that I am unable to type using the "Japanese (Anthy)"
  input source in password fields in gnome-shell. That is I am unable to
  type using it (I just get English) on the login screen in the password
  field (though I haven't tried the username field), I am unable to type
  using it in the graphical prompts for authentication, and I am unable
  to type using it when setting a new password through the gnome-
  control-center.

  I am running Ubuntu GNOME 15.10 with GNOME 3.18 but have also
  experienced this issue with Ubuntu GNOME 16.04 with GNOME 3.18 as well
  as with GNOME 3.20.

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

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


[Desktop-packages] [Bug 1566357] Re: Unable to type passwords with non-English/non-Latin input source

2017-10-31 Thread Daniel van Vugt
** Summary changed:

- Unable to type passwords with the "Japanese (Anthy)" input source
+ Unable to type passwords with non-English/non-Latin input source

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

Title:
  Unable to type passwords with non-English/non-Latin input source

Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I recently found that I am unable to type using the "Japanese (Anthy)"
  input source in password fields in gnome-shell. That is I am unable to
  type using it (I just get English) on the login screen in the password
  field (though I haven't tried the username field), I am unable to type
  using it in the graphical prompts for authentication, and I am unable
  to type using it when setting a new password through the gnome-
  control-center.

  I am running Ubuntu GNOME 15.10 with GNOME 3.18 but have also
  experienced this issue with Ubuntu GNOME 16.04 with GNOME 3.18 as well
  as with GNOME 3.20.

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

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


[Desktop-packages] [Bug 1652618] Re: Impossible to unlock the screen when using non-English language

2017-10-31 Thread Daniel van Vugt
See also bug 1566357

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

Title:
  Impossible to unlock the screen when using non-English language

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

Bug description:
  Steps to reproduce:
  1. Add another keyboard layout, e.g. Russian. Set key combination to switch 
languages to Capslock
  2. Change keyboard layout to Russian.
  3. Lock the screen with Ctrl-Alt-l
  4. Try to unlock the screen

  No matter what it's impossible now to unlock the screen. Changing keyboard 
layout with key combination or using mouse doesn't help. System always reports 
invalid password.
  It works absolutely fine if keyboard layout before locking the screen was 
English.

  I was able to reproduce it on clean 16.10 install in VM.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-shell 3.20.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec 26 16:43:30 2016
  DisplayManager: lightdm
  InstallationDate: Installed on 2016-09-16 (100 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to yakkety on 2016-12-09 (17 days ago)

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

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


[Desktop-packages] [Bug 1652618] Re: Impossible to unlock the screen when using non-English language

2017-10-31 Thread Daniel van Vugt
See also bug 1725676

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

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

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

Title:
  Impossible to unlock the screen when using non-English language

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

Bug description:
  Steps to reproduce:
  1. Add another keyboard layout, e.g. Russian. Set key combination to switch 
languages to Capslock
  2. Change keyboard layout to Russian.
  3. Lock the screen with Ctrl-Alt-l
  4. Try to unlock the screen

  No matter what it's impossible now to unlock the screen. Changing keyboard 
layout with key combination or using mouse doesn't help. System always reports 
invalid password.
  It works absolutely fine if keyboard layout before locking the screen was 
English.

  I was able to reproduce it on clean 16.10 install in VM.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-shell 3.20.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec 26 16:43:30 2016
  DisplayManager: lightdm
  InstallationDate: Installed on 2016-09-16 (100 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to yakkety on 2016-12-09 (17 days ago)

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

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


[Desktop-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

2017-10-31 Thread Hui Wang
@ubuntu-sponsors team,

We added a fix to pulseaudio (xenial and artful), Please help build a
new SRU version.

thx.

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

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

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


[Desktop-packages] [Bug 1729164] [NEW] there is no way to stop the clock under gnome

2017-10-31 Thread sds
Public bug reported:

under unity, "minimizing" the window stops the game clock.
under gnome, its does NOT.
there should be a way to stop the clock and continue later.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: aisleriot 1:3.22.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 31 22:35:39 2017
SourcePackage: aisleriot
UpgradeStatus: Upgraded to artful on 2017-10-22 (9 days ago)

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


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

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

Title:
  there is no way to stop the clock under gnome

Status in aisleriot package in Ubuntu:
  New

Bug description:
  under unity, "minimizing" the window stops the game clock.
  under gnome, its does NOT.
  there should be a way to stop the clock and continue later.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: aisleriot 1:3.22.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 22:35:39 2017
  SourcePackage: aisleriot
  UpgradeStatus: Upgraded to artful on 2017-10-22 (9 days ago)

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

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


[Desktop-packages] [Bug 1543192] Re: Xorg crashed with SIGABRT in OsAbort() ["no screens found"]

2017-10-31 Thread Robert Baumgartner
I'm getting this in 16.04 very frequently as well. If you want my system
info as well, or if I can help debug in some other way let me know and I
will be happy to help get this fixed.

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

Title:
  Xorg crashed with SIGABRT in OsAbort() ["no screens found"]

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/4de849dfec89af168af9cda3318221a2a654e530

  ---

  No idea what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-core 2:1.17.3-2ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CrashCounter: 1
  Date: Mon Feb  8 17:07:23 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21da]
  InstallationDate: Installed on 2015-04-30 (283 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 429149G
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic 
root=UUID=457973fc-512e-4b6a-b65b-85f15fa85b7b ro console=tty1 console=ttyS0 
panic=-1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   __libc_start_main (main=0x557f8180ff00, argc=11, argv=0x7fffc9e34fd8, 
init=, fini=, rtld_fini=, 
stack_end=0x7fffc9e34fc8) at libc-start.c:289
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 05/18/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET46WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 429149G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 429149G
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.66-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160127-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
  xserver.bootTime: Mon Feb  8 17:08:14 2016
  xserver.configfile: default
  xserver.errors: systemd-logind: failed to get session: PID 9847 does not 
belong to any known session
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 728
   vendor LGD
  xserver.version: 2:1.17.3-2ubuntu2

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

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


[Desktop-packages] [Bug 1705146] Re: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': corrupted size vs. prev_size: 0x0000000005405f00 ***

2017-10-31 Thread Robert Baumgartner
And the gnome-shell info (which matches post #8)

$ apt-cache policy gnome-shell
gnome-shell:
  Installed: 3.18.5-0ubuntu0.3
  Candidate: 3.18.5-0ubuntu0.3
  Version table:
 *** 3.18.5-0ubuntu0.3 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
100 /var/lib/dpkg/status
 3.18.4-0ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

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

Title:
  gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell':
  corrupted size vs. prev_size: 0x05405f00 ***

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  lschris@localhost:~$ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  lschris@localhost:~$ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  Happened during this update today:

  Start-Date: 2017-07-18  17:22:01
  Commandline: aptdaemon role='role-commit-packages' sender=':1.151'
  Upgrade: python-problem-report:amd64 (2.20.1-0ubuntu2.9, 2.20.1-0ubuntu2.10), 
python-apport:amd64 (2.20.1-0ubuntu2.9, 2.20.1-0ubuntu2.10), apport:amd64 
(2.20.1-0ubuntu2.9, 2.20.1-0ubuntu2.10), python3-apport:amd64 
(2.20.1-0ubuntu2.9, 2.20.1-0ubuntu2.10), apport-retrace:amd64 
(2.20.1-0ubuntu2.9, 2.20.1-0ubuntu2.10), apport-gtk:amd64 (2.20.1-0ubuntu2.9, 
2.20.1-0ubuntu2.10), python3-problem-report:amd64 (2.20.1-0ubuntu2.9, 
2.20.1-0ubuntu2.10)
  End-Date: 2017-07-18  17:27:27

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.5-0ubuntu0.3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/bin/gnome-shell': corrupted size vs. 
prev_size: 0x05405f00 ***
  CurrentDesktop: GNOME
  Date: Tue Jul 18 17:32:37 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-10-24 (998 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __libc_message (do_abort=2, fmt=fmt@entry=0x7f7ca6ab3e98 "*** Error in `%s': 
%s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ar_ptr=0x7f7ca6ce7b20 , ptr=0x5405f00, 
str=0x7f7ca6ab0c35 "corrupted size vs. prev_size", action=3) at malloc.c:5006
   _int_free (av=0x7f7ca6ce7b20 , p=, have_lock=0) 
at malloc.c:4014
   __GI___libc_free (mem=) at malloc.c:2968
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
  Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': 
corrupted size vs. prev_size: 0x05405f00 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin netdev plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1705146] Re: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': corrupted size vs. prev_size: 0x0000000005405f00 ***

2017-10-31 Thread Robert Baumgartner
I just got this same crash during a window switch (Activities Overview)
in GNOME. The desktop completely freezes (input devices continue to
work).

$ lsb_release -rd
Description:Ubuntu 16.04.3 LTS
Release:16.04

$ uname -a
Linux [redacted] 4.10.0-37-generic #41~16.04.1-Ubuntu SMP Fri Oct 6 22:42:59 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Some additional system info. Also note this is a Xen HVM in my case, and
that the system was pending a reboot after upgrading to
4.10.0-38-generic kernel. This is the first time seeing this specific
error, although I've been having a lot of Xorg-related crashes in
general on this particular system.

System:Host: [redacted] Kernel: 4.10.0-37-generic x86_64 (64 bit gcc: 5.4.0)
   Desktop: Gnome 3.18.5 (Gtk 3.18.9-1ubuntu3.3) dm: gdm3
   Distro: Ubuntu 16.04 xenial
PU:Multi core Intel Xeon E5-2699 v4 (-HT-MCP-) cache: 56320 KB
   flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3) bmips: 70399
   clock speeds: max: 2199 MHz 1: 2199 MHz 2: 2199 MHz 3: 2199 MHz
   4: 2199 MHz 5: 2199 MHz 6: 2199 MHz 7: 2199 MHz 8: 2199 MHz
   9: 2199 MHz 10: 2199 MHz 11: 2199 MHz 12: 2199 MHz 13: 2199 MHz
   14: 2199 MHz 15: 2199 MHz 16: 2199 MHz
Graphics:  Card: NVIDIA GP102 [TITAN X] bus-ID: 00:04.0 chip-ID: 10de:1b00
   Display Server: X.Org 1.18.4 drivers: cirrus,vesa,nouveau (unloaded: 
nvidia) FAILED: fbdev
   Resolution: 1920x1080@59.94hz
   GLX Renderer: TITAN X (Pascal)/PCIe/SSE2
   GLX Version: 4.5.0 NVIDIA 384.90 Direct Rendering: Yes
Audio: Card NVIDIA GP102 HDMI Audio Controller
   driver: snd_hda_intel bus-ID: 00:05.0 chip-ID: 10de:10ef
   Sound: Advanced Linux Sound Architecture v: k4.10.0-37-generic

** Attachment added: "Stacktrace"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1705146/+attachment/5001470/+files/Stacktrace

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

Title:
  gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell':
  corrupted size vs. prev_size: 0x05405f00 ***

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  lschris@localhost:~$ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  lschris@localhost:~$ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  Happened during this update today:

  Start-Date: 2017-07-18  17:22:01
  Commandline: aptdaemon role='role-commit-packages' sender=':1.151'
  Upgrade: python-problem-report:amd64 (2.20.1-0ubuntu2.9, 2.20.1-0ubuntu2.10), 
python-apport:amd64 (2.20.1-0ubuntu2.9, 2.20.1-0ubuntu2.10), apport:amd64 
(2.20.1-0ubuntu2.9, 2.20.1-0ubuntu2.10), python3-apport:amd64 
(2.20.1-0ubuntu2.9, 2.20.1-0ubuntu2.10), apport-retrace:amd64 
(2.20.1-0ubuntu2.9, 2.20.1-0ubuntu2.10), apport-gtk:amd64 (2.20.1-0ubuntu2.9, 
2.20.1-0ubuntu2.10), python3-problem-report:amd64 (2.20.1-0ubuntu2.9, 
2.20.1-0ubuntu2.10)
  End-Date: 2017-07-18  17:27:27

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.5-0ubuntu0.3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/bin/gnome-shell': corrupted size vs. 
prev_size: 0x05405f00 ***
  CurrentDesktop: GNOME
  Date: Tue Jul 18 17:32:37 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-10-24 (998 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __libc_message (do_abort=2, fmt=fmt@entry=0x7f7ca6ab3e98 "*** Error in `%s': 
%s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ar_ptr=0x7f7ca6ce7b20 , ptr=0x5405f00, 
str=0x7f7ca6ab0c35 "corrupted size vs. prev_size", action=3) at malloc.c:5006
   _int_free (av=0x7f7ca6ce7b20 , p=, have_lock=0) 
at malloc.c:4014
   __GI___libc_free (mem=) at malloc.c:2968
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
  Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': 
corrupted size vs. prev_size: 0x05405f00 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin netdev plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 731363] Re: Aisleriot solitaire not showing background texture

2017-10-31 Thread Sebastian Stark
By the way: as a workaround it is possible to set the background by
overriding the gtk theme css by adding something like this to
~/.config/gtk-3.0/gtk.css:

AisleriotBoard, aisleriot-board {
background-image: url('/home/seb/Pictures/aisleriot-background.jpg');
}

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

Title:
  Aisleriot solitaire not showing background texture

Status in aisleriot package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gnome-games

  As of Maverick, solitaire isn't showing its background texture and is
  using a basic green default again.  Problem also exists in Natty.

  http://mail.gnome.org/archives/games-list/2010-October/msg00018.html
  shows something changed with paths in the version that came out just
  before Maverick, so it may be responsible.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: gnome-games (not installed)
  ProcVersionSignature: Ubuntu 2.6.35-28.49-generic 2.6.35.11
  Uname: Linux 2.6.35-28-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Tue Mar  8 06:59:09 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-games

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

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


[Desktop-packages] [Bug 1728146] Re: package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other

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

** Changed in: sane-backends (Ubuntu)
   Status: New => Confirmed

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  installing wine from winhq-stable repo

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 21:27:48 2017
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2017-10-21 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  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/1728146/+subscriptions

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


[Desktop-packages] [Bug 1705146] Re: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': corrupted size vs. prev_size: 0x0000000005405f00 ***

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

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

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

Title:
  gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell':
  corrupted size vs. prev_size: 0x05405f00 ***

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  lschris@localhost:~$ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  lschris@localhost:~$ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  Happened during this update today:

  Start-Date: 2017-07-18  17:22:01
  Commandline: aptdaemon role='role-commit-packages' sender=':1.151'
  Upgrade: python-problem-report:amd64 (2.20.1-0ubuntu2.9, 2.20.1-0ubuntu2.10), 
python-apport:amd64 (2.20.1-0ubuntu2.9, 2.20.1-0ubuntu2.10), apport:amd64 
(2.20.1-0ubuntu2.9, 2.20.1-0ubuntu2.10), python3-apport:amd64 
(2.20.1-0ubuntu2.9, 2.20.1-0ubuntu2.10), apport-retrace:amd64 
(2.20.1-0ubuntu2.9, 2.20.1-0ubuntu2.10), apport-gtk:amd64 (2.20.1-0ubuntu2.9, 
2.20.1-0ubuntu2.10), python3-problem-report:amd64 (2.20.1-0ubuntu2.9, 
2.20.1-0ubuntu2.10)
  End-Date: 2017-07-18  17:27:27

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.5-0ubuntu0.3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/bin/gnome-shell': corrupted size vs. 
prev_size: 0x05405f00 ***
  CurrentDesktop: GNOME
  Date: Tue Jul 18 17:32:37 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-10-24 (998 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __libc_message (do_abort=2, fmt=fmt@entry=0x7f7ca6ab3e98 "*** Error in `%s': 
%s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ar_ptr=0x7f7ca6ce7b20 , ptr=0x5405f00, 
str=0x7f7ca6ab0c35 "corrupted size vs. prev_size", action=3) at malloc.c:5006
   _int_free (av=0x7f7ca6ce7b20 , p=, have_lock=0) 
at malloc.c:4014
   __GI___libc_free (mem=) at malloc.c:2968
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
  Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': 
corrupted size vs. prev_size: 0x05405f00 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin netdev plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1309247] Re: Cannot add any account using Online Accounts on 14.04

2017-10-31 Thread Disctanger
@Rey Leonard Amorato if you are using Virtual Box and if 3d acceleration
is enabled, try to turn off that feature and try to log in. This way
helped me when I was getting blank page instead of login screen in
online accounts.

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

Title:
  Cannot add any account using Online Accounts on 14.04

Status in gnome-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  When attempting to add an account i.e: facebook, google, etc., the
  first thing that pops out is "Please authorize your Facebook account"
  but there's only a blank page. The page does not load.

  Using Ubuntu 14.04

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

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


[Desktop-packages] [Bug 1724977] Re: two mouse cursors visible at the same time on rotated screen

2017-10-31 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: Unknown => Confirmed

** Changed in: gnome-shell
   Importance: Unknown => Medium

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

Title:
  two mouse cursors visible at the same time on rotated screen

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When my 2nd Asus (Ancor) display is in portrait mode and is set to be
  to the left of my centered landscape display in extended mode, moving
  the mouse to roughly the left 20% of my landscape display will show a
  mouse cursor on my landcape display AND portrait display at the same
  time.  Oddly moving a window into this area only shows on the
  landscape display.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 13:43:30 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1714596] Re: PDF images are blank

2017-10-31 Thread Mathew Hodson
** Tags added: regression-release

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

Title:
  PDF images are blank

Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  1. Download a PDFs with images such as - 
  
http://www.dvrpc.org/Connections2045/pdf/2045_DRAFT_Plan_for_Public_Comment.pdf
  
http://www.hopkinsmedicine.org/human_resources/_docs/employee_handbook_non-union_non-represented.pdf
  http://humanservices.arkansas.gov/dccece/classroom_docs/carseatsafety.pdf

  2. Open in Evince, note how first page is blank

  Open with Firefox and note how it displays a nice intro page.

  Ubuntu 17.04 LiveCD works fine
  Ubuntu 17.10 LiveCD does not

  For Evince Zesty (3.24.0) vs Artful (3.24.1) which might be any easy thing to 
rule out. (I also tried the artful -proposed evince which has the issue too)
  For Poppler Zesty (0.48.0) vs Artful (0.57.0) so my guess is bug is in 
poppler.

  Given my testing in Fedora (C#2) which worked fine with same version
  of poppler and by downgrading the packages I believe this a Ubuntu
  specific poppler bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.24.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Sep  1 17:22:35 2017
  SourcePackage: evince
  UpgradeStatus: Upgraded to artful on 2017-07-26 (37 days ago)

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

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


[Desktop-packages] [Bug 1729103] Re: Update gnome-desktop3 to 3.26.2

2017-10-31 Thread Jeremy Bicha
** Description changed:

  Impact
  --
  This updates the GNOME version number reported in Settings > Details > About 
to 3.26.2
  
  We do our own translations so the translation updates should have nearly
  no impact.
  
  Since we're updating most of the other GNOME packages to 3.26.2, it's
  appropriate to do this update too.
+ 
+ https://git.gnome.org/browse/gnome-desktop/tree/NEWS?h=gnome-3-26
+ https://git.gnome.org/browse/gnome-desktop/log?h=gnome-3-26
  
  Test Case
  =
  From Ubuntu 17.10, open the Settings app.
  Navigate to Details > About
  The GNOME version number should say 3.26.2
  
  Regression Potential
  
  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

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

Title:
  Update gnome-desktop3 to 3.26.2

Status in gnome-desktop3 package in Ubuntu:
  Triaged
Status in gnome-desktop3 source package in Artful:
  Triaged

Bug description:
  Impact
  --
  This updates the GNOME version number reported in Settings > Details > About 
to 3.26.2

  We do our own translations so the translation updates should have
  nearly no impact.

  Since we're updating most of the other GNOME packages to 3.26.2, it's
  appropriate to do this update too.

  https://git.gnome.org/browse/gnome-desktop/tree/NEWS?h=gnome-3-26
  https://git.gnome.org/browse/gnome-desktop/log?h=gnome-3-26

  Test Case
  =
  From Ubuntu 17.10, open the Settings app.
  Navigate to Details > About
  The GNOME version number should say 3.26.2

  Regression Potential
  
  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

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

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


[Desktop-packages] [Bug 1729103] [NEW] Update gnome-desktop3 to 3.26.2

2017-10-31 Thread Jeremy Bicha
Public bug reported:

Impact
--
This updates the GNOME version number reported in Settings > Details > About to 
3.26.2

We do our own translations so the translation updates should have nearly
no impact.

Since we're updating most of the other GNOME packages to 3.26.2, it's
appropriate to do this update too.

https://git.gnome.org/browse/gnome-desktop/tree/NEWS?h=gnome-3-26
https://git.gnome.org/browse/gnome-desktop/log?h=gnome-3-26

Test Case
=
>From Ubuntu 17.10, open the Settings app.
Navigate to Details > About
The GNOME version number should say 3.26.2

Regression Potential

There is a micro-release exception for GNOME:
https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

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

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


** Tags: artful upgrade-software-version

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

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

** Changed in: gnome-desktop3 (Ubuntu Artful)
   Status: New => Triaged

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

Title:
  Update gnome-desktop3 to 3.26.2

Status in gnome-desktop3 package in Ubuntu:
  Triaged
Status in gnome-desktop3 source package in Artful:
  Triaged

Bug description:
  Impact
  --
  This updates the GNOME version number reported in Settings > Details > About 
to 3.26.2

  We do our own translations so the translation updates should have
  nearly no impact.

  Since we're updating most of the other GNOME packages to 3.26.2, it's
  appropriate to do this update too.

  https://git.gnome.org/browse/gnome-desktop/tree/NEWS?h=gnome-3-26
  https://git.gnome.org/browse/gnome-desktop/log?h=gnome-3-26

  Test Case
  =
  From Ubuntu 17.10, open the Settings app.
  Navigate to Details > About
  The GNOME version number should say 3.26.2

  Regression Potential
  
  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

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

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


[Desktop-packages] [Bug 1729104] [NEW] loading Ubuntu from restart libsane didn't load

2017-10-31 Thread Anthony Middlebrooks
Public bug reported:

from reboot
says can't load libsane

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Mon Oct 30 19:48:01 2017
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental2ubuntu2.1
 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-8cdJP1/11-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
  trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
InstallationDate: Installed on 2017-10-23 (8 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful package-conflict package-from-proposed

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

Title:
  loading Ubuntu from restart libsane didn't load

Status in sane-backends package in Ubuntu:
  New

Bug description:
  from reboot
  says can't load libsane

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 30 19:48:01 2017
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-8cdJP1/11-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2017-10-23 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  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/1729104/+subscriptions

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


[Desktop-packages] [Bug 1729104] Re: loading Ubuntu from restart libsane didn't load

2017-10-31 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  loading Ubuntu from restart libsane didn't load

Status in sane-backends package in Ubuntu:
  New

Bug description:
  from reboot
  says can't load libsane

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 30 19:48:01 2017
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-8cdJP1/11-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2017-10-23 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  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/1729104/+subscriptions

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


[Desktop-packages] [Bug 1722121] Re: Gnome-Terminal ignores theme, preferences is unavailable, and copy not working when launching from right-click desktop

2017-10-31 Thread Egmont Koblinger
On "Ubuntu", xeyes follows the mouse movement when over the desktop. On
"GNOME" it doesn't.

I guess it means that Ubuntu's desktop background app isn't native X11,
and probably that's why somehow (still totally unclear to me how) gnome-
terminal inherits this X11-compat requirement from the menu there.

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

Title:
  Gnome-Terminal ignores theme, preferences is unavailable, and copy not
  working when launching from right-click desktop

Status in gnome-terminal package in Ubuntu:
  Confirmed

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

  gnome-terminal:
Installed: 3.24.2-0ubuntu4
Candidate: 3.24.2-0ubuntu4
Version table:
   *** 3.24.2-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Expected behavior

  Right-clicking on the desktop and selecting "Open Terminal" should
  give me the same terminal as running gnome-terminal or or opening
  terminal in the activity view.

  What happens
  Gnome-Terminal launches with the correct GTK theme, but not the correct theme 
variant (light instead of dark). The "Preferences" option is gone from the top 
bar. Trying to copy something from the terminal and pasting outputs 
"unavailable".

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  8 22:49:01 2017
  InstallationDate: Installed on 2017-09-30 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/ubuntu/+source/gnome-terminal/+bug/1722121/+subscriptions

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


[Desktop-packages] [Bug 1722121] Re: Gnome-Terminal ignores theme, preferences is unavailable, and copy not working when launching from right-click desktop

2017-10-31 Thread Egmont Koblinger
Correctly working windows are native Wayland. Faulty windows are X11
(XWayland), you can tell by e.g. xeyes following the mouse movement.

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

Title:
  Gnome-Terminal ignores theme, preferences is unavailable, and copy not
  working when launching from right-click desktop

Status in gnome-terminal package in Ubuntu:
  Confirmed

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

  gnome-terminal:
Installed: 3.24.2-0ubuntu4
Candidate: 3.24.2-0ubuntu4
Version table:
   *** 3.24.2-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Expected behavior

  Right-clicking on the desktop and selecting "Open Terminal" should
  give me the same terminal as running gnome-terminal or or opening
  terminal in the activity view.

  What happens
  Gnome-Terminal launches with the correct GTK theme, but not the correct theme 
variant (light instead of dark). The "Preferences" option is gone from the top 
bar. Trying to copy something from the terminal and pasting outputs 
"unavailable".

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  8 22:49:01 2017
  InstallationDate: Installed on 2017-09-30 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/ubuntu/+source/gnome-terminal/+bug/1722121/+subscriptions

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


[Desktop-packages] [Bug 1729101] [NEW] /usr/bin/zenity:11:elf_machine_rela_relative:elf_dynamic_do_Rela:_dl_relocate_object:dl_main:_dl_sysdep_start

2017-10-31 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
zenity.  This problem was most recently seen with package version 
3.18.1.1-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/a006e1e9d70bf0265672b5fc7583f1d5e1265b38 
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 and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: precise saucy xenial

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

Title:
  
/usr/bin/zenity:11:elf_machine_rela_relative:elf_dynamic_do_Rela:_dl_relocate_object:dl_main:_dl_sysdep_start

Status in zenity package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
zenity.  This problem was most recently seen with package version 
3.18.1.1-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/a006e1e9d70bf0265672b5fc7583f1d5e1265b38 
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 and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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


[Desktop-packages] [Bug 1607042] Re: LibreOffice should automatically detect installed dictionary and allow ease in changing to it

2017-10-31 Thread Bug Watch Updater
** Changed in: df-libreoffice
   Status: Unknown => Incomplete

** Changed in: df-libreoffice
   Importance: Unknown => Wishlist

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

Title:
  LibreOffice should automatically detect installed dictionary and allow
  ease in changing to it

Status in LibreOffice:
  Incomplete
Status in Ubuntu GNOME:
  New
Status in libreoffice package in Ubuntu:
  New

Bug description:
  I have found that even after installing the "English (UK)" language
  packs on Ubuntu GNOME 16.04 with GNOME 3.20 that I must set it in the
  settings for LibreOffice Writer and the majority of the other ones in
  the suit require this.

  Though I think it would be much easier if if one has the needed
  language packs installed for the only thing to really need doing to be
  setting the "Text language" thing at the bottom. Currently if I try
  and do that without setting it in the main settings in several places
  it just jumps back to "English (US)" immediately without giving me any
  hint of what I should do to achieve what I want.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1607042/+subscriptions

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


[Desktop-packages] [Bug 1729095] [NEW] Input of the admin password impossible

2017-10-31 Thread CAUDOUX DIDIER
Public bug reported:

Command :
gksu /opt/lampp/manager-linux-x64.run
Message :
/usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string 
constant "murrine-scrollbar", expected valid string constant
GNOME_SUDO_PASS
sudo: 1 saisie de mot de passe incorrecte

In the window that opens to enter the admin password, it is not possible
to access to the password field. It is only possible to click on the
buttons "cancel" or "validate".

See screen-shot in file attached.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gksu 2.0.2-9ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 31 23:52:38 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-01-14 (290 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: gksu
UpgradeStatus: Upgraded to artful on 2017-10-21 (10 days ago)

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


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

** Attachment added: "Capture du 2017-10-31 23-39-24.png"
   
https://bugs.launchpad.net/bugs/1729095/+attachment/5001412/+files/Capture%20du%202017-10-31%2023-39-24.png

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

Title:
  Input of the admin password impossible

Status in gksu package in Ubuntu:
  New

Bug description:
  Command :
  gksu /opt/lampp/manager-linux-x64.run
  Message :
  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid 
string constant "murrine-scrollbar", expected valid string constant
  GNOME_SUDO_PASS
  sudo: 1 saisie de mot de passe incorrecte

  In the window that opens to enter the admin password, it is not
  possible to access to the password field. It is only possible to click
  on the buttons "cancel" or "validate".

  See screen-shot in file attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gksu 2.0.2-9ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 23:52:38 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-01-14 (290 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gksu
  UpgradeStatus: Upgraded to artful on 2017-10-21 (10 days ago)

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

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


[Desktop-packages] [Bug 856210] Re: wow! some of my thoughts

2017-10-31 Thread Fabio Rossi
Dear,


I just wished to give out some  of my thoughts, please read  them here 
http://www.sujiapartment.com/will.php?UE84NTYyMTBAYnVncy5sYXVuY2hwYWQubmV0

FBIO ROSSI


From: Bug 856210 [mailto:856...@bugs.launchpad.net]
Sent: Tuesday, October 31, 2017 4:51 PM
To: ross...@inwind.it
Subject: You hate Thierry Henry

Stunning  photos... yes.

Tree growth connected with celestial movement and astral  cycles... no.


Can tree growth be affected  by our sun, the moon,  and possibly power lines?  
Yes.

Can a distant star affect a tree?   Not much (sure, there is some
light).

Do  *astral cycles* affect trees?  Fuck no...  what  a bunch of  hog
wash.


Money quote from  the posted article that lets you know it is nothing  but  
bullshit...

*I believe energies  inside the earth are transmuted and transmitted
into the cosmos  by the trees, so the  trees are like antennas,  senders
and receivers of earth  energies and stellar energies.*

Jeebus fuck - what a  load  of nonsense.


Sent from Mail for Windows 10

** Attachment added: "6B76F4F3398AE5E2.jpg"
   
https://bugs.launchpad.net/bugs/856210/+attachment/5001411/+files/6B76F4F3398AE5E2.jpg

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

Title:
  Horizontal Scrollbar in kde dont work (default theme)

Status in LibreOffice:
  Fix Released
Status in oxygen transparent:
  Unknown
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Oneiric:
  Fix Released
Status in libreoffice source package in Precise:
  Fix Released

Bug description:
  When using libreoffice in kunbuntu 11.10 beta, the horizontal
  scrollbar seems too large and cannot be moved (see screenshot in
  attachement). I've seen this bug in calc and impress.

  Thanks for your help !

  WORKAROUND: remove libreoffice-kde  (but you lose KDE integration -
  but it becomes useable)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/856210/+subscriptions

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


[Desktop-packages] [Bug 1728412] Re: Titlebar of firefox does not respond to touch screen

2017-10-31 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: Unknown => Confirmed

** Changed in: gnome-shell
   Importance: Unknown => Medium

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

Title:
  Titlebar of firefox does not respond to touch screen

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  I have a laptop with a touch screen and a new installation of 17.10.

  For the most part the touch screen is supported ok. I can move around
  most windows ok, I can zoom in the pdf viewer with a two-finger-pinch
  gesture. However, firefox has a differently looking toolbar and I can
  neither move the window, nor does it react to tapping the
  minimise/maximise/close buttons.

  I assume that I am running wayland by looking at these variables:

  echo $WAYLAND_DISPLAY $XDG_SESSION_DESKTOP $XDG_SESSION_TYPE 
  wayland-0 ubuntu wayland
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   peter 10998 F...m pulseaudio
   /dev/snd/controlC0:  peter 10998 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=f1546bcb-f4e8-4393-a32e-0f014e1e9bd3
  InstallationDate: Installed on 2017-10-29 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: HP HP Pavilion x2 Detachable
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=e11fcd52-994f-4f5f-814f-f95ea37ccc46 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8181
  dmi.board.vendor: HP
  dmi.board.version: 42.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.13:bd03/14/2016:svnHP:pnHPPavilionx2Detachable:pvr:rvnHP:rn8181:rvr42.25:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Pavilion x2 Detachable
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1722121] Re: Gnome-Terminal ignores theme, preferences is unavailable, and copy not working when launching from right-click desktop

2017-10-31 Thread Egmont Koblinger
Re-enabling DND (git revert 10e164d8) pretty much always causes a sudden
crash as soon as I try to drag out a tab, it's impossible to test that.

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

Title:
  Gnome-Terminal ignores theme, preferences is unavailable, and copy not
  working when launching from right-click desktop

Status in gnome-terminal package in Ubuntu:
  Confirmed

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

  gnome-terminal:
Installed: 3.24.2-0ubuntu4
Candidate: 3.24.2-0ubuntu4
Version table:
   *** 3.24.2-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Expected behavior

  Right-clicking on the desktop and selecting "Open Terminal" should
  give me the same terminal as running gnome-terminal or or opening
  terminal in the activity view.

  What happens
  Gnome-Terminal launches with the correct GTK theme, but not the correct theme 
variant (light instead of dark). The "Preferences" option is gone from the top 
bar. Trying to copy something from the terminal and pasting outputs 
"unavailable".

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  8 22:49:01 2017
  InstallationDate: Installed on 2017-09-30 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/ubuntu/+source/gnome-terminal/+bug/1722121/+subscriptions

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


[Desktop-packages] [Bug 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() [Global App Menu specific?]

2017-10-31 Thread Daniel Playfair Cal
** Attachment added: "Valgrind log of crash occurring (with more debug symbols)"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714989/+attachment/5001402/+files/17-11-01_09-18-49.valgrind

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text() from ffi_call_unix64() [Global App Menu specific?]

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Incomplete

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

  error report:
  https://errors.ubuntu.com/problem/1c95cc2653ab00054b5d1764e41d974328a5f49d

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

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

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


[Desktop-packages] [Bug 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() [Global App Menu specific?]

2017-10-31 Thread Daniel Playfair Cal
The JS stack trace from comment 45 is:

 == Stack trace for context 0x22ad77f0 ==
#0   0x1ffeffc980 b   
/usr/share/gnome-shell/extensions/freon@UshakovVasilii_Github.yahoo.com/extension.js:360
 (0x42dbdc48 @ 1995)
#1   0x1ffeffd680 I   resource:///org/gnome/gjs/modules/_legacy.js:82 
(0x3a4c2c48 @ 71)
#2 0x3a981920 i   
/usr/share/gnome-shell/extensions/freon@UshakovVasilii_Github.yahoo.com/extension.js:231
 (0x42dbdb38 @ 17)
#3   0x1ffeffe360 b   self-hosted:913 (0x3a4ee4d8 @ 346)
#4   0x1ffeffeb60 b   
/usr/share/gnome-shell/extensions/freon@UshakovVasilii_Github.yahoo.com/commandLineUtil.js:38
 (0x42dc66f8 @ 454)
#5   0x1ffefff970 b   self-hosted:917 (0x3a4ee4d8 @ 394)

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text() from ffi_call_unix64() [Global App Menu specific?]

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Incomplete

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

  error report:
  https://errors.ubuntu.com/problem/1c95cc2653ab00054b5d1764e41d974328a5f49d

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

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

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


[Desktop-packages] [Bug 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() [Global App Menu specific?]

2017-10-31 Thread Daniel Playfair Cal
** Attachment added: "Alternative valgrind log of the crash (No JS stack trace)"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714989/+attachment/5001403/+files/17-11-01_09-12-17.valgrind

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text() from ffi_call_unix64() [Global App Menu specific?]

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Incomplete

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

  error report:
  https://errors.ubuntu.com/problem/1c95cc2653ab00054b5d1764e41d974328a5f49d

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

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

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


[Desktop-packages] [Bug 1722121] Re: Gnome-Terminal ignores theme, preferences is unavailable, and copy not working when launching from right-click desktop

2017-10-31 Thread Egmont Koblinger
Pressing the global shortcut Ctrl+Alt+T, or pressing the Super key and
typing Terminal, or launching from the left Launcher once it's been
added as a favorite all launch via /usr/bin/gnome-terminal and result in
a good one.

Nautilus (Files) file manager window, right click -> Open in Terminal
does _not_ go thru /usr/bin/gnome-terminal, yet results in a good
terminal.

Desktop's right click menu does _not_ go thru /usr/bin/gnome-terminal
either (does it use the nautilus plugin? or some direct dbus/systemd
stuff?) and results in a buggy window.

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

Title:
  Gnome-Terminal ignores theme, preferences is unavailable, and copy not
  working when launching from right-click desktop

Status in gnome-terminal package in Ubuntu:
  Confirmed

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

  gnome-terminal:
Installed: 3.24.2-0ubuntu4
Candidate: 3.24.2-0ubuntu4
Version table:
   *** 3.24.2-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Expected behavior

  Right-clicking on the desktop and selecting "Open Terminal" should
  give me the same terminal as running gnome-terminal or or opening
  terminal in the activity view.

  What happens
  Gnome-Terminal launches with the correct GTK theme, but not the correct theme 
variant (light instead of dark). The "Preferences" option is gone from the top 
bar. Trying to copy something from the terminal and pasting outputs 
"unavailable".

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  8 22:49:01 2017
  InstallationDate: Installed on 2017-09-30 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/ubuntu/+source/gnome-terminal/+bug/1722121/+subscriptions

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


[Desktop-packages] [Bug 1722121] Re: Gnome-Terminal ignores theme, preferences is unavailable, and copy not working when launching from right-click desktop

2017-10-31 Thread Egmont Koblinger
I can confirm this with Ubuntu's packages, as well as manually compiled
VTE + gnome-terminal from git master (and hence no Ubuntu patches, no
wrapper startup script).

Happens on "Ubuntu" desktop environment [Wayland] only, not on "Ubuntu
(Xorg)" or any other. (Well, "GNOME" doesn't have a Terminal entry in
its "right-click on the desktop" menu, not sure if it's supposed to be
there or what makes it appear there.)

Terminal windows started up in these two different ways are also not
grouped together in the left-hand launchbar, or when Alt+Tabbing.

However, they are all handled by a single common gnome-terminal-server
process.

Ctrl+Shift+N (new window) somehow remembers the context and opens
another window of that kind. When pressed over a faulty window, the new
one will be faulty too. When pressed over a good one, the new one is
good too.

If highlighted in a correct window, shift+insert pasting works in all
the windows. If highlighted in a faulty window, shift+insert pasting
doesn't work in the same window or other faulty windows, but works  in
healthy windows.

(Note to myself: I could even try re-enabling tab DND across windows,
and drag from a faulty to a correct one or vice versa to see what
happens.)

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

Title:
  Gnome-Terminal ignores theme, preferences is unavailable, and copy not
  working when launching from right-click desktop

Status in gnome-terminal package in Ubuntu:
  Confirmed

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

  gnome-terminal:
Installed: 3.24.2-0ubuntu4
Candidate: 3.24.2-0ubuntu4
Version table:
   *** 3.24.2-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Expected behavior

  Right-clicking on the desktop and selecting "Open Terminal" should
  give me the same terminal as running gnome-terminal or or opening
  terminal in the activity view.

  What happens
  Gnome-Terminal launches with the correct GTK theme, but not the correct theme 
variant (light instead of dark). The "Preferences" option is gone from the top 
bar. Trying to copy something from the terminal and pasting outputs 
"unavailable".

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  8 22:49:01 2017
  InstallationDate: Installed on 2017-09-30 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/ubuntu/+source/gnome-terminal/+bug/1722121/+subscriptions

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


[Desktop-packages] [Bug 785681] Re: Unable to unblank screen, cursor still present

2017-10-31 Thread Sergio Callegari
I see the same with:

kubuntu 17.10
Nvidia graphics (G84GL [Quadro FX 570])
Nouveau driver

When power management kicks in to switch off the screen via dpms, then
it is impossible to resume operation. As you move the mouse, there is no
screenlock screen to enter the password, just a black screen with the
mouse cursor.

All the relevant KDE/plasma processes are active, and so is the
screenlocker process.

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

Title:
  Unable to unblank screen, cursor still present

Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete
Status in Baltix:
  New

Bug description:
  Binary package hint: xserver-xorg-video-intel

  This is ~ev filing this bug on behalf of Ellen.  When her laptop
  blanked the screen, she tried to unlock it; however, it did not return
  from this state and only the mouse cursor was ever visible.  Switching
  to a VT showed that all the desktop processes were still running.
  Killing gnome-screensaver did not fix the issue, nor did running unity
  --reset.  This issue occurs  sporadically.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  DRM.card0.DP.1:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.DP.2:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.HDMI.A.1:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.LVDS.1:
   status: connected
   enabled: enabled
   dpms: On
   modes: 1366x768
   edid-base64: 
AP///wBMo0FUAAATAQOQIhN4CsiVnldUkiYPUFQBAQEBAQEBAQEBAQEBAQEBQRxWoFAAFjAwICUAWMIQAAAaQRxWoFAAFjAwICUAWMIQAAAa/gBTQU1TVU5HCiAgICAg/gBMVE4xNTZBVDAyUDA2AMQ=
  DRM.card0.VGA.1:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  Date: Fri May 20 11:20:14 2011
  DistUpgraded: Log time: 2011-05-03 09:09:17.573737
  DistroCodename: natty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1862]
 Subsystem: ASUSTeK Computer Inc. Device [1043:1862]
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: ASUSTeK Computer Inc. P50IJ
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic 
root=UUID=59f9e85c-7640-46a4-9844-626f6dd584e9 ro quiet splash vt.handoff=7
  Renderer: Unknown
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to natty on 2011-05-03 (17 days ago)
  dmi.bios.date: 12/04/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: P50IJ
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr203:bd12/04/2009:svnASUSTeKComputerInc.:pnP50IJ:pvr1.0:rvnASUSTeKComputerInc.:rnP50IJ:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: P50IJ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu2
  version.ia32-libs: ia32-libs 20090808ubuntu13
  version.libdrm2: libdrm2 2.4.23-1ubuntu6
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2
  version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110107+b795ca6e-0ubuntu7

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

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


[Desktop-packages] [Bug 1729086] [NEW] Upgrading fontconfig-config causes fonts to look aliased

2017-10-31 Thread Sworddragon
Public bug reported:

I'm using Ubuntu 18.04 dev and upgrading fontconfig-config to version
2.12.6-0ubuntu1 changed its dependencies from "fonts-dejavu-core | ttf-
bitstream-vera | fonts-freefont-ttf | gsfonts-x11, ucf (>= 0.29)" to
"ucf (>= 0.29), fonts-dejavu-core | ttf-bitstream-vera | fonts-
liberation | fonts-freefont" which caused at default fonts-dejavu-core
being additionally installed.

My system has also ttf-mscorefonts-installer installed which utilizes
custom rules to emulate the sharp looking fonts behavior Windows systems
had. But installing fonts-dejavu-core alone causes this sharp look to
get aliased again in the most places. A workaround for fontconfig-config
is to install fonts-liberation as it seems to not break the sharp look.

I can't tell exactly which of the 3 possible packages is the main cause for 
this issue:
- Is that the installation of fonts-dejavu-core alone breaks the look a bug?
- Needs ttf-mscorefonts-installer an update to take over priority or such?
- Or is it possible that fontconfig-config could also technically support 
ttf-mscorefonts-installer as additional fonts dependency choice?

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

** Affects: fonts-dejavu (Ubuntu)
 Importance: Undecided
 Status: New

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

** Also affects: fonts-dejavu (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  Upgrading fontconfig-config causes fonts to look aliased

Status in fontconfig package in Ubuntu:
  New
Status in fonts-dejavu package in Ubuntu:
  New
Status in msttcorefonts package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 18.04 dev and upgrading fontconfig-config to version
  2.12.6-0ubuntu1 changed its dependencies from "fonts-dejavu-core |
  ttf-bitstream-vera | fonts-freefont-ttf | gsfonts-x11, ucf (>= 0.29)"
  to "ucf (>= 0.29), fonts-dejavu-core | ttf-bitstream-vera | fonts-
  liberation | fonts-freefont" which caused at default fonts-dejavu-core
  being additionally installed.

  My system has also ttf-mscorefonts-installer installed which utilizes
  custom rules to emulate the sharp looking fonts behavior Windows
  systems had. But installing fonts-dejavu-core alone causes this sharp
  look to get aliased again in the most places. A workaround for
  fontconfig-config is to install fonts-liberation as it seems to not
  break the sharp look.

  I can't tell exactly which of the 3 possible packages is the main cause for 
this issue:
  - Is that the installation of fonts-dejavu-core alone breaks the look a bug?
  - Needs ttf-mscorefonts-installer an update to take over priority or such?
  - Or is it possible that fontconfig-config could also technically support 
ttf-mscorefonts-installer as additional fonts dependency choice?

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

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


[Desktop-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser

2017-10-31 Thread Norbert
** Also affects: usb-creator (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  Steps to reproduce:
  1. Install any Gtk3 application such as Firefox or Chromium.
  2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS, 
"sftp://; = SFTP/SSH and so on)
- 3. Try to save file to the remote location from Gtk3 application.
+ 3. Try to save/open file to/from the remote location from Gtk3 application.
  
  Expected results:
  * user is able to find network folder and save/open file to/from it with 
GtkFileChooser dialog
  
  Actual results:
  * user is unable to find network folder and save/open file to/from it with 
GtkFileChooser dialog and many user applications are affected
  
  -
  Original bug description is below:
  
  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do it.
  
  In the mean time, every user of every application switching to GTK+3 --
  including Chromium, at some point between 58 and 60 -- (a change which
  happened in 16.04 LTS!!), loses the functionality to open or save
  directly to a network share.
  
  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day.
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares.
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.
  
  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3 package.
  
  Thanks in advance.
  
  Colin

** Description changed:

  Steps to reproduce:
- 1. Install any Gtk3 application such as Firefox or Chromium.
+ 1. Install any Gtk3 application such as Firefox or Chromium which use modern 
file-chooser dialog. 
  2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS, 
"sftp://; = SFTP/SSH and so on)
  3. Try to save/open file to/from the remote location from Gtk3 application.
  
  Expected results:
  * user is able to find network folder and save/open file to/from it with 
GtkFileChooser dialog
  
  Actual results:
  * user is unable to find network folder and save/open file to/from it with 
GtkFileChooser dialog and many user applications are affected
  
  -
  Original bug description is below:
  
  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do it.
  
  In the mean time, every user of every application switching to GTK+3 --
  including Chromium, at some point between 58 and 60 -- (a change which
  happened in 16.04 LTS!!), loses the functionality to open or save
  directly to a network share.
  
  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day.
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares.
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.
  
  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3 package.
  
  Thanks in advance.
  
  Colin

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

Title:
  GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
  shares in file chooser

Status in GTK+:
  Confirmed
Status in brasero package in Ubuntu:
  New
Status in chromium package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in gdebi package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in meld package in Ubuntu:
  New
Status in remmina package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in transmission package in Ubuntu:
  New
Status in usb-creator package in Ubuntu:
  New
Status in vinagre package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install any Gtk3 application such as Firefox or Chromium which use modern 
file-chooser dialog. 
  2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS, 
"sftp://; = SFTP/SSH and so on)
  3. Try to save/open file to/from the remote location from Gtk3 application.

  Expected results:
  * user is able to 

[Desktop-packages] [Bug 1729083] Re: nautilus-desktop crashed with signal 5 in _XReply()

2017-10-31 Thread Apport retracing service
*** This bug is a duplicate of bug 1725764 ***
https://bugs.launchpad.net/bugs/1725764

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  nautilus-desktop crashed with signal 5 in _XReply()

Status in nautilus package in Ubuntu:
  New

Bug description:
  error

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 16:31:35 2017
  ExecutablePath: /usr/bin/nautilus-desktop
  InstallationDate: Installed on 2017-10-31 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: nautilus-desktop
  ProcEnviron:
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CO.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgnome-desktop-3.so.12
  Title: nautilus-desktop crashed with signal 5 in _XReply()
  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/nautilus/+bug/1729083/+subscriptions

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


[Desktop-packages] [Bug 1467588] Re: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. (proc

2017-10-31 Thread Janbert Cahilig
how to fix this?

** Changed in: unity (Ubuntu)
 Assignee: (unassigned) => Janbert Cahilig (soulschester)

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

Title:
  Gtk-Message: GtkDialog mapped without a transient parent. This is
  discouraged. Gtk-Message: GtkDialog mapped without a transient parent.
  This is discouraged.  (process:17035): GLib-CRITICAL **:
  g_slice_set_config: assertion 'sys_page_size == 0' failed

Status in Unity:
  Expired
Status in apport package in Ubuntu:
  New
Status in synaptic package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in zenity package in Ubuntu:
  Confirmed

Bug description:
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

  (process:17035): GLib-CRITICAL **: g_slice_set_config: assertion
  'sys_page_size == 0' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Jun 22 16:56:16 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.26, 3.19.0-18-generic, x86_64: installed
   virtualbox, 4.3.26, 3.19.0-20-generic, x86_64: installed
   virtualbox, 4.3.26, 3.19.0-21-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1854]
  InstallationDate: Installed on 2015-06-02 (20 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Hewlett-Packard HP 2000 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic 
root=UUID=9ac32e8e-1bbd-4aa9-8f25-2b79e4052d96 ro quiet splash
  SourcePackage: unity
  UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   
  dmi.bios.date: 06/13/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.3A
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1854
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 64.2A
  dmi.chassis.asset.tag: 5CG3400HTV
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.3A:bd06/13/2013:svnHewlett-Packard:pnHP2000NotebookPC:pvr088F130059160:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 2000 Notebook PC
  dmi.product.version: 088F130059160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Mon Jun 22 15:28:27 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 845 
   vendor LGD
  xserver.version: 2:1.17.1-0ubuntu3

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

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


[Desktop-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser

2017-10-31 Thread Norbert
For meld see bug 1335457.

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

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

Title:
  GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
  shares in file chooser

Status in GTK+:
  Confirmed
Status in brasero package in Ubuntu:
  New
Status in chromium package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in gdebi package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in meld package in Ubuntu:
  New
Status in remmina package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in transmission package in Ubuntu:
  New
Status in vinagre package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install any Gtk3 application such as Firefox or Chromium.
  2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS, 
"sftp://; = SFTP/SSH and so on)
  3. Try to save file to the remote location from Gtk3 application.

  Expected results:
  * user is able to find network folder and save/open file to/from it with 
GtkFileChooser dialog

  Actual results:
  * user is unable to find network folder and save/open file to/from it with 
GtkFileChooser dialog and many user applications are affected

  -
  Original bug description is below:

  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day.
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares.
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

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

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


[Desktop-packages] [Bug 1728412] Re: Titlebar of firefox does not respond to touch screen

2017-10-31 Thread Sebastien Bacher
There is an upstream report about that on
https://bugzilla.gnome.org/show_bug.cgi?id=786910

** Changed in: gnome-shell (Ubuntu)
   Status: New => Triaged

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

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

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

Title:
  Titlebar of firefox does not respond to touch screen

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  I have a laptop with a touch screen and a new installation of 17.10.

  For the most part the touch screen is supported ok. I can move around
  most windows ok, I can zoom in the pdf viewer with a two-finger-pinch
  gesture. However, firefox has a differently looking toolbar and I can
  neither move the window, nor does it react to tapping the
  minimise/maximise/close buttons.

  I assume that I am running wayland by looking at these variables:

  echo $WAYLAND_DISPLAY $XDG_SESSION_DESKTOP $XDG_SESSION_TYPE 
  wayland-0 ubuntu wayland
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   peter 10998 F...m pulseaudio
   /dev/snd/controlC0:  peter 10998 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=f1546bcb-f4e8-4393-a32e-0f014e1e9bd3
  InstallationDate: Installed on 2017-10-29 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: HP HP Pavilion x2 Detachable
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=e11fcd52-994f-4f5f-814f-f95ea37ccc46 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8181
  dmi.board.vendor: HP
  dmi.board.version: 42.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.13:bd03/14/2016:svnHP:pnHPPavilionx2Detachable:pvr:rvnHP:rn8181:rvr42.25:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Pavilion x2 Detachable
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, SMB/CIFS, SFTP/SSH network shares in file chooser

2017-10-31 Thread Norbert
** Description changed:

  Steps to reproduce:
  1. Install any Gtk3 application such as Firefox or Chromium.
- 2. Mount network location through fstab or file-manager (SMB/CIFS, SFTP/SSH 
and so on)
+ 2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS, 
"sftp://; = SFTP/SSH and so on)
  3. Try to save file to the remote location from Gtk3 application.
  
  Expected results:
  * user is able to find network folder and save/open file to/from it with 
GtkFileChooser dialog
  
  Actual results:
  * user is unable to find network folder and save/open file to/from it with 
GtkFileChooser dialog and many user applications are affected
- 
  
  -
  Original bug description is below:
  
  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do it.
  
  In the mean time, every user of every application switching to GTK+3 --
  including Chromium, at some point between 58 and 60 -- (a change which
  happened in 16.04 LTS!!), loses the functionality to open or save
  directly to a network share.
  
  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day.
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares.
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.
  
  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3 package.
  
  Thanks in advance.
  
  Colin

** Summary changed:

- GTK+3 doesn't show FUSE/GVFS, SMB/CIFS, SFTP/SSH network shares in file 
chooser
+ GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares 
in file chooser

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

Title:
  GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
  shares in file chooser

Status in GTK+:
  Confirmed
Status in brasero package in Ubuntu:
  New
Status in chromium package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in gdebi package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in remmina package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in transmission package in Ubuntu:
  New
Status in vinagre package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install any Gtk3 application such as Firefox or Chromium.
  2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS, 
"sftp://; = SFTP/SSH and so on)
  3. Try to save file to the remote location from Gtk3 application.

  Expected results:
  * user is able to find network folder and save/open file to/from it with 
GtkFileChooser dialog

  Actual results:
  * user is unable to find network folder and save/open file to/from it with 
GtkFileChooser dialog and many user applications are affected

  -
  Original bug description is below:

  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day.
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares.
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

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

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


[Desktop-packages] [Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics

2017-10-31 Thread Adrian
I had the same problem with Intel + AMD tandem on a desktop. I solved it
by adding in /etc/environment:

MUTTER_ALLOW_HYBRID_GPUS=1

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

Title:
  gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid
  graphics

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gdm3 package in Fedora:
  Confirmed

Bug description:
  I've just upgraded to Ubuntu 17.10 and switched the login manager from
  sddm to gdm3. Unfortunately it doesn't list the -wayland sessions. The
  /usr/share/xsessions folder indeed only contains the -xorg -related
  sessions:

  $ ls -la /usr/share/xsessions
  total 36
  drwxr-xr-x   2 root root  4096 okt 18 16:00 .
  drwxr-xr-x 427 root root 20480 okt 18 15:56 ..
  -rw-r--r--   1 root root   201 okt 13 12:56 gnome-xorg.desktop
  -rw-r--r--   1 root root  2354 aug 23 16:39 plasma.desktop
  -rw-r--r--   1 root root   262 okt 13 12:56 ubuntu-xorg.desktop

  How can I enable the ubuntu-wayland session please?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.26.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 16:37:47 2017
  InstallationDate: Installed on 2016-09-05 (408 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to artful on 2017-10-18 (0 days ago)

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

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


[Desktop-packages] [Bug 1727043] Re: random screen rotation of laptop disply when using additional screen.

2017-10-31 Thread Sebastien Bacher
** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

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

** Bug watch added: github.com/systemd/systemd/issues #7151
   https://github.com/systemd/systemd/issues/7151

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/7151
   Importance: Unknown
   Status: Unknown

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

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

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

Title:
  random screen rotation of laptop disply when using additional screen.

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I'm on 17.10.  One screen - the laptop screen - rotates at random,
  typically when a video is playing, but not, I think always.  It
  rotates 180 degrees and stays upside down.  Mouse movememnts are
  reversed (ie correct for  the orientation of the screen).

  I tried

  gsettings set org.gnome.settings-daemon.plugins.orientation active
  false

  following a thread here https://askubuntu.com/questions/968169/screen-
  randomly-rotates-on-ubuntu-17-10/968284

  but it doesn't stop the behaviour.

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

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


[Desktop-packages] [Bug 1728412] Re: Titlebar of firefox does not respond to touch screen

2017-10-31 Thread Sebastien Bacher
other report https://bugzilla.gnome.org/show_bug.cgi?id=770185

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

Title:
  Titlebar of firefox does not respond to touch screen

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  I have a laptop with a touch screen and a new installation of 17.10.

  For the most part the touch screen is supported ok. I can move around
  most windows ok, I can zoom in the pdf viewer with a two-finger-pinch
  gesture. However, firefox has a differently looking toolbar and I can
  neither move the window, nor does it react to tapping the
  minimise/maximise/close buttons.

  I assume that I am running wayland by looking at these variables:

  echo $WAYLAND_DISPLAY $XDG_SESSION_DESKTOP $XDG_SESSION_TYPE 
  wayland-0 ubuntu wayland
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   peter 10998 F...m pulseaudio
   /dev/snd/controlC0:  peter 10998 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=f1546bcb-f4e8-4393-a32e-0f014e1e9bd3
  InstallationDate: Installed on 2017-10-29 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: HP HP Pavilion x2 Detachable
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=e11fcd52-994f-4f5f-814f-f95ea37ccc46 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8181
  dmi.board.vendor: HP
  dmi.board.version: 42.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.13:bd03/14/2016:svnHP:pnHPPavilionx2Detachable:pvr:rvnHP:rn8181:rvr42.25:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Pavilion x2 Detachable
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1728412] Re: Titlebar of firefox does not respond to touch screen

2017-10-31 Thread Sebastien Bacher
the issue is likely in gnome-shell/xwayland dealing with legacy x11
softwares

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

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

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

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

Title:
  Titlebar of firefox does not respond to touch screen

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  I have a laptop with a touch screen and a new installation of 17.10.

  For the most part the touch screen is supported ok. I can move around
  most windows ok, I can zoom in the pdf viewer with a two-finger-pinch
  gesture. However, firefox has a differently looking toolbar and I can
  neither move the window, nor does it react to tapping the
  minimise/maximise/close buttons.

  I assume that I am running wayland by looking at these variables:

  echo $WAYLAND_DISPLAY $XDG_SESSION_DESKTOP $XDG_SESSION_TYPE 
  wayland-0 ubuntu wayland
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   peter 10998 F...m pulseaudio
   /dev/snd/controlC0:  peter 10998 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=f1546bcb-f4e8-4393-a32e-0f014e1e9bd3
  InstallationDate: Installed on 2017-10-29 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: HP HP Pavilion x2 Detachable
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=e11fcd52-994f-4f5f-814f-f95ea37ccc46 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8181
  dmi.board.vendor: HP
  dmi.board.version: 42.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.13:bd03/14/2016:svnHP:pnHPPavilionx2Detachable:pvr:rvnHP:rn8181:rvr42.25:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Pavilion x2 Detachable
  dmi.sys.vendor: HP

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

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


[Desktop-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, SMB/CIFS, SFTP/SSH network shares in file chooser

2017-10-31 Thread Norbert
What is interesting gnome-mplayer shows my SMB/CIFS share.

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

Title:
  GTK+3 doesn't show FUSE/GVFS, SMB/CIFS, SFTP/SSH network shares in
  file chooser

Status in GTK+:
  Confirmed
Status in brasero package in Ubuntu:
  New
Status in chromium package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in gdebi package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in remmina package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in transmission package in Ubuntu:
  New
Status in vinagre package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install any Gtk3 application such as Firefox or Chromium.
  2. Mount network location through fstab or file-manager (SMB/CIFS, SFTP/SSH 
and so on)
  3. Try to save file to the remote location from Gtk3 application.

  Expected results:
  * user is able to find network folder and save/open file to/from it with 
GtkFileChooser dialog

  Actual results:
  * user is unable to find network folder and save/open file to/from it with 
GtkFileChooser dialog and many user applications are affected

  
  -
  Original bug description is below:

  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day.
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares.
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

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

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


[Desktop-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, SMB/CIFS, SFTP/SSH network shares in file chooser

2017-10-31 Thread Norbert
Gedit and Evince show my SMB/CIFS share. So some applications have
problems in their GtkFileChooser dialog code.

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

Title:
  GTK+3 doesn't show FUSE/GVFS, SMB/CIFS, SFTP/SSH network shares in
  file chooser

Status in GTK+:
  Confirmed
Status in brasero package in Ubuntu:
  New
Status in chromium package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in gdebi package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in remmina package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in transmission package in Ubuntu:
  New
Status in vinagre package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install any Gtk3 application such as Firefox or Chromium.
  2. Mount network location through fstab or file-manager (SMB/CIFS, SFTP/SSH 
and so on)
  3. Try to save file to the remote location from Gtk3 application.

  Expected results:
  * user is able to find network folder and save/open file to/from it with 
GtkFileChooser dialog

  Actual results:
  * user is unable to find network folder and save/open file to/from it with 
GtkFileChooser dialog and many user applications are affected

  
  -
  Original bug description is below:

  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day.
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares.
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

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

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


[Desktop-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, SMB/CIFS, SFTP/SSH network shares in file chooser

2017-10-31 Thread Norbert
And baobab shows my SMB/CIFS share.

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

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

Title:
  GTK+3 doesn't show FUSE/GVFS, SMB/CIFS, SFTP/SSH network shares in
  file chooser

Status in GTK+:
  Confirmed
Status in brasero package in Ubuntu:
  New
Status in chromium package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in gdebi package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in remmina package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in transmission package in Ubuntu:
  New
Status in vinagre package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install any Gtk3 application such as Firefox or Chromium.
  2. Mount network location through fstab or file-manager (SMB/CIFS, SFTP/SSH 
and so on)
  3. Try to save file to the remote location from Gtk3 application.

  Expected results:
  * user is able to find network folder and save/open file to/from it with 
GtkFileChooser dialog

  Actual results:
  * user is unable to find network folder and save/open file to/from it with 
GtkFileChooser dialog and many user applications are affected

  
  -
  Original bug description is below:

  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day.
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares.
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

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

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


[Desktop-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE network shares in file chooser

2017-10-31 Thread Norbert
Some Ubuntu users are newbies, they do not know about GVFS, FUSE and so
on, so they can't suppose to use /media folder for network filesystems.

This bug should be fixed as soon as possible. Xenial and Bionic are affected. 
Most Gtk3 applications are affected - the most common are Firefox, Google 
Chrome.

** Description changed:

+ Steps to reproduce:
+ 1. Install any Gtk3 application such as Firefox or Chromium.
+ 2. Mount network location through fstab or file-manager (SMB/CIFS, SFTP/SSH 
and so on)
+ 3. Try to save file to the remote location from Gtk3 application.
+ 
+ Expected results:
+ * user is able to find network folder and save/open file to/from it with 
GtkFileChooser dialog
+ 
+ Actual results:
+ * user is unable to find network folder and save/open file to/from it with 
GtkFileChooser dialog and many user applications are affected
+ 
+ 
+ -
+ Original bug description is below:
+ 
  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do it.
  
  In the mean time, every user of every application switching to GTK+3 --
  including Chromium, at some point between 58 and 60 -- (a change which
  happened in 16.04 LTS!!), loses the functionality to open or save
  directly to a network share.
  
- I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day. 
- They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares. 
+ I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day.
+ They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares.
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.
  
  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3 package.
  
  Thanks in advance.
  
  Colin

** Summary changed:

- GTK+3 doesn't show FUSE network shares in file chooser
+ GTK+3 doesn't show FUSE/GVFS, SMB/CIFS, SFTP/SSH network shares in file 
chooser

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

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

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

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

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

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

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

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

Title:
  GTK+3 doesn't show FUSE/GVFS, SMB/CIFS, SFTP/SSH network shares in
  file chooser

Status in GTK+:
  Confirmed
Status in brasero package in Ubuntu:
  New
Status in chromium package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in gdebi package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in remmina package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in transmission package in Ubuntu:
  New
Status in vinagre package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install any Gtk3 application such as Firefox or Chromium.
  2. Mount network location through fstab or file-manager (SMB/CIFS, SFTP/SSH 
and so on)
  3. Try to save file to the remote location from Gtk3 application.

  Expected results:
  * user is able to find network folder and save/open file to/from it with 
GtkFileChooser dialog

  Actual results:
  * user is unable to find network folder and save/open file to/from it with 
GtkFileChooser dialog and many user applications are affected

  
  -
  Original bug description is below:

  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple 

[Desktop-packages] [Bug 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane

2017-10-31 Thread Martin
I found out that I have to run scanimage -L with "sudo" to detect my
scanner.

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

Title:
  the change from libsane to libsane1 broke many (all?) 3rd party plug-
  ins for sane

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

Bug description:
  Note to SRU Team
  
  The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it 
needed to be a versioned Provides, not just a Provides.

  Impact
  ==

  1) The Debian maintainer renamed libsane to libsane1-experimental "to
  match with the soname". This apparently fixes a Lintian warning, but
  makes installing 3rd-party plug-ins hard, as they typically depend on
  "libsane", not on "libsane1". The first try to add a "Provides:
  libsane" to libsane1 (which created a virtual package) didn't make
  drivers installable that claim to depend on a minimum version of
  libsane as virtual packages are ignored in this case.

  2) The soname change might be justified by the new version breaking
  (several? most?) 3rd party plug-ins even if the library version number
  doesn't indicate any bigger change than any ordinary new version of
  the library - which might indicate that this phenomenon might be an
  upstream bug.

  libsane 1.0.25 in zesty includes libsane.so.1.25
  libsane1 1.0.27 in artful includes libsane.so.1.27

  It is to note that depending on the manufacturer for many old scanners
  there won't be new versions of the plug-ins that are recompiled like
  this.

  Test Case
  =
  Visit http://support.epson.net/linux/en/iscan_c.html
  Download the amd64 deb .tar.gz
  Unzip it.
  Install the iscan .deb from the core folder.

  It won't install before this SRU because it Depends: libsane

  Regression Potential
  
  The fix here was proposed to the Debian maintainer in July but there's been 
virtually zero response on it. In the meantime the workaround that was proposed 
initially has started to result in automatically uninstalling gtk - which makes 
the system basically useless.

  It doesn't seem like adding the Provides will make things any worse
  for third-party drivers but it has a goodme chance of making things
  better for some.

  Original Bug Report
  ===
  I don't know if that can be prevented in the long run. But both brscan (for 
my brother scanner) and iscan (for my epson scanners) have been broken by the 
change from libsane to libsane1. For iscan I have unpackaged the debian 
package, changed the dependency it contains from libsane to libsane1 and 
installed the changed package. But even then my epson scanners no more work 
leaving me without any scanner => Reporting a bug.

  Impossibility of workarounds
  
  Just installing an old version of libsane is impossible as it uninstalls 
libgtk (which depends on libsane1 which conflicts with libsane) making the 
system basically useless.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental1ubuntu2
  Uname: Linux 4.13.0-041300rc2-lowlatency x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sat Jul 29 08:38:15 2017
  EcryptfsInUse: Yes
  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/1707352/+subscriptions

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


[Desktop-packages] [Bug 1724587] Re: nautilus stops responding, Desktop too

2017-10-31 Thread teo1978
LOL just because you have had no other report you assume it's because of
an unusual configuration or hardware? That's a pretty random assumption.

Anyway, the stupidity with which bug importance in general gets set is
beyond hope, so who cares I guess. If it was only for this bug...

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

Title:
  nautilus stops responding, Desktop too

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  This happens randomly every once in a while:

  - Clicking on Nautilus' Launcher icon does nothing (it blinks for a while as 
if it was loading, then no window opens).
  - Desktop icons (icons of files and folders in the Desktop) don't respond to 
clicks or right-clicks
  - running nautilus from a terminal will not print any error message, won't 
open any nautilus window, but it will not exit either, just wait forever

  The workaround is to "ps aux | grep nautilus" to find nautilus'
  process id and kill it. Then everything goes back to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 18 16:09:05 2017
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1277x824+436+106'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2013-10-11 (1467 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1728977] Re: back to the choice of apps in alt+tab+shift

2017-10-31 Thread Sebastien Bacher
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: gnome-shell (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  back to the choice of apps in alt+tab+shift

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  back to the choice of apps in alt+tab+shift

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  Uname: Linux 4.14.0-041400rc7-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 18:21:20 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 
'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 
'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-10-30 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-31 (0 days ago)

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

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


[Desktop-packages] [Bug 1727653] Re: error: can't start new thread

2017-10-31 Thread Václav Haisman
Re #8: Is there a PPA for that?

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

Title:
  error: can't start new thread

Status in duplicity package in Ubuntu:
  In Progress

Bug description:
  $ uname -a
  Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  duplicity gets started daily via deja-dup automatically.

  Every now and then (approx. every third time) I get the following
  error:

  --

  Failed with an unknown error.

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
  manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
  fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in 
filtered_open_with_delete
  fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in 
filtered_open
  return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in 
__init__
  'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
374, in run
  create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
420, in _attach_fork_exec
  process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
  _start_new_thread(self.__bootstrap, ())
  error: can't start new thread

  --

  Restarting deja-dup manually fixes the problem and the next few days,
  automatic backup will run correctly until (see above).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:49:45 2017
  InstallationDate: Installed on 2017-10-20 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1724977] Re: two mouse cursors visible at the same time on rotated screen

2017-10-31 Thread Sebastien Bacher
** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  two mouse cursors visible at the same time on rotated screen

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When my 2nd Asus (Ancor) display is in portrait mode and is set to be
  to the left of my centered landscape display in extended mode, moving
  the mouse to roughly the left 20% of my landscape display will show a
  mouse cursor on my landcape display AND portrait display at the same
  time.  Oddly moving a window into this area only shows on the
  landscape display.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 13:43:30 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1729028] Re: gnome-shell crashes after period of inactivity

2017-10-31 Thread David Burke
I use font scaling. At one point I enabled fractional scaling but have
since completely disabled it including disabling org.gnome.mutter
.experimental-features.

"unplugging external monitor" I only use one monitor and this is a
desktop - but my 4k PB287 Asus monitor has perhaps the slowest turn on
speed ever designed by man. In the past I've ran into minor issues where
I suspect Ubuntu is simply shocked that a monitor could ever be so slow
and assumes I unplugged it then plugged it back in. So it's possible
that bug is related but hard to say for sure.

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

Title:
  gnome-shell crashes after period of inactivity

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Gnome shell crashes reliably and only after a period of inactivity
  (15+ minutes). I have not seen it crash while using the desktop - even
  for hours at a time. I suspect it has something to do with locking the
  screen or turning off the monitor. However even after attempting to
  disable both lockscreen and blank screen it still happens.

  After a crash dmesg shows [ 3726.608957] gnome-shell[2666]: segfault
  at 38 ip 7fc6a7330c30 sp 7fff0d12fe78 error 4 in
  libmutter-1.so.0.0.0[7fc6a72de000+141000]

  When the crash happens it goes back to the login screen. Logging in
  works fine.

  It happens pretty reliably but will sometimes successfully lock and
  blank the screen. I would say it happens 90% of the time I leave the
  computer alone for awhile.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 11:34:11 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'google-chrome.desktop', 'firefox.desktop', 'code.desktop', 
'org.gnome.Terminal.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
   b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25'
  InstallationDate: Installed on 2017-07-18 (105 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-18 (12 days ago)

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

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


[Desktop-packages] [Bug 1728810] Re: CUPS ERRORS

2017-10-31 Thread Sebastien Bacher
** Package changed: xorg (Ubuntu) => cups (Ubuntu)

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

Title:
  CUPS ERRORS

Status in cups package in Ubuntu:
  New

Bug description:
  There are problems in my PC about the "Server".-When I am traying to
  use my printer (wireless printer).-An advice apairs as: "failed to
  connect to server".

  I would have your help,thank You in advance.Sincerely Fernando
  Espinosa.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog:
   [  OK  ] Started Network Manager.
Starting Network Manager Wait Online...
   [  OK  ] Reached target Network.
   [  OK  ] Started Unattended Upgrades Shutdown.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Oct 31 00:32:15 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7310] [1002:9809] 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Wrestler [Radeon HD 7310] [17aa:365d]
  InstallationDate: Installed on 2016-11-27 (337 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 10103
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic 
root=UUID=e9b7906b-8c2c-4887-89be-701551b926e7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/05/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EKKT30BUS
  dmi.board.name: Remore CRB
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD EM DPK IPG
  dmi.chassis.type: 13
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrEKKT30BUS:bd03/05/2013:svnLENOVO:pn10103:pvrLenovoC345:rvnLENOVO:rnRemoreCRB:rvrWin8STDEMDPKIPG:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
  dmi.product.name: 10103
  dmi.product.version: Lenovo C345
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Oct 30 16:40:55 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: radeon

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

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


[Desktop-packages] [Bug 1728964] Re: caribou no function keys

2017-10-31 Thread Sebastien Bacher
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: caribou (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  caribou no function keys

Status in caribou package in Ubuntu:
  Incomplete

Bug description:
  caribou no function keys

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: caribou 0.4.21-2
  Uname: Linux 4.14.0-041400rc7-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 18:12:07 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-30 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: caribou
  UpgradeStatus: Upgraded to artful on 2017-10-31 (0 days ago)

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

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


[Desktop-packages] [Bug 1724137] Re: No output to external monitor via display port (and docking station)

2017-10-31 Thread Kevin
Can I do something to help solving this issue?

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

Title:
  No output to external monitor via display port (and docking station)

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

Bug description:
  Since my upgrade from ubuntu 16.04 to 17.10 the output to an external
  monitor via docking station and displayport doesn't work anymore.

  I can activate the external monitor via arandr (from xmonad) but there
  is no output.

  Disper is not working anymore (segmentation fault).

  The external monitor works with nvidia-340 drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xserver-xorg-video-nouveau 1:1.0.15-2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  BootLog:
   /dev/mapper/sda3_crypt: recovering journal
   /dev/mapper/sda3_crypt: clean, 1105421/882 files, 30688210/35399936 
blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Oct 17 07:47:40 2017
  DistUpgraded: 2017-10-16 20:56:53,501 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.28, 4.10.0-37-generic, x86_64: installed
   virtualbox, 5.1.28, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f5]
   NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Lenovo GK107GLM [Quadro K2000M] [17aa:21f5]
  InstallationDate: Installed on 2016-05-18 (516 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  MachineType: LENOVO 2447KD9
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=c2a0eb56-8f89-4a8a-b1b5-a152dfaec126 ro quiet splash acpi=force 
vt.handoff=7
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to artful on 2017-10-16 (0 days ago)
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETA3WW (2.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2447KD9
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ETA3WW(2.63):bd09/18/2015:svnLENOVO:pn2447KD9:pvrThinkPadW530:rvnLENOVO:rn2447KD9:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W530
  dmi.product.name: 2447KD9
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83+git20170928.7c711886-0ubuntu0ricotz~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Oct 17 07:38:48 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)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2
  xserver.video_driver: modeset

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

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


[Desktop-packages] [Bug 1726717] Re: Alignment of external screen limits placing of icons

2017-10-31 Thread Rüdiger Kupper
Yes, but it has immediately been closed as "won't fix".

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

Title:
  Alignment of external screen limits placing of icons

Status in Nautilus:
  Won't Fix
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Reporting against gnome-desktop since I do not know better. Please
  assign to appropriate package. Thanks!

  Using external monitors with the gnome desktop behaves unexpected in a few 
ways. One is, that the alignment of screens limits, where icons can be placed 
on that screens:
  My external monitor is higher than the internal screen of my laptop. I have 
aligned the screens at the bottom. This makes the bottom part of the (external, 
higher) screen unusable for placing icons.

  This is probably best seen on the attached screenshot.
  Thanks for caring!

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-session (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 08:49:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-12-13 (680 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1709708] Re: [Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but produces no sound on an HDMI TV until power cycled.

2017-10-31 Thread Adam Kwarciak
It is v4.14-rc4 which produced sound without playing with pulseaudio or
restarting display.

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

Title:
  [Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but
  produces no sound on an HDMI TV until power cycled.

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

Bug description:
  Upon bootup, the HDMI output connected to a Samsung TV shows up as an
  output. If this output is selected and a sound test run (either using
  the GUI or using aplay /user/share/sounds/alsa/Front_Center.wav) no
  sound is heard. Pavumeter does however show sound coming through.

  I found that sound can be fixed by allowing the display to sleep,
  waking it up, and then restarting pulseaudio (pulseaudio -k). After
  that sound output through HDMI to the TV will work until rebooted.

  The fix can be succesfully scripted as follows:

  xset dpms force off
  sleep 1
  pulseaudio -k

  The machine is an Intel NUC6CAYH, connected to a not particularly new
  Samsung 42" TV using an HDMI cable, running a fresh install of Ubuntu
  16.04.

  In earlier attempts at fixing the issue I set pulseaudio to never let
  the sound device sleep (commented out load-module module-suspend-on-
  idle in /etc/pulse/default.pa), and also set the default sampling rate
  to 48000 (default-sample-rate = 48000 in /etc/pulse/daemon.conf). Not
  sure if these settings contributed to the fix, but they are not
  sufficient on their own.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Aug  9 21:48:39 2017
  InstallationDate: Installed on 2017-08-06 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Title: [, Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio fails to detect 
card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J23203-402
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0029.2016.1124.1625:bd11/24/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-402:cvn:ct3:cvr:
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-08-06T22:55:35.510382
  mtime.conffile..etc.pulse.default.pa: 2017-08-06T22:51:49.639085

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

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


[Desktop-packages] [Bug 1725555] Re: control-center display panel cannot move monitors

2017-10-31 Thread Sebastien Bacher
thanks

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

** Also affects: gnome-control-center via
   https://bugzilla.gnome.org/show_bug.cgi?id=789711
   Importance: Unknown
   Status: Unknown

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

Title:
  control-center display panel cannot move monitors

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  Running wayland, gnome-shell, 17.10, up-to-date.

  I have two monitors plugged into my computer, a couple days ago,
  everything was fine.  Now, after a couple of crashes, and package
  upgrades, I can no longer re-arrange my monitors on the control center
  interface.  When I mouse over a monitor, the cursor changes into a
  grabby-hand, but when I click and drag, the monitors just stay where
  they are.  No movement at all.

  Things I've tried so far --

  - removing .config/monitors.xml and rebooting
  - disabling & re-enabling monitors

  I'm happy to do some debugging on this, but my searches and
  troubleshooting so far is coming up empty.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 21:03:06 2017
  InstallationDate: Installed on 2017-10-03 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1724105] Re: Privacy : Deactivating screen lock doesn't work

2017-10-31 Thread 1LinuxGuy
I updated the bug description, hoping it is clearer to understand.

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

Title:
  Privacy : Deactivating screen lock doesn't work

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  What steps do I need to follow to reproduce this bug : Install gnome-
  session. In that session, open System Settings/Privacy Uncheck Lock
  Screen.

  What did I expect to happen : When opening the lid of my laptop, I was
  expecting to see no login screen and be back right away in my session,
  without having to enter my password.

  What actually happens: After opening the lid, the screen flashes, then
  goes black. After hitting the space bar, I get the "clock screen",
  swipe up, then get login screen. Sometimes, the screen just freeze.
  Have to hard reboot.

  Side effect : Lock Screen activated, only way that the laptop will
  come back from sleep normally.

  
  Dell XPS 13 (9360)
  ---
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171016)
  Package: gnome-shell 3.26.1-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1729077] [NEW] wrong color of horizontally centered area of scan with CanoScan Lide 200

2017-10-31 Thread Helmut Tischer
Public bug reported:

This problem is 100% reproducable, also across reboots.

On a Ubuntu 16.04 and 17.04 and Windows7 system the Scanner CanoScan
Lide 200 works still completely fine.

Problem with Ubuntu 17.10 :
In a horizontally centered zone of about 1 centimeter width of the scan 
surface, over the full height of the surface, estimated 90% of the pixel values 
are completely wrong.
The distribution of the wrong pixels in this zone appears random.
With lineart and gray scan, the wrong pixels are black. With color scan, the 
wrong pixels are black or similar to red. The other pixels in the zone are a 
bit too bright. The effect is the same at all resolutions. See attached example 
snippets. The effect would continue vertically over the entire scan surface. 
The original was uniformly colored.

The scanner worked again with Ubuntu 17.10 after purging sane-
utils,libsane1,libsane-common (by overriding dependency-errors) and
installing libsane-common_1.0.25+git20150528-1ubuntu4_all.deb
libsane_1.0.25+git20150528-1ubuntu4_amd64.deb sane-
utils_1.0.25+git20150528-1ubuntu4_amd64.deb (again by overriding
dependency-errors) (and maybe re-plug scanner / reboot)

Trying these versions had the same problem as default Ubuntu 17.10:
archive.ubuntu.com : 1.0.27-1~experimental2ubuntu2.1, 
launchpad.net/~rolfbensch/+archive/ubuntu/sane-git : 1.0.27+git20171012-artful0

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Oct 31 20:48:39 2017
InstallationDate: Installed on 2015-12-31 (670 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: sane-backends
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

** Attachment added: "snippet of wrong scan. the effect would continue 
vertically over entire scan surface, and similar also bw and gray scans 
(affected pixels black)"
   
https://bugs.launchpad.net/bugs/1729077/+attachment/5001380/+files/color_speckle.jpg

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

Title:
  wrong color of horizontally centered area of scan with CanoScan Lide
  200

Status in sane-backends package in Ubuntu:
  New

Bug description:
  This problem is 100% reproducable, also across reboots.

  On a Ubuntu 16.04 and 17.04 and Windows7 system the Scanner CanoScan
  Lide 200 works still completely fine.

  Problem with Ubuntu 17.10 :
  In a horizontally centered zone of about 1 centimeter width of the scan 
surface, over the full height of the surface, estimated 90% of the pixel values 
are completely wrong.
  The distribution of the wrong pixels in this zone appears random.
  With lineart and gray scan, the wrong pixels are black. With color scan, the 
wrong pixels are black or similar to red. The other pixels in the zone are a 
bit too bright. The effect is the same at all resolutions. See attached example 
snippets. The effect would continue vertically over the entire scan surface. 
The original was uniformly colored.

  The scanner worked again with Ubuntu 17.10 after purging sane-
  utils,libsane1,libsane-common (by overriding dependency-errors) and
  installing libsane-common_1.0.25+git20150528-1ubuntu4_all.deb
  libsane_1.0.25+git20150528-1ubuntu4_amd64.deb sane-
  utils_1.0.25+git20150528-1ubuntu4_amd64.deb (again by overriding
  dependency-errors) (and maybe re-plug scanner / reboot)

  Trying these versions had the same problem as default Ubuntu 17.10:
  archive.ubuntu.com : 1.0.27-1~experimental2ubuntu2.1, 
launchpad.net/~rolfbensch/+archive/ubuntu/sane-git : 1.0.27+git20171012-artful0

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Oct 31 20:48:39 2017
  InstallationDate: Installed on 2015-12-31 (670 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  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/1729077/+subscriptions

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


[Desktop-packages] [Bug 1716359] Re: Unplugging headset with audio panel open mutes internal mic

2017-10-31 Thread Brian Murray
Hello Will, or anyone else affected,

Accepted unity-control-center into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unity-control-center/15.04.0+16.04.20170214-0ubuntu2 in a few hours,
and then in the -proposed repository.

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

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

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

** Changed in: unity-control-center (Ubuntu)
   Status: In Progress => Invalid

** Changed in: unity-control-center (Ubuntu Xenial)
   Status: New => Fix Committed

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

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

Title:
  Unplugging headset with audio panel open mutes internal mic

Status in OEM Priority Project:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Invalid
Status in unity-control-center source package in Xenial:
  Fix Committed

Bug description:
  
  Impact
  ==
  This is required by OEM team.

  Test Case
  =
  1. Open System Settings -> Sound -> select the input tab
  2. Plug headset and select Headset on Unknown Audio Device dialog.
  3. Check external mic is working
  4. Adjust the internal microphone volume.(Just change the volume value.)
  5. Adjust headset input volume around 100% in Input tab from Sound settings
  6. Unplug headset
  7. Check internet mic status

  Make sure the internal mic is not muted.

  Regression Potential
  ===
  - Make sure that plugging/unplugging headphones does the correct thing.
  - Make sure that manually selecting an headphone actually switch mic.
  - Please also check that output sound works too.

  Original Bug Report
  ===
  This bug was reported by our OEM team, I'm opening this public bug.

  The internal microphone is muted after he headset is unplugged when the 
System Settings is running.
  We can not reproduce this bug when closed the System Settings window before 
unplugged the headset.

  Reproduce steps:
  1. Open System Settings -> Sound -> select the input tab
  2. Plug headset and select Headset on Unknown Audio Device dialog.
  3. Check external mic is working
  4. Adjust the internal microphone volume.(Just change the volume value.)
  5. Adjust headset input volume around 100% in Input tab from Sound settings
  6. Unplug headset
  7. Check internet mic status

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1716359/+subscriptions

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


[Desktop-packages] [Bug 1724105] Re: Privacy : Deactivating screen lock doesn't work

2017-10-31 Thread 1LinuxGuy
** Description changed:

  What steps do I need to follow to reproduce this bug : Install gnome-
  session. In that session, open System Settings/Privacy Uncheck Lock
  Screen.
  
  What did I expect to happen : When opening the lid of my laptop, I was
  expecting to see no login screen and be back right away in my session,
  without having to enter my password.
  
  What actually happens: After opening the lid, the screen flashes, then
  goes black. After hitting the space bar, I get the "clock screen", swipe
  up, then get login screen. Sometimes, the screen just freeze. Have to
  hard reboot.
  
- Been like this also on Ubuntu Gnome 17.04
+ Side effect : Lock Screen activated, only way that the laptop will come
+ back from sleep normally.
+ 
  
  Dell XPS 13 (9360)
  ---
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171016)
  Package: gnome-shell 3.26.1-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

Title:
  Privacy : Deactivating screen lock doesn't work

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  What steps do I need to follow to reproduce this bug : Install gnome-
  session. In that session, open System Settings/Privacy Uncheck Lock
  Screen.

  What did I expect to happen : When opening the lid of my laptop, I was
  expecting to see no login screen and be back right away in my session,
  without having to enter my password.

  What actually happens: After opening the lid, the screen flashes, then
  goes black. After hitting the space bar, I get the "clock screen",
  swipe up, then get login screen. Sometimes, the screen just freeze.
  Have to hard reboot.

  Side effect : Lock Screen activated, only way that the laptop will
  come back from sleep normally.

  
  Dell XPS 13 (9360)
  ---
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171016)
  Package: gnome-shell 3.26.1-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1724587] Re: nautilus stops responding, Desktop too

2017-10-31 Thread Sebastien Bacher
the wiki page you are pointing states for low
"Bugs that affect unusual end-user configurations or uncommon hardware "

that's the case here since that's the only report of a such issue in
years

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

Title:
  nautilus stops responding, Desktop too

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  This happens randomly every once in a while:

  - Clicking on Nautilus' Launcher icon does nothing (it blinks for a while as 
if it was loading, then no window opens).
  - Desktop icons (icons of files and folders in the Desktop) don't respond to 
clicks or right-clicks
  - running nautilus from a terminal will not print any error message, won't 
open any nautilus window, but it will not exit either, just wait forever

  The workaround is to "ps aux | grep nautilus" to find nautilus'
  process id and kill it. Then everything goes back to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 18 16:09:05 2017
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1277x824+436+106'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2013-10-11 (1467 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1729028] Re: gnome-shell crashes after period of inactivity

2017-10-31 Thread Sebastien Bacher
could be similar to https://bugzilla.gnome.org/show_bug.cgi?id=789501,
do you use hidpi scaling?

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

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

Title:
  gnome-shell crashes after period of inactivity

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Gnome shell crashes reliably and only after a period of inactivity
  (15+ minutes). I have not seen it crash while using the desktop - even
  for hours at a time. I suspect it has something to do with locking the
  screen or turning off the monitor. However even after attempting to
  disable both lockscreen and blank screen it still happens.

  After a crash dmesg shows [ 3726.608957] gnome-shell[2666]: segfault
  at 38 ip 7fc6a7330c30 sp 7fff0d12fe78 error 4 in
  libmutter-1.so.0.0.0[7fc6a72de000+141000]

  When the crash happens it goes back to the login screen. Logging in
  works fine.

  It happens pretty reliably but will sometimes successfully lock and
  blank the screen. I would say it happens 90% of the time I leave the
  computer alone for awhile.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 11:34:11 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'google-chrome.desktop', 'firefox.desktop', 'code.desktop', 
'org.gnome.Terminal.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
   b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25'
  InstallationDate: Installed on 2017-07-18 (105 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-18 (12 days ago)

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

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


[Desktop-packages] [Bug 1729019] Re: Ambiance color affecting Gnome-Shell themes under Ubuntu Session

2017-10-31 Thread Sebastien Bacher
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: gnome-shell (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Ambiance color affecting Gnome-Shell themes under Ubuntu Session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1717023
  
https://launchpad.net/ubuntu/+source/ubuntu-themes/16.10+17.10.20171012.1-0ubuntu1

  After this change other gnome-shell themes not looking well under
  ubuntu session

  See the screenshot

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

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


[Desktop-packages] [Bug 1724105] Re: Privacy : Deactivating screen lock doesn't work

2017-10-31 Thread 1LinuxGuy
** Description changed:

- In System Settings, Privacy, Deactivating lock screen : does not work
- after opening laptop lid.
+ What steps do I need to follow to reproduce this bug : Open System
+ Settings/Privacy Uncheck Lock Screen.
  
- Still presented by the GDM users/password lock screen.
- 
- Worst case : sometimes, presented by the screen saver window, hitting
- space bar to reveal desktop cause a shell freeze.
+ What did I expect to happen : When opening the lid of my laptop, I was 
expecting to see no login screen and be back right away in my session, without 
having to enter my password.
+ 
+ What actually happens: After opening the lid, the screen flashes, then goes 
black. After hitting the space bar, I get the "clock screen", swipe up, then 
get login screen. Sometimes, the screen just freeze. Have to hard reboot.
  
  Been like this also on Ubuntu Gnome 17.04
+ 
  
  Dell XPS 13 (9360)
  ---
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171016)
  Package: gnome-shell 3.26.1-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

** Description changed:

- What steps do I need to follow to reproduce this bug : Open System
- Settings/Privacy Uncheck Lock Screen.
+ What steps do I need to follow to reproduce this bug : Install gnome-
+ session. In that session, open System Settings/Privacy Uncheck Lock
+ Screen.
  
- What did I expect to happen : When opening the lid of my laptop, I was 
expecting to see no login screen and be back right away in my session, without 
having to enter my password.
- 
- What actually happens: After opening the lid, the screen flashes, then goes 
black. After hitting the space bar, I get the "clock screen", swipe up, then 
get login screen. Sometimes, the screen just freeze. Have to hard reboot.
+ What did I expect to happen : When opening the lid of my laptop, I was
+ expecting to see no login screen and be back right away in my session,
+ without having to enter my password.
+ 
+ What actually happens: After opening the lid, the screen flashes, then
+ goes black. After hitting the space bar, I get the "clock screen", swipe
+ up, then get login screen. Sometimes, the screen just freeze. Have to
+ hard reboot.
  
  Been like this also on Ubuntu Gnome 17.04
- 
  
  Dell XPS 13 (9360)
  ---
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171016)
  Package: gnome-shell 3.26.1-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

Title:
  Privacy : Deactivating screen lock doesn't work

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  What steps do I need to follow to reproduce this bug : Install gnome-
  session. In that session, open System Settings/Privacy Uncheck Lock
  Screen.

  What did I expect to happen : When opening the lid of my laptop, I was
  expecting to see no login screen and be back right away in my session,
  without having to enter my password.

  What actually happens: After opening the lid, the screen flashes, then
  goes black. After hitting the space bar, I get the "clock screen",
  swipe up, then get login screen. Sometimes, the screen just freeze.
  Have to hard reboot.

  Side effect : Lock Screen activated, only way that the laptop will
  come back from sleep normally.

  
  Dell XPS 13 (9360)
  ---
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171016)
  Package: gnome-shell 3.26.1-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go 

[Desktop-packages] [Bug 1729028] Re: gnome-shell crashes after period of inactivity

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

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

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

Title:
  gnome-shell crashes after period of inactivity

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Gnome shell crashes reliably and only after a period of inactivity
  (15+ minutes). I have not seen it crash while using the desktop - even
  for hours at a time. I suspect it has something to do with locking the
  screen or turning off the monitor. However even after attempting to
  disable both lockscreen and blank screen it still happens.

  After a crash dmesg shows [ 3726.608957] gnome-shell[2666]: segfault
  at 38 ip 7fc6a7330c30 sp 7fff0d12fe78 error 4 in
  libmutter-1.so.0.0.0[7fc6a72de000+141000]

  When the crash happens it goes back to the login screen. Logging in
  works fine.

  It happens pretty reliably but will sometimes successfully lock and
  blank the screen. I would say it happens 90% of the time I leave the
  computer alone for awhile.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 11:34:11 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'google-chrome.desktop', 'firefox.desktop', 'code.desktop', 
'org.gnome.Terminal.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
   b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25'
  InstallationDate: Installed on 2017-07-18 (105 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-18 (12 days ago)

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

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


[Desktop-packages] [Bug 1724810] Re: 17.10/wayland causing flashes in virtualbox

2017-10-31 Thread Jeremy Bicha
** No longer affects: mutter (Ubuntu)

** Also affects: virtualbox (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

** No longer affects: virtualbox (Ubuntu Artful)

** Changed in: gnome-shell (Ubuntu Artful)
   Status: New => Triaged

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

Title:
  17.10/wayland causing flashes in virtualbox

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Artful:
  Triaged

Bug description:
  Hi,

  just as a quick response:

  I've installed the new 17.10 Desktop for testing in a virtual machine
  (VirtualBox 5.1.20 running on MacOS), and while it installed smoothly
  and booted instantly, there's a problem with the graphics (probably
  related to wayland): Especially when moving the mouse or starting new
  programs the screen flashes white every few seconds or sometimes shows
  just a blank grey screen for about a second. Not suited for regular
  work.

  But I have no clue which component precisely is causing that problem.

  regards

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

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


[Desktop-packages] [Bug 1729071] Re: totem crashed with SIGSEGV in wl_proxy_add_listener()

2017-10-31 Thread Apport retracing service
*** This bug is a duplicate of bug 1723130 ***
https://bugs.launchpad.net/bugs/1723130

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1723130
   totem crashed with SIGSEGV in wl_proxy_add_listener()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  totem crashed with SIGSEGV in wl_proxy_add_listener()

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  can't see an "avi" video

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: libgstreamer1.0-0 1.12.3-1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 20:59:03 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-01-03 (301 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
   LANG=it_IT.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f14f601477c : testb  
$0x4,0x28(%rdi)
   PC (0x7f14f601477c) ok
   source "$0x4" ok
   destination "0x28(%rdi)" (0x0028) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gstreamer1.0
  StacktraceTop:
   wl_proxy_add_listener () from 
/usr/lib/x86_64-linux-gnu/libwayland-client.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   eglSwapBuffers () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   cogl_onscreen_swap_buffers_with_damage () from 
/usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: totem crashed with SIGSEGV in wl_proxy_add_listener()
  UpgradeStatus: Upgraded to artful on 2017-10-22 (9 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1724105] Re: Privacy : Deactivating screen lock doesn't work

2017-10-31 Thread 1LinuxGuy
More infos...

I first installed a gnome-session in Ubuntu 17.10, to get a more Vanilla
Gnome. Now that I've modified the GDM Lock Screen to Vanilla Gnome*, so
far it works. The laptop correctly comes back from sleep after opening
the lid, and I'm presented with the "normal" clock screen. Then, I swipe
up to get the Login screen.

But... If I deactivate the Lock Screen, in the Privacy Settings, it
won't work. It behaves erratically, screen flashes, goes black, and come
back to the login screen.


* Link https://didrocks.fr/2017/09/11/ubuntu-gnome-shell-in-artful-day-11/

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

Title:
  Privacy : Deactivating screen lock doesn't work

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  In System Settings, Privacy, Deactivating lock screen : does not work
  after opening laptop lid.

  Still presented by the GDM users/password lock screen.

  Worst case : sometimes, presented by the screen saver window, hitting
  space bar to reveal desktop cause a shell freeze.

  Been like this also on Ubuntu Gnome 17.04

  Dell XPS 13 (9360)
  ---
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171016)
  Package: gnome-shell 3.26.1-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1724105] Re: Privacy : Deactivating screen lock doesn't work

2017-10-31 Thread 1LinuxGuy
** Description changed:

- In System Settings, Confidentiality, Deactivating lock screen : does not
- work after opening laptop lid.
+ In System Settings, Privacy, Deactivating lock screen : does not work
+ after opening laptop lid.
  
  Still presented by the GDM users/password lock screen.
  
  Worst case : sometimes, presented by the screen saver window, hitting
  space bar to reveal desktop cause a shell freeze.
  
  Been like this also on Ubuntu Gnome 17.04
  
  Dell XPS 13 (9360)
- --- 
+ ---
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171016)
  Package: gnome-shell 3.26.1-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

Title:
  Privacy : Deactivating screen lock doesn't work

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  In System Settings, Privacy, Deactivating lock screen : does not work
  after opening laptop lid.

  Still presented by the GDM users/password lock screen.

  Worst case : sometimes, presented by the screen saver window, hitting
  space bar to reveal desktop cause a shell freeze.

  Been like this also on Ubuntu Gnome 17.04

  Dell XPS 13 (9360)
  ---
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171016)
  Package: gnome-shell 3.26.1-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1729028] Re: gnome-shell crashes after period of inactivity

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

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

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

Title:
  gnome-shell crashes after period of inactivity

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Gnome shell crashes reliably and only after a period of inactivity
  (15+ minutes). I have not seen it crash while using the desktop - even
  for hours at a time. I suspect it has something to do with locking the
  screen or turning off the monitor. However even after attempting to
  disable both lockscreen and blank screen it still happens.

  After a crash dmesg shows [ 3726.608957] gnome-shell[2666]: segfault
  at 38 ip 7fc6a7330c30 sp 7fff0d12fe78 error 4 in
  libmutter-1.so.0.0.0[7fc6a72de000+141000]

  When the crash happens it goes back to the login screen. Logging in
  works fine.

  It happens pretty reliably but will sometimes successfully lock and
  blank the screen. I would say it happens 90% of the time I leave the
  computer alone for awhile.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 11:34:11 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'google-chrome.desktop', 'firefox.desktop', 'code.desktop', 
'org.gnome.Terminal.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
   b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25'
  InstallationDate: Installed on 2017-07-18 (105 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-18 (12 days ago)

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

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


[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

2017-10-31 Thread Spencer Seidel
... and my issue is now resolved in Ubuntu 17.10, at least on a fresh
install. Not sure what changed, but no changes are necessary to
/etc/nsswitch.conf in order to make resolving DNS work with internal
domains while connect to openconnect VPN. Probably I should stick with
LTS :-)

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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


[Desktop-packages] [Bug 1723080] Re: Caldav Issues with evolution 3.26

2017-10-31 Thread Jürgen Kübler
Received a response from bugzi...@gnome.org.  Basically a complain about
not filing the bug report correctly and a request for further
information that goes beyond my level of expertise as end user.

Advise like

"Also see https://wiki.gnome.org/Apps/Evolution/Debugging#CalDAV how to provide
debug output which would be needed here."

is not helpful to me.

I can't help here, anymore and will stop using bugzilla for gnome.org

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

Title:
  Caldav Issues with evolution 3.26

Status in evolution package in Ubuntu:
  New

Bug description:
  I noticed a series of issues with caldav  when switching to Ubuntu
  17.10.  Everthing works fine with Ubuntu GNOME 17.04.

  Error message during ics import:
  "Cannot receive calendar objects: Failed to put data: HTTP error code 201 
(Created): The server responded with an HTML page, which can mean there’s an 
error on the server or with the client request."
  The import successfully finished regardless.  It's still a nuisance.

  Attempts to pick a date (calendar entry and tasks) are followed by the 
message:
  "Evolution want to inhibit shortcuts.
  You can restore shortcuts by pressing Shift-Ctrl-Escape"

  Creating new tasks: Same error message as for ics import.  Tasks are
  only stored when date *and* time are specified. Error message needs to
  be ignored and window to be close with 'discard changes'.

  Update of calender appointments (external): just does not work

  Could not test handling of confirmations of meeting invites, yet

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

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


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

2017-10-31 Thread Łukasz Zemczak
Hello Mathieu, or anyone else affected,

Accepted network-manager-applet into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/network-manager-applet/1.2.6-0ubuntu0.16.04.4 in a few hours, and then
in the -proposed repository.

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

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

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

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

Title:
  Support for WPA Enterprise wireless networks

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Xenial:
  Fix Committed
Status in ubiquity source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  In some installations, WPA2 Enterprise support is required to have access to 
the network to complete the installation.

  [Test cases]
  1) Start installer from ubuntu-desktop image.
  2) Follow the prompts to connect to the wireless network
  3) Validate that a new dialog appears asking for the network password or 
credentials.

  [Regression potential]
  This impacts all wireless connections and so the type of regression to look 
for in general failure to connect to a secured wireless network when the 
authentication settings are correct (pre-shared key is correct), or in cases of 
connecting to an unsecured network.

  For network-manager-applet:
  - ubiquity uses nma gir to implement above
  - the nma gir is missbuilt in xenial, and does not have correct dependencies, 
thus is not usable in the same process when both NM and NMA are in use. This 
was fixed in zesty. I have cherrypicked a fix for misscompiled gir. There is 
minimal regression potential (just a rebuild) because there are no reverse 
dependencies of the nma gir in xenial. And there are unlikely to be any 
external users of nma gir on xenial, since it is broken / has wrong 
dependencies.

  ---

  Ubiquity doesn't appear to support WPA-Enterprise wifi networks --
  there's just a single textbox shown to enter a passphrase, but most
  WPA-Enterprise will require at least a specific username and password,
  and possibly certificates.

  NM should already export this information on DBus, it should be a
  matter of using libnm-gtk to query the user for the connection
  information rather than prompting for it directly from the installer.

  : "If the selected network does require
  authentication, Network Manager’s standard dialog should open for you
  to enter those authentication details as soon as you choose
  “Connect…”."

  (Not to be confused with bug 1018160, about WEP networks.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1107935/+subscriptions

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


[Desktop-packages] [Bug 1107935] Re: Support for WPA Enterprise wireless networks

2017-10-31 Thread Łukasz Zemczak
Hello Mathieu, or anyone else affected,

Accepted ubiquity into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/ubiquity/2.21.63.5
in a few hours, and then in the -proposed repository.

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

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

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

** Changed in: ubiquity (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

** Changed in: network-manager-applet (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  Support for WPA Enterprise wireless networks

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Xenial:
  Fix Committed
Status in ubiquity source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  In some installations, WPA2 Enterprise support is required to have access to 
the network to complete the installation.

  [Test cases]
  1) Start installer from ubuntu-desktop image.
  2) Follow the prompts to connect to the wireless network
  3) Validate that a new dialog appears asking for the network password or 
credentials.

  [Regression potential]
  This impacts all wireless connections and so the type of regression to look 
for in general failure to connect to a secured wireless network when the 
authentication settings are correct (pre-shared key is correct), or in cases of 
connecting to an unsecured network.

  For network-manager-applet:
  - ubiquity uses nma gir to implement above
  - the nma gir is missbuilt in xenial, and does not have correct dependencies, 
thus is not usable in the same process when both NM and NMA are in use. This 
was fixed in zesty. I have cherrypicked a fix for misscompiled gir. There is 
minimal regression potential (just a rebuild) because there are no reverse 
dependencies of the nma gir in xenial. And there are unlikely to be any 
external users of nma gir on xenial, since it is broken / has wrong 
dependencies.

  ---

  Ubiquity doesn't appear to support WPA-Enterprise wifi networks --
  there's just a single textbox shown to enter a passphrase, but most
  WPA-Enterprise will require at least a specific username and password,
  and possibly certificates.

  NM should already export this information on DBus, it should be a
  matter of using libnm-gtk to query the user for the connection
  information rather than prompting for it directly from the installer.

  : "If the selected network does require
  authentication, Network Manager’s standard dialog should open for you
  to enter those authentication details as soon as you choose
  “Connect…”."

  (Not to be confused with bug 1018160, about WEP networks.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1107935/+subscriptions

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


[Desktop-packages] [Bug 1699670] Re: Gnome screensaver lock always responses "incorrect password" when last active window's language is not the language of the password

2017-10-31 Thread Andrew Frolikov
I hadn't mention that I've been using lightdm. After switching to GDM
the issue was resolved.

** Description changed:

  Environment:
- OS - Ubuntu 16.04.2 LTS, DE - GNOME Shell 3.20.4, gnome-screensaver 3.6.1
+ OS - Ubuntu 16.04.2 LTS, DE - GNOME Shell 3.20.4, lightdm, gnome-screensaver 
3.6.1
  
  Prerequisites:
   - say, you have 2 language layouts installed
   - their layouts/character tables are completely different, so there is no 
chance you can type your password correctly using any language keyboard layout 
(e.g. you have en/ru, but not en/de etc.)
  
  Actual behavior:
  When the screen is being locked while your active window has the language 
which is not your password language set, you won't be able to log in back. Log 
in form shows that the language of the password is set (EN in my case) but it 
always returns 'Incorrect password' message in response to the correct input. 
Switching language layout using the keyboard shortcut or GUI doesn't help.
  'Switch user' trick allows you to log in back though, but it's a crutch.

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

Title:
  Gnome screensaver lock always responses "incorrect password" when last
  active window's language is not the language of the password

Status in gnome-screensaver package in Ubuntu:
  Confirmed

Bug description:
  Environment:
  OS - Ubuntu 16.04.2 LTS, DE - GNOME Shell 3.20.4, lightdm, gnome-screensaver 
3.6.1

  Prerequisites:
   - say, you have 2 language layouts installed
   - their layouts/character tables are completely different, so there is no 
chance you can type your password correctly using any language keyboard layout 
(e.g. you have en/ru, but not en/de etc.)

  Actual behavior:
  When the screen is being locked while your active window has the language 
which is not your password language set, you won't be able to log in back. Log 
in form shows that the language of the password is set (EN in my case) but it 
always returns 'Incorrect password' message in response to the correct input. 
Switching language layout using the keyboard shortcut or GUI doesn't help.
  'Switch user' trick allows you to log in back though, but it's a crutch.

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

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


[Desktop-packages] [Bug 1727356] Re: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed

2017-10-31 Thread Traumflug
Success, part II:

When attempting a Wayland session, the relevant syslog section grew from
107 lines to 396 lines. 'gnome-shell' messages are gone, it looks like a
session gets actually started. And then there are now a lot of messages
like this one:

Oct 31 18:08:01 piccard gnome-screensav[2194]: Anzeige kann nicht geöffnet 
werden:
Oct 31 18:08:01 piccard org.gnome.SettingsDaemon.Power.desktop[2208]: Anzeige 
kann nicht geöffnet werden:
Oct 31 18:08:01 piccard org.gnome.SettingsDaemon.Clipboard.desktop[2242]: 
Anzeige kann nicht geöffnet werden:

"Anzeige kann nicht geöffnet werden" = "can't open display".

So far no idea how this display should be set/activated/opened.

** Attachment added: "GDM-debug-shader-code-removed"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727356/+attachment/5001320/+files/GDM-debug-shader-code-removed

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

Title:
  Wayland does not start up on "Integrated Graphics Chipset: Intel(R)
  G33": Shader compilation failed

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  Upgraded from 17.04 today.

  Steps to reproduce:

  - Start the PC or log out/end session in case it's running with an Xorg 
desktop already.
  - Attempt to log in, using 'Ubuntu'

  Expected to happen:

  Desktop appears.

  Actually happening:

  5 seconds of black screen, then the login screen appears again.

  Partial diagnosis:

  - Logging in using 'Ubuntu on Xorg' works fine and as expected.

  - Extracted a syslog of such a failed attempt, see attached file.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-05-04 (539 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Package: gnome-shell 3.26.1-0ubuntu5
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags: artful package-from-proposed third-party-packages
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1722121] Re: Gnome-Terminal ignores theme, preferences is unavailable, and copy not working when launching from right-click desktop

2017-10-31 Thread Hunter Buchanan
I should add that mine wasn't a fresh install of Ubuntu 17.10, but
rather an upgrade from 17.04 (do-release-upgrade).

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

Title:
  Gnome-Terminal ignores theme, preferences is unavailable, and copy not
  working when launching from right-click desktop

Status in gnome-terminal package in Ubuntu:
  Confirmed

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

  gnome-terminal:
Installed: 3.24.2-0ubuntu4
Candidate: 3.24.2-0ubuntu4
Version table:
   *** 3.24.2-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Expected behavior

  Right-clicking on the desktop and selecting "Open Terminal" should
  give me the same terminal as running gnome-terminal or or opening
  terminal in the activity view.

  What happens
  Gnome-Terminal launches with the correct GTK theme, but not the correct theme 
variant (light instead of dark). The "Preferences" option is gone from the top 
bar. Trying to copy something from the terminal and pasting outputs 
"unavailable".

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  8 22:49:01 2017
  InstallationDate: Installed on 2017-09-30 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/ubuntu/+source/gnome-terminal/+bug/1722121/+subscriptions

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


[Desktop-packages] [Bug 1722121] Re: Gnome-Terminal ignores theme, preferences is unavailable, and copy not working when launching from right-click desktop

2017-10-31 Thread Hunter Buchanan
I'm seeing this issue as well. I can also confirm that copying doesn't
work when Terminal is opened by right-clicking the desktop and selecting
Open Terminal, but DOES work when I've opened it by other means.

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

Title:
  Gnome-Terminal ignores theme, preferences is unavailable, and copy not
  working when launching from right-click desktop

Status in gnome-terminal package in Ubuntu:
  Confirmed

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

  gnome-terminal:
Installed: 3.24.2-0ubuntu4
Candidate: 3.24.2-0ubuntu4
Version table:
   *** 3.24.2-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Expected behavior

  Right-clicking on the desktop and selecting "Open Terminal" should
  give me the same terminal as running gnome-terminal or or opening
  terminal in the activity view.

  What happens
  Gnome-Terminal launches with the correct GTK theme, but not the correct theme 
variant (light instead of dark). The "Preferences" option is gone from the top 
bar. Trying to copy something from the terminal and pasting outputs 
"unavailable".

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  8 22:49:01 2017
  InstallationDate: Installed on 2017-09-30 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/ubuntu/+source/gnome-terminal/+bug/1722121/+subscriptions

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


[Desktop-packages] [Bug 1727356] Re: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed

2017-10-31 Thread Traumflug
Success! Applying the attached Diff keeps gnome-shell working for Xorg,
still makes these shader compilation errors going away. More of this
success see next comment here.

This Diff is not a solution, of course, but it should narrow down the
problematic area a lot.

** Patch added: "remove-shader-code.diff"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727356/+attachment/5001319/+files/remove-shader-code.diff

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

Title:
  Wayland does not start up on "Integrated Graphics Chipset: Intel(R)
  G33": Shader compilation failed

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  Upgraded from 17.04 today.

  Steps to reproduce:

  - Start the PC or log out/end session in case it's running with an Xorg 
desktop already.
  - Attempt to log in, using 'Ubuntu'

  Expected to happen:

  Desktop appears.

  Actually happening:

  5 seconds of black screen, then the login screen appears again.

  Partial diagnosis:

  - Logging in using 'Ubuntu on Xorg' works fine and as expected.

  - Extracted a syslog of such a failed attempt, see attached file.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-05-04 (539 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Package: gnome-shell 3.26.1-0ubuntu5
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags: artful package-from-proposed third-party-packages
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1722121] Re: Gnome-Terminal ignores theme, preferences is unavailable, and copy not working when launching from right-click desktop

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

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

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

Title:
  Gnome-Terminal ignores theme, preferences is unavailable, and copy not
  working when launching from right-click desktop

Status in gnome-terminal package in Ubuntu:
  Confirmed

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

  gnome-terminal:
Installed: 3.24.2-0ubuntu4
Candidate: 3.24.2-0ubuntu4
Version table:
   *** 3.24.2-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Expected behavior

  Right-clicking on the desktop and selecting "Open Terminal" should
  give me the same terminal as running gnome-terminal or or opening
  terminal in the activity view.

  What happens
  Gnome-Terminal launches with the correct GTK theme, but not the correct theme 
variant (light instead of dark). The "Preferences" option is gone from the top 
bar. Trying to copy something from the terminal and pasting outputs 
"unavailable".

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  8 22:49:01 2017
  InstallationDate: Installed on 2017-09-30 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/ubuntu/+source/gnome-terminal/+bug/1722121/+subscriptions

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


  1   2   3   >