[Desktop-packages] [Bug 1762042] Re: Changing system language corrupts date format

[Launchpad Bug Tracker]

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

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

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

Title:
  Changing system language corrupts date format

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  ubuntu 18.04 (07.04.2018 updated)
  my system language was turkish and i changed to english but calendar remained 
in Turkish (with wrong format)
  please check screenshots

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

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

[Desktop-packages] [Bug 1765981] Re: File manager crashes to open hard disk partition

[Launchpad Bug Tracker]

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

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

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

Title:
  File manager crashes to open hard disk partition

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  What you expected to happen
  
  I expected nautilus to mount and open the partition right first time

  What actually happened
  
  File manager crashed (window closed), but drive was mounted. I had to reopen 
it.

  Steps followed
  
  I have a disk partition (filetype: fuse) which I tried to open using nautilus 
(navigation panel > other locations). See attached snapshot. I am using 18.04 
Beta2.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 21 22:05:18 2018
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'196'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1068x689+135+167'"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency']"
  InstallationDate: Installed on 2018-04-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/usr/bin/zsh
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1778317] [NEW] Owncloud always ask for password at startup

[Philippe Lucidarme]

Public bug reported:

At startup, ownCloud client always ask for password with the following
message:

Please enter ownCloud password:

User: 
Account: x...@xxx.xx

Click here to request an app password from the web interface.

Reading from keychain failed with error: 'No keychain service available'

I think ownCloud can't get password from gnome-keyring or something like
this...

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

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

Title:
  Owncloud always ask for password at startup

Status in gnome-shell-extension-appindicator package in Ubuntu:
  New

Bug description:
  At startup, ownCloud client always ask for password with the following
  message:

  Please enter ownCloud password:

  User: 
  Account: x...@xxx.xx

  Click here to request an app password from the web interface.

  Reading from keychain failed with error: 'No keychain service
  available'

  I think ownCloud can't get password from gnome-keyring or something
  like this...

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

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

[Desktop-packages] [Bug 1718533] Re: change from xorg evdev driver to libinput driver breaks touchscreen calibration configuration

[Launchpad Bug Tracker]

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

** Changed in: xserver-xorg-input-libinput (Ubuntu)
   Status: New => Confirmed

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

Title:
  change from xorg evdev driver to libinput driver breaks touchscreen
  calibration configuration

Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed

Bug description:
  when using xorg evdev driver with a touchscreen, it is possible to
  configure the touchscreen calibration with InputClass options, e.g.:

Option  "MinX"  "4128"
Option  "MaxX"  "62751"
Option  "MinY"  "4075"
Option  "MaxY"  "63636"

  however, the move to the libinput xorg driver does not use this so
  upgrades result in touchscreens that no longer are calibrated.
  Additionally, the normal touchscreen calibration program in Ubuntu,
  xinput_calibrator, does not work with the libinput xorg driver.  This
  results in a mis/un-calibrated touchscreen, and no way to calibrate
  it.

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

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

[Desktop-packages] [Bug 1718533] Re: change from xorg evdev driver to libinput driver breaks touchscreen calibration configuration

[Bert Van de Poel]

I had finally convinced an archaeological project I work with to upgrade
from Ubuntu 12.04 to a newer version and now our toughbook CF-19
touchscreens can't be calibrated :(

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

Title:
  change from xorg evdev driver to libinput driver breaks touchscreen
  calibration configuration

Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed

Bug description:
  when using xorg evdev driver with a touchscreen, it is possible to
  configure the touchscreen calibration with InputClass options, e.g.:

Option  "MinX"  "4128"
Option  "MaxX"  "62751"
Option  "MinY"  "4075"
Option  "MaxY"  "63636"

  however, the move to the libinput xorg driver does not use this so
  upgrades result in touchscreens that no longer are calibrated.
  Additionally, the normal touchscreen calibration program in Ubuntu,
  xinput_calibrator, does not work with the libinput xorg driver.  This
  results in a mis/un-calibrated touchscreen, and no way to calibrate
  it.

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

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

[Desktop-packages] [Bug 1778225] Re: Can't switch UI language for single users, only system-wide

[Gunnar Hjalmarsson]

/etc/default/locale and ~/.pam_environment are the only files which are
written to via the GUIs, and both of them look normal to me. The locale
output, however, is not consistent with those files. With that
~/.pam_environment file it ought to look like this:

LANG=en_US.UTF-8
LANGUAGE=en
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=de_DE.UTF-8
LC_TIME=de_DE.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=de_DE.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=de_DE.UTF-8
LC_NAME=de_DE.UTF-8
LC_ADDRESS=de_DE.UTF-8
LC_TELEPHONE=de_DE.UTF-8
LC_MEASUREMENT=de_DE.UTF-8
LC_IDENTIFICATION=de_DE.UTF-8
LC_ALL=

So the variables set by ~/.pam_environment seem to be overridden somehow
by settings somewhere else. Actually, I see in the attached
ProcEnviron.txt file that every single locale category has been set
explicitly (to German) - also variables which are not set by any of
those two files such as LC_CTYPE and LC_MESSAGES.

More questions:

Are you possibly accessing the PC remotely from some other machine via
SSH or something?

What's the output from these commands:

  dpkg-query -W gdm3

  cat /etc/environment

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

Title:
  Can't switch UI language for single users, only system-wide

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

Bug description:
  The title says it all ... I tried to switch the language of the user
  interface to English instead of German for a single user, which did
  not work. Applying the new language system-wide did the job, but
  forced all other users on that pc to have their graphical sessions in
  the new language too.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 22 14:56:26 2018
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2018-05-29 (23 days ago)

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

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

[Desktop-packages] [Bug 1764005] Re: Black-screen on boot with nvidia 390 for Budgie, MATE, Xubuntu, Kubuntu

[Emerson Novais Oliveira]

I have the same problem and the Gnome 3 eats a lot of my CPU reducing
the performance.

My machine:
Ubuntu 18.04
Vostro 3500
Intel Core i5 540m
NVidia GT-310m

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

Title:
  Black-screen on boot with nvidia 390 for Budgie, MATE, Xubuntu,
  Kubuntu

Status in nvidia-prime package in Ubuntu:
  Fix Released

Bug description:
  Upgraded from Ubuntu Budgie 17.10 to 18.04.  After the plymouth splash
  left with a black screen.

  Purged all the nivdia-* packages and rebooted - graphical logon and
  logged in ok with nouveau.

  Tried software & updates to reinstall the nvidia 390 drivers.
  Rebooted.  Left at black screen again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-driver-390 390.48-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Sat Apr 14 21:42:04 2018
  InstallationDate: Installed on 2016-11-26 (503 days ago)
  InstallationMedia: budgie-remix 16.10 "Budgie-remix" -  amd64 (20161013)
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: Upgraded to bionic on 2018-04-14 (0 days ago)

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

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

[Desktop-packages] [Bug 1216059] Re: Firefox difficulties with https and IPv6 addresses

[Jeff Lane]

Very old bug, won't fix as it's not a server issue

** Changed in: dell-poweredge
   Status: Confirmed => Invalid

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

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

Title:
  Firefox difficulties with https and IPv6 addresses

Status in The Dell-poweredge project:
  Invalid
Status in firefox package in Ubuntu:
  Invalid

