date:20180429

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

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

Title:
  [regression] output device not recognized anymore since update
  1:8.0-0ubuntu3.9

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is
  not showing anymore my soundcard.

  The command "pacmd list-sinks" only shows a dummy output

  When running on a fresh install of ubuntu 16.04, the sound is ok.
  When updating the install with locking the following files to version 
1:8.0-0ubuntu3 the sound keeps working:
  libpulse0:amd64
  libpulse-mainloop-glib0:amd64
  libpulse-dev:amd64
  pulseaudio-module-x11:amd64
  pulseaudio-module-bluetooth:amd64
  pulseaudio-utils:amd64

  When updating to 1:8.0-0ubuntu3.9, I just get a "dummy output".

  I tried running the following versions of Ubuntu (live usb), and get the same 
issue (no need to update to get the problem)
  17.04
  17.10
  18.04

  I attached the result of command "pactl list"
  I have also generated logs during the boot but I don't know how to attach 
multiple files

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

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

[Desktop-packages] [Bug 1767784] Re: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9

2018-04-29 Thread Hui Wang

@Flavien,

When the output changes into "Dummy output", please upload the alsa-
info.txt and pactl list sinks/pactl list cards


thanks.

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

Title:
  [regression] output device not recognized anymore since update
  1:8.0-0ubuntu3.9

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is
  not showing anymore my soundcard.

  The command "pacmd list-sinks" only shows a dummy output

  When running on a fresh install of ubuntu 16.04, the sound is ok.
  When updating the install with locking the following files to version 
1:8.0-0ubuntu3 the sound keeps working:
  libpulse0:amd64
  libpulse-mainloop-glib0:amd64
  libpulse-dev:amd64
  pulseaudio-module-x11:amd64
  pulseaudio-module-bluetooth:amd64
  pulseaudio-utils:amd64

  When updating to 1:8.0-0ubuntu3.9, I just get a "dummy output".

  I tried running the following versions of Ubuntu (live usb), and get the same 
issue (no need to update to get the problem)
  17.04
  17.10
  18.04

  I attached the result of command "pactl list"
  I have also generated logs during the boot but I don't know how to attach 
multiple files

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

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

[Desktop-packages] [Bug 1767711] Re: Nvidia+XFCE: Totem window is see-through during playback, colours washed out

** Summary changed:

- window is see-through during playback, colours washed out
+ Nvidia+XFCE: Totem window is see-through during playback, colours washed out

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

** Tags added: nvidia

** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  Nvidia+XFCE: Totem window is see-through during playback, colours
  washed out

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New
Status in xfce4 package in Ubuntu:
  New