Bug description:
  When a webserver uses an untrusted certificate (such as a self-signed
  certificate), Firefox encounters multiple bugs trying to use https
  over IPv6. The main upstream bug report is
   but
   also seems
  relevant.

  On Ubuntu 12.04 with firefox package 23.0+build2-0ubuntu0.12.04.1, I
  am not even prompted to add a security exception. I found that with
  Firefox on Ubuntu 10.04, I am prompted to add a security exception but
  have no way to click "add exception" (though we only care about Ubuntu
  12.04 for PowerEdge). This is problematic for Dell because iDRAC and
  CMC ship with self-signed certificates, so there is no way to reach
  the iDRAC or CMC web interface over IPv6 from Firefox. I see the same
  behavior whether entering an IPv6 address (e.g.
  https://[2001:DB8::1]/), when manually specifying the port (e.g.
  https://[2001:DB8::1]:443/) or when specifying a hostname with only an
   record (e.g. https://host-ipv6.example.com/). The same URLs work
  with Chromium.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1216059/+subscriptions

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

[Desktop-packages] [Bug 1456338] Re: USB floppy drive is running without floppy

[P_Aleksandrov]

> Ahh, ok.. try disabling udisks to see if that is the cause:
> systemctl stop udisks2.service
The wrong behaviour remained. Also when I booted in rescue mode (root shell), 
then resumed normal boot, stopped udisks2 and connected the device.
Is it possible that the problem is in systemd?

Now I have some old user configuration files (in /home) which I have not
deleted when reinstalled the system. But if I logout, the problem with
the device remains.

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

Title:
  USB floppy drive is running without floppy

Status in udisks2 package in Ubuntu:
  New

Bug description:
  When I connect USB floppy drive (Gembird) without floppy under Ubuntu, the 
drive engine seems to be running (the floppy drive LED is on and the drive is 
sounding). The same behaviour takes place if I connect the drive with a floppy 
and then remove the floppy. It seems that the system accesses the drive 
permanently when there is no floppy. Under Windows XP it works normally - when 
there is no floppy, the LED and engine are switched off. I have tried Ubuntu 
14.10 (amd64) with upstart, LXQt and KDE 5; Ubuntu 15.04 with systemd, LXQt - 
the same behaviour.
  If I boot using bash as init (init=/bin/bash) and connect the floppy drive 
after boot, the engine is off (the normal behaviour).
  lsof /dev/sdb during engine running outputs nothing.

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

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

[Desktop-packages] [Bug 1778225] Re: Can't switch UI language for single users, only system-wide

[Michael Satke]

Gunnar, thank you for your help. Here are my results:
__

locale

LANG=de_DE.UTF-8
LANGUAGE=de:en
LC_CTYPE=de_DE.UTF-8
LC_NUMERIC=de_DE.UTF-8
LC_TIME=de_DE.UTF-8
LC_COLLATE=de_DE.UTF-8
LC_MONETARY=de_DE.UTF-8
LC_MESSAGES=de_DE.UTF-8
LC_PAPER=de_DE.UTF-8
LC_NAME=de_DE.UTF-8
LC_ADDRESS=de_DE.UTF-8
LC_TELEPHONE=de_DE.UTF-8
LC_MEASUREMENT=de_DE.UTF-8
LC_IDENTIFICATION=de_DE.UTF-8
LC_ALL=
__

cat /etc/default/locale

LANG="de_AT.UTF-8"
LANGUAGE="de_AT:de"

__

cat ~/.pam_environment

LANGUAGEDEFAULT=en
LANGDEFAULT=en_US.UTF-8
LC_NUMERIC=de_DE.UTF-8
LC_TIME=de_DE.UTF-8
LC_MONETARY=de_DE.UTF-8
LC_PAPER=de_DE.UTF-8
LC_NAME=de_DE.UTF-8
LC_ADDRESS=de_DE.UTF-8
LC_TELEPHONE=de_DE.UTF-8
LC_MEASUREMENT=de_DE.UTF-8
LC_IDENTIFICATION=de_DE.UTF-8
PAPERSIZE=a4
__

I did not do any manual language configuring.

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

Title:
  Can't switch UI language for single users, only system-wide

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

Bug description:
  The title says it all ... I tried to switch the language of the user
  interface to English instead of German for a single user, which did
  not work. Applying the new language system-wide did the job, but
  forced all other users on that pc to have their graphical sessions in
  the new language too.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 22 14:56:26 2018
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2018-05-29 (23 days ago)

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

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

[Desktop-packages] [Bug 1778143] Re: SIGSEV when turning on display while screensaver is active (gnome-screensaver-dialog crash)

[fossfreedom]

Please install the debug symbols as described here and follow the
instructions also to produce a backtrace.

Thanks

https://wiki.ubuntu.com/DebuggingProgramCrash

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

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

Title:
  SIGSEV when turning on display while screensaver is active (gnome-
  screensaver-dialog crash)

Status in gnome-screensaver package in Ubuntu:
  Incomplete

Bug description:
  Since the update to Ubuntu 18.04 (ubuntu budgie) the screensaver
  stopped working.

  Description of the error:

  When I lock the screen, the display turns black (as intended). However, when 
I press a key or move the mouse to turn the display again, no login-dialog is 
shown - instead I see the lockscreen wallpaper and the mouse cursor shows 
graphical glitches (becoming invisible and visible when moving it).
  I can unlock again by typing `gnome-screensaver-command -d` into a tty.

  I have found out, that the program 'gnome-screensaver-dialog' crashes
  with a SIGSEV and causes the described failure. Purging and
  reinstalling the package 'gnome-screensaver' did not help. Running
  'gnome-screensaver-dialog' with gdb generates the attached output
  (which is hopefully useful for tracking down the problem).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-screensaver 3.6.1-8ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Fri Jun 22 00:15:10 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-14 (127 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  SourcePackage: gnome-screensaver
  UpgradeStatus: Upgraded to bionic on 2018-04-29 (53 days ago)

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

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

[Desktop-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

[jmkeller]

Same issue started post 18.04 upgrade.   AMD FX at 4.7 GHz goes into
thermal shutdown about a minute after getting booted up and into the
desktop.   I installed cpuefreqd and set the policy to power save high
(limiting the frequency scaling to about 50%) in order to keep the CPU
temp below the thermal cut off limit.

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

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

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edir   2354 F pulseaudio
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d
  InstallationDate: Installed on 2018-04-27 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-nouveau 1:1.0.15-2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 10HX.M034.20110426.SSH
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: RF511/RF411/RF711
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: 10HX
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 

[Desktop-packages] [Bug 1778225] Re: Can't switch UI language for single users, only system-wide

[Gunnar Hjalmarsson]

Hmm.. That's a mystery.

Can you please run the following commands and show the complete output
in a comment here:

locale

cat /etc/default/locale

cat ~/.pam_environment

Also, can you recall that you have configured languages/locales manually
somehow?

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

Title:
  Can't switch UI language for single users, only system-wide

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

Bug description:
  The title says it all ... I tried to switch the language of the user
  interface to English instead of German for a single user, which did
  not work. Applying the new language system-wide did the job, but
  forced all other users on that pc to have their graphical sessions in
  the new language too.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 22 14:56:26 2018
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2018-05-29 (23 days ago)

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

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

Re: [Desktop-packages] [Bug 1778093] Re: install starts with 2 screens. insteadl of 1

[George White]

Yes, there was a cable plugged in to the other port, but the monitor on 
the other end was set to a different input and I expected it to have 
been ignored.  The 'bug' is that during installation, there's no need to 
set up multiple screens, except as clones of each other, so that the 
installation will work from any screen.  If you're looking at the 
'wrong' monitor,  the initial symptom is indistinguishable from the 
installation hanging which makes the source of the problem harder to 
track down.  Part of the illusion is because the mouse was so far off 
screen, it seemed like it was frozen as well.

On 06/21/2018 07:21 PM, Daniel van Vugt wrote:
> You do indeed seem to have 2 monitors plugged in.
>
> If the LG is known to be faulty then please unplug it, and this is not a bug.
> If the LG is expected to work, then this is a bug.
>
> Do you find any difference/improvement in logging into "Ubuntu" (Xorg)
> vs "Ubuntu on Wayland"?
The only issue was trying to track down logs for diagnosis.
>
> ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
>
> ** Changed in: xorg-server (Ubuntu)
> Status: New => Incomplete
>

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

Title:
  install starts with 2 screens. insteadl of 1

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  The installation system comes up expecting 2 displays and the window
  decorations are in the non visible screen as is the control panel for
  performing the install.  By bringing the cursor to the active screen
  (it starts out far left off screen), I can start a terminal from the
  menu and then start gnome-control-center to fix the display and then
  the installation can proceed.

  I've seen this reported as a freeze, but it's not and just an issue
  with the display.  Perhaps because it fails to detect the proper
  monitor (mine is an ASUS VS22).  I also have an LG monitor, but this
  has a different problem by returning bad config info (the screen size
  is reported incorrectly)

  This occurred when installing the current 18.04 desktop distribution
  and behaves the same for EFI or BIOS boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.394
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 21 08:52:56 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3e91] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 13fe:5400 Kingston Technology Company Inc. 
   Bus 001 Device 003: ID 0c45:7605 Microdia 
   Bus 001 Device 002: ID 1bcf:053e Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. H370M-D3H
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: Default string
  dmi.board.name: H370M D3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd02/13/2018:svnGigabyteTechnologyCo.,Ltd.:pnH370M-D3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH370MD3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: H370M-D3H
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: 

[Desktop-packages] [Bug 1086374] Re: Backup cannot be restored (no signature chains found)

[c sights]

I encountered this backtrace when I had the wrong remote path.  It would
be better to have an error message for that case such as "No backup
chains found.  Did you specify correct remote path?"

Thanks!
C.

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

Title:
  Backup cannot be restored (no signature chains found)

Status in Duplicity:
  New
Status in Unity Control Center:
  New
Status in duplicity package in Ubuntu:
  Confirmed

Bug description:
  I get:

  [root@ ]# duplicity list-current-files scp://192.168.11.2/backup/caw-server1
  Local and Remote metadata are synchronized, no sync needed.
  Last full backup date: none
  Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1391, in 
  with_tempdir(main)
  File "/usr/bin/duplicity", line 1384, in with_tempdir
  fn()
  File "/usr/bin/duplicity", line 1322, in main
  list_current(col_stats)
  File "/usr/bin/duplicity", line 598, in list_current
  sig_chain = col_stats.get_signature_chain_at_time(time)
  File "/usr/lib64/python2.6/site-packages/duplicity/collections.py", line 977, 
in get_signature_chain_at_time
  raise CollectionsError("No signature chains found")
  CollectionsError: No signature chains found

  when trying to list files from my backup.  But the files seem ok outside of 
duplicity,
  This affects multiple servers backing up to different locations.

  OS is CentOS 6.2 x86
  Duplicity 0.6.18 from the repos

  ---
  Using archive dir: /root/.cache/duplicity/1dc0bb65e1eb97582ca301487786e1b1
  Using backup name: 1dc0bb65e1eb97582ca301487786e1b1
  Import of duplicity.backends.ftpsbackend Succeeded
  Import of duplicity.backends.u1backend Succeeded
  Import of duplicity.backends.ftpbackend Succeeded
  Import of duplicity.backends.webdavbackend Succeeded
  Import of duplicity.backends.hsibackend Succeeded
  Import of duplicity.backends.imapbackend Succeeded
  Import of duplicity.backends.botobackend Succeeded
  Import of duplicity.backends.cloudfilesbackend Succeeded
  Import of duplicity.backends.rsyncbackend Succeeded
  Import of duplicity.backends.sshbackend Succeeded
  Import of duplicity.backends.tahoebackend Succeeded
  Import of duplicity.backends.localbackend Succeeded
  Import of duplicity.backends.giobackend Succeeded
  Import of duplicity.backends.gdocsbackend Succeeded
  Main action: list-current
  

  duplicity 0.6.18 (February 29, 2012)
  Args: /usr/bin/duplicity -v9 list-current-files --no-encryption 
scp://192.168.11.1/backup/caw-server2
  Linux caw-server2.cawdekempen.be 2.6.32-220.23.1.el6.x86_64 #1 SMP Mon Jun 18 
18:58:52 BST 2012 x86_64 x86_64
  /usr/bin/python 2.6.6 (r266:84292, Jun 18 2012, 14:18:47) 
  [GCC 4.4.6 20110731 (Red Hat 4.4.6-3)]
  

  Local and Remote metadata are synchronized, no sync needed.
  0 files exist on backend
  0 files exist in cache
  Extracting backup chains from list of files: []
  Last full backup date: none
  Collection Status
  -
  Connecting with backend: SftpBackend
  Archive dir: /root/.cache/duplicity/1dc0bb65e1eb97582ca301487786e1b1

  Found 0 secondary backup chains.
  No backup chains with active signatures found
  No orphaned or incomplete backup sets found.
  Using temporary directory /tmp/duplicity-ckTuyx-tempdir
  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1391, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1384, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1322, in main
  list_current(col_stats)
File "/usr/bin/duplicity", line 598, in list_current
  sig_chain = col_stats.get_signature_chain_at_time(time)
File "/usr/lib64/python2.6/site-packages/duplicity/collections.py", line 
977, in get_signature_chain_at_time
  raise CollectionsError("No signature chains found")
  CollectionsError: No signature chains found

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

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

[Desktop-packages] [Bug 1778225] Re: Can't switch UI language for single users, only system-wide

[Michael Satke]

Gunnar, of course i logged out and in. Reboots did not help either.

** Attachment added: "Screenshots"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1778225/+attachment/5155616/+files/screenshots.png

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

Title:
  Can't switch UI language for single users, only system-wide

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

Bug description:
  The title says it all ... I tried to switch the language of the user
  interface to English instead of German for a single user, which did
  not work. Applying the new language system-wide did the job, but
  forced all other users on that pc to have their graphical sessions in
  the new language too.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 22 14:56:26 2018
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2018-05-29 (23 days ago)

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

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

[Desktop-packages] [Bug 1778244] Re: Text rendering too high (inside padding)

[John Runyon]

** Attachment added: "Screenshot of padding"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1778244/+attachment/5155603/+files/Screenshot%20from%202018-06-22%2010-25-16.png

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

Title:
  Text rendering too high (inside padding)

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Text is being rendered too high. This causes it to render inside
  padding, or worse yet inside the border of an input box (causing it to
  be cut off).

  Issue also occurs on Chrome (Version 67.0.3396.87 (Official Build) (64-bit)).
  Issue began occurring after upgrade to 18.04 from 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 66.0.3359.181-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBaYy/OAQEBASwYAQOAPiJ46giloldPoigPUFSlSwBxT4EAgYCpQLMA0cDRAAEBBHQAMPJwWoCwWIoAbVUhAAAe/wBVMk4xNDQ0MDAzMjgK/ABWWDI4ODBNTAogICAg/QAYVR9yHgAKICAgICAgAXgCAy3xUpAfAQIDBxYEExQFEhEGFSAhIiMJHweDAQAAbQMMABAAADwgAGADAgECOoAYcTgtQFgsRQBtVSEAAB4BHYAYcRwWIFgsJQBtVSEAAJ4BHQByUdAeIG4oVQBtVSEAAB6MCtCKIOAtEBA+lgBtVSEAABgAhg==
   modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 1920x1200 1920x1080 
1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 1920x1080 1920x1080 
1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1280x800 
1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600 720x576 
720x480 720x480 640x480 640x480 640x480 720x400
  DRM.card0-DP-2:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBaYwcgAQEBAQ8NAQOAJh6MKiyVplhKmiYhUFS/74CBgIGPcU9hT0lPRU8xTzFAMCoAmFEAKkAwcBMAeC0RAAAe/wBBMFkwMzE1MTAyNTEK/QAySx5SDgAKICAgICAg/ABWRzE5MQogICAgICAgAIE=
   modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 
832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  Date: Fri Jun 22 10:32:41 2018
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg'
   
'/usr/share/ubuntu:/home/jrunyon/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2018-03-07 (106 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  InstalledPlugins:
   /usr/lib/mozilla/plugins:
 => libgnome-shell-browser-plugin.so
   (size: 18856 bytes, mtime: Mon Apr 23 15:29:28 2018)
  Load-Avg-1min: 0.64
  Load-Processes-Running-Percent:   0.1%
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=eb4622c9-14d3-4a4e-bc10-49a41ebdb495 ro quiet splash 
nospec_store_bypass_disable nospectre_v2 noibrs noibpb nopti vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to bionic on 2018-06-18 (4 days ago)
  dmi.bios.date: 07/24/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0049.2017.0724.1541
  dmi.board.name: NUC7i7BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J31145-303
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0049.2017.0724.1541:bd07/24/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-303:cvn:ct3:cvr:
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1778244] Re: Text rendering too high (inside padding)

[John Runyon]

Minimum I've found to reproduce: 

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

Title:
  Text rendering too high (inside padding)

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Text is being rendered too high. This causes it to render inside
  padding, or worse yet inside the border of an input box (causing it to
  be cut off).

  Issue also occurs on Chrome (Version 67.0.3396.87 (Official Build) (64-bit)).
  Issue began occurring after upgrade to 18.04 from 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 66.0.3359.181-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBaYy/OAQEBASwYAQOAPiJ46giloldPoigPUFSlSwBxT4EAgYCpQLMA0cDRAAEBBHQAMPJwWoCwWIoAbVUhAAAe/wBVMk4xNDQ0MDAzMjgK/ABWWDI4ODBNTAogICAg/QAYVR9yHgAKICAgICAgAXgCAy3xUpAfAQIDBxYEExQFEhEGFSAhIiMJHweDAQAAbQMMABAAADwgAGADAgECOoAYcTgtQFgsRQBtVSEAAB4BHYAYcRwWIFgsJQBtVSEAAJ4BHQByUdAeIG4oVQBtVSEAAB6MCtCKIOAtEBA+lgBtVSEAABgAhg==
   modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 1920x1200 1920x1080 
1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 1920x1080 1920x1080 
1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1280x800 
1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600 720x576 
720x480 720x480 640x480 640x480 640x480 720x400
  DRM.card0-DP-2:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBaYwcgAQEBAQ8NAQOAJh6MKiyVplhKmiYhUFS/74CBgIGPcU9hT0lPRU8xTzFAMCoAmFEAKkAwcBMAeC0RAAAe/wBBMFkwMzE1MTAyNTEK/QAySx5SDgAKICAgICAg/ABWRzE5MQogICAgICAgAIE=
   modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 
832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  Date: Fri Jun 22 10:32:41 2018
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg'
   
'/usr/share/ubuntu:/home/jrunyon/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2018-03-07 (106 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  InstalledPlugins:
   /usr/lib/mozilla/plugins:
 => libgnome-shell-browser-plugin.so
   (size: 18856 bytes, mtime: Mon Apr 23 15:29:28 2018)
  Load-Avg-1min: 0.64
  Load-Processes-Running-Percent:   0.1%
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=eb4622c9-14d3-4a4e-bc10-49a41ebdb495 ro quiet splash 
nospec_store_bypass_disable nospectre_v2 noibrs noibpb nopti vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to bionic on 2018-06-18 (4 days ago)
  dmi.bios.date: 07/24/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0049.2017.0724.1541
  dmi.board.name: NUC7i7BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J31145-303
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0049.2017.0724.1541:bd07/24/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-303:cvn:ct3:cvr:
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1778244] [NEW] Text rendering too high (inside padding)

[John Runyon]

Public bug reported:

Text is being rendered too high. This causes it to render inside
padding, or worse yet inside the border of an input box (causing it to
be cut off).

Issue also occurs on Chrome (Version 67.0.3396.87 (Official Build) (64-bit)).
Issue began occurring after upgrade to 18.04 from 17.10.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: chromium-browser 66.0.3359.181-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: 
AP///wBaYy/OAQEBASwYAQOAPiJ46giloldPoigPUFSlSwBxT4EAgYCpQLMA0cDRAAEBBHQAMPJwWoCwWIoAbVUhAAAe/wBVMk4xNDQ0MDAzMjgK/ABWWDI4ODBNTAogICAg/QAYVR9yHgAKICAgICAgAXgCAy3xUpAfAQIDBxYEExQFEhEGFSAhIiMJHweDAQAAbQMMABAAADwgAGADAgECOoAYcTgtQFgsRQBtVSEAAB4BHYAYcRwWIFgsJQBtVSEAAJ4BHQByUdAeIG4oVQBtVSEAAB6MCtCKIOAtEBA+lgBtVSEAABgAhg==
 modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 1920x1200 1920x1080 
1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 1920x1080 1920x1080 
1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1280x800 
1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600 720x576 
720x480 720x480 640x480 640x480 640x480 720x400
DRM.card0-DP-2:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: 
AP///wBaYwcgAQEBAQ8NAQOAJh6MKiyVplhKmiYhUFS/74CBgIGPcU9hT0lPRU8xTzFAMCoAmFEAKkAwcBMAeC0RAAAe/wBBMFkwMzE1MTAyNTEK/QAySx5SDgAKICAgICAg/ABWRzE5MQogICAgICAgAIE=
 modes: 1280x1024 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 832x624 
800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400
DRM.card0-HDMI-A-1:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64: 
 modes:
Date: Fri Jun 22 10:32:41 2018
Desktop-Session:
 'ubuntu'
 '/etc/xdg/xdg-ubuntu:/etc/xdg'
 
'/usr/share/ubuntu:/home/jrunyon/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
DetectedPlugins:
 
Env:
 'None'
 'None'
InstallationDate: Installed on 2018-03-07 (106 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
InstalledPlugins:
 /usr/lib/mozilla/plugins:
   => libgnome-shell-browser-plugin.so
 (size: 18856 bytes, mtime: Mon Apr 23 15:29:28 2018)
Load-Avg-1min: 0.64
Load-Processes-Running-Percent:   0.1%
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=eb4622c9-14d3-4a4e-bc10-49a41ebdb495 ro quiet splash 
nospec_store_bypass_disable nospectre_v2 noibrs noibpb nopti vt.handoff=1
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to bionic on 2018-06-18 (4 days ago)
dmi.bios.date: 07/24/2017
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BNKBL357.86A.0049.2017.0724.1541
dmi.board.name: NUC7i7BNB
dmi.board.vendor: Intel Corporation
dmi.board.version: J31145-303
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0049.2017.0724.1541:bd07/24/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-303:cvn:ct3:cvr:
modified.conffile..etc.default.chromium-browser: [deleted]

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


** Tags: amd64 apport-bug bionic

** Attachment added: "Screenshot of "
   
https://bugs.launchpad.net/bugs/1778244/+attachment/5155587/+files/Screenshot%20from%202018-06-22%2010-34-22.png

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

Title:
  Text rendering too high (inside padding)

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Text is being rendered too high. This causes it to render inside
  padding, or worse yet inside the border of an input box (causing it to
  be cut off).

  Issue also occurs on Chrome (Version 67.0.3396.87 (Official Build) (64-bit)).
  Issue began occurring after upgrade to 18.04 from 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 66.0.3359.181-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBaYy/OAQEBASwYAQOAPiJ46giloldPoigPUFSlSwBxT4EAgYCpQLMA0cDRAAEBBHQAMPJwWoCwWIoAbVUhAAAe/wBVMk4xNDQ0MDAzMjgK/ABWWDI4ODBNTAogICAg/QAYVR9yHgAKICAgICAgAXgCAy3xUpAfAQIDBxYEExQFEhEGFSAhIiMJHweDAQAAbQMMABAAADwgAGADAgECOoAYcTgtQFgsRQBtVSEAAB4BHYAYcRwWIFgsJQBtVSEAAJ4BHQByUdAeIG4oVQBtVSEAAB6MCtCKIOAtEBA+lgBtVSEAABgAhg==
   modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 1920x1200 1920x1080 
1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 1920x1080 

[Desktop-packages] [Bug 1777427] Re: Locking screen takes 10+ secs (after hit SUPER + L)

[Vojtěch Dušátko]

There is a log of locking and unlocking from "journalctl -f" when it
happens

** Attachment added: "LockUnlock.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1777427/+attachment/5155584/+files/LockUnlock.log

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

Title:
  Locking screen takes 10+ secs (after hit SUPER + L)

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  System visually locks screen between 10 and 12 secs after hitting Super + L 
or pressing Lock button. This ~10 secs I can move with pointer and view what 
was on screen but clicking on whatever is not possible. 
  And when I waking up my Laptop from sleep that happens too

  Report Type: Bug
  Description: Ubuntu 18.04 LTS
  Package: gdm3:
 Installed: 3.28.2-0ubuntu1.2
 Candidate: 3.28.2-0ubuntu1.2
  Uname: Linux 4.15.0-23-generic
  Architecture: x86_64

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

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

[Desktop-packages] [Bug 1322728] Re: VPN Connection Failed With 2 Factor Authentication

[Manuel Muradás]

In https://bugs.launchpad.net/ubuntu/+source/network-manager-
openvpn/+bug/1322728/comments/12, I meant I have set my user, but not my
password. Sorry for the noise.

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

Title:
  VPN Connection Failed With 2 Factor Authentication

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

Bug description:
  Hi all,

  my setup is an openvpn access server with google 2 factor auth

  i was trying to connect to my VPN using the gnome openvpn module and
  get the following errors on syslog:

  May 23 22:23:00 laptop nm-openvpn[18049]: [OpenVPN Server] Peer Connection 
Initiated with [AF_INET]xx.xx.xx.xx:1194
  May 23 22:23:02 laptop nm-openvpn[18049]: AUTH: Received control message: 
AUTH_FAILED,CRV1:R,E:d1r12r21df232+owqrf23t23t23tCn:aXRf3r2s=:Enter Google 
Authenticator Code
  May 23 22:23:02 laptop nm-openvpn[18049]: SIGTERM[soft,auth-failure] 
received, process exiting
  May 23 22:23:02 laptop NetworkManager[1043]:  VPN plugin failed: 0

  i looked in the documentation but didn't found anything useful.

  any help will be appreciated

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

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

[Desktop-packages] [Bug 1322728] Re: VPN Connection Failed With 2 Factor Authentication

[Manuel Muradás]

Uhm, I'm using 18.04 and it's kind of working for me.
I have set my password in the VPN configuration, and set not to remember my 
password.
I first get prompted for my password and a few seconds later I get a second 
prompt for my Google Authenticator code.

The problem I'm facing is that if I set to remember my password, the
last input I entered (2FA code) overwrites the saved password, and next
time the old 2FA code is used instead of the password. I will report
this to a new ticket, I just wanted to let you know my experience in
case it helps you with yours.

Package: network-manager-gnome
Version: 1.8.10-2ubuntu1

Package: network-manager-openvpn
Version: 1.8.2-1

Package: network-manager-openvpn-gnome
Version: 1.8.2-1

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

Title:
  VPN Connection Failed With 2 Factor Authentication

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

Bug description:
  Hi all,

  my setup is an openvpn access server with google 2 factor auth

  i was trying to connect to my VPN using the gnome openvpn module and
  get the following errors on syslog:

  May 23 22:23:00 laptop nm-openvpn[18049]: [OpenVPN Server] Peer Connection 
Initiated with [AF_INET]xx.xx.xx.xx:1194
  May 23 22:23:02 laptop nm-openvpn[18049]: AUTH: Received control message: 
AUTH_FAILED,CRV1:R,E:d1r12r21df232+owqrf23t23t23tCn:aXRf3r2s=:Enter Google 
Authenticator Code
  May 23 22:23:02 laptop nm-openvpn[18049]: SIGTERM[soft,auth-failure] 
received, process exiting
  May 23 22:23:02 laptop NetworkManager[1043]:  VPN plugin failed: 0

  i looked in the documentation but didn't found anything useful.

  any help will be appreciated

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

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

[Desktop-packages] [Bug 1456338] Re: USB floppy drive is running without floppy

[Phillip Susi]

Ahh, ok.. try disabling udisks to see if that is the cause:

systemctl stop udisks2.service

Then connect the drive.

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

Title:
  USB floppy drive is running without floppy

Status in udisks2 package in Ubuntu:
  New

Bug description:
  When I connect USB floppy drive (Gembird) without floppy under Ubuntu, the 
drive engine seems to be running (the floppy drive LED is on and the drive is 
sounding). The same behaviour takes place if I connect the drive with a floppy 
and then remove the floppy. It seems that the system accesses the drive 
permanently when there is no floppy. Under Windows XP it works normally - when 
there is no floppy, the LED and engine are switched off. I have tried Ubuntu 
14.10 (amd64) with upstart, LXQt and KDE 5; Ubuntu 15.04 with systemd, LXQt - 
the same behaviour.
  If I boot using bash as init (init=/bin/bash) and connect the floppy drive 
after boot, the engine is off (the normal behaviour).
  lsof /dev/sdb during engine running outputs nothing.

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

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

[Desktop-packages] [Bug 1778233] Re: Xorg crash when using mouse

[Ville Haapala]

** Attachment added: "crash report from /var/crash/"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1778233/+attachment/5155547/+files/_usr_lib_xorg_Xorg.0.crash

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

Title:
  Xorg crash when using mouse

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes when moving mouse Xorg crashes.

  I have a Logitech mouse with free spinning scroll wheel (MX Master).
  100% sure way to reproduce the problem is put the wheel is free spin
  mode and scroll as fast as possible for a few seconds.

  Also the crash happens randomly every couple of days during normal use
  when moving mouse normally.

  I have tried both Nouveau and Nvidia proprietary GPU drivers. Same
  behavior on both.

  
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  xserver-xorg-core:
Installed: 2:1.19.6-1ubuntu4
Candidate: 2:1.19.6-1ubuntu4
Version table:
   *** 2:1.19.6-1ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  Date: Fri Jun 22 16:09:44 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF119 [GeForce GT 610] [1043:8496]
  InstallationDate: Installed on 2018-06-05 (16 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Intel Corporation S2600CW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic 
root=UUID=09005743-f23a-4610-8ea7-102ba625db6a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2018
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: SE5C610.86B.01.01.0024.021320181901
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: S2600CW
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H12881-251
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrSE5C610.86B.01.01.0024.021320181901:bd02/13/2018:svnIntelCorporation:pnS2600CW:pvr:rvnIntelCorporation:rnS2600CW:rvrH12881-251:cvn..:ct17:cvr..:
  dmi.product.family: Family
  dmi.product.name: S2600CW
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  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/ubuntu/+source/xorg/+bug/1778233/+subscriptions

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

[Desktop-packages] [Bug 1778233] [NEW] Xorg crash when using mouse

[Ville Haapala]

Public bug reported:

Sometimes when moving mouse Xorg crashes.

I have a Logitech mouse with free spinning scroll wheel (MX Master).
100% sure way to reproduce the problem is put the wheel is free spin
mode and scroll as fast as possible for a few seconds.

Also the crash happens randomly every couple of days during normal use
when moving mouse normally.

I have tried both Nouveau and Nvidia proprietary GPU drivers. Same
behavior on both.


Description:Ubuntu 18.04 LTS
Release:18.04


xserver-xorg-core:
  Installed: 2:1.19.6-1ubuntu4
  Candidate: 2:1.19.6-1ubuntu4
  Version table:
 *** 2:1.19.6-1ubuntu4 500
500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
Date: Fri Jun 22 16:09:44 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GF119 [GeForce GT 610] [1043:8496]
InstallationDate: Installed on 2018-06-05 (16 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Intel Corporation S2600CW
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic 
root=UUID=09005743-f23a-4610-8ea7-102ba625db6a ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/13/2018
dmi.bios.vendor: Intel Corporation
dmi.bios.version: SE5C610.86B.01.01.0024.021320181901
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: S2600CW
dmi.board.vendor: Intel Corporation
dmi.board.version: H12881-251
dmi.chassis.asset.tag: 
dmi.chassis.type: 17
dmi.chassis.vendor: ..
dmi.chassis.version: ..
dmi.modalias: 
dmi:bvnIntelCorporation:bvrSE5C610.86B.01.01.0024.021320181901:bd02/13/2018:svnIntelCorporation:pnS2600CW:pvr:rvnIntelCorporation:rnS2600CW:rvrH12881-251:cvn..:ct17:cvr..:
dmi.product.family: Family
dmi.product.name: S2600CW
dmi.product.version: 
dmi.sys.vendor: Intel Corporation
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic crash kubuntu ubuntu

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

Title:
  Xorg crash when using mouse

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes when moving mouse Xorg crashes.

  I have a Logitech mouse with free spinning scroll wheel (MX Master).
  100% sure way to reproduce the problem is put the wheel is free spin
  mode and scroll as fast as possible for a few seconds.

  Also the crash happens randomly every couple of days during normal use
  when moving mouse normally.

  I have tried both Nouveau and Nvidia proprietary GPU drivers. Same
  behavior on both.

  
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  xserver-xorg-core:
Installed: 2:1.19.6-1ubuntu4
Candidate: 2:1.19.6-1ubuntu4
Version table:
   *** 2:1.19.6-1ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  Date: Fri Jun 22 16:09:44 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF119 [GeForce GT 610] [1043:8496]
  InstallationDate: Installed on 2018-06-05 (16 days ago)
  InstallationMedia: Kubuntu 

[Desktop-packages] [Bug 1778225] Re: Can't switch UI language for single users, only system-wide

[Gunnar Hjalmarsson]

I assume it was the Language Support tool you used. How did it "not
work"? You need to relogin before the new display language gets
effective.

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

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

Title:
  Can't switch UI language for single users, only system-wide

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

Bug description:
  The title says it all ... I tried to switch the language of the user
  interface to English instead of German for a single user, which did
  not work. Applying the new language system-wide did the job, but
  forced all other users on that pc to have their graphical sessions in
  the new language too.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 22 14:56:26 2018
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2018-05-29 (23 days ago)

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

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

[Desktop-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~3v1n0/nux/+git/nux/+merge/348392

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

Title:
  leftover conffile forces GNOME is software rendering

Status in nux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  In Progress
Status in nux source package in Xenial:
  Fix Committed
Status in xorg source package in Xenial:
  Confirmed
Status in nux source package in Artful:
  Fix Committed
Status in xorg source package in Artful:
  Confirmed
Status in nux source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  In Progress

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case ]

  · Install xenial
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
in an environment with no 3d support (VMs are easy tests)

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

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

[Desktop-packages] [Bug 1778225] [NEW] Can't switch UI language for single users, only system-wide

[Michael Satke]

Public bug reported:

The title says it all ... I tried to switch the language of the user
interface to English instead of German for a single user, which did not
work. Applying the new language system-wide did the job, but forced all
other users on that pc to have their graphical sessions in the new
language too.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.1-0ubuntu1.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 22 14:56:26 2018
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to bionic on 2018-05-29 (23 days ago)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Can't switch UI language for single users, only system-wide

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

Bug description:
  The title says it all ... I tried to switch the language of the user
  interface to English instead of German for a single user, which did
  not work. Applying the new language system-wide did the job, but
  forced all other users on that pc to have their graphical sessions in
  the new language too.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 22 14:56:26 2018
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2018-05-29 (23 days ago)

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

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

[Desktop-packages] [Bug 1777154] Re: Displays screen contents upon waking from sleep (before login)

[Marc Deslauriers]

** Information type changed from Private Security to Public Security

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

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

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

Title:
  Displays screen contents upon waking from sleep (before login)

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Seems to be an issue with the GNOME shell - upon waking from sleep,
  displays screen contents for several seconds before defaulting to the
  login screen. Could be a serious security issue for some  people.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 15 09:14:54 2018
  DistUpgraded: 2018-05-21 16:23:12,151 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Iris Graphics 540 [8086:1926] (rev 0a) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Iris Graphics 540 [103c:81ac]
  InstallationDate: Installed on 2017-11-20 (207 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: HP HP ENVY x360 m6 Convertible
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=4386fd35-55a3-4f9f-9973-e5a05d2912c6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-21 (24 days ago)
  dmi.bios.date: 06/05/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.28
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81AC
  dmi.board.vendor: HP
  dmi.board.version: 53.27
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.28:bd06/05/2017:svnHP:pnHPENVYx360m6Convertible:pvrType1ProductConfigId:rvnHP:rn81AC:rvr53.27:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY x360 m6 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Jun 13 17:34:04 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~3v1n0/nux/+git/nux/+merge/348390

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

Title:
  leftover conffile forces GNOME is software rendering

Status in nux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  In Progress
Status in nux source package in Xenial:
  Fix Committed
Status in xorg source package in Xenial:
  Confirmed
Status in nux source package in Artful:
  Fix Committed
Status in xorg source package in Artful:
  Confirmed
Status in nux source package in Bionic:
  Fix Committed
Status in xorg source package in Bionic:
  In Progress

Bug description:
  [ Impact ]

  GNOME shell and other 3D programs run using software rendering after
  unity removal.

  This SRU covers only the upgrade case or if nux-tools removal happens
  after this update, for people who already upgraded and in broken state
  another SRU will follow.

  [ Test case ]

  · Install xenial
  · Upgrade to bionic or artful
    (assuming you're using a GNOME session)
  · sudo apt remove nux-tools
  · log into your session
  . From terminal:
    - printenv LIBGL_ALWAYS_SOFTWARE
    Should print nothing (and return an error)

  Same should happen if you don't remove nux-tools but you change
  `/usr/lib/nux/unity_support_test` not to run properly (replace with a script 
exiting 1), but you're running a GNOME session.

  · If running Unity session instead, ensure that
printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running
in an environment with no 3d support (VMs are easy tests)

  [ Regression Potential ]

  Unity desktops with no 3d support could not start anymore.

  ===

  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

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

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

[Desktop-packages] [Bug 1777848] Re: screen never locks

[Marc Deslauriers]

** Information type changed from Private Security to Public

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

Title:
  screen never locks

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  Using lockscreen keybord shortcut (Super+L) doesnt lock screen. The
  systm just freezes a few seconds. Putting the system to sleep
  (suspend), after settings are set to  lock screen when screen is
  blank, also does not lock the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-screensaver 3.6.1-8ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jun 20 11:57:27 2018
  InstallationDate: Installed on 2016-09-28 (629 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-screensaver
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (48 days ago)

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

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

[Desktop-packages] [Bug 1778213] Re: Swipe to unlock should only be for mobile / touchscreen

[Colin Watson]

** Project changed: launchpad => gnome-shell (Ubuntu)

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

Title:
  Swipe to unlock should only be for mobile / touchscreen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  It makes no sense to have to swipe the lockscreen using a regular
  mouse...

  I know you can just start writing your password, instead of swiping
  first, but most people don't.

  Whenever I install Ubuntu for someone - I will often get calls about this 
shortly after.
  Most find it annoying it seems to me.

  Would be nice if it was off by default, or at least an easy option to 
completely drop it.
  Maybe detect if user has touch screen?

  PS: This was about Ubuntu LTS (not "launchpad itself"..)

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

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

[Desktop-packages] [Bug 1767027] Re: Search current folder only in nautilus doesn't work (Ubuntu 18.04)

[Sebastien Bacher]

** Also affects: nautilus (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  Search current folder only in nautilus doesn't work (Ubuntu 18.04)

Status in nautilus package in Ubuntu:
  In Progress
Status in nautilus source package in Bionic:
  New

Bug description:
  I upgraded to Ubuntu 18.04 prerelease from Ubuntu 17.10 and am finding
  that Nautilus searches all subfolders when I start typing, not just
  the present folder, even though I have the "search only current
  folder" option selected in its preferences, and "Only searching the
  current folder" does appear in the GUI as I am searching. Nonetheless
  results appear from subfolders (which I wouldn't mind, but which I
  turn off due to its poor performance compared to current-folder-only).

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

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

[Desktop-packages] [Bug 1778213] [NEW] Swipe to unlock should only be for mobile / touchscreen

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

It makes no sense to have to swipe the lockscreen using a regular
mouse...

I know you can just start writing your password, instead of swiping
first, but most people don't.

Whenever I install Ubuntu for someone - I will often get calls about this 
shortly after.
Most find it annoying it seems to me.

Would be nice if it was off by default, or at least an easy option to 
completely drop it.
Maybe detect if user has touch screen?

PS: This was about Ubuntu LTS (not "launchpad itself"..)

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

-- 
Swipe to unlock should only be for mobile / touchscreen
https://bugs.launchpad.net/bugs/1778213
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

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

[Desktop-packages] [Bug 1777427] Re: Locking screen takes 10+ secs (after hit SUPER + L)

[Vojtěch Dušátko]

I found that it's could be because overloaded Intel HD 4000. It's
happening only when I have many windows (10+) opened on many (3+)
workspaces and second monitor is connected. After boot it's not
happening now.

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

Title:
  Locking screen takes 10+ secs (after hit SUPER + L)

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  System visually locks screen between 10 and 12 secs after hitting Super + L 
or pressing Lock button. This ~10 secs I can move with pointer and view what 
was on screen but clicking on whatever is not possible. 
  And when I waking up my Laptop from sleep that happens too

  Report Type: Bug
  Description: Ubuntu 18.04 LTS
  Package: gdm3:
 Installed: 3.28.2-0ubuntu1.2
 Candidate: 3.28.2-0ubuntu1.2
  Uname: Linux 4.15.0-23-generic
  Architecture: x86_64

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

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

[Desktop-packages] [Bug 1778205] [NEW] Audio playback is choppy in vlc on ubuntu 18o4

[Thiruvenkatam Nagarajan]

Public bug reported:

This ubuntu is in a virtual box in windows 10.I have had no problem wtth vlc in 
lubuntu 19.04 in an oldlaptop as the only os
Thanks

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1001 F pulseaudio
  teeyen 1363 F pulseaudio
Date: Fri Jun 22 15:39:28 2018
InstallationDate: Installed on 2018-05-08 (45 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


** Tags: amd64 apport-bug bionic

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

Title:
  Audio playback is choppy in vlc on ubuntu 18o4

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This ubuntu is in a virtual box in windows 10.I have had no problem wtth vlc 
in lubuntu 19.04 in an oldlaptop as the only os
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1001 F pulseaudio
teeyen 1363 F pulseaudio
  Date: Fri Jun 22 15:39:28 2018
  InstallationDate: Installed on 2018-05-08 (45 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Desktop-packages] [Bug 1760487] Re: Shell crashes when I start skype under Wayland session

[Russell Jones]

Apparently this needs to be re-reported with the command

ubuntu-bug _usr_bin_Xwayland.1000.crash

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

Title:
  Shell crashes when I start skype under Wayland session

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  In terminal type

  1. snap install skype --classic
  2. skype

  Shell crashes and you end up at login screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  2 01:16:10 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['firefox_firefox.desktop', 
'org.gnome.Terminal.desktop', 'org.gnome.Nautilus.desktop', 
'gnome-system-monitor_gnome-system-monitor.desktop', 
'android-studio_android-studio.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-03-18 (14 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180317)
  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/1760487/+subscriptions

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

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import certificates in Ubuntu 18.04

[Krzysztof Studnicki]

I can't find a workaround and it is crucial that I have a new
certificates, because we use them to authenticate ourselves and send
emails in our company.

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

Title:
  Seahorse unable to import certificates in Ubuntu 18.04

Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in seahorse package in Ubuntu:
  Confirmed

Bug description:
  seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu
  18.04 LTS / GNOME 3.28.1

  When trying to import a certificate into seahorse/gnome-keyring on
  Ubuntu 18.04, seahorse GUI application shows the 'import' button
  greyed out, while mouse hovering the "import" button shows the message
  "Cannot import because there are no compatible importers".

  This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as
  I've just tested on my wife's laptop, but happens in my Laptop with
  Ubuntu 18.04 LTS (Seahorse 3.20.0-5).

  Because that problem, it's not possible to digitally sign documents
  with LibreOffice.

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

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

[Desktop-packages] [Bug 1774597] Re: G-C-C privacy option don't allow sending manual report

[Sebastien Bacher]

the SRU is in the bionic queue now

** Changed in: gnome-control-center (Ubuntu Bionic)
   Importance: Undecided => Low

** Changed in: gnome-control-center (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  G-C-C privacy option don't allow sending manual report

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]
* The current label "Manual" is in fact shutting down whoopsie completely 
and not providing any graĥical way to set manual reports (which is our default 
on 18.04)
* We want to SRU gnome-initial-setup for 18.04.1 so that sending reports is 
linked to sending error report: opt-in -> automated report is set; opt-out -> 
no report is set. We need a way to represent those 3 states of error reporting:
 - never
 - manual
 - auto
   
  [ Test Case ]
* Install new gnome-control-center version, go to the privacy panel
* Click on the error reporting line
* In the model window, play with the switch and toggle, and check in d-feet 
the whoopsie state. Basically you can't adapt error reporting mode 
(manual/auto) if you decided to not report error mode.
* Check as well that the main UI toggles between "never/manual/auto"

  [ Regression potential ]
* This code would affect the privacy g-c-c panel.
* Note that we have 3 new strings to translate ("never" is already 
translated in G-C-C). Those are:
  - "Send error reports to Canonical"
  - "Send reports automatically"
  - "Show a dialog for each error before reporting"

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

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

[Desktop-packages] [Bug 1778197] [NEW] package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package libnvidia

[ubuntu]

Public bug reported:

help!help!help!help!help!help!help!help!help!

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: nvidia-340 (not installed)
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Fri Jun 22 17:09:10 2018
ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', 
which is also in package libnvidia-compute-390:amd64 390.48-0ubuntu3
InstallationDate: Installed on 2018-06-14 (7 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: nvidia-graphics-drivers-340
Title: package nvidia-340 (not installed) failed to install/upgrade: trying to 
overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package 
libnvidia-compute-390:amd64 390.48-0ubuntu3
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade: trying
  to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is
  also in package libnvidia-compute-390:amd64 390.48-0ubuntu3

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  help!help!help!help!help!help!help!help!help!

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Fri Jun 22 17:09:10 2018
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package 
libnvidia-compute-390:amd64 390.48-0ubuntu3
  InstallationDate: Installed on 2018-06-14 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: trying 
to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in 
package libnvidia-compute-390:amd64 390.48-0ubuntu3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1778197/+subscriptions

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

[Desktop-packages] [Bug 1775145] Re: Please merge gnome-shell 3.28.2 from Debian

[Sebastien Bacher]

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

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

** Changed in: gnome-shell (Ubuntu Bionic)
   Status: New => In Progress

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

Title:
  Please merge gnome-shell 3.28.2 from Debian

Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell source package in Bionic:
  In Progress
Status in gnome-shell source package in Cosmic:
  In Progress

Bug description:
  Please merge gnome-shell 3.28.2 from Debian.

  It only contains a few bug fixes:
    https://gitlab.gnome.org/GNOME/gnome-shell/commit/c70b18764

  but that includes a fix for LP: #1765261 (gnome-shell#240)

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

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

[Desktop-packages] [Bug 93281] Re: "Suspend failed" message gives false advice

[Matthew Paul Thomas]

Eleven years later, gnome-power-manager no longer includes this string or 
anything like it, so I guess this is fixed.


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

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

Title:
  "Suspend failed" message gives false advice

Status in gnome-power-manager package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu Feisty

  When suspend fails, or at least when gnome-power-manager thinks it
  failed (bug 89983), a bubble appears in the corner of the screen:
  "Your computer failed to suspend. Check the help file for common
  problems."

  Problems with this:
  * It's not necessarily your computer.
  * "Help file"? What help file?
  * Even if you get as far as opening the Help Center, Ubuntu has hundreds of 
help pages, and the only relevant one is one you can't navigate to from the 
home page anyway.

  Suggested text for now: "The computer failed to suspend. For more
  information, search for “suspend failure” in Ubuntu Help."

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

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

[Desktop-packages] [Bug 1772878] Re: Shotwell slideshow settings do not open

[Sebastien Bacher]

The issue has been fixed upstream in 0.28 but after the current tarball
went out

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

** Changed in: shotwell (Ubuntu)
   Status: New => In Progress

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

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

Title:
  Shotwell slideshow settings do not open

Status in Shotwell:
  Unknown
Status in shotwell package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 18.04 LTS - Shotwell 028.2

  The Shotwell slideshow opens and works with some pre-defined settings.

  When I try to access the slideshow settings, the monitor freezes but I
  can unfreeze the display by pressing the Esc key.

  I opened shotwell via the terminal and extracted this comment:-

  (shotwell:6518): Gtk-CRITICAL **: 10:37:09.819: Error building
  template class 'SlideshowPageSettingsDialog' for an instance of type
  'SlideshowPageSettingsDialog': .:20:1 Parsed template definition for
  type 'SettingsDialog', expected type 'SlideshowPageSettingsDialog'

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

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

[Desktop-packages] [Bug 1778190] [NEW] Can't add a route without gateway in Network Manager VPN.IPv4 window

[Peklo]

Public bug reported:

Dear Ubuntu programers,

I would like report about possibly bug in Network Manager and edit VPN 
connection.
In edit window for VPN and IPv4 I can't add a route without gateway, because 
the Gateway field is red highlight. And I can't click to the button "Apply", 
because it is grey (see the attached picture).

I don't know if this a bug or not.
But I don't know gateway for VPN connection, because the VPN connection uses 
PPP.

If I add the route via nmcli, it works well:

==
# nmcli c e Skylab
nmcli> set ipv4.routes 192.168.240.0/24
nmcli> print
...
ipv4.routes:{ ip = 192.168.240.0/24 }
...
nmcli> save

# ip r
192.168.240.0/24 dev ppp0 proto static scope link metric 50 
==

I can't set this setting via GUI Network Manager.

I know, that is workaround via nmcli, but the way is not good for normal
users. When Ubuntu is for "normal" users mainly, the GUI is better way.


$ lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04

$ apt-cache policy gnome-control-center
gnome-control-center:
  Installed: 1:3.28.1-0ubuntu1.18.04.1
  Candidate: 1:3.28.1-0ubuntu1.18.04.1
  Version table:
 *** 1:3.28.1-0ubuntu1.18.04.1 500
500 http://cz.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:3.28.1-0ubuntu1 500
500 http://cz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages


Thank you.
Yours Faithfully
Radomir.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.1-0ubuntu1.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 22 09:22:30 2018
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2018-06-08 (13 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "NM-VPN-IPv4-cannot-route-without-gw.png"
   
https://bugs.launchpad.net/bugs/1778190/+attachment/5155449/+files/NM-VPN-IPv4-cannot-route-without-gw.png

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

Title:
  Can't add a route without gateway in Network Manager VPN.IPv4 window

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

Bug description:
  Dear Ubuntu programers,

  I would like report about possibly bug in Network Manager and edit VPN 
connection.
  In edit window for VPN and IPv4 I can't add a route without gateway, because 
the Gateway field is red highlight. And I can't click to the button "Apply", 
because it is grey (see the attached picture).

  I don't know if this a bug or not.
  But I don't know gateway for VPN connection, because the VPN connection uses 
PPP.

  If I add the route via nmcli, it works well:

  ==
  # nmcli c e Skylab
  nmcli> set ipv4.routes 192.168.240.0/24
  nmcli> print
  ...
  ipv4.routes:{ ip = 192.168.240.0/24 }
  ...
  nmcli> save

  # ip r
  192.168.240.0/24 dev ppp0 proto static scope link metric 50 
  ==

  I can't set this setting via GUI Network Manager.

  I know, that is workaround via nmcli, but the way is not good for
  normal users. When Ubuntu is for "normal" users mainly, the GUI is
  better way.


  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  $ apt-cache policy gnome-control-center
  gnome-control-center:
Installed: 1:3.28.1-0ubuntu1.18.04.1
Candidate: 1:3.28.1-0ubuntu1.18.04.1
Version table:
   *** 1:3.28.1-0ubuntu1.18.04.1 500
  500 http://cz.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://cz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages


  Thank you.
  Yours Faithfully
  Radomir.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 22 09:22:30 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-06-08 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

[Desktop-packages] [Bug 1778185] [NEW] printing problem

[Neeraj Kumar Meesa]

Public bug reported:

i am unable to get a print from my canon lbp2900b printer eventhough the
system displays printing completed dialogue.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CupsErrorLog:
 E [22/Jun/2018:12:44:04 +0530] [cups-deviced] PID 4699 (gutenprint52+usb) 
stopped with status 1!
 E [22/Jun/2018:12:47:46 +0530] [cups-deviced] PID 5020 (gutenprint52+usb) 
stopped with status 1!
 E [22/Jun/2018:12:48:30 +0530] [Client 208] Returning IPP 
client-error-document-format-not-supported for Print-Job 
(ipp://localhost:631/printers/LBP2900) from localhost
 E [22/Jun/2018:12:48:47 +0530] [Client 254] Returning IPP 
client-error-document-format-not-supported for Print-Job 
(ipp://localhost:631/printers/LBP2900) from localhost
 E [22/Jun/2018:12:51:57 +0530] [cups-deviced] PID 5289 (gutenprint52+usb) 
stopped with status 1!
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 22 12:55:11 2018
InstallationDate: Installed on 2018-06-11 (10 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lpstat: device for LBP2900: usb://Canon/LBP2900?serial=C299PKTi
MachineType: Dell Inc. Vostro 3800
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/LBP2900.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/LBP2900.ppd: Permission denied
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=cf57e9ec-eb6b-4a11-afb5-2a09b659f987 ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/04/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0T1D10
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd04/04/2014:svnDellInc.:pnVostro3800:pvr:rvnDellInc.:rn0T1D10:rvrA01:cvnDellInc.:ct3:cvr:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Vostro 3800
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

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

Title:
  printing problem

Status in cups package in Ubuntu:
  New

Bug description:
  i am unable to get a print from my canon lbp2900b printer eventhough
  the system displays printing completed dialogue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CupsErrorLog:
   E [22/Jun/2018:12:44:04 +0530] [cups-deviced] PID 4699 (gutenprint52+usb) 
stopped with status 1!
   E [22/Jun/2018:12:47:46 +0530] [cups-deviced] PID 5020 (gutenprint52+usb) 
stopped with status 1!
   E [22/Jun/2018:12:48:30 +0530] [Client 208] Returning IPP 
client-error-document-format-not-supported for Print-Job 
(ipp://localhost:631/printers/LBP2900) from localhost
   E [22/Jun/2018:12:48:47 +0530] [Client 254] Returning IPP 
client-error-document-format-not-supported for Print-Job 
(ipp://localhost:631/printers/LBP2900) from localhost
   E [22/Jun/2018:12:51:57 +0530] [cups-deviced] PID 5289 (gutenprint52+usb) 
stopped with status 1!
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 22 12:55:11 2018
  InstallationDate: Installed on 2018-06-11 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lpstat: device for LBP2900: usb://Canon/LBP2900?serial=C299PKTi
  MachineType: Dell Inc. Vostro 3800
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/LBP2900.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/LBP2900.ppd: Permission denied
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=cf57e9ec-eb6b-4a11-afb5-2a09b659f987 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/04/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0T1D10
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd04/04/2014:svnDellInc.:pnVostro3800:pvr:rvnDellInc.:rn0T1D10:rvrA01:cvnDellInc.:ct3:cvr:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Vostro 3800
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1778082] Re: Language Support Is Incomplete dialog must show package list to install

[Murz]

And after process is finished, there are no useful info too (screehshot
is attached), only the text:

> Package successfully installed.

So the main user question is which packages are installed?

** Attachment added: "finish.png"
   
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1778082/+attachment/5155433/+files/finish.png

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

Title:
  Language Support Is Incomplete dialog must show package list to
  install

Status in language-selector package in Ubuntu:
  New

Bug description:
  When Ubuntu have missing language packages, it shows in tray System
  Notification Helper message with text "Language support is incomplete,
  additional packages are required".

  But when user do one simple mouse click on this notification - Ubuntu
  immediately asks user password with "Authentication Required" popup
  window, without describing what is planned to do, which packages are
  missing and will be installed.

  After typing password - user will not see any useful info too - only
  small window with unnamed progress bar and standard text phrases.

  After process finished - there are also zero useful info, only that
  process is finished.

  
  Please show more information about this process, before ask user password!

  Very useful info will be:

  - How this missed packages are detected?

  - Why those packages are missed?

  - What packages will planned to install/upgrade (package names,
  versions)?

  - Total size of planned downloads.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: language-selector-common 0.188.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Jun 21 17:51:49 2018
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: language-selector
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1774597] Re: G-C-C privacy option don't allow sending manual report

[Didier Roche]

It's an option which was already present (only the "never" one wasn't):
whoopsie upload crash reports automatically.

See the g-c-c panel from that version to see the option dialog box.

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

Title:
  G-C-C privacy option don't allow sending manual report

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  New

Bug description:
  [ Impact ]
* The current label "Manual" is in fact shutting down whoopsie completely 
and not providing any graĥical way to set manual reports (which is our default 
on 18.04)
* We want to SRU gnome-initial-setup for 18.04.1 so that sending reports is 
linked to sending error report: opt-in -> automated report is set; opt-out -> 
no report is set. We need a way to represent those 3 states of error reporting:
 - never
 - manual
 - auto
   
  [ Test Case ]
* Install new gnome-control-center version, go to the privacy panel
* Click on the error reporting line
* In the model window, play with the switch and toggle, and check in d-feet 
the whoopsie state. Basically you can't adapt error reporting mode 
(manual/auto) if you decided to not report error mode.
* Check as well that the main UI toggles between "never/manual/auto"

  [ Regression potential ]
* This code would affect the privacy g-c-c panel.
* Note that we have 3 new strings to translate ("never" is already 
translated in G-C-C). Those are:
  - "Send error reports to Canonical"
  - "Send reports automatically"
  - "Show a dialog for each error before reporting"

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

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