Bug description:
  Since the upgrade to Ubuntu 18.04, the Totem player will show
  everything behind it during playback, and the colours of the video are
  washed-out.  https://i.imgur.com/0AwJMmf.jpg  I did not find
  'tranparency' nor 'opacity' setting in the program preferences, and
  the colour adjudgement settings are pinned to +/-0.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Apr 28 14:56:29 2018
  InstallationDate: Installed on 2016-06-05 (692 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: totem
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (1 days ago)

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

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

[Desktop-packages] [Bug 1759300] Re: Touchpad right click (bottom right) area does not work

** Summary changed:

- touchpad right click
+ Touchpad right click (bottom right) area does not work

** Summary changed:

- Touchpad right click (bottom right) area does not work
+ Gnome Shell: Touchpad right click (bottom right) area does not work

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

Title:
  Gnome Shell: Touchpad right click (bottom right) area does not work

Status in gsettings-desktop-schemas package in Ubuntu:
  Invalid

Bug description:
  The right (second) touchpad click does not work.
  It ceased to work about three months ago.
  ubuntu 18,04 aser ex2519

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1759300/+subscriptions

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

[Desktop-packages] [Bug 1603183] Re: Unity8/Mir: Bottom right area of touchpad no longer treated as right click

This bug relates to Unity8 and Mir only.

Gnome Shell users please see bug 1759300 instead.

** Summary changed:

- Bottom right area of touchpad no longer treated as right click
+ Unity8/Mir: Bottom right area of touchpad no longer treated as right click

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

Title:
  Unity8/Mir: Bottom right area of touchpad no longer treated as right
  click

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Triaged
Status in gsettings-ubuntu-touch-schemas package in Ubuntu:
  Fix Released
Status in libinput package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Invalid
Status in unity8-desktop-session package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Using the touchpad I was not able to trigger any right click (with a
  single finger in the bottom right area), and I tought it was a problem
  of how unity8 handled the right clicks. Instead I just tried with a
  mouse and right click trigger different actions from left clicks.

  In the end the problem is that my touchpad right click is considered a
  left click by the system. This does not happen with an usb mouse.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1603183/+subscriptions

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

[Desktop-packages] [Bug 1766480] Re: Touchpad scroll and middle/right click not working as expected

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

** This bug has been marked a duplicate of bug 1759300
   Touchpad right click (bottom right) area does not work

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

Title:
  Touchpad scroll and middle/right click not working as expected

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  This could probably fixed through configuration, but it should work
  automatically. Testing Ubuntu 18.04 beta, the touchpad has no special
  regions for scrolling or anything.

  By default in Xorg-based Ubuntu, top right corner of touchpad is
  middle-click (mouse button 2), bottom right is right-click (mouse
  button 3), and right side is vertical scrolling. For a while the
  bottom edge defaulted to horizontal scrolling, but that changed in
  17.10 or something.

  I'm aware that new touchpad interaction methods have developed, like
  dragging with two fingers anywhere on the touchpad to scroll or
  something. But people may not know this, or their touchpad might not
  support multitouch.

  (The Xorg-based settings for touchpad remain when switching back to
  Xorg like with the Metacity Flashback login option.)

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

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

[Desktop-packages] [Bug 1767711] Re: window is see-through during playback, colours washed out

2018-04-29 Thread Moses Moore

gnome-calculator (3.28.0): does not have the same problem.
gedit (3.28.1): does not have the same problem.

Other video players (VLC, mplayer, parole) do not have the same problem.

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

Title:
  window is see-through during playback, colours washed out

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Since the upgrade to Ubuntu 18.04, the Totem player will show
  everything behind it during playback, and the colours of the video are
  washed-out.  https://i.imgur.com/0AwJMmf.jpg  I did not find
  'tranparency' nor 'opacity' setting in the program preferences, and
  the colour adjudgement settings are pinned to +/-0.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Apr 28 14:56:29 2018
  InstallationDate: Installed on 2016-06-05 (692 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: totem
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (1 days ago)

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

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

[Desktop-packages] [Bug 1716830] Re: package texlive-latex-base-doc 2015.20160320-1ubuntu0.1 failed to install/upgrade: trying to overwrite '/usr/share/doc/texlive-doc/latex/url/miscdoc.sty', which is

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

** Changed in: texlive-base (Ubuntu)
   Status: New => Confirmed

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

Title:
  package texlive-latex-base-doc 2015.20160320-1ubuntu0.1 failed to
  install/upgrade: trying to overwrite '/usr/share/doc/texlive-
  doc/latex/url/miscdoc.sty', which is also in package texlive-latex-
  recommended-doc 2013.20140215-1ubuntu0.1

Status in texlive-base package in Ubuntu:
  Confirmed

Bug description:
  Failed during Ubuntu 14.04 to 16.04 upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: texlive-latex-base-doc 2015.20160320-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Sep 12 20:16:25 2017
  DpkgTerminalLog:
   Preparing to unpack 
.../texlive-latex-base-doc_2015.20160320-1ubuntu0.1_all.deb ...
   Unpacking texlive-latex-base-doc (2015.20160320-1ubuntu0.1) over 
(2013.20140215-1ubuntu0.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/texlive-latex-base-doc_2015.20160320-1ubuntu0.1_all.deb 
(--unpack):
trying to overwrite '/usr/share/doc/texlive-doc/latex/url/miscdoc.sty', 
which is also in package texlive-latex-recommended-doc 2013.20140215-1ubuntu0.1
  DuplicateSignature:
   package:texlive-latex-base-doc:2015.20160320-1ubuntu0.1
   Unpacking texlive-latex-base-doc (2015.20160320-1ubuntu0.1) over 
(2013.20140215-1ubuntu0.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/texlive-latex-base-doc_2015.20160320-1ubuntu0.1_all.deb 
(--unpack):
trying to overwrite '/usr/share/doc/texlive-doc/latex/url/miscdoc.sty', 
which is also in package texlive-latex-recommended-doc 2013.20140215-1ubuntu0.1
  ErrorMessage: trying to overwrite 
'/usr/share/doc/texlive-doc/latex/url/miscdoc.sty', which is also in package 
texlive-latex-recommended-doc 2013.20140215-1ubuntu0.1
  InstallationDate: Installed on 2012-12-07 (1740 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: texlive-base
  Title: package texlive-latex-base-doc 2015.20160320-1ubuntu0.1 failed to 
install/upgrade: trying to overwrite 
'/usr/share/doc/texlive-doc/latex/url/miscdoc.sty', which is also in package 
texlive-latex-recommended-doc 2013.20140215-1ubuntu0.1
  UpgradeStatus: Upgraded to xenial on 2017-09-12 (0 days ago)

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

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

[Desktop-packages] [Bug 1670171] Re: Import SVG in Libreoffice Impress fails

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

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

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

Title:
  Import SVG in Libreoffice Impress fails

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  When importing an SVG in Impress, the image is displayed as blank dark grey 
rectangle.
  The SVG is OK as it's correctly displayed in Inkscape.

  Converting this SVG into PNG (for example with Imagemagick) works as a
  work-around.

  Let me know if more information is needed - more than happy to supply
  what's required.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libreoffice 1:5.2.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-40.43-generic 4.8.17
  Uname: Linux 4.8.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Sun Mar  5 19:14:02 2017
  InstallationDate: Installed on 2014-04-26 (1044 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (142 days ago)

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

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

[Desktop-packages] [Bug 1658903] Re: Libreoffice print doesn't see the second page.

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

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

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

Title:
   Libreoffice print doesn't see the second page.

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  ubuntu-bug  does not define the process. Libreoffice print
  doesn't see the second page.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: evince 3.22.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 24 11:44:18 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-08-27 (515 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: evince
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (97 days ago)

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

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

[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-04-29 Thread Ibrahim Essam

I had the same problem after upgrading from ubuntu 17.10
It was fixed by removing xorg.conf file

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Desktop-packages] [Bug 1767912] Re: Mouse Keys enabled/enables during session when setting shows disabled

2018-04-29 Thread Karim Hollosi

** Description changed:

After starting a session, the numpad behaves as if Mouse Keys is
enabled. Going to Settings > Universal Access > Mouse Keys shows that
the feature is disabled. To disable Mouse Keys, the setting must be
enabled first, then disabled. Alternatively, the following commands must
be used in terminal:

gsettings set org.gnome.desktop.a11y.keyboard mousekeys-enable true
gsettings set org.gnome.desktop.a11y.keyboard mousekeys-enable false

These settings will only persist for the session. It has been observed
that the function seemingly enables itself during a session, with no
known trigger. At the same time, the num lock or shift + num lock hotkey
does not function. Whether that is a separate bug is another story, but
neither key combination results in the accidental or purposeful
activation or deactivation of Mouse Keys.

Problem observed in Ubuntu 18.04. gsettings-desktop-schemas version
3.28.0-1ubuntu1. Has been previously observed in 17.10 and 16.04.

Current temporary workaround is to add the two commands above into a
script to run on startup. This does not solve inadvertent activations
later on, however.

+ EDIT: Mouse Keys observed to enable itself when I type "xset led on"
+ into terminal to enable keyboard backlight.
+
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 30 06:36:09 2018
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2018-04-28 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
Mouse Keys enabled/enables during session when setting shows disabled

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

Bug description:
After starting a session, the numpad behaves as if Mouse Keys is
enabled. Going to Settings > Universal Access > Mouse Keys shows that
the feature is disabled. To disable Mouse Keys, the setting must be
enabled first, then disabled. Alternatively, the following commands
must be used in terminal:

gsettings set org.gnome.desktop.a11y.keyboard mousekeys-enable true
gsettings set org.gnome.desktop.a11y.keyboard mousekeys-enable false

These settings will only persist for the session. It has been observed
that the function seemingly enables itself during a session, with no
known trigger. At the same time, the num lock or shift + num lock
hotkey does not function. Whether that is a separate bug is another
story, but neither key combination results in the accidental or
purposeful activation or deactivation of Mouse Keys.

Problem observed in Ubuntu 18.04. gsettings-desktop-schemas version
3.28.0-1ubuntu1. Has been previously observed in 17.10 and 16.04.

Current temporary workaround is to add the two commands above into a
script to run on startup. This does not solve inadvertent activations
later on, however.

EDIT: Mouse Keys observed to enable itself when I type "xset led on"
into terminal to enable keyboard backlight.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 30 06:36:09 2018
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2018-04-28 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767921] [NEW] Fails to load GNOME desktop

2018-04-29 Thread Toshihiro Ueki

Public bug reported:

What causes this:
1. Type wrong password to login first.
2. Type right password and login.

After that:
There is nothing on screen but for mouse pointer and dark-purple wallpaper.
And no access to HDD/SSD, because access lamp doesn't flash.

How frequently:
Every time I did that.

Supplement:
I can't distinguish which causes this problem, xorg or gnome.

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] 許可がありません: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 30 12:14:51 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems 4th Gen Core Processor Integrated 
Graphics Controller [1179:0007]
InstallationDate: Installed on 2018-04-27 (3 days ago)
InstallationMedia: 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 002: ID 04f2:b3b2 Chicony Electronics Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: TOSHIBA dynabook R73/NW56E
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ja_JP.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=e1d39ab2-7146-4fd5-985f-7361d7a78a0c ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/23/2015
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 4.80
dmi.board.asset.tag: 00
dmi.board.name: dynabook R73/NW56E
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 00
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion4.80:bd06/23/2015:svnTOSHIBA:pndynabookR73/NW56E:pvrPR73NW56SUAE:rvnTOSHIBA:rndynabookR73/NW56E:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.family: 00
dmi.product.name: dynabook R73/NW56E
dmi.product.version: PR73NW56SUAE
dmi.sys.vendor: TOSHIBA
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 freeze 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/1767921

Title:
  Fails to load GNOME desktop

Status in xorg package in Ubuntu:
  New

Bug description:
  What causes this:
  1. Type wrong password to login first.
  2. Type right password and login.

  After that:
  There is nothing on screen but for mouse pointer and dark-purple wallpaper.
  And no access to HDD/SSD, because access lamp doesn't flash.

  How frequently:
  Every time I did that.

  Supplement:
  I can't distinguish which causes this problem, xorg or gnome.

  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] 許可がありません: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 12:14:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems 4th Gen Core Processor Integrated

[Desktop-packages] [Bug 1767065] Re: [regression] pulseaudio+bluetooth crash causing user to be logged out (since pulseaudio 1:8.0-0ubuntu3.9)

** Summary changed:

- pulseaudio+bluetooth crash causing user to be logged out (since pulseaudio 
1:8.0-0ubuntu3.9)
+ [regression] pulseaudio+bluetooth crash causing user to be logged out (since 
pulseaudio 1:8.0-0ubuntu3.9)

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

Title:
  [regression] pulseaudio+bluetooth crash causing user to be logged out
  (since pulseaudio 1:8.0-0ubuntu3.9)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I'm a sysadmin and have gotten multiple reports recently from users of
  them randomly getting logged out of their machines. From what I can
  tell from the journalctl printout this appears immediately after
  either bluetoothd or pulsaudio crashes.

  This is happening multiple time each day for each user. It doesn't
  happen to all users, but the reports seem to be getting more frequent
  by the day. From what I have noticed there recently was an update for
  pulseaudio and its bluetooth integration.

  Here is the journalctl printout:
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSource
  Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 
path=/MediaEndpoint/A2DPSink
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of 
process 8042 (n/a) owned by '108' high priority at nice level -11.
  Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 
processes of 1 users.
  Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already 
running.
  Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus 
can't be made
  Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): 
session closed for user lightdm

  We are running Ubuntu 16.04 LTS with the latest updated.

  EDIT: Worth mentioning, this error happens with both Unity and Gnome as 
desktop environments.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', 
'/dev/snd/pcmC2D9p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/pcmC2D8p', '/dev/snd/pcmC2D7p', '/dev/snd/controlC1', 
'/dev/snd/pcmC2D3p', '/dev/snd/controlC2', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:8.0-0ubuntu3.9
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  xenial
  Uname: Linux 4.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X299-DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC2D0', 
'/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D9p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/controlC2', 
'/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: pulseaudio 1:8.0-0ubuntu3.9
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu

[Desktop-packages] [Bug 1767784] Re: output device not recognized anymore since update 1:8.0-0ubuntu3.9

** Tags added: regression-update

** Summary changed:

- output device not recognized anymore since update 1:8.0-0ubuntu3.9
+ [regression] output device not recognized anymore since update 
1:8.0-0ubuntu3.9

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

Title:
  [regression] output device not recognized anymore since update
  1:8.0-0ubuntu3.9

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is
  not showing anymore my soundcard.

  The command "pacmd list-sinks" only shows a dummy output

  When running on a fresh install of ubuntu 16.04, the sound is ok.
  When updating the install with locking the following files to version 
1:8.0-0ubuntu3 the sound keeps working:
  libpulse0:amd64
  libpulse-mainloop-glib0:amd64
  libpulse-dev:amd64
  pulseaudio-module-x11:amd64
  pulseaudio-module-bluetooth:amd64
  pulseaudio-utils:amd64

  When updating to 1:8.0-0ubuntu3.9, I just get a "dummy output".

  I tried running the following versions of Ubuntu (live usb), and get the same 
issue (no need to update to get the problem)
  17.04
  17.10
  18.04

  I attached the result of command "pactl list"
  I have also generated logs during the boot but I don't know how to attach 
multiple files

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

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

[Desktop-packages] [Bug 1767730] Re: Chrome / Chrome Browser Title Bar Button Bug

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

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

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


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

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

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Incomplete

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

Title:
  Chrome / Chrome Browser Title Bar Button Bug

Status in Ubuntu theme:
  Incomplete
Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  Chrome / Chrome Browser Title Bar Button Bug

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

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

[Desktop-packages] [Bug 1767258] Re: Atheros QCA9565 bluetooth hardware not detected

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

** This bug is no longer a duplicate of bug 1532267
   Atheros QCA9565 Bluetooth not recognized
** This bug has been marked a duplicate of bug 1475639
   Atheros QCA9565: No adapter found in bluetooth

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

Title:
  Atheros QCA9565 bluetooth hardware not detected

Status in bluez package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  New

Bug description:
  I can't open bluetooth in the setting panel,it's gray.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (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
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 12:01:53 2018
  InstallationDate: Installed on 2018-03-15 (43 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307)
  InterestingModules: bnep btusb bluetooth
  MachineType: Acer TravelMate P257-MG
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=cd20b9a0-1844-4466-9658-8981e660c11a ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: BA50_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.14:bd11/27/2015:svnAcer:pnTravelMateP257-MG:pvrV3.72:rvnAcer:rnBA50_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BDW
  dmi.product.name: TravelMate P257-MG
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer
  hciconfig:

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

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

[Desktop-packages] [Bug 1767912] Re: Mouse Keys enabled/enables during session when setting shows disabled

2018-04-29 Thread Karim Hollosi

Looks like this bug goes all the way back to 8.04, reading the later
comments in the following bug report:

https://bugs.launchpad.net/ubuntu/+source/gnome-control-
center/+bug/197589

Comment 34 onwards.

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

Title:
Mouse Keys enabled/enables during session when setting shows disabled

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

gsettings set org.gnome.desktop.a11y.keyboard mousekeys-enable true
gsettings set org.gnome.desktop.a11y.keyboard mousekeys-enable false

These settings will only persist for the session. It has been observed
that the function seemingly enables itself during a session, with no
known trigger. At the same time, the num lock or shift + num lock
hotkey does not function. Whether that is a separate bug is another
story, but neither key combination results in the accidental or
purposeful activation or deactivation of Mouse Keys.

Problem observed in Ubuntu 18.04. gsettings-desktop-schemas version
3.28.0-1ubuntu1. Has been previously observed in 17.10 and 16.04.

Current temporary workaround is to add the two commands above into a
script to run on startup. This does not solve inadvertent activations
later on, however.

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

[Desktop-packages] [Bug 1767722] Re: Dock groups active programs under wrong Favorite Icon

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

** Summary changed:

- Dock groups active programs under wrong Favorite Icon
+ Nautilus windows get grouped under PhpStorm in the dock

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

Title:
  Nautilus windows get grouped under PhpStorm in the dock

Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  I noticed active Nautilus windows get grouped under PhpStorm (even
  after PhpStorm gets closed) in my doc.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell-extension-ubuntu-dock 0.9.1
  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: Sat Apr 28 13:49:31 2018
  InstallationDate: Installed on 2018-04-27 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  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/1767722/+subscriptions

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

[Desktop-packages] [Bug 1756147] Re: Error/warning on terminal when clicking "Privacy" tab

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

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

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

Title:
  Error/warning on terminal when clicking "Privacy" tab

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

Bug description:
  Many error/warning messages are written to the terminal (stdout and/or
  stderr) when operating gnome-control-center.

  For example, clicking the "Privacy" category tab produces this:

  (gnome-control-center:11277): privacy-cc-panel-WARNING **: 10:27:13.217: 
Failed fetch permissions from flatpak permission store: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.impl.portal.PermissionStore was not provided by any .service 
files
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.2-0ubuntu0.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Tags: artful third-party-packages
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1767711] Re: window is see-through during playback, colours washed out

Do you find the same problem in gedit and gnome-calculator? (bug
1760818)

** Description changed:

- Since the upgrade to Ubuntu 18.10, the Totem player will show everything
+ Since the upgrade to Ubuntu 18.04, the Totem player will show everything
  behind it during playback, and the colours of the video are washed-out.
  https://i.imgur.com/0AwJMmf.jpg  I did not find 'tranparency' nor
  'opacity' setting in the program preferences, and the colour adjudgement
  settings are pinned to +/-0.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Apr 28 14:56:29 2018
  InstallationDate: Installed on 2016-06-05 (692 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: totem
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (1 days ago)

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

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

Title:
  window is see-through during playback, colours washed out

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Since the upgrade to Ubuntu 18.04, the Totem player will show
  everything behind it during playback, and the colours of the video are
  washed-out.  https://i.imgur.com/0AwJMmf.jpg  I did not find
  'tranparency' nor 'opacity' setting in the program preferences, and
  the colour adjudgement settings are pinned to +/-0.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Apr 28 14:56:29 2018
  InstallationDate: Installed on 2016-06-05 (692 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: totem
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (1 days ago)

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

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

[Desktop-packages] [Bug 1736820] Re: Laptop doesn't suspend on lid close

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

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

Title:
  Laptop doesn't suspend on lid close

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Laptop is Thinkpad T450. On previous releases of Ubuntu I would close
  the lid to suspend it. 17.10 doesn't suspend on lid close, which has
  caused my laptop to overheat in my bag a couple of times.

  I have installed tweak tool and made sure the power section toggle
  switch is on. But it makes no difference. I have also tried rebooting,
  flipping the toggle back and forth, and still nothing.

  Should I see a key change somewhere in dconf-editor once I flip the switch? 
  Does suspend work for others, on the T450?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  6 23:25:07 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' b"['xkill', 'goxel']"
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'google-chrome.desktop', 
'chrome-hebeiaianhihkafkbopcfpkgloimgagb-Default.desktop', 'discord.desktop', 
'chrome-flidaonfhnkbealpaagddgffpppelhhb-Profile_1.desktop', 
'chrome-celnaknmndcdcjcagffhbhciignkeokb-Default.desktop', 
'chrome-dcdbodpaldbchkfinnjphocleggfceip-Default.desktop', 
'chrome-ddiddklncfgbfaaahngklemobghhjkim-Default.desktop', 
'chrome-fimghoffjcofmboofohmacdeabiimdeg-Profile_1.desktop', 
'irccloud-desktop_irccloud-desktop.desktop', 'telegramdesktop.desktop', 
'org.gnome.Terminal.desktop', 'code.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-08-02 (126 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  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/1736820/+subscriptions

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

[Desktop-packages] [Bug 1767715] Re: suspend to RAM not working in 18.04

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

It looks like you might have 2 or 3 different bugs here.

The failure to suspend is reported in bug 1736820 and others.

The gnome-shell assertion is bug 1730254.

** This bug has been marked a duplicate of bug 1736820
   Laptop doesn't suspend on lid close

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

Title:
  suspend to RAM not working in 18.04

Status in gdm3 package in Ubuntu:
  Confirmed

Bug description:
  System: Ubuntu 18.04 fresh install
  HW: Macbook Pro Retina 15"

  Settings in Tweak: Suspend on Lid closed

  The machine does not suspend after lid is closed

  syslog: ---
  Apr 28 21:42:18 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:18 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:19 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:19 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:22 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:22 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:26 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:26 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:26 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:26 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:34 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:34 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:34 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:34 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:35 mbpr15a gnome-shell[1460]: _st_paint_shadow_with_opacity: 
assertion 'shadow_pipeline != NULL' failed

  ...
  -

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 21:46:37 2018
  InstallationDate: Installed on 2018-04-28 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767668] Re: GNOME Shell stuck at lock screen for a long time when undocked

Yeah the delays look like they're triggered by changes in your network
interfaces (e.g. the removal of the dock/ethernet interface):

Apr 28 16:27:59 farnsworth nm-dispatcher: find-scripts: Cannot execute 
'/etc/NetworkManager/dispatcher.d/test': not executable by owner.
Apr 28 16:27:59 farnsworth nm-dispatcher: req:5 'connectivity-change': new 
request (1 scripts)
Apr 28 16:27:59 farnsworth nm-dispatcher: req:5 'connectivity-change': start 
running ordered scripts...
Apr 28 16:28:00 farnsworth systemd-resolved[1528]: Using degraded feature set 
(UDP) for DNS server 192.168.42.254.
Apr 28 16:30:02 farnsworth kernel: [24130.753251] nfs: server calculon not 
responding, timed out
Apr 28 16:30:05 farnsworth kernel: [24133.825210] nfs: server calculon not 
responding, timed out
Apr 28 16:31:22 farnsworth /usr/lib/gdm3/gdm-x-session[5449]: (**) Option "fd" 
"28"
Apr 28 16:31:22 farnsworth /usr/lib/gdm3/gdm-x-session[5449]: (II) event2  - 
Power Button: device removed


** Tags added: unlock

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

Title:
  GNOME Shell stuck at lock screen for a long time when undocked

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Steps to reproduce on my Thinkpad X270

  1.  Start with laptop docked with internal and external screen in use
  2.  Lock machine (and potentially wait for blank screen to kick in - need to 
test)
  3.  Undock
  4.  Hit a key to wake screen up
  5.  Notice that the lock screen doesn't scroll up immediately
  6.  Wait for a couple of minutes until lock screen clears and you can type 
your password again
  7.  Notice that even though you can now use the desktop, you can switch to 
tty3, 4, etc

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

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

[Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled

2018-04-29 Thread Bug Watch Updater

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

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

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

Title:
  Top bar and shell dialogs are not displayed properly when zoom is
  enabled

Status in Mutter:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When zoom is enabled, the top bar and some shell dialogs (wireless
  network selection, shutdown dialog, etc.) are not displayed properly.
  (See the attached screenshots.)

  Steps to reproduce the issue:
  1. Enable Zoom in Setting > Universal Access
  2. (Optional) Set zoom factor to around 3 (or higher)
  3. Look at the top bar. You will notice that all texts and icons are now 
gone. If you move your cursor to the right of the top bar, and then click on 
the status menu, you will see that only a portion of the menu is shown.
  4. For the shell dialogs, go to the Settings app. In the Wifi section, choose 
one of the secured network available. You will see that the password dialog is 
not displayed in its entirety.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 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
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 12:54:24 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-size' b'96'
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled

Please help the Gnome developers to diagnose this problem by reporting it 
upstream here:
https://gitlab.gnome.org/GNOME/gnome-shell/issues

** Tags added: zoom

** Tags added: visual-quality

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

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

Title:
  Top bar and shell dialogs are not displayed properly when zoom is
  enabled

Status in Mutter:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When zoom is enabled, the top bar and some shell dialogs (wireless
  network selection, shutdown dialog, etc.) are not displayed properly.
  (See the attached screenshots.)

  Steps to reproduce the issue:
  1. Enable Zoom in Setting > Universal Access
  2. (Optional) Set zoom factor to around 3 (or higher)
  3. Look at the top bar. You will notice that all texts and icons are now 
gone. If you move your cursor to the right of the top bar, and then click on 
the status menu, you will see that only a portion of the menu is shown.
  4. For the shell dialogs, go to the Settings app. In the Wifi section, choose 
one of the secured network available. You will see that the password dialog is 
not displayed in its entirety.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 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
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 12:54:24 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-size' b'96'
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767912] [NEW] Mouse Keys enabled/enables during session when setting shows disabled

2018-04-29 Thread Karim Hollosi

Public bug reported:

After starting a session, the numpad behaves as if Mouse Keys is
enabled. Going to Settings > Universal Access > Mouse Keys shows that
the feature is disabled. To disable Mouse Keys, the setting must be
enabled first, then disabled. Alternatively, the following commands must
be used in terminal:

gsettings set org.gnome.desktop.a11y.keyboard mousekeys-enable true
gsettings set org.gnome.desktop.a11y.keyboard mousekeys-enable false

These settings will only persist for the session. It has been observed
that the function seemingly enables itself during a session, with no
known trigger. At the same time, the num lock or shift + num lock hotkey
does not function. Whether that is a separate bug is another story, but
neither key combination results in the accidental or purposeful
activation or deactivation of Mouse Keys.

Problem observed in Ubuntu 18.04. gsettings-desktop-schemas version
3.28.0-1ubuntu1. Has been previously observed in 17.10 and 16.04.

Current temporary workaround is to add the two commands above into a
script to run on startup. This does not solve inadvertent activations
later on, however.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 30 06:36:09 2018
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2018-04-28 (1 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

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

Title:
  Mouse Keys enabled/enables during session when setting shows disabled

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

Bug description:
  After starting a session, the numpad behaves as if Mouse Keys is
  enabled. Going to Settings > Universal Access > Mouse Keys shows that
  the feature is disabled. To disable Mouse Keys, the setting must be
  enabled first, then disabled. Alternatively, the following commands
  must be used in terminal:

  gsettings set org.gnome.desktop.a11y.keyboard mousekeys-enable true
  gsettings set org.gnome.desktop.a11y.keyboard mousekeys-enable false

  These settings will only persist for the session. It has been observed
  that the function seemingly enables itself during a session, with no
  known trigger. At the same time, the num lock or shift + num lock
  hotkey does not function. Whether that is a separate bug is another
  story, but neither key combination results in the accidental or
  purposeful activation or deactivation of Mouse Keys.

  Problem observed in Ubuntu 18.04. gsettings-desktop-schemas version
  3.28.0-1ubuntu1. Has been previously observed in 17.10 and 16.04.

  Current temporary workaround is to add the two commands above into a
  script to run on startup. This does not solve inadvertent activations
  later on, however.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 06:36:09 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-04-28 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled

Actually, maybe don't bother.

I think this may be a known bug:
https://bugzilla.gnome.org/show_bug.cgi?id=789050

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

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

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

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

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

Title:
  Top bar and shell dialogs are not displayed properly when zoom is
  enabled

Status in Mutter:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When zoom is enabled, the top bar and some shell dialogs (wireless
  network selection, shutdown dialog, etc.) are not displayed properly.
  (See the attached screenshots.)

  Steps to reproduce the issue:
  1. Enable Zoom in Setting > Universal Access
  2. (Optional) Set zoom factor to around 3 (or higher)
  3. Look at the top bar. You will notice that all texts and icons are now 
gone. If you move your cursor to the right of the top bar, and then click on 
the status menu, you will see that only a portion of the menu is shown.
  4. For the shell dialogs, go to the Settings app. In the Wifi section, choose 
one of the secured network available. You will see that the password dialog is 
not displayed in its entirety.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 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
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 12:54:24 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-size' b'96'
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

** Summary changed:

- Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop 
with an Intel GPU)
+ Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a 
desktop with an Intel GPU)

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

Title:
  Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on
  a desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS.

  * Add 'nomodeset' to your kernel command line.

  
  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

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

[Desktop-packages] [Bug 1767312] Re: totem wrong color on h264 videos

Please also try this as a workaround:

sudo apt remove mesa-va-drivers

** Package changed: totem (Ubuntu) => gstreamer-vaapi (Ubuntu)

** Changed in: gstreamer-vaapi (Ubuntu)
   Importance: Low => High

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

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

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

** Tags added: radeon

** Summary changed:

- totem wrong color on h264 videos
+ [radeon] totem wrong color on h264 videos

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

Title:
  [radeon] totem wrong color on h264 videos

Status in gstreamer-vaapi package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian 
stable, debian testing) aren't affected).
  When i try to reproduce a video that use h264 codec, i've wrong colors.
  I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6

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

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

[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

Joseph, Zihang, that is bug 1765261. Not this one.

Also, if you find yourself logged out unexpectedly, please look for
crash files in /var/crash and report them using the 'ubuntu-bug'
command.

Finally, if anyone is experiencing this particular bug then please help 
upstream to debug it here:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/227

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

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

Status in gdm:
  New
Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  WORKAROUND: After typing an incorrect password, click Cancel, then
  click your name, then enter your password again.

  ---

  Trying to log into my session (Gnome, Xorg), if I enter the wrong
  password before entering it correctly, the session doesn't load and I
  get a purple screen, a mouse cursor, and an invisible but clickable
  menu in the top right. If I enter it correctly the first time, there
  is no problem.

  I've replicated this from a fresh boot, after logging out and after
  'sudo service gdm restart' from the Ctrl-Alt-F4 console.

  This is a fresh install, and didn't occur when I was using a previous
  install of 18.04 (until Friday).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  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: Sun Apr 22 20:31:13 2018
  InstallationDate: Installed on 2018-04-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767494] Re: Some Gnome Shell extensions are visible and active in Lock Screen

Gnome Shell can't control what extensions do.

Bugs caused by extensions need to be fixed in those extensions.

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

** Information type changed from Public to Public Security

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

Title:
  Some Gnome Shell extensions are visible and active in Lock Screen

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

Bug description:
  This is a bad Gnome Shell security flaw. When the screen is locked,
  nothing should be available. But I see the Dash do Dock extension and
  I can even start applications from it. Even though I cannot see the
  apps running, but when I unlock, I can see them. This is a huge
  security risk and should be fixed asap in Gnome. This is both in
  Ubuntu 17.10 and 18.04.

  I have reported upstream, too:
  https://bugzilla.gnome.org/show_bug.cgi?id=795615

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 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: Fri Apr 27 22:58:26 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['ubuntu-appindicat...@ubuntu.com', 'weather-extens...@xeked.com', 
'dash-to-d...@micxgx.gmail.com', 'weatherinthecl...@jasonlg1979.github.io', 
'ubuntu-d...@ubuntu.com']"
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'show-battery-percentage' b'true'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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-extension-dashtodock/+bug/1767494/+subscriptions

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

[Desktop-packages] [Bug 1765261] Re: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt. Usually works on the second attempt

Excellent news. Thanks!

Upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/240

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

** Description changed:

+ Upstream:
+ https://gitlab.gnome.org/GNOME/gnome-shell/issues/240
+ 
  Ubuntu 18.04 login screen rejects a valid password on first attempt.
  Always works on the second attempt..
  
  This seems to be a new problem, just started today.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Thu Apr 19 11:16:17 2018
  InstallationDate: Installed on 2017-12-12 (127 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

** Tags added: fixed-in-3.28.2 fixed-in-3.29.2

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

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

** Changed in: gnome-shell (Ubuntu)
   Status: Triaged => 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/1765261

Title:
  [regression] Ubuntu 18.04 login screen rejects a valid password on
  first attempt. Usually works on the second attempt

Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  Upstream:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/240

  Ubuntu 18.04 login screen rejects a valid password on first attempt.
  Always works on the second attempt..

  This seems to be a new problem, just started today.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Thu Apr 19 11:16:17 2018
  InstallationDate: Installed on 2017-12-12 (127 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gdm3
  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/1765261/+subscriptions

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

[Desktop-packages] [Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback

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

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  There is not stereo playback only mono playback

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
   /dev/snd/controlC1:  kaj1755 F pulseaudio
   /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
   /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
  Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS2AV00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.product.name: 20FMS2AV00
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1714749] Re: Screen tearing with when PSR (Panel Self Refresh) is enabled

** Summary changed:

- Screen tearing with when PSR is enabled
+ Screen tearing with when PSR (Panel Self Refresh) is enabled

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

Title:
  Screen tearing with when PSR (Panel Self Refresh) is enabled

Status in X.Org X server:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I've been experiencing pretty bad screen tearing on 17.10 on my XPS 13
  9560 with Kaby Lake. I did not experience this on 16.04/16.10 and IIRC
  not even on 17.04.

  After a lot of hit and trial, I was able to fix the issue completely
  by disabling Intel PSR mode in Grub config.

  Change `i915.enable_psr=1` to `i915.enable_psr=0` in
  `/boot/grub/grub.cfg` fixed the problem for me but I think this
  disables some power saving features.

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

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

[Desktop-packages] [Bug 1603183] Re: Bottom right area of touchpad no longer treated as right click

Libinput does not related to this bug.

Maybe see bug 1759300 instead.

** Changed in: libinput (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Bottom right area of touchpad no longer treated as right click

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Triaged
Status in gsettings-ubuntu-touch-schemas package in Ubuntu:
  Fix Released
Status in libinput package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Invalid
Status in unity8-desktop-session package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Using the touchpad I was not able to trigger any right click (with a
  single finger in the bottom right area), and I tought it was a problem
  of how unity8 handled the right clicks. Instead I just tried with a
  mouse and right click trigger different actions from left clicks.

  In the end the problem is that my touchpad right click is considered a
  left click by the system. This does not happen with an usb mouse.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1603183/+subscriptions

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

[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

** Tags added: bionic

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS.

  * Add 'nomodeset' to your kernel command line.

  
  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

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

[Desktop-packages] [Bug 1692394] Re: Speaker volume overlay sometimes jitters left/right slightly when pressing volume keys

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

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

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

Title:
  Speaker volume overlay sometimes jitters left/right slightly when
  pressing volume keys

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  When I press the volume keys on my keyboard the shell displays an
  overlay showing the volume level. Normally this overlay is stationary,
  but sometimes when adjusting the volume, the overlay shifts slightly a
  pixel or two left or right.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu3
  Architecture: amd64
  Date: Mon May 22 11:02:57 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'yelp.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (18 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767383] Re: touchpad right+click not working

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

The GUI way of applying that is:

gnome-tweaks > Keyboard & Mouse > Touchpad > Mouse Click Emulation =
Area

But that is certainly not adequately discoverable. You have to install
'gnome-tweaks' too.

I think the right solution is to get the above setting moved into gnome-
control-center where people can find it. I think someone might have
logged that feature request already but I can't find it right now.

P.S. I disagree with your suggested fix. Most Dell/Lenovos use clickpads
these days, just like Apple.

** This bug has been marked a duplicate of bug 1759300
   touchpad right click

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

Title:
  touchpad right+click not working

Status in libinput package in Ubuntu:
  New
Status in xserver-xorg-input-synaptics package in Ubuntu:
  New

Bug description:
  - Freshly installed 18.04 (from 16.04, in which everything was working
  great).  This behavior is consistent across several tested
  applications (firefox, ubuntu desktop, terminal).

  What I expected to happen:
   1. I right click the touchpad, see appropriate response from relevant 
application under mouse.

  What actually happened:
   1. The right click is registered as a primary click, so there was not an 
appropriate response.

  Notes:
   1. The two-finger-tap works fine, and generates the appropriate right+click 
response from all tested apps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-input-synaptics 1.9.0-1ubuntu1
  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'
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 09:02:56 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Precision 5520
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=8c6fa604-8659-4664-ab49-b2428cf656fd ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 0R6JFH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/25/2018:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.
  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/libinput/+bug/1767383/+subscriptions

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

[Desktop-packages] [Bug 1262043] Re: failed to record video.

2018-04-29 Thread igor Cerqueira

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

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

Title:
  failed to record video.

Status in cheese package in Ubuntu:
  Fix Released

Bug description:
  It happens when I click "record a video".

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

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

[Desktop-packages] [Bug 1262043] Re: failed to record video.

2018-04-29 Thread igor Cerqueira

** Description changed:

  Failure happens when I'm recording a video, when I press "record a
- video" simplisme the cheese hangs, from what I know it's happening on
- multiple computers.
+ video".

** Description changed:

- Failure happens when I'm recording a video, when I press "record a
- video".
+ Failure happens when I click "record a video".

** Description changed:

- Failure happens when I click "record a video".
+ It happens when I click "record a video".

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

Title:
  failed to record video.

Status in cheese package in Ubuntu:
  Fix Released

Bug description:
  It happens when I click "record a video".

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

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

[Desktop-packages] [Bug 1767908] [NEW] when I click "install" nothing happens

2018-04-29 Thread igor Cerqueira

Public bug reported:

I can't install apps (.deb) correctly with Ubuntu Software, when I click
"install" nothing happens, but some minutes later the app appears
already installed in my applications list.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.1-0ubuntu4
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: Sun Apr 29 22:04:04 2018
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2018-04-29 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.28.1-0ubuntu4
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  when I click "install" nothing happens

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I can't install apps (.deb) correctly with Ubuntu Software, when I
  click "install" nothing happens, but some minutes later the app
  appears already installed in my applications list.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4
  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: Sun Apr 29 22:04:04 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-04-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767903] [NEW] I am unable to connect external LCD to my laptop via HDMI

2018-04-29 Thread Abdullah Ahmed

Public bug reported:

This issue pop-up after I upgraded to 18.04 LTS. (It was working fine on
16.04)

In graphics section, I am seeing Gallium 0.4 but my graphics are Intel
HD 520

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
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 30 05:56:30 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
 virtualbox, 5.2.10, 4.4.0-121-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:5049]
   Subsystem: Lenovo Mars [Radeon HD 8670A/8670M/8750M] [17aa:5049]
InstallationDate: Installed on 2017-01-23 (461 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:57e3 Realtek Semiconductor Corp. 
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 09da:010e A4Tech Co., Ltd. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20EV0004UE
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=9e6972ea-13cb-4a69-ba84-efbfda8ae024 ro recovery nomodeset
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/12/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: R00ET41W (1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20EV0004UE
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR00ET41W(1.16):bd04/12/2016:svnLENOVO:pn20EV0004UE:pvrThinkPadE560:rvnLENOVO:rn20EV0004UE:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad E560
dmi.product.name: 20EV0004UE
dmi.product.version: ThinkPad E560
dmi.sys.vendor: LENOVO
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: Mon Apr 30 05:07:12 2018
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4

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


** Tags: amd64 apport-bug bionic third-party-packages 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/1767903

Title:
  I am unable to connect external LCD to my laptop via HDMI

Status in xorg package in Ubuntu:
  New

Bug description:
  This issue pop-up after I upgraded to 18.04 LTS. (It was working fine
  on 16.04)

  In graphics section, I am seeing Gallium 0.4 but my graphics are Intel
  HD 520

  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
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 05:56:30 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
   virtualbox, 5.2.10, 4.4.0-121-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:5049]
 Subsystem: Lenovo Mars [Radeon HD 8670A/8670M/8750M] [17aa:5049]
  InstallationDate: Installed on 2017-01-23 (461 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:57e3 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus

[Desktop-packages] [Bug 1767454] Re: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04

2018-04-29 Thread Bug Watch Updater

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

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

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

Title:
  "Other Locations" does not automatically find Samba servers in Ubuntu
  18.04

Status in gvfs:
  Confirmed
Status in samba:
  Unknown
Status in nautilus package in Ubuntu:
  New
Status in samba package in Ubuntu:
  New

Bug description:
  Ubuntu: 18.04 clean install
  Nautilus: 1:3.26.3-0ubuntu4

  The actions taken to produce the problem:
  Click on “Other Locations” in Nautilus.

  The expected result of these actions:
  Samba servers to automatically show up under “Networks”. This is the behavior 
in Ubuntu 17.10 using Nautilus 1:3.26.0-0ub. Also, clicking on “”Windows 
Network” immediately shows "Folder is Empty".

  The actual result of these actions:
  The Samba servers never show up under “Networks” and clicking on "Windows 
Network" always immediately comes up with "Folder is Empty".

  Further information:
  This happens on both machines with a clean Ubuntu 18.04 install. My Ubuntu 
17.10 machines still work like expected.

  I can still manually type in the Samba information in "Connect to
  Server" and the 18.04 machines connect just fine.

  
  From syslog:
  Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 
pid=1333] Activating service name='org.gnome.Nautilus' requested by ':1.13' 
(uid=1000 pid=1468 comm="/usr/bin/gnome-shell " label="unconfined")
  Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 
pid=1333] Successfully activated service 'org.gnome.Nautilus'
  Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Activating 
via systemd: service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.131' (uid=1000 
pid=4857 comm="/usr/bin/nautilus --gapplication-service " label="unconfined")
  Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Starting Hostname 
Service...
  Apr 27 13:49:35 david-HP-ProBook-440-G2 nautilus[4857]: Called "net usershare 
info" but it failed: Failed to execute child process “net” (No such file or 
directory)
  Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] 
Successfully activated service 'org.freedesktop.hostname1'
  Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Started Hostname Service.
  Apr 27 13:49:40 david-HP-ProBook-440-G2 gvfsd[1432]: mkdir failed on 
directory /var/cache/samba: Permission denied

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

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

[Desktop-packages] [Bug 1767900] [NEW] Ubuntu can't log into starbucks WIFI

2018-04-29 Thread Ole

Public bug reported:

Summarized the problem and the solution here.  Apparently all other OSs
can authenticate, hence it must be an Ubuntu issue:

https://askubuntu.com/questions/1023429/cant-connect-to-google-
starbucks-wifi-on-ubuntu-17-10/1029893#1029893

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

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

Title:
  Ubuntu can't log into starbucks WIFI

Status in network-manager package in Ubuntu:
  New

Bug description:
  Summarized the problem and the solution here.  Apparently all other
  OSs can authenticate, hence it must be an Ubuntu issue:

  https://askubuntu.com/questions/1023429/cant-connect-to-google-
  starbucks-wifi-on-ubuntu-17-10/1029893#1029893

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

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

[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-04-29 Thread Bernadette Addison

Edited to add: I’ve also tried disabling the nouveau-nvidia drivers
before and then after installing the nvidia-390 drivers but still not
working.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-04-29 Thread Bernadette Addison

Having the same issue as most users here. Installed fresh copy of 18.04
to brand new hard drive, brand new dell XPS 15. Nvidia GTX 1050 on
boardInstalled drivers nvidia-390 from ppa. Now the machine will
only boot to black dos screen and I am not even able to get to the tty
because none of the combination key commands work. My only recourse is
to install from scratch again. Tried this with the normal installation
and with the minimal installation. Nvidia drivers simply do not work.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Desktop-packages] [Bug 1704781] Re: With gdm3 a restart is needed when switching prime profiles

2018-04-29 Thread Doug McMahon

Last year this may have mattered. (17.10
 Now in 18.04 a restart is required  anyway so marking invalid.

** Changed in: nvidia-prime (Ubuntu)
   Status: Confirmed => Invalid

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

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

Title:
  With gdm3 a restart is needed when switching prime profiles

Status in gdm3 package in Ubuntu:
  Invalid
Status in nvidia-prime package in Ubuntu:
  Invalid

Bug description:
  Test case:
  Install nvidia drivers ,restart.
  Open nvidia-settings, switch prime profile.
  Will be prompted to log out/in, do so

  What happens: user goes into a log in loop
  To actually get back to the ubuntu-session one must restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nvidia-prime 0.8.4
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jul 17 07:57:24 2017
  InstallationDate: Installed on 2017-07-15 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170708)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1241745] Re: 10de:0dfa [HP EliteBook 8560w] Changing the screen brightness does not work anymore in 319.xx

2018-04-29 Thread peddanet

So 5 years and the bug still seems to be in version 390??

I have ASUS ROG G752VS with NVIDIA GTX 1070, and I can adjust the
keyboard backlight but not the display brightness. iN The Nvidia server
settings I can adjust a little bit the contrast...

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

Title:
  10de:0dfa [HP EliteBook 8560w] Changing the screen brightness does not
  work anymore in 319.xx

Status in Nvidia:
  Confirmed
Status in nvidia-graphics-drivers-319 package in Ubuntu:
  Triaged

Bug description:
  Changing the screen brightness always used to work on my HP Elitebook
  8560w -- both with the function keys and in the dialog "Brightness &
  Lock" in the system settings. The environment light sensor also used
  to work IIRC.

  Since the update to 13.10, this stopped working. Methods I have tried that 
didn't work for adapting the brightness are:
  * Adding GRUB_CMDLINE_LINUX="acpi_backlight=vendor" to /etc/default/grub
  * Adding GRUB_CMDLINE_LINUX=”acpi_osi="!Windows 2012" to /etc/default/grub

  Currently I am changing the brightness manually using  xrandr --output
  LVDS-0 --brightness 0.9. However, AFAIK this does not really change
  the brightness, but only changes the contrast.

  WORKAROUND: Use nvidia-graphics-drivers-304.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  319.60  Wed Sep 25 14:28:26 
PDT 2013
   GCC version:  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8)
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Oct 18 19:50:36 2013
  DistUpgraded: 2013-10-17 17:20:47,580 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-319-updates, 319.60, 3.11.0-12-generic, x86_64: installed
   nvidia-319-updates, 319.60, 3.8.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF108GLM [Quadro 1000M] [10de:0dfa] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:1631]
  InstallationDate: Installed on 2013-01-06 (285 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  JockeyStatus:
   kmod:nvidia_319_updates - nvidia_319_updates (Proprietary, Enabled, Not in 
use)
   kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
   kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:nvidia_319 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
  MachineType: Hewlett-Packard HP EliteBook 8560w
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=53f83a14-cacc-48fd-bb4b-354d69eb7f0e ro quiet splash 
"acpi_osi=!Windows 2012"
  SourcePackage: xorg
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (1 days ago)
  dmi.bios.date: 06/11/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SVD Ver. F.27
  dmi.board.name: 1631
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 01.3B
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SVDVer.F.27:bd06/11/2012:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3B:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8560w
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1

[Desktop-packages] [Bug 1759468] Re: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_c

e.u.c still get reports from users on gtk .30, seems like the gtk fix is
not working?

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

Title:
  gnome-control-center (11) gtk_style_context_clear_property_cache →
  gtk_css_widget_node_update_style → gtk_css_node_ensure_style →
  gtk_css_node_ensure_style → gtk_css_node_validate_internal

Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.28.0-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/6b1f4dd86167bf5eb53ddca8469b5084208ddd22 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1767872] [NEW] /usr/bin/nautilus:ERROR:../src/nautilus-file.c:721:nautilus_file_get_internal: assertion failed: (location != NULL)

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
nautilus.  This problem was most recently seen with package version 
1:3.26.3-0ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/868bb572668dceedfb0e3acd9b17197ca0208938 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: bionic

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

Title:
  /usr/bin/nautilus:ERROR:../src/nautilus-
  file.c:721:nautilus_file_get_internal: assertion failed: (location !=
  NULL)

Status in nautilus package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
nautilus.  This problem was most recently seen with package version 
1:3.26.3-0ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/868bb572668dceedfb0e3acd9b17197ca0208938 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1767871] [NEW] /usr/bin/gnome-control-center:11:maybe_add_app_id:children_changed:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.28.1-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/3a5b4bfcb598ac34a0b6249c7ce3787819dd2065 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: artful bionic zesty

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

Title:
  /usr/bin/gnome-control-
  
center:11:maybe_add_app_id:children_changed:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.28.1-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/3a5b4bfcb598ac34a0b6249c7ce3787819dd2065 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1767873] [NEW] /usr/lib/gnome-initial-setup/gnome-initial-setup:double free or corruption (!prev)

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-initial-setup.  This problem was most recently seen with package version 
3.28.0-2ubuntu6, the problem page at 
https://errors.ubuntu.com/problem/9e80579a18180e27a9a2ae3a0bef59f87858bba0 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Affects: gnome-initial-setup (Ubuntu)
 Importance: High
 Assignee: Robert Ancell (robert-ancell)
 Status: New


** Tags: bionic

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

Title:
  /usr/lib/gnome-initial-setup/gnome-initial-setup:double free or
  corruption (!prev)

Status in gnome-initial-setup package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-initial-setup.  This problem was most recently seen with package version 
3.28.0-2ubuntu6, the problem page at 
https://errors.ubuntu.com/problem/9e80579a18180e27a9a2ae3a0bef59f87858bba0 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1767877] [NEW] /usr/bin/gnome-software:realloc(): invalid old size

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.28.1-0ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/ef4d4c0327e15e2fad0077b413cefdcf872f8a8a 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Affects: gnome-software (Ubuntu)
 Importance: High
 Assignee: Robert Ancell (robert-ancell)
 Status: New


** Tags: bionic

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

Title:
  /usr/bin/gnome-software:realloc(): invalid old size

Status in gnome-software package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.28.1-0ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/ef4d4c0327e15e2fad0077b413cefdcf872f8a8a 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1767878] [NEW] /usr/bin/gnome-software:11:_int_free:GI_libc_free:g_free:array_free:snapd_client_finalize

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.28.1-0ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/402021ea77c81f4377e02e5e8813a8d6c4206a01 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Affects: gnome-software (Ubuntu)
 Importance: High
 Assignee: Robert Ancell (robert-ancell)
 Status: New


** Tags: bionic

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

Title:
  /usr/bin/gnome-
  software:11:_int_free:__GI___libc_free:g_free:array_free:snapd_client_finalize

Status in gnome-software package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.28.1-0ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/402021ea77c81f4377e02e5e8813a8d6c4206a01 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1767877] Re: /usr/bin/gnome-software:realloc(): invalid old size

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

** Changed in: gnome-software (Ubuntu)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  /usr/bin/gnome-software:realloc(): invalid old size

Status in gnome-software package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.28.1-0ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/ef4d4c0327e15e2fad0077b413cefdcf872f8a8a 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1767878] Re: /usr/bin/gnome-software:11:_int_free:GI_libc_free:g_free:array_free:snapd_client_finalize

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

** Changed in: gnome-software (Ubuntu)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  /usr/bin/gnome-
  software:11:_int_free:__GI___libc_free:g_free:array_free:snapd_client_finalize

Status in gnome-software package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.28.1-0ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/402021ea77c81f4377e02e5e8813a8d6c4206a01 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1767650] Re: Screen rotates upside-down when laptop is not flat

Could you give the output of those commands?
 $ G_MESSAGES_DEBUG=all /usr/sbin/iio-sensor-proxy
 $ udevadm info --export-db | grep iio


** Package changed: gdm3 (Ubuntu) => iio-sensor-proxy (Ubuntu)

** Changed in: iio-sensor-proxy (Ubuntu)
   Importance: Undecided => Low

** Changed in: iio-sensor-proxy (Ubuntu)
   Status: New => Incomplete

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

Title:
  Screen rotates upside-down when laptop is not flat

Status in iio-sensor-proxy package in Ubuntu:
  Incomplete

Bug description:
  HP Elitebook Folio 9470m.  This system is not a tablet or convertible,
  and does not have a touchscreen.

  If the laptop is sitting flat during boot, the display orientation is
  normal.

  If the laptop is not sitting flat during boot, or if it is moved out
  of flat, the display rotates and the orientation it rotates to is
  inverted upside-down.

  This happens at the login screen as well as after login.

  This laptop should really never have the screen rotate in the first
  place, as it's not a tablet or convertible, but in the event that
  rotation is happening it shouldn't be upside-down.

  
  I have locked the rotation in gnome shell and in the login screen using the 
rotation lock button in the respective system menus.  It would be nice if there 
was a system-wide setting & this didn't need to be done on a per-user basis.

  This gsettings command will also lock the gnome-shell rotation:

  gsettings set org.gnome.settings-daemon.peripherals.touchscreen
  orientation-lock true

  However the above key doesn't affect the login screen, which has its
  own separate rotation button in its own version of the system menu.

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  Codename: bionic
  $ apt-cache policy gdm3
  gdm3:
Installed: 3.28.0-0ubuntu1
Candidate: 3.28.0-0ubuntu1
Version table:
   *** 3.28.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.28.1-0ubuntu2
Candidate: 3.28.1-0ubuntu2
Version table:
   *** 3.28.1-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  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: Sat Apr 28 09:17:35 2018
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1767650/+subscriptions

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

[Desktop-packages] [Bug 1765363] Re: prime-select intel is not powering off the nvidia card

2018-04-29 Thread Alain Rouet

Seems like you're right, François. I installed Powertop on both Ubuntu 18.04 
(~12.5W at idle) and Fedora 27 (~5W) on the same laptop to measure the power 
comsumption. The method is not what I'd call scientific, but the difference is 
big enough to tell there's indeed something wrong.
On Fedora, I installed the proprietary driver via RPM Fusion, and disabled it 
with "modprobe.blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm" kernel 
parameter.

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

Title:
  prime-select intel is not powering off the nvidia card

Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  Right now, it seems that prime-select intel makes sure the nvidia driver is 
not loaded, as nvidia-settings reports.
  But my power consumption is > 20W.
  cat /proc/acpi/bbswitch reports the card is still on. 

  
  If bbswitch and powertop are reliable, then the nvidia card is still powered.
  This is a thinkpad w520 in Optimus mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-prime 0.8.7
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 19 19:56:21 2018
  Dependencies:
   
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-12-14 (125 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: nvidia-prime
  UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago)

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

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

[Desktop-packages] [Bug 1767312] Re: totem wrong color on h264 videos

Could you include the output of the command "dpkg -l | grep gstreamer"?

Do you get the issue on any h264 video? Do you use an xorg or wayland
session and what is your video driver?

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

** Changed in: totem (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  totem wrong color on h264 videos

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian 
stable, debian testing) aren't affected).
  When i try to reproduce a video that use h264 codec, i've wrong colors.
  I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6

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

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

[Desktop-packages] [Bug 1643282] Re: key-direction not respected on OVPN import

The fix was added in 1.8.0 which is in bionic

** Changed in: network-manager-openvpn (Ubuntu)
   Importance: Undecided => Low

** Changed in: network-manager-openvpn (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  key-direction not respected on OVPN import

Status in network-manager-openvpn package in Ubuntu:
  Fix Released

Bug description:
  When creating a VPN connection in Network Manager by importing an
  existing .ovpn file, the key-direction field is not respected.

  I needed to manually go into Advanced->TLS Authentication and set the
  Key Direction to 1.

  For example, my .ovpn file ends with the line:

  key-direction 1

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager-openvpn 1.1.93-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov 20 09:06:20 2016
  InstallationDate: Installed on 2016-06-30 (143 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1766495] Re: "your libfreerdp does not support h264"

2018-04-29 Thread Kevin

Not sure how Ian was able to work around this. On a fresh install of
Kubuntu 18.04 and a fresh install of Remmina, the only option available
is Quick Connect. I suspect I'd have more options /once I was able to
connect/, such as remembering the connection, but it won't let you do
that when it's failing out with this error about libfreerdp. And the
main settings in Remmina don't have any H264 settings.

Basically, for a fresh install, all signs point to being hooped.

I can't fall back on KRDC because, while it works (and connects), its
keyboard capture doesn't work and it has no scaling options, and even
when you specify them as additional parameters, they don't work. So I
need Remmina to work :(

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

Title:
  "your libfreerdp does not support h264"

Status in remmina package in Ubuntu:
  New

Bug description:
  When I try to connect via RDP, Remmina gives this error:

  "You requested an h264 GFX mode for server , but your
  libfreerdp does not support h264. Please check color depth settings."

  However, (1) I don't see any color depth settings in Remmina GUI, and
  (2) ubuntu-restricted-extras is installed. I have libx264-152 version
  2:0.152.2854+gite9a5903-2.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: remmina 1.2.0-rcgit.29+dfsg-1ubuntu1
  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: KDE
  Date: Tue Apr 24 09:29:44 2018
  InstallationDate: Installed on 2018-03-23 (31 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  SourcePackage: remmina
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767454] Re: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04

https://bugzilla.gnome.org/show_bug.cgi?id=780958 looks like the same
issue

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

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

** Bug watch added: Samba Bugzilla #12876
   https://bugzilla.samba.org/show_bug.cgi?id=12876

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

Title:
  "Other Locations" does not automatically find Samba servers in Ubuntu
  18.04

Status in gvfs:
  Unknown
Status in samba:
  Unknown
Status in nautilus package in Ubuntu:
  New
Status in samba package in Ubuntu:
  New

Bug description:
  Ubuntu: 18.04 clean install
  Nautilus: 1:3.26.3-0ubuntu4

  The actions taken to produce the problem:
  Click on “Other Locations” in Nautilus.

  The expected result of these actions:
  Samba servers to automatically show up under “Networks”. This is the behavior 
in Ubuntu 17.10 using Nautilus 1:3.26.0-0ub. Also, clicking on “”Windows 
Network” immediately shows "Folder is Empty".

  The actual result of these actions:
  The Samba servers never show up under “Networks” and clicking on "Windows 
Network" always immediately comes up with "Folder is Empty".

  Further information:
  This happens on both machines with a clean Ubuntu 18.04 install. My Ubuntu 
17.10 machines still work like expected.

  I can still manually type in the Samba information in "Connect to
  Server" and the 18.04 machines connect just fine.

  
  From syslog:
  Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 
pid=1333] Activating service name='org.gnome.Nautilus' requested by ':1.13' 
(uid=1000 pid=1468 comm="/usr/bin/gnome-shell " label="unconfined")
  Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 
pid=1333] Successfully activated service 'org.gnome.Nautilus'
  Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Activating 
via systemd: service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.131' (uid=1000 
pid=4857 comm="/usr/bin/nautilus --gapplication-service " label="unconfined")
  Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Starting Hostname 
Service...
  Apr 27 13:49:35 david-HP-ProBook-440-G2 nautilus[4857]: Called "net usershare 
info" but it failed: Failed to execute child process “net” (No such file or 
directory)
  Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] 
Successfully activated service 'org.freedesktop.hostname1'
  Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Started Hostname Service.
  Apr 27 13:49:40 david-HP-ProBook-440-G2 gvfsd[1432]: mkdir failed on 
directory /var/cache/samba: Permission denied

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

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

[Desktop-packages] [Bug 1767454] Re: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04

The upstream report claims it has been fixed in samba 4.8, we might have to 
look for a change to backport there
Another reference, https://bugzilla.samba.org/show_bug.cgi?id=12876

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

** Also affects: samba via
   https://bugzilla.samba.org/show_bug.cgi?id=12876
   Importance: Unknown
   Status: Unknown

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

Title:
  "Other Locations" does not automatically find Samba servers in Ubuntu
  18.04

Status in gvfs:
  Unknown
Status in samba:
  Unknown
Status in nautilus package in Ubuntu:
  New
Status in samba package in Ubuntu:
  New

Bug description:
  Ubuntu: 18.04 clean install
  Nautilus: 1:3.26.3-0ubuntu4

  The actions taken to produce the problem:
  Click on “Other Locations” in Nautilus.

  The expected result of these actions:
  Samba servers to automatically show up under “Networks”. This is the behavior 
in Ubuntu 17.10 using Nautilus 1:3.26.0-0ub. Also, clicking on “”Windows 
Network” immediately shows "Folder is Empty".

  The actual result of these actions:
  The Samba servers never show up under “Networks” and clicking on "Windows 
Network" always immediately comes up with "Folder is Empty".

  Further information:
  This happens on both machines with a clean Ubuntu 18.04 install. My Ubuntu 
17.10 machines still work like expected.

  I can still manually type in the Samba information in "Connect to
  Server" and the 18.04 machines connect just fine.

  
  From syslog:
  Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 
pid=1333] Activating service name='org.gnome.Nautilus' requested by ':1.13' 
(uid=1000 pid=1468 comm="/usr/bin/gnome-shell " label="unconfined")
  Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 
pid=1333] Successfully activated service 'org.gnome.Nautilus'
  Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Activating 
via systemd: service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.131' (uid=1000 
pid=4857 comm="/usr/bin/nautilus --gapplication-service " label="unconfined")
  Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Starting Hostname 
Service...
  Apr 27 13:49:35 david-HP-ProBook-440-G2 nautilus[4857]: Called "net usershare 
info" but it failed: Failed to execute child process “net” (No such file or 
directory)
  Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] 
Successfully activated service 'org.freedesktop.hostname1'
  Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Started Hostname Service.
  Apr 27 13:49:40 david-HP-ProBook-440-G2 gvfsd[1432]: mkdir failed on 
directory /var/cache/samba: Permission denied

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

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

[Desktop-packages] [Bug 1767454] Re: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04

@tony, could you give some details about that SMB3_11 setting? Is that a
known upstream issue/documented somewhere?

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

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

Title:
  "Other Locations" does not automatically find Samba servers in Ubuntu
  18.04

Status in gvfs:
  Unknown
Status in samba:
  Unknown
Status in nautilus package in Ubuntu:
  New
Status in samba package in Ubuntu:
  New

Bug description:
  Ubuntu: 18.04 clean install
  Nautilus: 1:3.26.3-0ubuntu4

  The actions taken to produce the problem:
  Click on “Other Locations” in Nautilus.

  The expected result of these actions:
  Samba servers to automatically show up under “Networks”. This is the behavior 
in Ubuntu 17.10 using Nautilus 1:3.26.0-0ub. Also, clicking on “”Windows 
Network” immediately shows "Folder is Empty".

  The actual result of these actions:
  The Samba servers never show up under “Networks” and clicking on "Windows 
Network" always immediately comes up with "Folder is Empty".

  Further information:
  This happens on both machines with a clean Ubuntu 18.04 install. My Ubuntu 
17.10 machines still work like expected.

  I can still manually type in the Samba information in "Connect to
  Server" and the 18.04 machines connect just fine.

  
  From syslog:
  Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 
pid=1333] Activating service name='org.gnome.Nautilus' requested by ':1.13' 
(uid=1000 pid=1468 comm="/usr/bin/gnome-shell " label="unconfined")
  Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 
pid=1333] Successfully activated service 'org.gnome.Nautilus'
  Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Activating 
via systemd: service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.131' (uid=1000 
pid=4857 comm="/usr/bin/nautilus --gapplication-service " label="unconfined")
  Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Starting Hostname 
Service...
  Apr 27 13:49:35 david-HP-ProBook-440-G2 nautilus[4857]: Called "net usershare 
info" but it failed: Failed to execute child process “net” (No such file or 
directory)
  Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] 
Successfully activated service 'org.freedesktop.hostname1'
  Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Started Hostname Service.
  Apr 27 13:49:40 david-HP-ProBook-440-G2 gvfsd[1432]: mkdir failed on 
directory /var/cache/samba: Permission denied

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

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

[Desktop-packages] [Bug 1767096] Re: Random Xorg crashes

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

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

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

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

Title:
  Random Xorg crashes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Xorg crashes randomly: environment just freezes for a second and I'm
  getting login screen.

  ProblemType: Bug
  DistroRelease: elementary 0.4.1
  Package: xorg 1:7.7+13ubuntu3 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: Pantheon
  Date: Thu Apr 26 12:57:22 2018
  InstallationDate: Installed on 2018-03-01 (55 days ago)
  InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20180214)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1762921] Re: xorg

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

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

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

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

Title:
  xorg

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  xorg failure at start up and crashes at times

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-35.39~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-35-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Wed Apr 11 02:13:59 2018
  SourcePackage: xorg
  UpgradeStatus: Upgraded to artful on 2018-02-17 (52 days ago)

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

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

[Desktop-packages] [Bug 1767321] Re: Xorg freeze

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

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

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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu 18.04, display freezes for ~1-5 seconds at seemingly random
  intervals. When it resumes, gnome shell's dock flickers as if the
  problem was caused by it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 20:02:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:8079]
   Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] [1002:6604] 
(rev 81) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Opal XT [Radeon R7 M265] [103c:814f]
  InstallationDate: Installed on 2018-04-03 (24 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  MachineType: HP HP EliteBook 850 G3
  ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-20-lowlatency 
root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro 
rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash 
module.sig_enforce=1 intel_pstate=skylake_hwp radeon.si_support=0 
radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.10
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.6F
  dmi.chassis.asset.tag: 5CG6351LQL
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.10:bd07/31/2016:svnHP:pnHPEliteBook850G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6F:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 850 G3
  dmi.sys.vendor: HP
  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/1767321/+subscriptions

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

[Desktop-packages] [Bug 1767817] Re: Full text search does not work

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

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

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

Title:
  Full text search does not work

Status in nautilus package in Ubuntu:
  New

Bug description:
  Background: I have installed Tracker. It has finished indexing. I can
  also use Tracker's command line interface to search by content.

  1.

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  2.

  nautilus:
Installed: 1:3.26.3-0ubuntu4
Candidate: 1:3.26.3-0ubuntu4
Version table:
   *** 1:3.26.3-0ubuntu4 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3. I expect to be able to search files by content from Nautilus,
  because this feature worked in 17.10.

  4. I get no results from full text search unless the search matches
  file names.

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

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

[Desktop-packages] [Bug 1323683] Re: Gnome-screenshot should ask if another screenshot should be taken

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

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

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

Title:
  Gnome-screenshot should ask if another screenshot should be taken

Status in gnome-screenshot package in Ubuntu:
  Confirmed

Bug description:
  This is really a suggestion for usability improvement, not a bug.
  When the user wants to take many screenshots with the Gnome-screenshot tool 
it's very tiresome because after each picture taken the screenshot tool closes 
and has to be found in the dash and started again. The Snipping Tool in Windows 
7 is always offering to take another shot  after taking one.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-screenshot 3.10.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 27 16:31:07 2014
  InstallationDate: Installed on 2013-07-22 (308 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: gnome-screenshot
  UpgradeStatus: Upgraded to trusty on 2014-05-07 (19 days ago)

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

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

[Desktop-packages] [Bug 1323683] Re: Gnome-screenshot should ask if another screenshot should be taken

** Changed in: gnome-screenshot (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Gnome-screenshot should ask if another screenshot should be taken

Status in gnome-screenshot package in Ubuntu:
  Confirmed

Bug description:
  This is really a suggestion for usability improvement, not a bug.
  When the user wants to take many screenshots with the Gnome-screenshot tool 
it's very tiresome because after each picture taken the screenshot tool closes 
and has to be found in the dash and started again. The Snipping Tool in Windows 
7 is always offering to take another shot  after taking one.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-screenshot 3.10.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 27 16:31:07 2014
  InstallationDate: Installed on 2013-07-22 (308 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: gnome-screenshot
  UpgradeStatus: Upgraded to trusty on 2014-05-07 (19 days ago)

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

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

[Desktop-packages] [Bug 1767818] Re: gnome-screenshot: missing "take another screenshot" option

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

** Changed in: gnome-screenshot (Ubuntu)
   Importance: Undecided => Wishlist

** This bug has been marked a duplicate of bug 1323683
   Gnome-screenshot should ask if another screenshot should be taken

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

Title:
  gnome-screenshot: missing "take another screenshot" option

Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  Gnome-screenshot utility does not offer the option to take another
  screenshot once one has been taken. We are obliged to close the
  application and open it again.

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

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

[Desktop-packages] [Bug 1715365] Re: gnome-session-check-accelerated crashed with SIGSEGV

2018-04-29 Thread psychok7

Just ran into this nasty bug in Ubuntu 18.04. Hope it gets fixed soon
because i have some users that are non technical people and telling them
to CTRL + DEL + F1 is not a great way

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

Title:
  gnome-session-check-accelerated crashed with SIGSEGV

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  bug at login

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-session-bin 3.25.90-0ubuntu2
  Uname: Linux 4.12.0-041200-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Sep  3 09:34:09 2017
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/lib/gnome-session/gnome-session-check-accelerated
  InstallationDate: Installed on 2015-04-16 (874 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: /usr/lib/gnome-session/gnome-session-check-accelerated
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: gnome-session
  StacktraceTop:
   ()
   g_hash_table_lookup () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gdk_x11_atom_to_xatom_for_display () at 
/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ()
   __libc_start_main (main=0x55f3e2ce4200, argc=1, argv=0x7ffcebd38af8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffcebd38ae8) at ../csu/libc-start.c:291
  Title: gnome-session-check-accelerated crashed with SIGSEGV
  UpgradeStatus: Upgraded to artful on 2017-08-25 (11 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1761606] Re: Two Wi-Fi network applets appear after logging back into live-usb Lubuntu 18.04 session.

2018-04-29 Thread fabritrento

the same problem is present in xubuntu 18.04LTS, two wifi icons is
displayed in the panel

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

Title:
  Two Wi-Fi network applets appear after logging back into live-usb
  Lubuntu 18.04 session.

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

Bug description:
  Lubuntu 18.04 ISO version: 20180404
  network-manager-applet version: 1.8.10-2ubuntu1
  After logging into my Wi-Fi network then logging out then logging back into 
the Live-USB session Two Wi-Fi network applets appeared where One would be the 
expected outcome.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager-gnome 1.8.10-2ubuntu1
  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
  CasperVersion: 1.392
  CurrentDesktop: LXDE
  Date: Thu Apr  5 21:06:24 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.166 metric 
600
  LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Zero-Daya2f10fa9-551c-4a4f-93ba-5fe6c22c4134  wifi  
1522962221  Thu Apr  5 21:03:41 2018  yes  0 no 
   /org/freedesktop/NetworkManager/Settings/2  yes wlp3s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/2  --
   Wired connection 1  472b45a7-c95b-3638-b452-3f6720688df8  ethernet  
1522961321  Thu Apr  5 20:48:41 2018  yes  4294966297no 
   /org/freedesktop/NetworkManager/Settings/1  no  --  -- --
  --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Zero-Daya2f10fa9-551c-4a4f-93ba-5fe6c22c4134  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1589215] Re: 'Unknown Application Name' menu item in Indicator Applet Appmenu when LibreOffice is running

2018-04-29 Thread cigtoxdoc

Can confirm on 18.04 LTS when using Unity Desktop.  Is there any work
around?

John

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

Title:
  'Unknown Application Name' menu item in Indicator Applet Appmenu when
  LibreOffice is running

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Sometimes I get the issue of a menu having the name of a different
  application and being unusable, or being an application menu for the
  focused window but being titled 'Unknown Application Name', with
  LibreOffice. I also get this with GNOME apps but was told that this is
  a separate issue to the one I reported here:
  https://bugs.launchpad.net/ubuntu/+source/gnome-
  calculator/+bug/1584720 (see comment #5).

  The issue is with using Indicator Applet Appmenu in the panel on
  gnome-flashback installed on standard Ubuntu (which I call Ubuntu
  (GNOME) Flashback).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libreoffice-writer 1:5.1.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jun  5 10:32:35 2016
  InstallationDate: Installed on 2016-04-26 (39 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1759621] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()

2018-04-29 Thread Michaël Lambé

Here is the log from `journalctl /usr/bin/gnome-shell`


** Attachment added: "journalctl /usr/bin/gnome-shell > log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1759621/+attachment/5130266/+files/log.tar.gz

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text() from ffi_call_unix64()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/811164cadd3e9e891f9e2d439bda59925f91a62c

  ---

  trying to get vpn up and running

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 28 18:00:19 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['vpn-indica...@howdoicomputer.fastmail.com']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'org.gnome.Terminal.desktop', 
'cisco-anyconnect.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-03-23 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fd17cf23d3d :
movzbl 0x16(%rax),%edx
   PC (0x7fd17cf23d3d) ok
   source "0x16(%rax)" (0x00024562) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_label_set_text () at /usr/lib/gnome-shell/libst-1.0.so
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (4 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

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

2018-04-29 Thread kutuzof

@ew0 I setup the usbquirks.conf the way you recommended. I also
confirmed that the address is right with lsusb. However it doesn't seem
to have had any effect. How can I confirm that it's being loaded?

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

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

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Hi

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

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

  Description:  Ubuntu 13.04
  Release:  13.04

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

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


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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1762827
   package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: 
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different 
from other instances of package libsane1:i386

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

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

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Seemed to occur during installation of wine

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Fri Apr 27 16:31:43 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-yNYew1/135-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-04-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767351] Re: package libsane1 1.0.27-1~experimental3ubuntu2 [modified: lib/udev/rules.d/60-libsane1.rules] failed to install/upgrade: trying to overwrite shared '/lib/udev/rule

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

** This bug has been marked a duplicate of bug 1762827
   package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: 
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different 
from other instances of package libsane1:i386

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

Title:
  package libsane1 1.0.27-1~experimental3ubuntu2 [modified:
  lib/udev/rules.d/60-libsane1.rules] failed to install/upgrade: trying
  to overwrite shared '/lib/udev/rules.d/60-libsane1.rules', which is
  different from other instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  installing wine-stable

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental3ubuntu2 [modified: 
lib/udev/rules.d/60-libsane1.rules]
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 14:18:31 2018
  ErrorMessage: trying to overwrite shared 
'/lib/udev/rules.d/60-libsane1.rules', which is different from other instances 
of package libsane1:i386
  InstallationDate: Installed on 2018-03-11 (46 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311)
  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: sane-backends
  Title: package libsane1 1.0.27-1~experimental3ubuntu2 [modified: 
lib/udev/rules.d/60-libsane1.rules] failed to install/upgrade: trying to 
overwrite shared '/lib/udev/rules.d/60-libsane1.rules', which is different from 
other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

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

** This bug has been marked a duplicate of bug 1762827
   package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: 
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different 
from other instances of package libsane1:i386

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

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

Status in sane-backends package in Ubuntu:
  New

Bug description:
  sorry i dont know much about it. a window opened after clicking on
  report button and i am here.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Sun Apr 29 20:01:47 2018
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-04-19 (9 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

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

** This bug has been marked a duplicate of bug 1762827
   package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: 
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different 
from other instances of package libsane1:i386

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

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

Status in sane-backends package in Ubuntu:
  New

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

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Sat Apr 21 16:13:38 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-gbFGck/08-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-04-11 (16 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1237370] Re: Xorg crashed with SIGABRT in OsAbort()

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

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

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

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

Bug description:
  crashed after booting

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-core 2:1.14.2.901-2ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.336ubuntu1
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CrashCounter: 1
  Date: Mon Sep 30 11:36:07 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  GraphicsCard:
   NVIDIA Corporation C79 [GeForce 9300 / nForce 730i] [10de:086c] (rev b1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8356]
  LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcCmdline: /usr/bin/X -core :2 -auth /var/run/lightdm/root/:2 -nolisten tcp 
vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed 
boot=casper  quiet splash -- persistent BOOT_IMAGE=/casper/vmlinuz.efi
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   __libc_start_main (main=0x7fc0100951a0, argc=9, ubp_av=0x7fff6ecb3898, 
init=, fini=, rtld_fini=, 
stack_end=0x7fff6ecb3888) at libc-start.c:260
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/14/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0404
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5N7A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0404:bd10/14/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N7A-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.10+13.10.20130927.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu9
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Wed Oct  9 15:46:13 2013
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button KEYBOARD, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputMicrosoft Mouse  MOUSE, id 10
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: OutputDP-0   
VGA-0
  xserver.version: 2:1.14.2.901-2ubuntu6
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1237370] Re: Xorg crashed with SIGABRT in OsAbort()

2018-04-29 Thread zixuan wang

I'am having the same issue with Ubuntu 16.04.

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

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

Bug description:
  crashed after booting

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-core 2:1.14.2.901-2ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.336ubuntu1
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CrashCounter: 1
  Date: Mon Sep 30 11:36:07 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  GraphicsCard:
   NVIDIA Corporation C79 [GeForce 9300 / nForce 730i] [10de:086c] (rev b1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8356]
  LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcCmdline: /usr/bin/X -core :2 -auth /var/run/lightdm/root/:2 -nolisten tcp 
vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed 
boot=casper  quiet splash -- persistent BOOT_IMAGE=/casper/vmlinuz.efi
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   __libc_start_main (main=0x7fc0100951a0, argc=9, ubp_av=0x7fff6ecb3898, 
init=, fini=, rtld_fini=, 
stack_end=0x7fff6ecb3888) at libc-start.c:260
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/14/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0404
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5N7A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0404:bd10/14/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N7A-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.10+13.10.20130927.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu9
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Wed Oct  9 15:46:13 2013
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button KEYBOARD, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputMicrosoft Mouse  MOUSE, id 10
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: OutputDP-0   
VGA-0
  xserver.version: 2:1.14.2.901-2ubuntu6
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-04-29 Thread claudio@ubuntu

To me it looks that there is something broken wider than what most comments 
touch.
On my laptop with a NVIDIA Corporation GK107M [GeForce GT 750M] (prime) card, 
since 17.10 (including 18.04):
- nouveau drivers work very poorly with Xorg: too slow to play video (tearing, 
drop frames, etc).
- nouveau drivers work very poorly with Xorg: too slow to play video (tearing, 
drop frames, etc).
- nvidia-340 drivers with prime selection of both nvidia and intel: No Xorg, no 
Wayland.
- nvidia-390 drivers with prime selection of nvidia: No Xorg, Waylang stuck in 
login loop.
- nvidia-390 drivers with prime selection of intel on Xorg: too slow to play 
video (tearing, drop frames, etc).
- nvidia-390 drivers with prime selection of intel on Wayland: everything seems 
to work.

I would prefer to run Xorg on 18.04 because Wayland on 17.10 crashed one
in a while probably due to extensions.

Ping if more info is needed (logs, tests) or it this should be moved to
its own ticket.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-04-29 Thread claudio@ubuntu

** Also affects: xserver-xorg-video-nouveau (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Desktop-packages] [Bug 1704781] Re: With gdm3 a restart is needed when switching prime profiles

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

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

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

Title:
  With gdm3 a restart is needed when switching prime profiles

Status in gdm3 package in Ubuntu:
  Confirmed
Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  Test case:
  Install nvidia drivers ,restart.
  Open nvidia-settings, switch prime profile.
  Will be prompted to log out/in, do so

  What happens: user goes into a log in loop
  To actually get back to the ubuntu-session one must restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nvidia-prime 0.8.4
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jul 17 07:57:24 2017
  InstallationDate: Installed on 2017-07-15 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170708)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1759462] Re: Keyboard shortcuts not operational on 18.04

2018-04-29 Thread WinEunuchs2Unix

Reply to #8, problem seems to have gone away on it's own today. Had
tried multiple DE's that didn't work and went into Unity. A message that
"Updates are available" appeared. Clicking on it installed nothing but
probably ran `sudo apt update`, `sudo apt upgrade` in the background.
Rebooted into 16.04. Later rebooted into 18.04 test environment and
`Ctrl`+`Alt`+`T` and media keys are working.

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

Title:
  Keyboard shortcuts not operational on 18.04

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

Bug description:
  After installing 18.04, I noticed that certain keyboard shortcuts no
  longer function.

  It appears to be related to the shortcuts that gnome-settings-daemon
  control as my shortcuts that are provided by my desktop (Budgie) still
  function.

  Some examples are:

  * Media keys for volume up/down/mute
  * ctrl-alt-t for the terminal. I tried changing the shortcut to test. Same 
behaviour.

  I double checked, and it looks like the needed daemon is still
  running,

  ```
  dustin3337  0.0  0.2 500736 22216 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-keyboard
  dustin3338  0.0  0.3 943372 25732 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-media-keys
  dustin3343  0.0  0.0 274908  5844 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-mouse
  dustin3345  0.0  0.3 519896 25144 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-power
  dustin3348  0.0  0.1 346004 10212 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-print-notifications
  dustin3351  0.0  0.0 374684  7952 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-smartcard
  dustin3355  0.0  0.1 329584  8064 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-sound
  dustin3361  0.0  0.1 449708  9856 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-sharing
  dustin3367  0.0  0.0 272416  4772 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
  dustin3375  0.0  0.0 420028  5804 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-rfkill
  dustin3383  0.0  0.2 507120 23244 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-wacom
  dustin3385  0.0  0.3 498040 25040 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-xsettings
  dustin3387  0.0  0.0 274900  5936 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-a11y-settings
  dustin3392  0.0  0.2 496016 22044 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-clipboard
  dustin3395  0.0  0.3 810156 25976 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-color
  dustin3396  0.0  0.2 471656 21080 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-datetime
  dustin3400  0.0  0.0 361196  7116 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-housekeeping
  dustin3433  0.0  0.1 505404 12576 ?Sl   21:03   0:00 
/usr/lib/gnome-settings-daemon/gsd-printer
  dustin9776  0.0  0.0  18188  1032 pts/1S+   21:19   0:00 grep 
--color=auto gnome-settings-daemon
  ```

  Reboot does not seem to help. However, occasionally the shortcuts do
  seem to work - but only very occasionally.

  Any other info needed?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 27 21:12:18 2018
  InstallationDate: Installed on 2018-03-05 (22 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180304)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767818] [NEW] gnome-screenshot: missing "take another screenshot" option

2018-04-29 Thread Pierre van Male

Public bug reported:

Gnome-screenshot utility does not offer the option to take another
screenshot once one has been taken. We are obliged to close the
application and open it again.

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

** Attachment added: "screenshot illustration"
   
https://bugs.launchpad.net/bugs/1767818/+attachment/5130181/+files/Screenshot%20from%202018-04-29%2010-27-47.png

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

Title:
  gnome-screenshot: missing "take another screenshot" option

Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  Gnome-screenshot utility does not offer the option to take another
  screenshot once one has been taken. We are obliged to close the
  application and open it again.

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

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

[Desktop-packages] [Bug 1767817] [NEW] Full text search does not work

2018-04-29 Thread Mordi

Public bug reported:

Background: I have installed Tracker. It has finished indexing. I can
also use Tracker's command line interface to search by content.

1.

Description:Ubuntu 18.04 LTS
Release:18.04

2.

nautilus:
  Installed: 1:3.26.3-0ubuntu4
  Candidate: 1:3.26.3-0ubuntu4
  Version table:
 *** 1:3.26.3-0ubuntu4 500
500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

3. I expect to be able to search files by content from Nautilus, because
this feature worked in 17.10.

4. I get no results from full text search unless the search matches file
names.

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


** Tags: bionic nautilus tracker

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

Title:
  Full text search does not work

Status in nautilus package in Ubuntu:
  New

Bug description:
  Background: I have installed Tracker. It has finished indexing. I can
  also use Tracker's command line interface to search by content.

  1.

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  2.

  nautilus:
Installed: 1:3.26.3-0ubuntu4
Candidate: 1:3.26.3-0ubuntu4
Version table:
   *** 1:3.26.3-0ubuntu4 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3. I expect to be able to search files by content from Nautilus,
  because this feature worked in 17.10.

  4. I get no results from full text search unless the search matches
  file names.

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

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

[Desktop-packages] [Bug 1767757] Re: On Screen board is not poping out for firefox

2018-04-29 Thread Paul White

** Package changed: ubuntu => onboard (Ubuntu)

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

Title:
  On Screen board is not poping out for firefox

Status in onboard package in Ubuntu:
  New

Bug description:
  I just upgraded to Ubuntu 18.04. I found that the on-screen keyboard
  which is available in Universal Access is not popping out when I use
  the Mozilla Firefox to search or type something.

  Can any One answer me what to do?

  I have tried caribou too... But no change in problem

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

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

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

2018-04-29 Thread Aj Kothari

Public bug reported:

sorry i dont know much about it. a window opened after clicking on
report button and i am here.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
Date: Sun Apr 29 20:01:47 2018
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
InstallationDate: Installed on 2018-04-19 (9 days ago)
InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package artful

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

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

Status in sane-backends package in Ubuntu:
  New

Bug description:
  sorry i dont know much about it. a window opened after clicking on
  report button and i am here.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Sun Apr 29 20:01:47 2018
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-04-19 (9 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1767757] [NEW] On Screen board is not poping out for firefox