[Desktop-packages] [Bug 1979175] Re: Gnome screensaver always overrides xscreensaver in xdg-screensaver

[Stuart Langridge]

Agreed that this is about the built-in screensaver, but I don't really
know what the best vocabulary is here; feel free to edit the bug title
if it's clearer.

As far as I can tell, there is no way to tell Gnome to stop owning the
d-bus screensaver names. (The answer is not to make everyone who needs
to inhibit the screensaver change yet again to do things another way, of
course.)

I use xscreensaver because it's cool; I would like the fun screensavers,
not just blankness, and I'd like the most up-to-date ones because there
are new ones.

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

Title:
  Gnome screensaver always overrides xscreensaver in xdg-screensaver

Status in xdg-utils package in Ubuntu:
  New

Bug description:
  /usr/bin/xdg-screensaver checks for various different screensavers
  with lines like this:

  # Consider "xscreensaver" a separate DE
  xscreensaver-command -version 2> /dev/null | grep XScreenSaver > /dev/null && 
DE="xscreensaver"
  # Consider "gnome-screensaver" a separate DE
  dbus-send --print-reply --dest=org.freedesktop.DBus /org/freedesktop/DBus 
org.freedesktop.DBus.GetNameOwner string:org.gnome.ScreenSaver > /dev/null 2>&1 
&& DE="gnome_screensaver"

  However, gnome-shell always owns that org.gnome.ScreenSaver name on
  the bus and that cannot be prevented, even if gnome-screensaver is
  disabled. What this means is that if you install xscreensaver on a
  default Ubuntu installation and then disable gnome-screensaver, xdg-
  screensaver will still treat the running screensaver as being gnome-
  screensaver.

  When Firefox plays videos, it regularly calls "xdg-screensaver reset"
  to inhibit the screensaver, which is correct behaviour. However,
  because of the above bug, this call doesn't actually work because
  gnome-screensaver can't be told to stop owning its name on the bus. So
  what this means in practice is that on Ubuntu, if you install
  xscreensaver, then the screensaver will come on even while videos are
  playing in Firefox, and that's not supposed to happen.

  Proposed fix: move the xscreensaver check in xdg-screensaver to
  *after* the check for gnome-screensaver, so that if xscreensaver is
  present then it takes priority. This is likely to be correct because
  xscreensaver isn't present by default, so it being installed at all
  indicates some desire on the user's part to have it running.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xdg-utils 1.1.3-2ubuntu1.20.04.2 [modified: usr/bin/xdg-screensaver]
  ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-48-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 20 07:20:51 2022
  InstallationDate: Installed on 2020-06-20 (729 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: xdg-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1979175] [NEW] Gnome screensaver always overrides xscreensaver in xdg-screensaver

[Stuart Langridge]

Public bug reported:

/usr/bin/xdg-screensaver checks for various different screensavers with
lines like this:

# Consider "xscreensaver" a separate DE
xscreensaver-command -version 2> /dev/null | grep XScreenSaver > /dev/null && 
DE="xscreensaver"
# Consider "gnome-screensaver" a separate DE
dbus-send --print-reply --dest=org.freedesktop.DBus /org/freedesktop/DBus 
org.freedesktop.DBus.GetNameOwner string:org.gnome.ScreenSaver > /dev/null 2>&1 
&& DE="gnome_screensaver"

However, gnome-shell always owns that org.gnome.ScreenSaver name on the
bus and that cannot be prevented, even if gnome-screensaver is disabled.
What this means is that if you install xscreensaver on a default Ubuntu
installation and then disable gnome-screensaver, xdg-screensaver will
still treat the running screensaver as being gnome-screensaver.

When Firefox plays videos, it regularly calls "xdg-screensaver reset" to
inhibit the screensaver, which is correct behaviour. However, because of
the above bug, this call doesn't actually work because gnome-screensaver
can't be told to stop owning its name on the bus. So what this means in
practice is that on Ubuntu, if you install xscreensaver, then the
screensaver will come on even while videos are playing in Firefox, and
that's not supposed to happen.

Proposed fix: move the xscreensaver check in xdg-screensaver to *after*
the check for gnome-screensaver, so that if xscreensaver is present then
it takes priority. This is likely to be correct because xscreensaver
isn't present by default, so it being installed at all indicates some
desire on the user's part to have it running.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xdg-utils 1.1.3-2ubuntu1.20.04.2 [modified: usr/bin/xdg-screensaver]
ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-48-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 20 07:20:51 2022
InstallationDate: Installed on 2020-06-20 (729 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: xdg-utils
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Gnome screensaver always overrides xscreensaver in xdg-screensaver

Status in xdg-utils package in Ubuntu:
  New

Bug description:
  /usr/bin/xdg-screensaver checks for various different screensavers
  with lines like this:

  # Consider "xscreensaver" a separate DE
  xscreensaver-command -version 2> /dev/null | grep XScreenSaver > /dev/null && 
DE="xscreensaver"
  # Consider "gnome-screensaver" a separate DE
  dbus-send --print-reply --dest=org.freedesktop.DBus /org/freedesktop/DBus 
org.freedesktop.DBus.GetNameOwner string:org.gnome.ScreenSaver > /dev/null 2>&1 
&& DE="gnome_screensaver"

  However, gnome-shell always owns that org.gnome.ScreenSaver name on
  the bus and that cannot be prevented, even if gnome-screensaver is
  disabled. What this means is that if you install xscreensaver on a
  default Ubuntu installation and then disable gnome-screensaver, xdg-
  screensaver will still treat the running screensaver as being gnome-
  screensaver.

  When Firefox plays videos, it regularly calls "xdg-screensaver reset"
  to inhibit the screensaver, which is correct behaviour. However,
  because of the above bug, this call doesn't actually work because
  gnome-screensaver can't be told to stop owning its name on the bus. So
  what this means in practice is that on Ubuntu, if you install
  xscreensaver, then the screensaver will come on even while videos are
  playing in Firefox, and that's not supposed to happen.

  Proposed fix: move the xscreensaver check in xdg-screensaver to
  *after* the check for gnome-screensaver, so that if xscreensaver is
  present then it takes priority. This is likely to be correct because
  xscreensaver isn't present by default, so it being installed at all
  indicates some desire on the user's part to have it running.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xdg-utils 1.1.3-2ubuntu1.20.04.2 [modified: usr/bin/xdg-screensaver]
  ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-48-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 20 07:20:51 2022
  InstallationDate: Installed on 2020-06-20 (729 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  

[Desktop-packages] [Bug 1944081] [NEW] Package Manager indicator has incorrect, old wording and bad grammar

[Stuart Langridge]

Public bug reported:

If I create an issue with installed packages, I get a "no entry sign"
icon in my Ubuntu 20.04 top panel. (I am not sure which package creates
this indicator; please reassign if it's not software-properties.) This
indicator has a menu (screenshot attached) with text reading:

An error occurred, please run Package Manager from the right-click menu
or apt-get in a terminal to see what is wrong. The error message was: '
Error: BrokenCount > 0' This usually means that your installed packages
have unmet dependencies

This message has numerous problems.

1. There is no "right-click menu"; a left-click or a right-click on this icon 
both show the same thing
2. There is no "Package Manager" entry in the shown menu (there is the error 
message above, a separator, "Show updates", a separator, "Show notifications", 
and "Preferences")
3. It recommends running "apt-get" which should be "apt"
4. The error message has a space at the start of it
5. The error message uses straight quotes rather than typographic quotes
6. It does not end with a full stop despite being written as prose

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: software-properties-gtk 0.98.9.5
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 19 17:07:00 2021
InstallationDate: Installed on 2020-06-20 (456 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  Package Manager indicator has incorrect, old wording and bad grammar

Status in software-properties package in Ubuntu:
  New

Bug description:
  If I create an issue with installed packages, I get a "no entry sign"
  icon in my Ubuntu 20.04 top panel. (I am not sure which package
  creates this indicator; please reassign if it's not software-
  properties.) This indicator has a menu (screenshot attached) with text
  reading:

  An error occurred, please run Package Manager from the right-click
  menu or apt-get in a terminal to see what is wrong. The error message
  was: ' Error: BrokenCount > 0' This usually means that your installed
  packages have unmet dependencies

  This message has numerous problems.

  1. There is no "right-click menu"; a left-click or a right-click on this icon 
both show the same thing
  2. There is no "Package Manager" entry in the shown menu (there is the error 
message above, a separator, "Show updates", a separator, "Show notifications", 
and "Preferences")
  3. It recommends running "apt-get" which should be "apt"
  4. The error message has a space at the start of it
  5. The error message uses straight quotes rather than typographic quotes
  6. It does not end with a full stop despite being written as prose

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.9.5
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 19 17:07:00 2021
  InstallationDate: Installed on 2020-06-20 (456 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1935777] [NEW] Power Saving settings have incomprehensible meanings/labels for Wi-Fi and Bluetooth

[Stuart Langridge]

Public bug reported:

In the Power Saving section of the Power tab of the Settings app, there
are two switches, one labelled "Wi-Fi" with subheading "Wi-Fi can be
turned off to save power" and the other labelled "Bluetooth" with
subheading "Bluetooth can be turned off to save power". On my machine,
the "Wi-Fi" switch is off and the "Bluetooth" switch is on. (Screenshot
attached.)

I do not know what these switches mean, and I do not know what will
change if I change their settings.

Does this mean

* yes Ubuntu is permitted to switch off your wifi to save power but it's not 
permitted to switch off your Bluetooth, or
* it is permitted to switch off your Bluetooth but not permitted to switch off 
your wifi, or 
* your bluetooth is already switched off to save power but wifi is always on, 
or 
* wifi is already switched off to save power but bluetooth is always on, or
* something else entirely?

I am utterly confused.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.5-0ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-59-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul 11 17:49:14 2021
InstallationDate: Installed on 2020-06-20 (386 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "photo_2021-07-11_17-49-25.jpg"
   
https://bugs.launchpad.net/bugs/1935777/+attachment/5510369/+files/photo_2021-07-11_17-49-25.jpg

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

Title:
  Power Saving settings have incomprehensible meanings/labels for Wi-Fi
  and Bluetooth

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

Bug description:
  In the Power Saving section of the Power tab of the Settings app,
  there are two switches, one labelled "Wi-Fi" with subheading "Wi-Fi
  can be turned off to save power" and the other labelled "Bluetooth"
  with subheading "Bluetooth can be turned off to save power". On my
  machine, the "Wi-Fi" switch is off and the "Bluetooth" switch is on.
  (Screenshot attached.)

  I do not know what these switches mean, and I do not know what will
  change if I change their settings.

  Does this mean

  * yes Ubuntu is permitted to switch off your wifi to save power but it's not 
permitted to switch off your Bluetooth, or
  * it is permitted to switch off your Bluetooth but not permitted to switch 
off your wifi, or 
  * your bluetooth is already switched off to save power but wifi is always on, 
or 
  * wifi is already switched off to save power but bluetooth is always on, or
  * something else entirely?

  I am utterly confused.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.5-0ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-59-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 11 17:49:14 2021
  InstallationDate: Installed on 2020-06-20 (386 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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/1935777/+subscriptions

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

[Desktop-packages] [Bug 1893806] [NEW] Ubiquity icon is misleading and not very well executed

[Stuart Jaggers]

Public bug reported:

The visual metaphor for the current Ubiquity icon caused some confusion
(e.g., see https://www.omgubuntu.co.uk/2020/03/ubuntu-installer-icon-
strange).  Also, IMO, the design with lots of small particles doesn't
map well to the Yaru icon style, which requires an outline at smaller
sizes.  The upshot of this is that neither the idea nor the execution
are universally popular.

Over on the Yaru side, we've just merged a new design into Master, which
hopefully makes it clearer that the icon writes Ubuntu to hard disk:
https://github.com/ubuntu/yaru/pull/2340.

This "bug" could be fixed by backporting the new icon to Focal Fossa
before 20.04.02 - are we able to proceed?

Thank you!

EDIT:

1) Version of Ubuntu = 20.04 and 20.04.01 live disk

2) N/A

3) Expected a clear and well-executed icon for the installer when using
the live disk

4) Got the current icon which (see above) is sub-optimal.

** Affects: yaru-theme (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  The visual metaphor for the current Ubiquity icon caused some confusion
  (e.g., see https://www.omgubuntu.co.uk/2020/03/ubuntu-installer-icon-
  strange).  Also, IMO, the design with lots of small particles doesn't
  map well to the Yaru icon style, which requires an outline at smaller
  sizes.  The upshot of this is that neither the idea nor the execution
  are universally popular.
  
  Over on the Yaru side, we've just merged a new design into Master, which
  hopefully makes it clearer that the icon writes Ubuntu to hard disk:
  https://github.com/ubuntu/yaru/pull/2340.
  
  This "bug" could be fixed by backporting the new icon to Focal Fossa
  before 20.04.02 - are we able to proceed?
  
  Thank you!
+ 
+ EDIT:
+ 
+ 1) Version of Ubuntu = 20.04 and 20.04.01 live disk
+ 
+ 2) N/A
+ 
+ 3) Expected a clear and well-executed icon for the installer when using
+ the live disk
+ 
+ 4) Got the current icon which (see above) is sub-optimal.

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

Title:
  Ubiquity icon is misleading and not very well executed

Status in yaru-theme package in Ubuntu:
  New

Bug description:
  The visual metaphor for the current Ubiquity icon caused some
  confusion (e.g., see https://www.omgubuntu.co.uk/2020/03/ubuntu-
  installer-icon-strange).  Also, IMO, the design with lots of small
  particles doesn't map well to the Yaru icon style, which requires an
  outline at smaller sizes.  The upshot of this is that neither the idea
  nor the execution are universally popular.

  Over on the Yaru side, we've just merged a new design into Master,
  which hopefully makes it clearer that the icon writes Ubuntu to hard
  disk: https://github.com/ubuntu/yaru/pull/2340.

  This "bug" could be fixed by backporting the new icon to Focal Fossa
  before 20.04.02 - are we able to proceed?

  Thank you!

  EDIT:

  1) Version of Ubuntu = 20.04 and 20.04.01 live disk

  2) N/A

  3) Expected a clear and well-executed icon for the installer when
  using the live disk

  4) Got the current icon which (see above) is sub-optimal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1893806/+subscriptions

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

[Desktop-packages] [Bug 1873403] Re: [nvidia] Screen turns off when trying to set some fractional scaling values

[Stuart Still]

I've tried this from pop!_os 20.04, nVidia 2060 super GTX, 4k monitor.

Starting off in 100% scaling, I select 125% scaling. Before enabling
proposed, this resulted in the screen switching off.

Since enabling proposed and installing the updated packages, this now
doesn't switch the screen off, but the behaviour is still not correct. I
believe I'm now experiencing
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1875285 and
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593 (the
latter of which is marked as fixed).

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

Title:
  [nvidia] Screen turns off when trying to set some fractional scaling
  values

Status in mutter package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed
Status in mutter source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers source package in Focal:
  Confirmed

Bug description:
  [ Impact ]

  When the nvidia driver is installed, the screen turns off when trying
  to set some fractional scaling values like 150%. And it stays off even
  after rebooting and logging in again.

  And from ssh I can see there's no current mode set anymore (just like
  in bug 1869750):

  $ xrandr
  Screen 0: minimum 8 x 8, current 960 x 600, maximum 16384 x 16384
  DVI-I-0 disconnected (normal left inverted right x axis y axis)
  DVI-I-1 disconnected (normal left inverted right x axis y axis)
  DP-0 disconnected (normal left inverted right x axis y axis)
  DP-1 connected primary (normal left inverted right x axis y axis)
     1920x1200 59.95 +  59.88

  [ Test case ]

  In a Nvidia system:
  - From g-c-c enable fractional scaling
  - Set all the available fractional scaling values and ensure they work
+ In any case the screen should be turned off

  [ Regression potential ]

  Wrong screen size is set and panning might be enabled.

  ---

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: mutter 3.36.1-3ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 17 15:51:15 2020
  InstallationDate: Installed on 2020-02-03 (73 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200124)SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1887420] [NEW] network-cellular-connected-symbolic isn't monochrome

[Stuart Jaggers]

Public bug reported:

[Impact]

 * The icon called network-cellular-connected-symbolic appears at the
top right of the desktop when users connect to their phones via
bluetooth to use data.  The icon includes green fill, which is
inconsistent with the monochrome icons used for (e.g.) wifi.  See GitHub
issue https://github.com/ubuntu/yaru/issues/2192.

 * Reason to backport to Focal: the inconsistency was missed because I
don't use this feature and it's an unfortunate oversight.  When the icon
appears, it does so in a prominent position and is constantly visible to
the user, giving a poor impression of Ubuntu.

[Test Case]

 * Use Bluetooth tethering so your laptop is making use of your phone's
data connection.  Notice that, unlike the rest of the icons at the top
right of the screen, the symbol for the connection isn't monochrome.

 * Build Yaru from Master and notice how all icons are now monochrome.

[Regression Potential]

 * No regression potential.

 * Tested by building Yaru from source.

[Other Info]

 * Link to the GitHub PR: https://github.com/ubuntu/yaru/pull/2252.

** Affects: yaru-theme (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  network-cellular-connected-symbolic isn't monochrome

Status in yaru-theme package in Ubuntu:
  New

Bug description:
  [Impact]

   * The icon called network-cellular-connected-symbolic appears at the
  top right of the desktop when users connect to their phones via
  bluetooth to use data.  The icon includes green fill, which is
  inconsistent with the monochrome icons used for (e.g.) wifi.  See
  GitHub issue https://github.com/ubuntu/yaru/issues/2192.

   * Reason to backport to Focal: the inconsistency was missed because I
  don't use this feature and it's an unfortunate oversight.  When the
  icon appears, it does so in a prominent position and is constantly
  visible to the user, giving a poor impression of Ubuntu.

  [Test Case]

   * Use Bluetooth tethering so your laptop is making use of your
  phone's data connection.  Notice that, unlike the rest of the icons at
  the top right of the screen, the symbol for the connection isn't
  monochrome.

   * Build Yaru from Master and notice how all icons are now monochrome.

  [Regression Potential]

   * No regression potential.

   * Tested by building Yaru from source.

  [Other Info]

   * Link to the GitHub PR: https://github.com/ubuntu/yaru/pull/2252.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1887420/+subscriptions

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

[Desktop-packages] [Bug 1887419] [NEW] Lollypop music player mixes Yaru and Adwaita symbols

[Stuart Jaggers]

Public bug reported:

[Impact]

 * The Yaru theme has some of the icons used by Lollypop but not all of
them.  This results in the Lollypop sidebar having a mix of Adwaita
symbols (with 2px strokes) and Yaru ones (which have 1px).  See GitHub
issue https://github.com/ubuntu/yaru/issues/2208.

 * Reason to backport to Focal: displaying symbols from two different
themes gives a poor impression of Ubuntu to users who want to use a
popular native music player.

[Test Case]

 * Install Lollypop and look at the sidebar. Some of the symbols are
heavy and some are light.  (Alternatively, the GitHub issue linked above
has a screenshot.)

 * Build Yaru from Master and notice how the Lollypop sidebar is now
consistent with itself and the rest of the Yaru theme.

[Regression Potential]

 * No regression potential.

 * Tested by building Yaru from source.

[Other Info]

 * Links to the GitHub PRs: https://github.com/ubuntu/yaru/pull/2235 and
https://github.com/ubuntu/yaru/pull/2253.

** Affects: yaru-theme (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Lollypop music player mixes Yaru and Adwaita symbols

Status in yaru-theme package in Ubuntu:
  New

Bug description:
  [Impact]

   * The Yaru theme has some of the icons used by Lollypop but not all
  of them.  This results in the Lollypop sidebar having a mix of Adwaita
  symbols (with 2px strokes) and Yaru ones (which have 1px).  See GitHub
  issue https://github.com/ubuntu/yaru/issues/2208.

   * Reason to backport to Focal: displaying symbols from two different
  themes gives a poor impression of Ubuntu to users who want to use a
  popular native music player.

  [Test Case]

   * Install Lollypop and look at the sidebar. Some of the symbols are
  heavy and some are light.  (Alternatively, the GitHub issue linked
  above has a screenshot.)

   * Build Yaru from Master and notice how the Lollypop sidebar is now
  consistent with itself and the rest of the Yaru theme.

  [Regression Potential]

   * No regression potential.

   * Tested by building Yaru from source.

  [Other Info]

   * Links to the GitHub PRs: https://github.com/ubuntu/yaru/pull/2235
  and https://github.com/ubuntu/yaru/pull/2253.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1887419/+subscriptions

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

[Desktop-packages] [Bug 1887411] [NEW] system-users-symbolic icon has unclear visual metaphor

[Stuart Jaggers]

Public bug reported:

[Impact]

 * The system-users-symbolic icon doesn't represent users in the plural.
It shows a single generic figure (head and shoulders) representing one
user.  This is a misleading visual metaphor, since a single head and
shoulders is universally recognised as the current or logged-in user.

 * Reason to backport to Focal: the corresponding Adwaita icon shows two
users.  Third party apps that use the icon will expect it to represent
more than one person.  Failing to provide a suitable icon will have
confusing results in Ubuntu.

[Test Case]

 * Install Lollypop and look at the sidebar.  "Compilations" has the
symbol of a single user, which is confusing.  Lollypop requested an icon
with multiple figures to represent multiple artists, but Ubuntu supplied
something inappropriate.  This issue may be duplicated whenever a third
party app uses this icon.

 * Build Yaru from Master and notice how the icon now has the same
visual metaphor as Adwaita (i.e., it shows two users).  The Lollypop UI
makes more sense and the theme honours the app's intentions.

[Regression Potential]

 * No regression potential.

 * Tested by building Yaru from source.

[Other Info]

 * Link to the Github PR: https://github.com/ubuntu/yaru/pull/2209

** Affects: yaru-theme (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  system-users-symbolic icon has unclear visual metaphor

Status in yaru-theme package in Ubuntu:
  New

Bug description:
  [Impact]

   * The system-users-symbolic icon doesn't represent users in the
  plural.  It shows a single generic figure (head and shoulders)
  representing one user.  This is a misleading visual metaphor, since a
  single head and shoulders is universally recognised as the current or
  logged-in user.

   * Reason to backport to Focal: the corresponding Adwaita icon shows
  two users.  Third party apps that use the icon will expect it to
  represent more than one person.  Failing to provide a suitable icon
  will have confusing results in Ubuntu.

  [Test Case]

   * Install Lollypop and look at the sidebar.  "Compilations" has the
  symbol of a single user, which is confusing.  Lollypop requested an
  icon with multiple figures to represent multiple artists, but Ubuntu
  supplied something inappropriate.  This issue may be duplicated
  whenever a third party app uses this icon.

   * Build Yaru from Master and notice how the icon now has the same
  visual metaphor as Adwaita (i.e., it shows two users).  The Lollypop
  UI makes more sense and the theme honours the app's intentions.

  [Regression Potential]

   * No regression potential.

   * Tested by building Yaru from source.

  [Other Info]

   * Link to the Github PR: https://github.com/ubuntu/yaru/pull/2209

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1887411/+subscriptions

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

[Desktop-packages] [Bug 1879318] Re: Removing gnome software snap plugin breaks gnome software storefront on Xubuntu 20.04

[Stuart]

Of course it does, that's why I removed it. All recommended applications
shown on the gnome storefront are snaps, all of them, see for yourself.
Also when you search it always shows snaps first instead of repo apps.
So the workaround is not a solution.

Screenshots:
https://imgur.com/Xk2E69a
https://imgur.com/24DjV4N

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

Title:
  Removing gnome software snap plugin breaks gnome software storefront
  on Xubuntu 20.04

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  How to reproduce:

  1) Fresh install of Xubuntu 20.04
  2) Open "Terminal"
  3) Type "sudo apt autoremove --purge snapd gnome-software-plugin-snap"
  4) Launch "Gnome Software"

  Result:
  I removed snapd & the Gnome Software snap plugin and I noticed that it broke 
the Gnome Software front page, where you can see all the featured and 
recommended applications etc. See attached screenshot. After running "sudo apt 
autoremove --purge snapd gnome-software-plugin-snap" the Gnome Software Center 
should default back to showing applications from the Ubuntu repository and not 
snap store. The same happens in Ubuntu 18.04!

  I tried clearing the app-info cache but to no avail.

  $pkill gnome-software
  $sudo rm -r /var/cache/app-info
  $sudo appstreamcli refresh --force --verbose

  Gnome-Software terminal output:
  12:06:06:0632 Gs  enabled plugins: desktop-categories, fwupd, os-release, 
packagekit, packagekit-local, packagekit-offline, packagekit-proxy, 
packagekit-refine-repos, packagekit-refresh, packagekit-upgrade, 
packagekit-url-to-app, appstream, desktop-menu-path, hardcoded-blacklist, 
modalias, odrs, packagekit-refine, rewrite-resource, packagekit-history, 
provenance, systemd-updates, generic-updates, provenance-license, icons, 
key-colors, key-colors-metadata
  12:06:06:0633 Gs  disabled plugins: dpkg, dummy, repos
  12:06:07:0935 Gs  Only 0 apps for popular list, hiding
  12:06:07:0965 Gs  hiding category audio-video featured applications: found 
only 0 to show, need at least 9
  12:06:07:0965 Gs  hiding category graphics featured applications: found only 
0 to show, need at least 9
  12:06:08:0925 Gs  Only 2 apps for recent list, hiding

  Screenshot:
  https://imgur.com/a/F4BCWQu

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.36.0-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.445
  CurrentDesktop: XFCE
  Date: Mon May 18 11:56:16 2020
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snapN/A
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.xdg.autostart.gnome-software-service.desktop: [deleted]

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

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

[Desktop-packages] [Bug 1879318] Re: Removing gnome software snap plugin breaks gnome software storefront on Xubuntu 20.04

[Stuart]

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

** Attachment removed: "Screenshot_2020-05-18_11-55-25.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1879318/+attachment/5373385/+files/Screenshot_2020-05-18_11-55-25.png

** Description changed:

  How to reproduce:
  
  1) Fresh install of Xubuntu 20.04
  2) Open "Terminal"
  3) Type "sudo apt autoremove --purge snapd gnome-software-plugin-snap"
  4) Launch "Gnome Software"
  
  Result:
  I removed snapd & the Gnome Software snap plugin and I noticed that it broke 
the Gnome Software front page, where you can see all the featured and 
recommended applications etc. See attached screenshot. After running "sudo apt 
autoremove --purge snapd gnome-software-plugin-snap" the Gnome Software Center 
should default back to showing applications from the Ubuntu repository and not 
snap store. The same happens in Ubuntu 18.04!
  
  I tried clearing the app-info cache but to no avail.
  
  $pkill gnome-software
  $sudo rm -r /var/cache/app-info
  $sudo appstreamcli refresh --force --verbose
  
  Gnome-Software terminal output:
  12:06:06:0632 Gs  enabled plugins: desktop-categories, fwupd, os-release, 
packagekit, packagekit-local, packagekit-offline, packagekit-proxy, 
packagekit-refine-repos, packagekit-refresh, packagekit-upgrade, 
packagekit-url-to-app, appstream, desktop-menu-path, hardcoded-blacklist, 
modalias, odrs, packagekit-refine, rewrite-resource, packagekit-history, 
provenance, systemd-updates, generic-updates, provenance-license, icons, 
key-colors, key-colors-metadata
  12:06:06:0633 Gs  disabled plugins: dpkg, dummy, repos
  12:06:07:0935 Gs  Only 0 apps for popular list, hiding
  12:06:07:0965 Gs  hiding category audio-video featured applications: found 
only 0 to show, need at least 9
  12:06:07:0965 Gs  hiding category graphics featured applications: found only 
0 to show, need at least 9
  12:06:08:0925 Gs  Only 2 apps for recent list, hiding
+ 
+ Screenshot:
+ https://imgur.com/a/F4BCWQu
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.36.0-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.445
  CurrentDesktop: XFCE
  Date: Mon May 18 11:56:16 2020
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snapN/A
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.xdg.autostart.gnome-software-service.desktop: [deleted]

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

Title:
  Removing gnome software snap plugin breaks gnome software storefront
  on Xubuntu 20.04

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  How to reproduce:

  1) Fresh install of Xubuntu 20.04
  2) Open "Terminal"
  3) Type "sudo apt autoremove --purge snapd gnome-software-plugin-snap"
  4) Launch "Gnome Software"

  Result:
  I removed snapd & the Gnome Software snap plugin and I noticed that it broke 
the Gnome Software front page, where you can see all the featured and 
recommended applications etc. See attached screenshot. After running "sudo apt 
autoremove --purge snapd gnome-software-plugin-snap" the Gnome Software Center 
should default back to showing applications from the Ubuntu repository and not 
snap store. The same happens in Ubuntu 18.04!

  I tried clearing the app-info cache but to no avail.

  $pkill gnome-software
  $sudo rm -r /var/cache/app-info
  $sudo appstreamcli refresh --force --verbose

  Gnome-Software terminal output:
  12:06:06:0632 Gs  enabled plugins: desktop-categories, fwupd, os-release, 
packagekit, packagekit-local, packagekit-offline, packagekit-proxy, 
packagekit-refine-repos, packagekit-refresh, packagekit-upgrade, 
packagekit-url-to-app, appstream, desktop-menu-path, hardcoded-blacklist, 
modalias, odrs, packagekit-refine, rewrite-resource, packagekit-history, 
provenance, systemd-updates, generic-updates, provenance-license, icons, 
key-colors, key-colors-metadata
  12:06:06:0633 Gs  disabled plugins: dpkg, dummy, repos
  12:06:07:0935 Gs  Only 0 apps for popular list, hiding
  12:06:07:0965 Gs  hiding category audio-video featured applications: found 
only 0 to show, need at least 9
  12:06:07:0965 Gs  hiding category graphics featured applications: found only 
0 to show, need at least 9
  12:06:08:0925 Gs  Only 2 apps for recent list, hiding

  Screenshot:
  

[Desktop-packages] [Bug 1879318] Re: Removing gnome software snap plugin breaks gnome software storefront on Xubuntu 20.04

[Stuart]

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

** Description changed:

  How to reproduce:
  
  1) Fresh install of Xubuntu 20.04
  2) Open "Terminal"
  3) Type "sudo apt autoremove --purge snapd gnome-software-plugin-snap"
  4) Launch "Gnome Software"
  
  Result:
- I removed snapd & the Gnome Software snap plugin and I noticed that it broke 
the Gnome Software front page, where you can see all the featured and 
recommended applications etc. See attached screenshot. After running "sudo apt 
autoremove --purge snapd gnome-software-plugin-snap" the Gnome Software Center 
should default back to showing applications from the Ubuntu repository and not 
snap store.
+ I removed snapd & the Gnome Software snap plugin and I noticed that it broke 
the Gnome Software front page, where you can see all the featured and 
recommended applications etc. See attached screenshot. After running "sudo apt 
autoremove --purge snapd gnome-software-plugin-snap" the Gnome Software Center 
should default back to showing applications from the Ubuntu repository and not 
snap store. The same happens in Ubuntu 18.04!
  
  I tried clearing the app-info cache but to no avail.
  
  $pkill gnome-software
  $sudo rm -r /var/cache/app-info
  $sudo appstreamcli refresh --force --verbose
  
  Gnome-Software terminal output:
  12:06:06:0632 Gs  enabled plugins: desktop-categories, fwupd, os-release, 
packagekit, packagekit-local, packagekit-offline, packagekit-proxy, 
packagekit-refine-repos, packagekit-refresh, packagekit-upgrade, 
packagekit-url-to-app, appstream, desktop-menu-path, hardcoded-blacklist, 
modalias, odrs, packagekit-refine, rewrite-resource, packagekit-history, 
provenance, systemd-updates, generic-updates, provenance-license, icons, 
key-colors, key-colors-metadata
  12:06:06:0633 Gs  disabled plugins: dpkg, dummy, repos
  12:06:07:0935 Gs  Only 0 apps for popular list, hiding
  12:06:07:0965 Gs  hiding category audio-video featured applications: found 
only 0 to show, need at least 9
  12:06:07:0965 Gs  hiding category graphics featured applications: found only 
0 to show, need at least 9
  12:06:08:0925 Gs  Only 2 apps for recent list, hiding
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.36.0-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.445
  CurrentDesktop: XFCE
  Date: Mon May 18 11:56:16 2020
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snapN/A
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.xdg.autostart.gnome-software-service.desktop: [deleted]

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

Title:
  Removing gnome software snap plugin breaks gnome software storefront
  on Xubuntu 20.04

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  How to reproduce:

  1) Fresh install of Xubuntu 20.04
  2) Open "Terminal"
  3) Type "sudo apt autoremove --purge snapd gnome-software-plugin-snap"
  4) Launch "Gnome Software"

  Result:
  I removed snapd & the Gnome Software snap plugin and I noticed that it broke 
the Gnome Software front page, where you can see all the featured and 
recommended applications etc. See attached screenshot. After running "sudo apt 
autoremove --purge snapd gnome-software-plugin-snap" the Gnome Software Center 
should default back to showing applications from the Ubuntu repository and not 
snap store. The same happens in Ubuntu 18.04!

  I tried clearing the app-info cache but to no avail.

  $pkill gnome-software
  $sudo rm -r /var/cache/app-info
  $sudo appstreamcli refresh --force --verbose

  Gnome-Software terminal output:
  12:06:06:0632 Gs  enabled plugins: desktop-categories, fwupd, os-release, 
packagekit, packagekit-local, packagekit-offline, packagekit-proxy, 
packagekit-refine-repos, packagekit-refresh, packagekit-upgrade, 
packagekit-url-to-app, appstream, desktop-menu-path, hardcoded-blacklist, 
modalias, odrs, packagekit-refine, rewrite-resource, packagekit-history, 
provenance, systemd-updates, generic-updates, provenance-license, icons, 
key-colors, key-colors-metadata
  12:06:06:0633 Gs  disabled plugins: dpkg, dummy, repos
  12:06:07:0935 Gs  Only 0 apps for popular list, hiding
  12:06:07:0965 Gs  hiding category audio-video featured applications: found 
only 0 to show, need at least 9
  12:06:07:0965 Gs  hiding category 

[Desktop-packages] [Bug 1879318] Re: Removing gnome software snap plugin breaks gnome software storefront on Xubuntu 20.04

[Stuart]

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

Gnome Software Center should default back to showing applications from
the Ubuntu repository but there's nothing.

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

Title:
  Removing gnome software snap plugin breaks gnome software storefront
  on Xubuntu 20.04

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  How to reproduce:

  1) Fresh install of Xubuntu 20.04
  2) Open "Terminal"
  3) Type "sudo apt autoremove --purge snapd gnome-software-plugin-snap"
  4) Launch "Gnome Software"

  Result:
  I removed snapd & the Gnome Software snap plugin and I noticed that it broke 
the Gnome Software front page, where you can see all the featured and 
recommended applications etc. See attached screenshot. After running "sudo apt 
autoremove --purge snapd gnome-software-plugin-snap" the Gnome Software Center 
should default back to showing applications from the Ubuntu repository and not 
snap store.

  I tried clearing the app-info cache but to no avail.

  $pkill gnome-software
  $sudo rm -r /var/cache/app-info
  $sudo appstreamcli refresh --force --verbose

  Gnome-Software terminal output:
  12:06:06:0632 Gs  enabled plugins: desktop-categories, fwupd, os-release, 
packagekit, packagekit-local, packagekit-offline, packagekit-proxy, 
packagekit-refine-repos, packagekit-refresh, packagekit-upgrade, 
packagekit-url-to-app, appstream, desktop-menu-path, hardcoded-blacklist, 
modalias, odrs, packagekit-refine, rewrite-resource, packagekit-history, 
provenance, systemd-updates, generic-updates, provenance-license, icons, 
key-colors, key-colors-metadata
  12:06:06:0633 Gs  disabled plugins: dpkg, dummy, repos
  12:06:07:0935 Gs  Only 0 apps for popular list, hiding
  12:06:07:0965 Gs  hiding category audio-video featured applications: found 
only 0 to show, need at least 9
  12:06:07:0965 Gs  hiding category graphics featured applications: found only 
0 to show, need at least 9
  12:06:08:0925 Gs  Only 2 apps for recent list, hiding

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.36.0-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.445
  CurrentDesktop: XFCE
  Date: Mon May 18 11:56:16 2020
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snapN/A
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.xdg.autostart.gnome-software-service.desktop: [deleted]

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

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

[Desktop-packages] [Bug 1879318] Re: Removing gnome software snap plugin breaks gnome software storefront on Xubuntu 20.04

[Stuart]

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

This is not the same bug. Please compare screenshots, bug report 1873060
has a big empty space between apps and categories. I don't even have
apps showing in the front page at all.

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

Title:
  Removing gnome software snap plugin breaks gnome software storefront
  on Xubuntu 20.04

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  How to reproduce:

  1) Fresh install of Xubuntu 20.04
  2) Open "Terminal"
  3) Type "sudo apt autoremove --purge snapd gnome-software-plugin-snap"
  4) Launch "Gnome Software"

  Result:
  I removed snapd & the Gnome Software snap plugin and I noticed that it broke 
the Gnome Software front page, where you can see all the featured and 
recommended applications etc. See attached screenshot. After running "sudo apt 
autoremove --purge snapd gnome-software-plugin-snap" the Gnome Software Center 
should default back to showing applications from the Ubuntu repository and not 
snap store.

  I tried clearing the app-info cache but to no avail.

  $pkill gnome-software
  $sudo rm -r /var/cache/app-info
  $sudo appstreamcli refresh --force --verbose

  Gnome-Software terminal output:
  12:06:06:0632 Gs  enabled plugins: desktop-categories, fwupd, os-release, 
packagekit, packagekit-local, packagekit-offline, packagekit-proxy, 
packagekit-refine-repos, packagekit-refresh, packagekit-upgrade, 
packagekit-url-to-app, appstream, desktop-menu-path, hardcoded-blacklist, 
modalias, odrs, packagekit-refine, rewrite-resource, packagekit-history, 
provenance, systemd-updates, generic-updates, provenance-license, icons, 
key-colors, key-colors-metadata
  12:06:06:0633 Gs  disabled plugins: dpkg, dummy, repos
  12:06:07:0935 Gs  Only 0 apps for popular list, hiding
  12:06:07:0965 Gs  hiding category audio-video featured applications: found 
only 0 to show, need at least 9
  12:06:07:0965 Gs  hiding category graphics featured applications: found only 
0 to show, need at least 9
  12:06:08:0925 Gs  Only 2 apps for recent list, hiding

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.36.0-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.445
  CurrentDesktop: XFCE
  Date: Mon May 18 11:56:16 2020
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snapN/A
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.xdg.autostart.gnome-software-service.desktop: [deleted]

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

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

[Desktop-packages] [Bug 1879318] [NEW] Removing gnome software snap plugin breaks gnome software storefront on Xubuntu 20.04

[Stuart]

Public bug reported:

How to reproduce:

1) Fresh install of Xubuntu 20.04
2) Open "Terminal"
3) Type "sudo apt autoremove --purge snapd gnome-software-plugin-snap"
4) Launch "Gnome Software"

Result:
I removed snapd & the Gnome Software snap plugin and I noticed that it broke 
the Gnome Software front page, where you can see all the featured and 
recommended applications etc. See attached screenshot. After running "sudo apt 
autoremove --purge snapd gnome-software-plugin-snap" the Gnome Software Center 
should default back to showing applications from the Ubuntu repository and not 
snap store.

I tried clearing the app-info cache but to no avail.

$pkill gnome-software
$sudo rm -r /var/cache/app-info
$sudo appstreamcli refresh --force --verbose

Gnome-Software terminal output:
12:06:06:0632 Gs  enabled plugins: desktop-categories, fwupd, os-release, 
packagekit, packagekit-local, packagekit-offline, packagekit-proxy, 
packagekit-refine-repos, packagekit-refresh, packagekit-upgrade, 
packagekit-url-to-app, appstream, desktop-menu-path, hardcoded-blacklist, 
modalias, odrs, packagekit-refine, rewrite-resource, packagekit-history, 
provenance, systemd-updates, generic-updates, provenance-license, icons, 
key-colors, key-colors-metadata
12:06:06:0633 Gs  disabled plugins: dpkg, dummy, repos
12:06:07:0935 Gs  Only 0 apps for popular list, hiding
12:06:07:0965 Gs  hiding category audio-video featured applications: found only 
0 to show, need at least 9
12:06:07:0965 Gs  hiding category graphics featured applications: found only 0 
to show, need at least 9
12:06:08:0925 Gs  Only 2 apps for recent list, hiding

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-software 3.36.0-0ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.445
CurrentDesktop: XFCE
Date: Mon May 18 11:56:16 2020
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-snapN/A
LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.xdg.autostart.gnome-software-service.desktop: [deleted]

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


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot_2020-05-18_11-55-25.png"
   
https://bugs.launchpad.net/bugs/1879318/+attachment/5373385/+files/Screenshot_2020-05-18_11-55-25.png

** Summary changed:

- Removing gnome software snap plugin breaks gnome software storefront on 
Ubuntu 20.04
+ Removing gnome software snap plugin breaks gnome software storefront on 
Xubuntu 20.04

** Description changed:

  How to reproduce:
  
  1) Fresh install of Xubuntu 20.04
  2) Open "Terminal"
  3) Type "sudo apt autoremove --purge snapd gnome-software-plugin-snap"
  4) Launch "Gnome Software"
  
- Result
+ Result:
  I removed snapd & the Gnome Software snap plugin and I noticed that it broke 
the Gnome Software front page, where you can see all the featured and 
recommended applications etc. See attached screenshot. After running "sudo apt 
autoremove --purge snapd gnome-software-plugin-snap" the Gnome Software Center 
should default back to showing applications from the Ubuntu repository and not 
snap store.
  
  I tried clearing the app-info cache but to no avail.
  
  $pkill gnome-software
  $sudo rm -r /var/cache/app-info
  $sudo appstreamcli refresh --force --verbose
  
  Gnome-Software terminal output:
  12:06:06:0632 Gs  enabled plugins: desktop-categories, fwupd, os-release, 
packagekit, packagekit-local, packagekit-offline, packagekit-proxy, 
packagekit-refine-repos, packagekit-refresh, packagekit-upgrade, 
packagekit-url-to-app, appstream, desktop-menu-path, hardcoded-blacklist, 
modalias, odrs, packagekit-refine, rewrite-resource, packagekit-history, 
provenance, systemd-updates, generic-updates, provenance-license, icons, 
key-colors, key-colors-metadata
  12:06:06:0633 Gs  disabled plugins: dpkg, dummy, repos
  12:06:07:0935 Gs  Only 0 apps for popular list, hiding
  12:06:07:0965 Gs  hiding category audio-video featured applications: found 
only 0 to show, need at least 9
  12:06:07:0965 Gs  hiding category graphics featured applications: found only 
0 to show, need at least 9
  12:06:08:0925 Gs  Only 2 apps for recent list, hiding
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.36.0-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 

[Desktop-packages] [Bug 847708] Re: "Restart Firefox" button in crash dialog does not restart Firefox but just exits instead

[Stuart Langridge]

This is still an issue in 18.04 at least.

** Changed in: firefox (Ubuntu)
   Status: Expired => New

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

Title:
  "Restart Firefox" button in crash dialog does not restart Firefox but
  just exits instead

Status in firefox package in Ubuntu:
  New

Bug description:
  When Firefox crashes, the crash dialog (allowing submission of a
  report upstream) has a "Restart Firefox" button. Clicking that button
  does not, as far as I can tell, restart Firefox; instead, the crash
  dialog closes, and I have to restart Firefox myself.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: firefox 6.0.2+build2+nobinonly-0ubuntu0.11.04.1
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic-pae 2.6.38.8
  Uname: Linux 2.6.38-11-generic-pae i686
  Architecture: i386
  Date: Mon Sep 12 12:01:33 2011
  FirefoxPackages:
   firefox 6.0.2+build2+nobinonly-0ubuntu0.11.04.1
   flashplugin-installer N/A
   adobe-flashplugin 10.3.183.4-0natty1
   icedtea-plugin N/A
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   LC_MESSAGES=en_GB.utf8
   SHELL=/bin/bash
  SourcePackage: firefox
  UpgradeStatus: Upgraded to natty on 2011-01-18 (236 days ago)

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

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

[Desktop-packages] [Bug 1875307] [NEW] Missing application icons Gnome-Software Xubuntu 20.04

[Stuart]

Public bug reported:

The majority of application icons in gnome software are missing. Even if
I re-install snapd gnome-software-plugin-snap, see attached screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-software 3.36.0-0ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Mon Apr 27 10:15:30 2020
InstallationDate: Installed on 2020-04-24 (2 days ago)
InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-snapN/A
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "gnomesoftwaremissingrepoicons2.png"
   
https://bugs.launchpad.net/bugs/1875307/+attachment/5361437/+files/gnomesoftwaremissingrepoicons2.png

** Description changed:

- The majority of application icons in gnome software is missing. Even if
+ The majority of application icons in gnome software are missing. Even if
  I re-install snapd gnome-software-plugin-snap, see attached screenshot.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.36.0-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Mon Apr 27 10:15:30 2020
  InstallationDate: Installed on 2020-04-24 (2 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InstalledPlugins:
-  gnome-software-plugin-flatpak N/A
-  gnome-software-plugin-snapN/A
+  gnome-software-plugin-flatpak N/A
+  gnome-software-plugin-snapN/A
  SourcePackage: gnome-software
  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-software in Ubuntu.
https://bugs.launchpad.net/bugs/1875307

Title:
  Missing application icons Gnome-Software Xubuntu 20.04

Status in gnome-software package in Ubuntu:
  New

Bug description:
  The majority of application icons in gnome software are missing. Even
  if I re-install snapd gnome-software-plugin-snap, see attached
  screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.36.0-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Mon Apr 27 10:15:30 2020
  InstallationDate: Installed on 2020-04-24 (2 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snapN/A
  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/1875307/+subscriptions

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

[Desktop-packages] [Bug 1870925] [NEW] UI freeze exception to remove problematic legacy action icons

[Stuart Jaggers]

Public bug reported:

The Yaru team added some icons to the theme for use in legacy GTK2 apps
(e.g., document-new, document-export and so on).

These looked good in apps like Inkscape.  However, during regression
testing, it was found that the icons caused unpredictable behaviour in
other GTK2 apps.  https://github.com/ubuntu/yaru/issues/2108 includes
screenshots.

The only way to fix is this to provide a 100% complete legacy icon set
including all sizes, which isn't achievable for 20.04.

So, our PR https://github.com/ubuntu/yaru/pull/2127 has removed the
legacy icons from Yaru for now.  It would be great to have a feature
freeze exception for this.  Any existing screenshots shouldn't be
affected unless they show third party GTK2 apps on the desktop, and it
would be a minor cosmetic difference if there's a difference at all.

If we don't have the freeze exception, some legacy apps will look poor,
as you can see from the issue
https://github.com/ubuntu/yaru/issues/2108.  Apologies for not realising
this before the freeze!  The benefit is a more consistent and
professional visual experience for users who install and use GTK2 apps.

** Affects: yaru-theme (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  UI freeze exception to remove problematic legacy action icons

Status in yaru-theme package in Ubuntu:
  New

Bug description:
  The Yaru team added some icons to the theme for use in legacy GTK2
  apps (e.g., document-new, document-export and so on).

  These looked good in apps like Inkscape.  However, during regression
  testing, it was found that the icons caused unpredictable behaviour in
  other GTK2 apps.  https://github.com/ubuntu/yaru/issues/2108 includes
  screenshots.

  The only way to fix is this to provide a 100% complete legacy icon set
  including all sizes, which isn't achievable for 20.04.

  So, our PR https://github.com/ubuntu/yaru/pull/2127 has removed the
  legacy icons from Yaru for now.  It would be great to have a feature
  freeze exception for this.  Any existing screenshots shouldn't be
  affected unless they show third party GTK2 apps on the desktop, and it
  would be a minor cosmetic difference if there's a difference at all.

  If we don't have the freeze exception, some legacy apps will look
  poor, as you can see from the issue
  https://github.com/ubuntu/yaru/issues/2108.  Apologies for not
  realising this before the freeze!  The benefit is a more consistent
  and professional visual experience for users who install and use GTK2
  apps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1870925/+subscriptions

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

[Desktop-packages] [Bug 416725] Re: Pulseaudio bluetooth module does not recognize a2dp profile

[stuart naylor]

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

The thing is its debatable if bluez.class = "0x240404" as I don't think
it is as its HSP/HFP and your device is multiprofile and the default is
HSP/HFP.

```
21,18 | 10 | 2Major Service Class
CoD Bit 21: Audio (Speaker, Microphone, Headset service, …)
CoD Bit 18: Rendering (Printing, Speaker, …)
Major Device Class
CoD Bits 10: Audio/Video (headset,speaker,stereo, video display, vcr…)
Minor Device Class
CoD Bits 2: Wearable Headset Device
```

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

Title:
  Pulseaudio bluetooth module does not recognize a2dp profile

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: pulseaudio-module-bluetooth

  Hi,
  I'm trying to use the auto detection of the bluetooth devices, but the module 
does not recognizes my device as a2dp stereo device.

  Release: Karmic Koala Alpha4
  Package Version: 1:0.9.16~test5-0ubuntu1

  
  I: module-udev-detect.c: /dev/snd/controlC0 is accessible: yes

   
  I: card.c: Created 1 "bluez_card.00_11_67_80_00_14"   

   
  I: sink.c: Created sink 1 "bluez_sink.00_11_67_80_00_14" with sample spec 
s16le 1ch 8000Hz and channel map mono   
   
  I: sink.c: bluetooth.protocol = "sco" 

   
  I: sink.c: device.intended_roles = "phone"

   
  I: sink.c: device.description = "BCK-08"  

   
  I: sink.c: device.string = "00:11:67:80:00:14"

   
  I: sink.c: device.api = "bluez"   

   
  I: sink.c: device.class = "sound" 

   
  I: sink.c: device.bus = "bluetooth"
  I: sink.c: device.form_factor = "headset"
  I: sink.c: bluez.path = "/org/bluez/4955/hci0/dev_00_11_67_80_00_14"
  I: sink.c: bluez.class = "0x240404"
  I: sink.c: bluez.name = "BCK-08"
  I: sink.c: device.icon_name = "audio-headset-bluetooth"
  I: source.c: Created source 2 "bluez_sink.00_11_67_80_00_14.monitor" with 
sample spec s16le 1ch 8000Hz and channel map mono
  I: source.c: device.description = "Monitor of BCK-08"
  I: source.c: device.class = "monitor"
  I: source.c: device.string = "00:11:67:80:00:14"
  I: source.c: device.api = "bluez"
  I: source.c: device.bus = "bluetooth"
  I: source.c: device.form_factor = "headset"
  I: source.c: bluez.path = "/org/bluez/4955/hci0/dev_00_11_67_80_00_14"
  I: source.c: bluez.class = "0x240404"
  I: source.c: bluez.name = "BCK-08"
  I: source.c: device.icon_name = "audio-headset-bluetooth"
  I: source.c: Created source 3 "bluez_source.00_11_67_80_00_14" with sample 
spec s16le 1ch 8000Hz and channel map mono
  I: source.c: bluetooth.protocol = "hsp"
  I: source.c: device.intended_roles = "phone"
  I: source.c: device.description = "BCK-08"
  I: source.c: device.string = "00:11:67:80:00:14"
  I: source.c: device.api = "bluez"
  I: source.c: device.class = "sound"
  I: source.c: device.bus = "bluetooth"
  I: source.c: device.form_factor = "headset"
  I: source.c: bluez.path = "/org/bluez/4955/hci0/dev_00_11_67_80_00_14"
  I: source.c: bluez.class = "0x240404"
  I: source.c: bluez.name = "BCK-08"
  I: source.c: device.icon_name = "audio-headset-bluetooth"

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

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

[Desktop-packages] [Bug 1865257] Re: Pulseaudio needs kernal conf IMU=size (64)

[stuart naylor]

Should be listed for RPi as the MTU is 64 but not sure how to report
specific Rpi kernel bugs?

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

Title:
  Pulseaudio needs kernal conf IMU=size (64)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Since Pulseaudio 11.0
  https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/11.0/
  "Improved bluetooth MTU configuration
  The packet size (a.k.a. MTU, "maximum transmission unit") that PulseAudio 
uses with the bluetooth HSP profile was previously always configured to be 48 
bytes. That worked with most hardware, but some adapters require a different 
packet size. Now PulseAudio asks the kernel what packet size should be used, 
which fixes the problem.

  However, a new problem appeared: some adapters that used to work with
  48 byte packet size don't any more work with the size that the kernel
  tells PulseAudio to use. If you find that HSP audio stopped working
  when upgrading to PulseAudio 11.0, you can revert to the old behaviour
  by passing option "autodetect_mtu=no" to module-bluetooth-discover in
  /etc/pulse/default.pa. If that fixes the problem, then please report
  the problem to the BlueZ and/or PulseAudio developers, so that the
  kernel can be fixed.

  Update: We decided to disable the MTU autodetection in 11.1 by
  default, because the feature caused too much problems and it looked
  like the kernel would not really get fixed even when people reported
  issues."

  Presume its a config option in the kernel that differs on each model.
  Pi3/4 should be 64 as they are very much like the 48 byte packages in
  reverse as don't work with the default of 48.

  Its listed as Pulse audio but presume it should be a config setting of
  the kernel for each Pi model.

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

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

[Desktop-packages] [Bug 1865257] [NEW] Pulseaudio needs kernal conf IMU=size (64)

[stuart naylor]

Public bug reported:

Since Pulseaudio 11.0
https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/11.0/
"Improved bluetooth MTU configuration
The packet size (a.k.a. MTU, "maximum transmission unit") that PulseAudio uses 
with the bluetooth HSP profile was previously always configured to be 48 bytes. 
That worked with most hardware, but some adapters require a different packet 
size. Now PulseAudio asks the kernel what packet size should be used, which 
fixes the problem.

However, a new problem appeared: some adapters that used to work with 48
byte packet size don't any more work with the size that the kernel tells
PulseAudio to use. If you find that HSP audio stopped working when
upgrading to PulseAudio 11.0, you can revert to the old behaviour by
passing option "autodetect_mtu=no" to module-bluetooth-discover in
/etc/pulse/default.pa. If that fixes the problem, then please report the
problem to the BlueZ and/or PulseAudio developers, so that the kernel
can be fixed.

Update: We decided to disable the MTU autodetection in 11.1 by default,
because the feature caused too much problems and it looked like the
kernel would not really get fixed even when people reported issues."

Presume its a config option in the kernel that differs on each model.
Pi3/4 should be 64 as they are very much like the 48 byte packages in
reverse as don't work with the default of 48.

Its listed as Pulse audio but presume it should be a config setting of
the kernel for each Pi model.

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


** Tags: kernel-bug

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

Title:
  Pulseaudio needs kernal conf IMU=size (64)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Since Pulseaudio 11.0
  https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/11.0/
  "Improved bluetooth MTU configuration
  The packet size (a.k.a. MTU, "maximum transmission unit") that PulseAudio 
uses with the bluetooth HSP profile was previously always configured to be 48 
bytes. That worked with most hardware, but some adapters require a different 
packet size. Now PulseAudio asks the kernel what packet size should be used, 
which fixes the problem.

  However, a new problem appeared: some adapters that used to work with
  48 byte packet size don't any more work with the size that the kernel
  tells PulseAudio to use. If you find that HSP audio stopped working
  when upgrading to PulseAudio 11.0, you can revert to the old behaviour
  by passing option "autodetect_mtu=no" to module-bluetooth-discover in
  /etc/pulse/default.pa. If that fixes the problem, then please report
  the problem to the BlueZ and/or PulseAudio developers, so that the
  kernel can be fixed.

  Update: We decided to disable the MTU autodetection in 11.1 by
  default, because the feature caused too much problems and it looked
  like the kernel would not really get fixed even when people reported
  issues."

  Presume its a config option in the kernel that differs on each model.
  Pi3/4 should be 64 as they are very much like the 48 byte packages in
  reverse as don't work with the default of 48.

  Its listed as Pulse audio but presume it should be a config setting of
  the kernel for each Pi model.

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

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

[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.

[stuart naylor]

Isn't this because HSP is not handled by pulse audio but ofono since
PA11.0?

https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/11.0/

Ofono is HSP 1.6 and wideband audio 16khz but ubuntu conf doesn't
implement?

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support.

Status in PulseAudio:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1855521] PulseList.txt

[stuart]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1855521/+attachment/5311058/+files/PulseList.txt

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

Title:
  [Dell Inspiron 5490] Internal microphone not detected

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No input device available for selection.

  Output of dmesg | grep snd:
  
  [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [2.532503] snd_hda_codec_realtek hdaudioC0D0:  Headphone Mic=0x1a
  [2.532504] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x19
  ---
  Alsamixer checked for mutes, all OK. Internal mic not present.

  Cannot remap using hdajackretask due to error tee:
  /sys/class/sound/hwC0D0/reconfig: Device or resource busy.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom3754 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 08:10:21 2019
  InstallationDate: Installed on 2019-12-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom1357 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-12-06 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5490
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.2
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1855521] RfKill.txt

[stuart]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1855521/+attachment/5311059/+files/RfKill.txt

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

Title:
  [Dell Inspiron 5490] Internal microphone not detected

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No input device available for selection.

  Output of dmesg | grep snd:
  
  [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [2.532503] snd_hda_codec_realtek hdaudioC0D0:  Headphone Mic=0x1a
  [2.532504] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x19
  ---
  Alsamixer checked for mutes, all OK. Internal mic not present.

  Cannot remap using hdajackretask due to error tee:
  /sys/class/sound/hwC0D0/reconfig: Device or resource busy.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom3754 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 08:10:21 2019
  InstallationDate: Installed on 2019-12-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom1357 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-12-06 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5490
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.2
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1855521] WifiSyslog.txt

[stuart]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1855521/+attachment/5311061/+files/WifiSyslog.txt

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

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

Title:
  [Dell Inspiron 5490] Internal microphone not detected

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No input device available for selection.

  Output of dmesg | grep snd:
  
  [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [2.532503] snd_hda_codec_realtek hdaudioC0D0:  Headphone Mic=0x1a
  [2.532504] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x19
  ---
  Alsamixer checked for mutes, all OK. Internal mic not present.

  Cannot remap using hdajackretask due to error tee:
  /sys/class/sound/hwC0D0/reconfig: Device or resource busy.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom3754 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 08:10:21 2019
  InstallationDate: Installed on 2019-12-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom1357 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-12-06 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5490
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.2
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1855521] UdevDb.txt

[stuart]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1855521/+attachment/5311060/+files/UdevDb.txt

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

Title:
  [Dell Inspiron 5490] Internal microphone not detected

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No input device available for selection.

  Output of dmesg | grep snd:
  
  [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [2.532503] snd_hda_codec_realtek hdaudioC0D0:  Headphone Mic=0x1a
  [2.532504] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x19
  ---
  Alsamixer checked for mutes, all OK. Internal mic not present.

  Cannot remap using hdajackretask due to error tee:
  /sys/class/sound/hwC0D0/reconfig: Device or resource busy.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom3754 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 08:10:21 2019
  InstallationDate: Installed on 2019-12-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom1357 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-12-06 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5490
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.2
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1855521] ProcModules.txt

[stuart]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1855521/+attachment/5311057/+files/ProcModules.txt

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

Title:
  [Dell Inspiron 5490] Internal microphone not detected

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No input device available for selection.

  Output of dmesg | grep snd:
  
  [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [2.532503] snd_hda_codec_realtek hdaudioC0D0:  Headphone Mic=0x1a
  [2.532504] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x19
  ---
  Alsamixer checked for mutes, all OK. Internal mic not present.

  Cannot remap using hdajackretask due to error tee:
  /sys/class/sound/hwC0D0/reconfig: Device or resource busy.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom3754 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 08:10:21 2019
  InstallationDate: Installed on 2019-12-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom1357 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-12-06 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5490
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.2
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1855521] ProcInterrupts.txt

[stuart]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1855521/+attachment/5311056/+files/ProcInterrupts.txt

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

Title:
  [Dell Inspiron 5490] Internal microphone not detected

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No input device available for selection.

  Output of dmesg | grep snd:
  
  [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [2.532503] snd_hda_codec_realtek hdaudioC0D0:  Headphone Mic=0x1a
  [2.532504] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x19
  ---
  Alsamixer checked for mutes, all OK. Internal mic not present.

  Cannot remap using hdajackretask due to error tee:
  /sys/class/sound/hwC0D0/reconfig: Device or resource busy.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom3754 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 08:10:21 2019
  InstallationDate: Installed on 2019-12-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom1357 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-12-06 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5490
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.2
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1855521] ProcEnviron.txt

[stuart]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1855521/+attachment/5311055/+files/ProcEnviron.txt

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

Title:
  [Dell Inspiron 5490] Internal microphone not detected

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No input device available for selection.

  Output of dmesg | grep snd:
  
  [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [2.532503] snd_hda_codec_realtek hdaudioC0D0:  Headphone Mic=0x1a
  [2.532504] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x19
  ---
  Alsamixer checked for mutes, all OK. Internal mic not present.

  Cannot remap using hdajackretask due to error tee:
  /sys/class/sound/hwC0D0/reconfig: Device or resource busy.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom3754 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 08:10:21 2019
  InstallationDate: Installed on 2019-12-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom1357 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-12-06 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5490
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.2
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1855521] ProcCpuinfoMinimal.txt

[stuart]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1855521/+attachment/5311054/+files/ProcCpuinfoMinimal.txt

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

Title:
  [Dell Inspiron 5490] Internal microphone not detected

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No input device available for selection.

  Output of dmesg | grep snd:
  
  [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [2.532503] snd_hda_codec_realtek hdaudioC0D0:  Headphone Mic=0x1a
  [2.532504] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x19
  ---
  Alsamixer checked for mutes, all OK. Internal mic not present.

  Cannot remap using hdajackretask due to error tee:
  /sys/class/sound/hwC0D0/reconfig: Device or resource busy.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom3754 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 08:10:21 2019
  InstallationDate: Installed on 2019-12-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom1357 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-12-06 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5490
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.2
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1855521] ProcCpuinfo.txt

[stuart]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1855521/+attachment/5311053/+files/ProcCpuinfo.txt

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

Title:
  [Dell Inspiron 5490] Internal microphone not detected

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No input device available for selection.

  Output of dmesg | grep snd:
  
  [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [2.532503] snd_hda_codec_realtek hdaudioC0D0:  Headphone Mic=0x1a
  [2.532504] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x19
  ---
  Alsamixer checked for mutes, all OK. Internal mic not present.

  Cannot remap using hdajackretask due to error tee:
  /sys/class/sound/hwC0D0/reconfig: Device or resource busy.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom3754 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 08:10:21 2019
  InstallationDate: Installed on 2019-12-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom1357 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-12-06 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5490
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.2
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1855521] Lspci.txt

[stuart]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1855521/+attachment/5311052/+files/Lspci.txt

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

Title:
  [Dell Inspiron 5490] Internal microphone not detected

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No input device available for selection.

  Output of dmesg | grep snd:
  
  [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [2.532503] snd_hda_codec_realtek hdaudioC0D0:  Headphone Mic=0x1a
  [2.532504] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x19
  ---
  Alsamixer checked for mutes, all OK. Internal mic not present.

  Cannot remap using hdajackretask due to error tee:
  /sys/class/sound/hwC0D0/reconfig: Device or resource busy.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom3754 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 08:10:21 2019
  InstallationDate: Installed on 2019-12-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom1357 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-12-06 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5490
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.2
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1855521] IwConfig.txt

[stuart]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1855521/+attachment/5311051/+files/IwConfig.txt

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

Title:
  [Dell Inspiron 5490] Internal microphone not detected

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No input device available for selection.

  Output of dmesg | grep snd:
  
  [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [2.532503] snd_hda_codec_realtek hdaudioC0D0:  Headphone Mic=0x1a
  [2.532504] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x19
  ---
  Alsamixer checked for mutes, all OK. Internal mic not present.

  Cannot remap using hdajackretask due to error tee:
  /sys/class/sound/hwC0D0/reconfig: Device or resource busy.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom3754 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 08:10:21 2019
  InstallationDate: Installed on 2019-12-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom1357 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-12-06 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5490
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.2
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1855521] CurrentDmesg.txt

[stuart]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1855521/+attachment/5311050/+files/CurrentDmesg.txt

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

Title:
  [Dell Inspiron 5490] Internal microphone not detected

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No input device available for selection.

  Output of dmesg | grep snd:
  
  [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [2.532503] snd_hda_codec_realtek hdaudioC0D0:  Headphone Mic=0x1a
  [2.532504] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x19
  ---
  Alsamixer checked for mutes, all OK. Internal mic not present.

  Cannot remap using hdajackretask due to error tee:
  /sys/class/sound/hwC0D0/reconfig: Device or resource busy.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom3754 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 08:10:21 2019
  InstallationDate: Installed on 2019-12-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom1357 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-12-06 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5490
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.2
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1855521] Re: [Dell Inspiron 5490] Internal microphone not detected

[stuart]

apport information

** Tags added: apport-collected

** Description changed:

  No input device available for selection.
  
  Output of dmesg | grep snd:
  
  [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [2.532503] snd_hda_codec_realtek hdaudioC0D0:  Headphone Mic=0x1a
  [2.532504] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x19
  ---
  Alsamixer checked for mutes, all OK. Internal mic not present.
  
  Cannot remap using hdajackretask due to error tee:
  /sys/class/sound/hwC0D0/reconfig: Device or resource busy.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom3754 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 08:10:21 2019
  InstallationDate: Installed on 2019-12-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu8.2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  tom1357 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 19.10
+ InstallationDate: Installed on 2019-12-06 (2 days ago)
+ InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. 
Integrated_Webcam_HD
+  Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint
+  Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: Dell Inc. Inspiron 5490
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
+ RelatedPackageVersions:
+  linux-restricted-modules-5.3.0-24-generic N/A
+  linux-backports-modules-5.3.0-24-generic  N/A
+  linux-firmware1.183.2
+ Tags:  eoan
+ Uname: Linux 5.3.0-24-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 10/30/2019
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.3.0
+ dmi.board.name: 0012KY
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
+ dmi.product.family: Inspiron
+ dmi.product.name: Inspiron 5490
+ dmi.product.sku: 0955
+ dmi.sys.vendor: Dell Inc.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1855521/+attachment/5311048/+files/AlsaInfo.txt

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

Title:
  [Dell Inspiron 5490] Internal microphone not detected

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No input device available for selection.

  Output of dmesg | grep snd:
  
  [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 

[Desktop-packages] [Bug 1855521] CRDA.txt

[stuart]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1855521/+attachment/5311049/+files/CRDA.txt

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

Title:
  [Dell Inspiron 5490] Internal microphone not detected

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No input device available for selection.

  Output of dmesg | grep snd:
  
  [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [2.532503] snd_hda_codec_realtek hdaudioC0D0:  Headphone Mic=0x1a
  [2.532504] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x19
  ---
  Alsamixer checked for mutes, all OK. Internal mic not present.

  Cannot remap using hdajackretask due to error tee:
  /sys/class/sound/hwC0D0/reconfig: Device or resource busy.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom3754 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 08:10:21 2019
  InstallationDate: Installed on 2019-12-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom1357 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-12-06 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:565a Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 27c6:538d Goodix FingerPrint
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5490
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=b815e847-77a7-4ad7-8c24-7dddbf722055 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.2
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1855521] [NEW] Internal microphone not detected

[stuart]

Public bug reported:

No input device available for selection.

Output of dmesg | grep snd:

[2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
[2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
[2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs:
[2.532503] snd_hda_codec_realtek hdaudioC0D0:  Headphone Mic=0x1a
[2.532504] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x19
---
Alsamixer checked for mutes, all OK. Internal mic not present.

Cannot remap using hdajackretask due to error tee:
/sys/class/sound/hwC0D0/reconfig: Device or resource busy.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tom3754 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Dec  7 08:10:21 2019
InstallationDate: Installed on 2019-12-06 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/30/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.0
dmi.board.name: 0012KY
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5490
dmi.product.sku: 0955
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug eoan

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

Title:
  Internal microphone not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  No input device available for selection.

  Output of dmesg | grep snd:
  
  [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [2.532503] snd_hda_codec_realtek hdaudioC0D0:  Headphone Mic=0x1a
  [2.532504] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x19
  ---
  Alsamixer checked for mutes, all OK. Internal mic not present.

  Cannot remap using hdajackretask due to error tee:
  /sys/class/sound/hwC0D0/reconfig: Device or resource busy.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom3754 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 08:10:21 2019
  InstallationDate: Installed on 2019-12-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0012KY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5490
  dmi.product.sku: 0955
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1609750] Re: Audio not working on Acer Chromebook R11

[daniel primo stuart]

Kernel needs this patch for maxim98090 to work on cyan and some baytrail
chromebooks:
https://github.com/torvalds/linux/commit/d5e120422db8808e1c8b1507900ca393a877c58f

As it didn't make to 5.3 on time, would be nice if it were backported by
ubuntu devs

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

Title:
  Audio not working on Acer Chromebook R11

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Audio is not working at all on Acer Chromebook R11 (codename CYAN).
  It's a Intel Braswell platform. snd_hda_intel messages seem normal,
  but Pulseaudio does not detect sound hardware.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-1.1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  Date: Thu Aug  4 14:12:03 2016
  InstallationDate: Installed on 2016-07-22 (13 days ago)
  InstallationMedia:
   
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE
  --- 
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08
  InstallationDate: Installed on 2016-07-22 (13 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux-image-4.4.0-33-generic 4.4.0-33.52
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-33-generic N/A
   linux-backports-modules-4.4.0-33-generic  N/A
   linux-firmware1.159
  Tags:  yakkety
  Uname: Linux 4.4.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/20/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

[Desktop-packages] [Bug 119899]

[Stuart-stuarthalliday]

Eh?

Surely you can't expect mere mortal humans to do this?

What if they've never read your posting?

No, the solution is for the *program* to prompt the user to perform a
Folder rebuild and then do it.

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

Title:
  After-the-fact Filters on custom header won't match for IMAP messages

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: thunderbird

  Message filtering appears to be broken on Thunderbird
  2.0.0.4~rc1-0ubuntu1 in Gutsy with IMAP. I created a filter for the
  warthogs list and it would not move the messages from my inbox to the
  folder I had created. It also did not put anything into the filter
  log. I tried using the Thunderbird on Feisty with my laptop and it
  worked fine when using the same settings. Chris Jones mentioned he
  also noticed the same or perhaps a similar issue today.

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

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

[Desktop-packages] [Bug 1827948] Re: Use libreoffice-style-breeze as the default icon theme

[Stuart Jaggers]

In isolation I don't prefer one icon set to the other, but I agree that
Breeze is a better fit for the desktop style, so I would be +1.

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

Title:
  Use libreoffice-style-breeze as the default icon theme

Status in libreoffice package in Ubuntu:
  New

Bug description:
  The Yaru icon theme uses 1 pixel strokes for its symbolic icon set. 
  So do the breeze icons for libreoffice.

  All in all does the breeze icon set for libre office fit very good to
  the look of the Yaru icons.

  https://i.imgur.com/tgioycv.png

  https://i.imgur.com/WwKvjMh.png

  Thus I would suggest to use it as the default icon set in Ubuntu to
  guarantee a consistent look and feel across the desktop

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

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

[Desktop-packages] [Bug 1798074] Re: LIbreoffice crashes on startup

[Stuart Langridge]

Unfortunately I removed the archive version of LO and installed the snap
version, which is not exhibiting the problem, because I need to be able
to edit documents; I can therefore no longer replicate the bug. But
pleasingly it looks as though Jani can, so I'll leave it in their hands.

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

Title:
  LIbreoffice crashes on startup

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  On starting up LibreOffice, it crashes. Starting from a terminal with
  just "libreoffice", I see the "general open a document" libreoffice
  window and a popup dialog titled "LibreOffice 6.0 Document Recovery",
  with text "Due to an unexpected error, LibreOffice crashed. All the
  files you were working on will now be saved. The next time LibreOffice
  is launched, your files will be recovered automatically. The following
  files will be recovered:" (and no files to be recovered are listed).
  Clicking "OK" on this dialog hides it and the general window, and then
  shows them both again; clicking OK on that dialog exits. LibreOffice
  does not start.

  Running "libreoffice --norestore" gives a stack trace:


  $ libreoffice --norestore
  Application Error

  
  Fatal exception: Signal 6
  Stack:
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7fa00e2c8568]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c3c6)[0x7fa00e2f13c6]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fa00df02e97]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7fa00df04801]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2d5b562)[0x7fa01126a562]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0xa2)[0x7fa0111f61c2]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x1d0d580)[0x7fa01021c580]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cecb6d)[0x7fa0111fbb6d]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x163b2)[0x7fa00e2cb3b2]
  /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c28f)[0x7fa00e2f128f]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20]
  /lib/x86_64-linux-gnu/libc.so.6(+0x18e5a1)[0x7fa00e0525a1]
  
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7fa00c0e7aa4]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2d6972b)[0x7fa01127872b]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9156)[0x7fa00c0dd156]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9398)[0x7fa00c0dd398]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8db66)[0x7fa00c0a1b66]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc0fc2)[0x7fa00c0d4fc2]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143]
  /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d179)[0x7fa00c0a1179]
  
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x155)[0x7fa00baf60f5]
  /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c4c0)[0x7fa00baf64c0]
  
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7fa00baf654c]
  /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x414d4)[0x7f9ff8b524d4]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x2e)[0x7fa0111f68ce]
  
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7fa0111f8075]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x1d12fa3)[0x7fa010221fa3]
  /usr/lib/libreoffice/program/libmergedlo.so(+0x2cee756)[0x7fa0111fd756]
  /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7fa0111fd860]
  
/usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7fa0102430c5]
  /usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x55dd01f4578b]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7fa00dee5b97]
  /usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x55dd01f457ca]

  I have tried entirely removing my profile, ~/.config/libreoffice , but
  the same problem still exhibits.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-common 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Oct 16 12:58:04 2018
  InstallationDate: Installed on 2014-04-07 (1653 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-04-28 (171 days ago)

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

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

[Desktop-packages] [Bug 1820135] [NEW] Feature freeze exception to address three icon bugs

[Stuart Jaggers]

Public bug reported:

Following UI freeze, testing has discovered some icon bugs which could
be fixed if an exception were granted.  They are as follows.

1) Missing symlinks cause Gnome control centre to fall back to non-Yaru
symbols for power settings and online accounts.  The fallback symbols
are thicker than the corresponding ones in Yaru and look out of place
next to the others.

https://github.com/ubuntu/yaru/issues/1259 describes the issue and
https://github.com/ubuntu/yaru/pull/1262 fixes it by adding the missing
symlinks (both with screenshots).

2) A background process puts a poorly rendered, pixellated Yaru icon on
the launcher when it errors.  The cause was determined to be a symlink.
Removing this causes the process to fall back to a pre-Yaru icon which
is properly rendered.  The proposed fix at this stage is merely to
remove the symlink, because an old icon rendered properly is better than
a Yaru one with pixels.

https://github.com/ubuntu/yaru/issues/1210 describes the issue and
diagnosis (with screenshots) and
https://github.com/ubuntu/yaru/pull/1267 fixes it.

3) A missing symlink causes Gnome Notes to use a non-Yaru icon when we
have a Yaru icon for Notes.  Adding the missing symlink would fix this.

https://github.com/ubuntu/yaru/issues/1180#issuecomment-472493170
describes the problem with screenshot.

All three issues could be fixed and fully tested with minimal risk
simply by adding a small number of symlinks and removing one other.  The
benefit would be making the theme more polished in time for 19.04,
rather than shipping it with three bugs that could be fixed.  The
changes have been tested by the Yaru team in branches of Yaru and the
nature of these cosmetic changes makes them low risk.  Because they're
icon defects, they would otherwise be visible to all users of Ubuntu,
and fixing them would have a good ratio of risk to benefit IMHO.

** Affects: yaru-theme (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Feature freeze exception to address three icon bugs

Status in yaru-theme package in Ubuntu:
  New

Bug description:
  Following UI freeze, testing has discovered some icon bugs which could
  be fixed if an exception were granted.  They are as follows.

  1) Missing symlinks cause Gnome control centre to fall back to non-
  Yaru symbols for power settings and online accounts.  The fallback
  symbols are thicker than the corresponding ones in Yaru and look out
  of place next to the others.

  https://github.com/ubuntu/yaru/issues/1259 describes the issue and
  https://github.com/ubuntu/yaru/pull/1262 fixes it by adding the
  missing symlinks (both with screenshots).

  2) A background process puts a poorly rendered, pixellated Yaru icon
  on the launcher when it errors.  The cause was determined to be a
  symlink.  Removing this causes the process to fall back to a pre-Yaru
  icon which is properly rendered.  The proposed fix at this stage is
  merely to remove the symlink, because an old icon rendered properly is
  better than a Yaru one with pixels.

  https://github.com/ubuntu/yaru/issues/1210 describes the issue and
  diagnosis (with screenshots) and
  https://github.com/ubuntu/yaru/pull/1267 fixes it.

  3) A missing symlink causes Gnome Notes to use a non-Yaru icon when we
  have a Yaru icon for Notes.  Adding the missing symlink would fix
  this.

  https://github.com/ubuntu/yaru/issues/1180#issuecomment-472493170
  describes the problem with screenshot.

  All three issues could be fixed and fully tested with minimal risk
  simply by adding a small number of symlinks and removing one other.
  The benefit would be making the theme more polished in time for 19.04,
  rather than shipping it with three bugs that could be fixed.  The
  changes have been tested by the Yaru team in branches of Yaru and the
  nature of these cosmetic changes makes them low risk.  Because they're
  icon defects, they would otherwise be visible to all users of Ubuntu,
  and fixing them would have a good ratio of risk to benefit IMHO.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1820135/+subscriptions

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

[Desktop-packages] [Bug 1816269] Re: No image on KVM switch

[Stuart]

@Update: Disabling DP1.2 and DDC/CI on the monitors seems to solve this.
The monitors are Dell U2415.

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

Title:
  No image on KVM switch

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Hi all,

  I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04
  (uname -r = 4.18.0-15-generic). I have the NUC connected via USB-C to
  a dual DisplayPort adapter, to an Avocent SV340D KVM.

  If I have the KVM on the switch for the NUC, everything works great.
  If I switch the KVM to another channel, and then switch back to the
  NUC, I only get black screens. The only solution is to hard reboot the
  NUC.

  Any help would be appreciated.

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

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

[Desktop-packages] [Bug 1816269] Re: No image on KVM switch

[Stuart]

@Update: cancel above comment, worked initially.

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

Title:
  No image on KVM switch

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Hi all,

  I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04
  (uname -r = 4.18.0-15-generic). I have the NUC connected via USB-C to
  a dual DisplayPort adapter, to an Avocent SV340D KVM.

  If I have the KVM on the switch for the NUC, everything works great.
  If I switch the KVM to another channel, and then switch back to the
  NUC, I only get black screens. The only solution is to hard reboot the
  NUC.

  Any help would be appreciated.

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

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

[Desktop-packages] [Bug 1816269] [NEW] No image on KVM switch

[Stuart]

Public bug reported:

Hi all,

I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04
(uname -r = 4.18.0-15-generic). I have the NUC connected via USB-C to a
dual DisplayPort adapter, to an Avocent SV340D KVM.

If I have the KVM on the switch for the NUC, everything works great. If
I switch the KVM to another channel, and then switch back to the NUC, I
only get black screens. The only solution is to hard reboot the NUC.

Any help would be appreciated.

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

** Description changed:

  Hi all,
  
  I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04
  (uname -r = 4.18.0-15-generic). I have the NUC connected via USB-C to a
  dual DisplayPort adapter, to an Avocent SV340D KVM.
  
  If I have the KVM on the switch for the NUC, everything works great. If
  I switch the KVM to another channel, and then switch back to the NUC, I
  only get black screens. The only solution is to hard reboot the NUC.
  
- Any help would be aprpeciated.
+ Any help would be appreciated.

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

Title:
  No image on KVM switch

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Hi all,

  I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04
  (uname -r = 4.18.0-15-generic). I have the NUC connected via USB-C to
  a dual DisplayPort adapter, to an Avocent SV340D KVM.

  If I have the KVM on the switch for the NUC, everything works great.
  If I switch the KVM to another channel, and then switch back to the
  NUC, I only get black screens. The only solution is to hard reboot the
  NUC.

  Any help would be appreciated.

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

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

[Desktop-packages] [Bug 1763975] Re: DP1.2 daisy-chain flickering

[Stuart]

Just wondering if there is any update on this?

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

Title:
  DP1.2 daisy-chain flickering

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Hi all,

  I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04
  (uname -r = 4.15.0-15-generic). I have the NUC connected via USB-C to
  DisplayPort, to an Avocent SV340D KVM, then to a Dell U2415 which has
  DP1.2 enabled and is daisy-chainged to another Dell U2415 (DP1.2
  disabled on the second monitor as per Dell instructions).

  I am getting flickering whereby randomly display1 or display2 turn
  black and then back on again. When I disable DP1.2 on the display1,
  and therefore get a duplicate display (as opposed to extended) on
  display2, I get no flickering at all.

  The same setup yields no flickering when running from a Windows 10
  box, so don't think it is the monitors.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 14 12:52:24 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5927] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:2068]
  InstallationDate: Installed on 2018-04-01 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180401)
  MachineType: Intel Corporation NUC7i7BNH
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0062.2018.0222.1644
  dmi.board.name: NUC7i7BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J31145-307
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0062.2018.0222.1644:bd02/22/2018:svnIntelCorporation:pnNUC7i7BNH:pvrJ31153-308:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-307:cvnIntelCorporation:ct3:cvr2:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC7i7BNH
  dmi.product.version: J31153-308
  dmi.sys.vendor: Intel Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  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/linux/+bug/1763975/+subscriptions

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

[Desktop-packages] [Bug 1798074] [NEW] LIbreoffice crashes on startup

[Stuart Langridge]

Public bug reported:

On starting up LibreOffice, it crashes. Starting from a terminal with
just "libreoffice", I see the "general open a document" libreoffice
window and a popup dialog titled "LibreOffice 6.0 Document Recovery",
with text "Due to an unexpected error, LibreOffice crashed. All the
files you were working on will now be saved. The next time LibreOffice
is launched, your files will be recovered automatically. The following
files will be recovered:" (and no files to be recovered are listed).
Clicking "OK" on this dialog hides it and the general window, and then
shows them both again; clicking OK on that dialog exits. LibreOffice
does not start.

Running "libreoffice --norestore" gives a stack trace:


$ libreoffice --norestore
Application Error


Fatal exception: Signal 6
Stack:
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7fa00e2c8568]
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c3c6)[0x7fa00e2f13c6]
/lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fa00df02e97]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7fa00df04801]
/usr/lib/libreoffice/program/libmergedlo.so(+0x2d5b562)[0x7fa01126a562]
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0xa2)[0x7fa0111f61c2]
/usr/lib/libreoffice/program/libmergedlo.so(+0x1d0d580)[0x7fa01021c580]
/usr/lib/libreoffice/program/libmergedlo.so(+0x2cecb6d)[0x7fa0111fbb6d]
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x163b2)[0x7fa00e2cb3b2]
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c28f)[0x7fa00e2f128f]
/lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20]
/lib/x86_64-linux-gnu/libc.so.6(+0x18e5a1)[0x7fa00e0525a1]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7fa00c0e7aa4]
/usr/lib/libreoffice/program/libmergedlo.so(+0x2d6972b)[0x7fa01127872b]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9156)[0x7fa00c0dd156]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9398)[0x7fa00c0dd398]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8db66)[0x7fa00c0a1b66]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc0fc2)[0x7fa00c0d4fc2]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143]
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d179)[0x7fa00c0a1179]
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x155)[0x7fa00baf60f5]
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c4c0)[0x7fa00baf64c0]
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7fa00baf654c]
/usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x414d4)[0x7f9ff8b524d4]
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x2e)[0x7fa0111f68ce]
/usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7fa0111f8075]
/usr/lib/libreoffice/program/libmergedlo.so(+0x1d12fa3)[0x7fa010221fa3]
/usr/lib/libreoffice/program/libmergedlo.so(+0x2cee756)[0x7fa0111fd756]
/usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7fa0111fd860]
/usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7fa0102430c5]
/usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x55dd01f4578b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7fa00dee5b97]
/usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x55dd01f457ca]

I have tried entirely removing my profile, ~/.config/libreoffice , but
the same problem still exhibits.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libreoffice-common 1:6.0.6-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Oct 16 12:58:04 2018
InstallationDate: Installed on 2014-04-07 (1653 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
PackageArchitecture: all
SourcePackage: libreoffice
UpgradeStatus: Upgraded to bionic on 2018-04-28 (171 days ago)

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


** Tags: amd64 apport-bug bionic third-party-packages

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

Title:
  LIbreoffice crashes on startup

Status in libreoffice package in Ubuntu:
  New

Bug description:
  On starting up LibreOffice, it crashes. Starting from a terminal with
  just "libreoffice", I see the "general open a document" libreoffice
  window and a popup dialog titled "LibreOffice 6.0 Document Recovery",
  with text "Due to an unexpected error, LibreOffice crashed. All the
  files you were working on will now be saved. The next time LibreOffice
  is launched, your files will be recovered automatically. The following
  files will be recovered:" (and no files to be recovered are listed).
  Clicking "OK" on this dialog hides it and the general 

[Desktop-packages] [Bug 1796865] [NEW] package libwoff1 1.0.2-1build0.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

[Harry Stuart Curtis]

Public bug reported:

lsb_release -rd

Description:Ubuntu 18.04.1 LTS
Release:18.04

What I expected to happen:

I expected Ubuntu to start without any errors.

What happened instead:

I received an error after logging in saying that a system app had a
problem.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libwoff1 1.0.2-1build0.1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
AptOrdering:
 libbrotli1:amd64: Install
 libwoff1:amd64: Install
 libwebkit2gtk-4.0-37:amd64: Install
 libjavascriptcoregtk-4.0-18:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Mon Oct  8 11:18:45 2018
Dependencies:
 gcc-8-base 8.2.0-1ubuntu2~18.04
 libbrotli1 1.0.3-1ubuntu1.2
 libc6 2.27-3ubuntu1
 libgcc1 1:8.2.0-1ubuntu2~18.04
 libstdc++6 8.2.0-1ubuntu2~18.04
DuplicateSignature:
 package:libwoff1:1.0.2-1build0.1
 Unpacking libwoff1:amd64 (1.0.2-1build0.1) ...
 dpkg-deb: error: failed to read archive 
'/var/cache/apt/archives/libwoff1_1.0.2-1build0.1_amd64.deb': No such file or 
directory
 dpkg: error processing archive 
/var/cache/apt/archives/libwoff1_1.0.2-1build0.1_amd64.deb (--unpack):
  dpkg-deb --fsys-tarfile subprocess returned error exit status 2
ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
InstallationDate: Installed on 2018-03-29 (193 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
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.3ubuntu0.1
SourcePackage: woff2
Title: package libwoff1 1.0.2-1build0.1 failed to install/upgrade: dpkg-deb 
--fsys-tarfile subprocess returned error exit status 2
UpgradeStatus: Upgraded to bionic on 2018-05-08 (153 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package libwoff1 1.0.2-1build0.1 failed to install/upgrade: dpkg-deb
  --fsys-tarfile subprocess returned error exit status 2

Status in woff2 package in Ubuntu:
  New

Bug description:
  lsb_release -rd

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  What I expected to happen:

  I expected Ubuntu to start without any errors.

  What happened instead:

  I received an error after logging in saying that a system app had a
  problem.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libwoff1 1.0.2-1build0.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  AptOrdering:
   libbrotli1:amd64: Install
   libwoff1:amd64: Install
   libwebkit2gtk-4.0-37:amd64: Install
   libjavascriptcoregtk-4.0-18:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Oct  8 11:18:45 2018
  Dependencies:
   gcc-8-base 8.2.0-1ubuntu2~18.04
   libbrotli1 1.0.3-1ubuntu1.2
   libc6 2.27-3ubuntu1
   libgcc1 1:8.2.0-1ubuntu2~18.04
   libstdc++6 8.2.0-1ubuntu2~18.04
  DuplicateSignature:
   package:libwoff1:1.0.2-1build0.1
   Unpacking libwoff1:amd64 (1.0.2-1build0.1) ...
   dpkg-deb: error: failed to read archive 
'/var/cache/apt/archives/libwoff1_1.0.2-1build0.1_amd64.deb': No such file or 
directory
   dpkg: error processing archive 
/var/cache/apt/archives/libwoff1_1.0.2-1build0.1_amd64.deb (--unpack):
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  InstallationDate: Installed on 2018-03-29 (193 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  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.3ubuntu0.1
  SourcePackage: woff2
  Title: package libwoff1 1.0.2-1build0.1 failed to install/upgrade: dpkg-deb 
--fsys-tarfile subprocess returned error exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-05-08 (153 days ago)

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

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

[Desktop-packages] [Bug 1760849] Re: Enhancement: Make the login screen follow the mouse to other monitors

[Stuart Bishop]

Upstream issue shuffled to to
https://gitlab.gnome.org/GNOME/gdm/issues/372

** Changed in: gdm
   Importance: Medium => Undecided

** Changed in: gdm
   Status: Expired => New

** Changed in: gdm
 Remote watch: GNOME Bug Tracker #794971 => None

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

Title:
  Enhancement: Make the login screen follow the mouse to other monitors

Status in gdm:
  New
Status in gdm3 package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu login screen is tiled on all displays, not mirrored, making
  it nearly impossible to login when using an external monitor if the
  laptop screen is not visible.

  There appears to be no available control to alter the display settings
  of the login screen. Prior to bionic, the controls followed the mouse
  onto different displays so you could login by giving the mouse a swipe
  to the right to get the controls to appear.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 22:13:53 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.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/gdm/+bug/1760849/+subscriptions

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

[Desktop-packages] [Bug 1763975] Re: DP1.2 daisy-chain flickering

[Stuart]

@update. Started occurring even when bypassing the Avocent.

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

Title:
  DP1.2 daisy-chain flickering

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi all,

  I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04
  (uname -r = 4.15.0-15-generic). I have the NUC connected via USB-C to
  DisplayPort, to an Avocent SV340D KVM, then to a Dell U2415 which has
  DP1.2 enabled and is daisy-chainged to another Dell U2415 (DP1.2
  disabled on the second monitor as per Dell instructions).

  I am getting flickering whereby randomly display1 or display2 turn
  black and then back on again. When I disable DP1.2 on the display1,
  and therefore get a duplicate display (as opposed to extended) on
  display2, I get no flickering at all.

  The same setup yields no flickering when running from a Windows 10
  box, so don't think it is the monitors.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 14 12:52:24 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5927] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:2068]
  InstallationDate: Installed on 2018-04-01 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180401)
  MachineType: Intel Corporation NUC7i7BNH
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0062.2018.0222.1644
  dmi.board.name: NUC7i7BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J31145-307
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0062.2018.0222.1644:bd02/22/2018:svnIntelCorporation:pnNUC7i7BNH:pvrJ31153-308:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-307:cvnIntelCorporation:ct3:cvr2:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC7i7BNH
  dmi.product.version: J31153-308
  dmi.sys.vendor: Intel Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  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/1763975/+subscriptions

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

[Desktop-packages] [Bug 1763975] Re: DP1.2 daisy-chain flickering

[Stuart]

The flickering does not happen if I bypass the Avocent SV340D KVM and
plug directly into the monitor. Any thoughts as to why this would
happen?

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

Title:
  DP1.2 daisy-chain flickering

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi all,

  I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04
  (uname -r = 4.15.0-15-generic). I have the NUC connected via USB-C to
  DisplayPort, to an Avocent SV340D KVM, then to a Dell U2415 which has
  DP1.2 enabled and is daisy-chainged to another Dell U2415 (DP1.2
  disabled on the second monitor as per Dell instructions).

  I am getting flickering whereby randomly display1 or display2 turn
  black and then back on again. When I disable DP1.2 on the display1,
  and therefore get a duplicate display (as opposed to extended) on
  display2, I get no flickering at all.

  The same setup yields no flickering when running from a Windows 10
  box, so don't think it is the monitors.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 14 12:52:24 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5927] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:2068]
  InstallationDate: Installed on 2018-04-01 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180401)
  MachineType: Intel Corporation NUC7i7BNH
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0062.2018.0222.1644
  dmi.board.name: NUC7i7BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J31145-307
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0062.2018.0222.1644:bd02/22/2018:svnIntelCorporation:pnNUC7i7BNH:pvrJ31153-308:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-307:cvnIntelCorporation:ct3:cvr2:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC7i7BNH
  dmi.product.version: J31153-308
  dmi.sys.vendor: Intel Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  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/1763975/+subscriptions

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

[Desktop-packages] [Bug 1763975] Re: DP1.2 daisy-chain flickering

[Stuart]

** Description changed:

  Hi all,
  
  I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04
  (uname -r = 4.15.0-15-generic). I have the NUC connected via USB-C to
- DisplayPort on a Dell U2414 which has DP1.2 enabled and is daisy-
- chainged to another Dell U2414 (DP1.2 disabled on the second monitor as
- per Dell instructions).
+ DisplayPort, to an Avocent SV340D KVM, then to a Dell U2415 which has
+ DP1.2 enabled and is daisy-chainged to another Dell U2415 (DP1.2
+ disabled on the second monitor as per Dell instructions).
  
  I am getting flickering whereby randomly display1 or display2 turn black
  and then back on again. When I disable DP1.2 on the display1, and
  therefore get a duplicate display (as opposed to extended) on display2,
  I get no flickering at all.
  
  The same setup yields no flickering when running from a Windows 10 box,
  so don't think it is the monitors.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 14 12:52:24 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation Device [8086:5927] (rev 06) (prog-if 00 [VGA controller])
-Subsystem: Intel Corporation Device [8086:2068]
+  Intel Corporation Device [8086:5927] (rev 06) (prog-if 00 [VGA controller])
+    Subsystem: Intel Corporation Device [8086:2068]
  InstallationDate: Installed on 2018-04-01 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180401)
  MachineType: Intel Corporation NUC7i7BNH
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0062.2018.0222.1644
  dmi.board.name: NUC7i7BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J31145-307
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0062.2018.0222.1644:bd02/22/2018:svnIntelCorporation:pnNUC7i7BNH:pvrJ31153-308:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-307:cvnIntelCorporation:ct3:cvr2:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC7i7BNH
  dmi.product.version: J31153-308
  dmi.sys.vendor: Intel Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  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

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

Title:
  DP1.2 daisy-chain flickering

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi all,

  I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04
  (uname -r = 4.15.0-15-generic). I have the NUC connected via USB-C to
  DisplayPort, to an Avocent SV340D KVM, then to a Dell U2415 which has
  DP1.2 enabled and is daisy-chainged to another Dell U2415 (DP1.2
  disabled on the second monitor as per Dell instructions).

  I am getting flickering whereby randomly display1 or display2 turn
  black and then back on again. When I disable DP1.2 on the display1,
  and therefore get a duplicate display (as opposed to extended) on
  display2, I get no flickering at all.

  The same setup yields no flickering when running from a Windows 10
  box, so don't think it is the monitors.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 14 12:52:24 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5927] (rev 06) 

[Desktop-packages] [Bug 1763975] [NEW] DP1.2 daisy-chain flickering

[Stuart]

Public bug reported:

Hi all,

I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04
(uname -r = 4.15.0-15-generic). I have the NUC connected via USB-C to
DisplayPort on a Dell U2414 which has DP1.2 enabled and is daisy-
chainged to another Dell U2414 (DP1.2 disabled on the second monitor as
per Dell instructions).

I am getting flickering whereby randomly display1 or display2 turn black
and then back on again. When I disable DP1.2 on the display1, and
therefore get a duplicate display (as opposed to extended) on display2,
I get no flickering at all.

The same setup yields no flickering when running from a Windows 10 box,
so don't think it is the monitors.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 14 12:52:24 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:5927] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device [8086:2068]
InstallationDate: Installed on 2018-04-01 (12 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180401)
MachineType: Intel Corporation NUC7i7BNH
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/22/2018
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BNKBL357.86A.0062.2018.0222.1644
dmi.board.name: NUC7i7BNB
dmi.board.vendor: Intel Corporation
dmi.board.version: J31145-307
dmi.chassis.type: 3
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0062.2018.0222.1644:bd02/22/2018:svnIntelCorporation:pnNUC7i7BNH:pvrJ31153-308:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-307:cvnIntelCorporation:ct3:cvr2:
dmi.product.family: Intel NUC
dmi.product.name: NUC7i7BNH
dmi.product.version: J31153-308
dmi.sys.vendor: Intel Corporation
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
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 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/1763975

Title:
  DP1.2 daisy-chain flickering

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi all,

  I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04
  (uname -r = 4.15.0-15-generic). I have the NUC connected via USB-C to
  DisplayPort on a Dell U2414 which has DP1.2 enabled and is daisy-
  chainged to another Dell U2414 (DP1.2 disabled on the second monitor
  as per Dell instructions).

  I am getting flickering whereby randomly display1 or display2 turn
  black and then back on again. When I disable DP1.2 on the display1,
  and therefore get a duplicate display (as opposed to extended) on
  display2, I get no flickering at all.

  The same setup yields no flickering when running from a Windows 10
  box, so don't think it is the monitors.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 14 12:52:24 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5927] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Device [8086:2068]
  InstallationDate: Installed on 2018-04-01 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180401)
  MachineType: Intel Corporation NUC7i7BNH
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 

[Desktop-packages] [Bug 1760849] Re: Enhancement: Make the login screen follow the mouse to other monitors

[Stuart Bishop]

https://bugzilla.gnome.org/show_bug.cgi?id=794971

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

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

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

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

Title:
  Enhancement: Make the login screen follow the mouse to other monitors

Status in gdm:
  Unknown
Status in gdm3 package in Ubuntu:
  New

Bug description:
  The Ubuntu login screen is tiled on all displays, not mirrored, making
  it nearly impossible to login when using an external monitor if the
  laptop screen is not visible.

  There appears to be no available control to alter the display settings
  of the login screen. Prior to bionic, the controls followed the mouse
  onto different displays so you could login by giving the mouse a swipe
  to the right to get the controls to appear.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 22:13:53 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.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/gdm/+bug/1760849/+subscriptions

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

[Desktop-packages] [Bug 1757321] Re: udisks2 must depend on libblockdev-crypto2 and libblockdev-mdraid2 instead of suggests [Can't mount encrypted USB drive after upgrade to bionic]

[Stuart Bishop]

This also affects the Live CD, where attempting to mount encrypted
volumes for testing or rescue purposes fails with this rather scary
error.

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

Title:
  udisks2 must depend on libblockdev-crypto2 and libblockdev-mdraid2
  instead of suggests [Can't mount encrypted USB drive after upgrade to
  bionic]

Status in udisks2 package in Ubuntu:
  Triaged

Bug description:
  after upgrading to bionic, attempts to mount an encrypted USB drive
  fail with the error "function bd_crypto_luks_open_blob called but not
  implemented"

  Installing libblockdev-crypto2 and libblockdev-crypto-dev and
  rebooting appears to have fixed it, but should that be necessary?  or
  at least better documented?
  (https://www.distrowatch.com/weekly.php?issue=20171113 is the only
  reference I could find on the error)

  [Workaround]
  1. Install libblockdev-crypto2
  2. Restart udisks:
$ systemctl restart udisks2

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udisks2 2.7.6-2ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  CustomUdevRuleFiles: 90-xhc_sleep.rules 70-snap.core.rules
  Date: Tue Mar 20 20:28:39 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-08-21 (942 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  MachineType: Apple Inc. MacBookPro11,4
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=1
  SourcePackage: udisks2
  UpgradeStatus: Upgraded to bionic on 2018-03-20 (0 days ago)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0172.B04.1506051511
  dmi.board.name: Mac-06F11FD93F0323C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,4
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11FD93F0323C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro11,4
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Desktop-packages] [Bug 1760849] [NEW] Unable to login unless primary display avaiable, not mirrored

[Stuart Bishop]

Public bug reported:

The Ubuntu login screen is tiled on all displays, not mirrored, making
it nearly impossible to login when using an external monitor if the
laptop screen is not visible.

There appears to be no available control to alter the display settings
of the login screen. Prior to bionic, the controls followed the mouse
onto different displays so you could login by giving the mouse a swipe
to the right to get the controls to appear.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdm3 3.28.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  3 22:13:53 2018
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Unable to login unless primary display avaiable, not mirrored

Status in gdm3 package in Ubuntu:
  New

Bug description:
  The Ubuntu login screen is tiled on all displays, not mirrored, making
  it nearly impossible to login when using an external monitor if the
  laptop screen is not visible.

  There appears to be no available control to alter the display settings
  of the login screen. Prior to bionic, the controls followed the mouse
  onto different displays so you could login by giving the mouse a swipe
  to the right to get the controls to appear.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 22:13:53 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.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/gdm3/+bug/1760849/+subscriptions

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

[Desktop-packages] [Bug 1758917] Re: Can see and interact with dock on lock screen

[Stuart]

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

@Daniel - thanks, again. I tried uninstalling and reinstalling both
gnome-shell-extension-ubuntu-dock and gnome-shell-extension-dashtodock.
Neither fixed it.

But rather, now, when I lock the screen, the screen turns black and
turns off and re-awakens on keyboard/mouse movement.

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

Title:
  Can see and interact with dock on lock screen

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

Bug description:
  When I lock my screen, or the session becomes locked due to
  inactivity, I can see and interact with the dock on the lock screen.

  I am able to launch applications, though I cannot see the applications
  or interact with them until I log in. But upon logging in, those
  applications are open.

  I am using the dash-to-dock extension.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-screensaver 3.6.1-8ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 26 09:44:25 2018
  InstallationDate: Installed on 2018-03-24 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: Upgraded to bionic on 2018-03-26 (0 days ago)

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

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

[Desktop-packages] [Bug 1758917] [NEW] Can see and interact with dock on lock screen

[Stuart]

Public bug reported:

When I lock my screen, or the session becomes locked due to inactivity,
I can see and interact with the dock on the lock screen.

I am able to launch applications, though I cannot see the applications
or interact with them until I log in. But upon logging in, those
applications are open.

I am using the dash-to-dock extension.

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-screensaver 3.6.1-8ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 26 09:44:25 2018
InstallationDate: Installed on 2018-03-24 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
SourcePackage: gnome-screensaver
Symptom: security
Title: Screen locking issue
UpgradeStatus: Upgraded to bionic on 2018-03-26 (0 days ago)

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


** Tags: amd64 apport-bug bionic third-party-packages

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

Title:
  Can see and interact with dock on lock screen

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  When I lock my screen, or the session becomes locked due to
  inactivity, I can see and interact with the dock on the lock screen.

  I am able to launch applications, though I cannot see the applications
  or interact with them until I log in. But upon logging in, those
  applications are open.

  I am using the dash-to-dock extension.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-screensaver 3.6.1-8ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 26 09:44:25 2018
  InstallationDate: Installed on 2018-03-24 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: Upgraded to bionic on 2018-03-26 (0 days ago)

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

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

[Desktop-packages] [Bug 1731911] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait()

[Stuart]

@Kir Kolyshkin - did trying the commits on the master branch of mutter
after 3.26 fix this?

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

Title:
  Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError() from xwl_read_events() from ospoll_wait()

Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid
Status in mutter package in Fedora:
  Fix Committed

Bug description:
  https://errors.ubuntu.com/problem/c27f5c4fef272640ec1027318712f0434c7c8857

  ---

  no idea how to reproduce

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Nov 13 13:55:16 2017
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-15-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:1507]
  InstallationDate: Installed on 2013-09-03 (1531 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -core -listen 4 
-listen 5 -displayfd 6
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/false
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   ?? ()
  Title: Xwayland crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1758706] Re: Session logs out after screen turns off

[Stuart]

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

xwayland crash log

** Attachment added: "_usr_bin_Xwayland.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1758706/+attachment/5090250/+files/_usr_bin_Xwayland.1000.crash

** Information type changed from Private Security to Public

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

Title:
  Session logs out after screen turns off

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This is the same bug as #1721428

  :/var/crash$ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  I am using a NUC7i7BNH connected via HDMI. The screen turns off after
  5 minutes of inactivity and automatic screen lock is also turned on to
  lock the screen after screen turns off.

  When I resume activity, I am presented with the logon screen, which
  after entering my password, reloads another logon screen. When I then
  enter my password the second time, I am logged in, but it is a new
  session.

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

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

[Desktop-packages] [Bug 1758706] [NEW] Session logs out after screen turns off

[Stuart]

Public bug reported:

This is the same bug as #1721428

:/var/crash$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10

I am using a NUC7i7BNH connected via HDMI. The screen turns off after 5
minutes of inactivity and automatic screen lock is also turned on to
lock the screen after screen turns off.

When I resume activity, I am presented with the logon screen, which
after entering my password, reloads another logon screen. When I then
enter my password the second time, I am logged in, but it is a new
session.

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

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

Title:
  Session logs out after screen turns off

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This is the same bug as #1721428

  :/var/crash$ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  I am using a NUC7i7BNH connected via HDMI. The screen turns off after
  5 minutes of inactivity and automatic screen lock is also turned on to
  lock the screen after screen turns off.

  When I resume activity, I am presented with the logon screen, which
  after entering my password, reloads another logon screen. When I then
  enter my password the second time, I am logged in, but it is a new
  session.

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

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

[Desktop-packages] [Bug 1721428] Re: Artful (17.10) Session logout after screen turned off

[Stuart]

@Daniel

Why was this bug closed? @matt.mahin suggestion doesn't seem to fix
this.

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

Title:
  Artful (17.10) Session logout after screen turned off

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  Whenever I turn off my screen, the computer (a desktop PC) logs me out
  of my session.

  Here is a discussion thread with users of similar issue:
  
https://ubuntuforums.org/showthread.php?t=2372388=13694312=1#post13694312

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

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

[Desktop-packages] [Bug 1677202] Re: Sound playback delays

[Stuart Langridge]

Yup; wired audio, on a normal 3.5mm jack headphone cable (not HDMI or
similar).

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

Title:
  Sound playback delays

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Sound playback on my machine seems to be delayed. Playing an error
  beep hangs for half a second or so before playing, making tab
  completion extremely irritating (because the completion itself also
  hangs); starting a video or music track is silent for the first second
  or so. This seems to be fixed, as per
  http://askubuntu.com/questions/218444/sound-output-starts-
  delayed/440787#440787, by disabling pulseaudio's "module-suspend-on-
  idle" feature. I don't need this feature at all because my machine is
  a desktop box without a battery, permanently plugged into power, and
  therefore any minimal power saving it produces is far outweighed by
  the annoyance. However, since other people don't experience this
  problem, perhaps it's chipset specific? I also experience Audacity
  taking a long time to start up, which also seems to have been helped
  by this fix.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.2
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Mar 29 11:56:24 2017
  InstallationDate: Installed on 2014-04-07 (1087 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (237 days ago)
  dmi.bios.date: 12/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1707
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: PCS
  dmi.chassis.type: 3
  dmi.chassis.vendor: PC SPECIALIST
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1707:bd12/13/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-A:rvrRev1.xx:cvnPCSPECIALIST:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2017-03-29T11:51:11.884294

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

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

[Desktop-packages] [Bug 1723857] Re: onscreen keyboard appears whenever i touch touchscreen

[Stuart Gillies]

It's a simple problem. Fix it please otherwise I will have to go back to
17.04

It pops up every time I type in this box, and obscures the box.

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

Title:
  onscreen keyboard appears whenever i touch touchscreen

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

Bug description:
  Impact
  ==
  I'm in 17.10. Whenever I touch the touchscreen, the keyboard appears. It is 
disabled in System Preferences > Universal Access.  This didn't happen in any 
previous Ubuntus, including 17.04 GNOME, nor in Fedora, which is GNOME based.

  Test Case
  =
  0. Find a laptop with a touch screen that works.
  1. Settings > Universal Access > Typing > Screen Keyboard = OFF
  2. Touch the screen.

  Regression Potential
  

  Workaround
  ==
  https://extensions.gnome.org/extension/1326/block-caribou/

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

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

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

[Stuart Smith]

Looks like this...
https://bugzilla.gnome.org/show_bug.cgi?id=783853

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

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

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

Status in gnome-shell package in Ubuntu:
  Confirmed

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

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

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

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

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

  Not observed on my Wayland system.

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

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

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

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

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

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

[Stuart Smith]

This issue is occurring for me too with amdgpu. I experience the same
problem under both Xorg and Wayland sessions. This is only an issue with
my monitor connected via DisplayPort - when I connect via HDMI gnome-
shell does not crash if the monitor goes to sleep.

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

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

Status in gnome-shell package in Ubuntu:
  Confirmed

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

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

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

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

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

  Not observed on my Wayland system.

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

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

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

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

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

[Desktop-packages] [Bug 1697920] [NEW] Gnome Software front end showed spinner on all actions; had to kill service process to fix

[Stuart Langridge]

Public bug reported:

When opening Gnome Software, the front screen worked fine for me
(showing the featured app, editor's picks and so on) but taking any
action (clicking a different tab, or clicking an application, or doing a
search) showed an empty window with a spinner. There was a long-running
"/usr/bin/gnome-software --gapplication-service" process running;
killing that process and then starting Gnome Software made everything
work again (and updated the featured app to be the current one).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-software 3.20.1+git20170208.0.a34b091-0ubuntu1~xenial1
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Jun 14 12:38:50 2017
InstallationDate: Installed on 2014-04-07 (1164 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: gnome-software
UpgradeStatus: Upgraded to xenial on 2016-08-04 (314 days ago)

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


** Tags: amd64 apport-bug third-party-packages xenial

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

Title:
  Gnome Software front end showed spinner on all actions; had to kill
  service process to fix

Status in gnome-software package in Ubuntu:
  New

Bug description:
  When opening Gnome Software, the front screen worked fine for me
  (showing the featured app, editor's picks and so on) but taking any
  action (clicking a different tab, or clicking an application, or doing
  a search) showed an empty window with a spinner. There was a long-
  running "/usr/bin/gnome-software --gapplication-service" process
  running; killing that process and then starting Gnome Software made
  everything work again (and updated the featured app to be the current
  one).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.1+git20170208.0.a34b091-0ubuntu1~xenial1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jun 14 12:38:50 2017
  InstallationDate: Installed on 2014-04-07 (1164 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (314 days ago)

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

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

[Desktop-packages] [Bug 1677202] [NEW] Sound playback delays

[Stuart Langridge]

Public bug reported:

Sound playback on my machine seems to be delayed. Playing an error beep
hangs for half a second or so before playing, making tab completion
extremely irritating (because the completion itself also hangs);
starting a video or music track is silent for the first second or so.
This seems to be fixed, as per http://askubuntu.com/questions/218444
/sound-output-starts-delayed/440787#440787, by disabling pulseaudio's
"module-suspend-on-idle" feature. I don't need this feature at all
because my machine is a desktop box without a battery, permanently
plugged into power, and therefore any minimal power saving it produces
is far outweighed by the annoyance. However, since other people don't
experience this problem, perhaps it's chipset specific? I also
experience Audacity taking a long time to start up, which also seems to
have been helped by this fix.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3.2
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Mar 29 11:56:24 2017
InstallationDate: Installed on 2014-04-07 (1087 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to xenial on 2016-08-04 (237 days ago)
dmi.bios.date: 12/13/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1707
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z87-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: PCS
dmi.chassis.type: 3
dmi.chassis.vendor: PC SPECIALIST
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1707:bd12/13/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-A:rvrRev1.xx:cvnPCSPECIALIST:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2017-03-29T11:51:11.884294

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


** Tags: amd64 apport-bug third-party-packages xenial

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

Title:
  Sound playback delays

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Sound playback on my machine seems to be delayed. Playing an error
  beep hangs for half a second or so before playing, making tab
  completion extremely irritating (because the completion itself also
  hangs); starting a video or music track is silent for the first second
  or so. This seems to be fixed, as per
  http://askubuntu.com/questions/218444/sound-output-starts-
  delayed/440787#440787, by disabling pulseaudio's "module-suspend-on-
  idle" feature. I don't need this feature at all because my machine is
  a desktop box without a battery, permanently plugged into power, and
  therefore any minimal power saving it produces is far outweighed by
  the annoyance. However, since other people don't experience this
  problem, perhaps it's chipset specific? I also experience Audacity
  taking a long time to start up, which also seems to have been helped
  by this fix.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.2
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Mar 29 11:56:24 2017
  InstallationDate: Installed on 2014-04-07 (1087 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (237 days ago)
  dmi.bios.date: 12/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1707
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: PCS
  dmi.chassis.type: 3
  dmi.chassis.vendor: PC SPECIALIST
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1707:bd12/13/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-A:rvrRev1.xx:cvnPCSPECIALIST:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2017-03-29T11:51:11.884294

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

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

[Desktop-packages] [Bug 1442649] Re: nautilus trash doesn't include btrfs and zfs subvolumes

[Stuart Bishop]

Work around is to use the trash-cli package and empty trash from the
command line.

Upstream fixes in nautilus seems stalled, per
https://bugzilla.gnome.org/show_bug.cgi?id=604015 , with no comments
from maintainers for the several months that patches have been
available.

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

Title:
  nautilus trash doesn't include btrfs and zfs subvolumes

Status in GLib:
  Incomplete
Status in glib2.0 package in Ubuntu:
  Triaged
Status in gvfs package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Files in `/path/to/subvolume/.Trash-1000` aren't listed in the global
  trash.

  Comment by bug triage team: comment 4 has a spot-on analysis of where
  this issue is coming from, an inconsistency between trash handling in
  gvfs and glib/gio.  The problem has been around for quite a while.

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

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

[Desktop-packages] [Bug 1660855] [NEW] Can't start gnome-software to show a particular snap package

[Stuart Langridge]

Public bug reported:

I'd like to be able to launch gnome-software showing the details page
for a particular snap. I can do this for packages from the Ubuntu
archive (gnome-software --details-pkg=inkscape works fine, for example),
and gnome-software _supports_ snaps: if I search for ohmygiraffe in
gnome-software it finds that snap package no problem. But "gnome-
software --details-pkg=ohmygiraffe" does not work, and there seems to be
no equivalent option for snaps. I can pass --search=ohmygiraffe but that
shows search results with one matching result, not the actual install
screen for the snap.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-software 3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jan 31 23:52:58 2017
InstallationDate: Installed on 2014-04-07 (1030 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: gnome-software
UpgradeStatus: Upgraded to xenial on 2016-08-04 (180 days ago)

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


** Tags: amd64 apport-bug third-party-packages xenial

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

Title:
  Can't start gnome-software to show a particular snap package

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I'd like to be able to launch gnome-software showing the details page
  for a particular snap. I can do this for packages from the Ubuntu
  archive (gnome-software --details-pkg=inkscape works fine, for
  example), and gnome-software _supports_ snaps: if I search for
  ohmygiraffe in gnome-software it finds that snap package no problem.
  But "gnome-software --details-pkg=ohmygiraffe" does not work, and
  there seems to be no equivalent option for snaps. I can pass
  --search=ohmygiraffe but that shows search results with one matching
  result, not the actual install screen for the snap.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 31 23:52:58 2017
  InstallationDate: Installed on 2014-04-07 (1030 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (180 days ago)

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

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

Re: [Desktop-packages] [Bug 1451728] Re: [master] kde-config-telepathy-accounts package install error

[Asa-Jane Stuart-Campbell]

Nei Bernd, skriv norsk da.

Or English, so everyone can understand without google translate.

2017-01-27 23:27 GMT+01:00 Bernd :

> bitte deutsch schreiben
>
>
> Am 27.01.2017 um 14:15 schrieb malvonni:
> > Thanks!
> >
> > Em sex, 27 de jan de 2017 11:11, Bernd  escreveu:
> >
> >> bitte deutsch schreiben
> >>
> >>
> >>
> >> Am 26.01.2017 um 19:36 schrieb N H:
> >>> I have experienced this problem as well, while adding KDE to the
> desktop
> >>> environments on my copy of Ubuntu. As I like XFCE for most things, but
> >>> decided to see how recent versions of KDE look. During installation,
> the
> >>> KDE accounts config package kept trying to overwrite files provides by
> >>> other packages. Apt-get install -f did not do it's job, and threw the
> >>> same errors. I eventually just grabbed the .deb files using pkgs.org
> and
> >>> installed them with dpkg --force-all. This resulted in all sorts of
> file
> >>> conflicts, which as I used the --force-all option, it overrided and
> >>> installed anyway. KDE seems to be working normally. If I need to, I
> will
> >>> reinstalled the package that got overwritten, once again with the
> >>> --force-all option to make sure it does it's job. However is packaging
> >>> those two packages, need to decided who provides what, or move the
> >>> configs off to a third package that they both could depend on instead
> of
> >>> conflicting.
> >>>
> >> --
> >> You received this bug notification because you are subscribed to a
> >> duplicate bug report (1572183).
> >> https://bugs.launchpad.net/bugs/1451728
> >>
> >> Title:
> >>[master] kde-config-telepathy-accounts package install error
> >>
> >> Status in Kubuntu PPA:
> >>Fix Released
> >> Status in Telepathy KDE:
> >>Fix Released
> >> Status in kaccounts-integration package in Ubuntu:
> >>In Progress
> >> Status in kaccounts-providers package in Ubuntu:
> >>Triaged
> >> Status in ktp-accounts-kcm package in Ubuntu:
> >>Triaged
> >> Status in libaccounts-glib package in Ubuntu:
> >>Fix Released
> >> Status in kaccounts-providers source package in Wily:
> >>Triaged
> >> Status in ktp-accounts-kcm source package in Wily:
> >>Triaged
> >>
> >> Bug description:
> >>Installing from Kubuntu 15.04 backports:
> >>
> >>Unpacking kde-config-telepathy-accounts
> >> (15.04.0-0ubuntu1~ubuntu15.04~ppa1) over (0.9.0-0ubuntu1) ...
> >>dpkg: error processing archive
> >> /var/cache/apt/archives/kde-config-telepathy-accounts_15.
> 04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
> >> (--unpack):
> >> trying to overwrite '/usr/share/accounts/services/
> facebook-im.service',
> >> which is also in package account-plugin-facebook
> >> 0.12+15.04.20150415.1-0ubuntu1
> >>dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
> >>
> >>SRU information
> >>===
> >>
> >>[Impact] It's not possible to install KDE and Unity in co-existence
> >>because of several file conflicts: many files under
> >>/usr/share/accounts/{providers,services}/ are provided by both the
> >>package "kaccounts-providers" and packages build from the "account-
> >>plugins" source package, for example 'account-plugin-facebook'.
> >>
> >>[Test case] Install both kaccounts-providers and
> >> account-plugin-facebook: you'll get file conflicts for
> >> /usr/share/accounts/services/facebook-im.service and
> >> /usr/share/accounts/providers/facebook.provider.
> >>You might get other conflicts as well, but those are due to bug
> 1565772
> >> (also nominated for SRU).
> >>
> >>[Regression potential] Minimal: the changed packages belong to the
> >>default KDE installation, and have already landed in Yakkety. Things
> >>appear to be working fine there: account creation is still possible
> >>under KDE, even after changing the file paths as per this fix.
> >>
> >> To manage notifications about this bug go to:
> >> https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+subscriptions
> >>
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1628428).
> https://bugs.launchpad.net/bugs/1451728
>
> Title:
>   [master] kde-config-telepathy-accounts package install error
>
> Status in Kubuntu PPA:
>   Fix Released
> Status in Telepathy KDE:
>   Fix Released
> Status in kaccounts-integration package in Ubuntu:
>   In Progress
> Status in kaccounts-providers package in Ubuntu:
>   Triaged
> Status in ktp-accounts-kcm package in Ubuntu:
>   Triaged
> Status in libaccounts-glib package in Ubuntu:
>   Fix Released
> Status in kaccounts-providers source package in Wily:
>   Triaged
> Status in ktp-accounts-kcm source package in Wily:
>   Triaged
>
> Bug description:
>   Installing from Kubuntu 15.04 backports:
>
>   Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1)
> over (0.9.0-0ubuntu1) ...
>   dpkg: error processing archive /var/cache/apt/archives/kde-
> 

[Desktop-packages] [Bug 1641414] [NEW] ERR_INSECURE_RESPONSE because of BUILD_NOT_TIMELY on many SSL certs which are public

[Stuart Langridge]

Public bug reported:

Bug filed upstream at
https://bugs.chromium.org/p/chromium/issues/detail?id=664798# -- added
here in case the issue is to do with Ubuntu packaging of chromium rather
than an upstream bug.

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML,
like Gecko) Ubuntu Chromium/53.0.2785.143 Chrome/53.0.2785.143
Safari/537.36

Example URL:
https://ir.ebaystatic.com/rtm/3/RTMS/Image/9739_UK_Retail_Q2_RefurbishedTechHub_BREC_300x130.jpg

Steps to reproduce the problem:
1. Visit 
https://ir.ebaystatic.com/rtm/3/RTMS/Image/9739_UK_Retail_Q2_RefurbishedTechHub_BREC_300x130.jpg
2. Observe the Chromium "Your connection is not private" window is shown; under 
advanced, it says "The server presented a certificate that was not publicly 
disclosed using the Certificate Transparency policy. This is a requirement for 
some certificates, to ensure that they are trustworthy and protect against 
attackers."

What is the expected behavior?
The image is displayed

What went wrong?
chrome://net-internals for this request shows:
CERT_CT_COMPLIANCE_CHECKED
build_timely = false
certificate = (snip)
ct_compliance_status = "BUILD_NOT_TIMELY"

The cert for this page seems to be publicly transparent: see
https://crt.sh/?q=8E+31+45+71+77+40+9F+31+FC+CE+26+09+25+8B+E7+26+8E+A2+3C+9F+D3+77+80+A2+5B+10+3E+A4+68+DD+32+E1

Did this work before? Yes don't know; recently

Chrome version: 53.0.2785.143  Channel: stable
OS Version: Ubuntu 16.04
Flash Version: Shockwave Flash 22.0 r0

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: chromium-browser 53.0.2785.143-0ubuntu0.16.04.1.1254
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
DRM.card0-DP-1:
 edid-base64: 
 dpms: Off
 modes: 
 enabled: disabled
 status: disconnected
DRM.card0-HDMI-A-1:
 edid-base64: 
 dpms: Off
 modes: 
 enabled: disabled
 status: disconnected
DRM.card0-HDMI-A-2:
 edid-base64: 
 dpms: Off
 modes: 
 enabled: disabled
 status: disconnected
DRM.card0-HDMI-A-3:
 edid-base64: 
AP///wAEaaMnMvwCAC8XAQOAPCJ4KqWVqlRPoSYKUFS37wDRwLMAlQCBgIFAgQCBwHFPVl4AoKCgKVAwIDUAVVAhAAAa/wBEQkxNVEYxOTU2MzQK/QAYTBhjIQAKICAgICAg/ABBU1VTIFBCMjc4CiAgAQkCAyVxUgECAxESEwQUBQ4PHR4fkCAhIiMJFweDAQAAZQMMABAAjArQiiDgLRAQPpYAVVAhAAAYAR0AclHQHiBuKFUAVVAhAAAeAR0AvFLQHiC4KFVAVVAhAAAejArQkCBAMSAMQFUAVVAhAAAYmA==
 dpms: On
 modes: 2560x1440 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 
1920x1080i 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 1680x1050 
1280x1024 1280x1024 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 
1280x720 1440x576 1024x768 1024x768 1024x768 1440x480 1440x480 832x624 800x600 
800x600 800x600 800x600 720x576 720x480 720x480 640x480 640x480 640x480 640x480 
720x400
 enabled: enabled
 status: connected
DRM.card0-VGA-1:
 edid-base64: 
 dpms: Off
 modes: 
 enabled: disabled
 status: disconnected
Date: Sun Nov 13 14:43:20 2016
Desktop-Session:
 'ubuntu'
 '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg'
 
'/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
Env:
 'None'
 'None'
InstallationDate: Installed on 2014-04-07 (951 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
Load-Avg-1min: 1.54
Load-Processes-Running-Percent:   0.1%
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed 
root=UUID=ad1b3110-ee9a-4dac-839d-604080e0020d ro quiet splash vt.handoff=7
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to xenial on 2016-08-04 (101 days ago)
dmi.bios.date: 12/13/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1707
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z87-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: PCS
dmi.chassis.type: 3
dmi.chassis.vendor: PC SPECIALIST
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1707:bd12/13/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-A:rvrRev1.xx:cvnPCSPECIALIST:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
etcconfigcpepperflashpluginnonfree:
 flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
 flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed 
-e "s/,/./g"`
 CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 

[Desktop-packages] [Bug 1626494] Re: Some app screenshots wrongly stretched in Ubuntu version of Gnome Software

[Stuart Langridge]

** Attachment added: "Upstream Gnome Software showing letterboxed screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1626494/+attachment/4746166/+files/67FdM8Wid.png

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

Title:
  Some app screenshots wrongly stretched in Ubuntu version of Gnome
  Software

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Looking at Thunar in Gnome Software, the Ubuntu version of GS
  stretches the screenshot, making it look ugly. Upstream apparently
  doesn't do this and uses grey letterboxing. (See attached
  screenshots.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 22 12:02:12 2016
  InstallationDate: Installed on 2014-04-07 (899 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (49 days ago)

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

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

[Desktop-packages] [Bug 1626494] [NEW] Some app screenshots wrongly stretched in Ubuntu version of Gnome Software

[Stuart Langridge]

Public bug reported:

Looking at Thunar in Gnome Software, the Ubuntu version of GS stretches
the screenshot, making it look ugly. Upstream apparently doesn't do this
and uses grey letterboxing. (See attached screenshots.)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Sep 22 12:02:12 2016
InstallationDate: Installed on 2014-04-07 (899 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: gnome-software
UpgradeStatus: Upgraded to xenial on 2016-08-04 (49 days ago)

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


** Tags: amd64 apport-bug third-party-packages xenial

** Attachment added: "Ubuntu software showing Thunar with stretched screenshot"
   
https://bugs.launchpad.net/bugs/1626494/+attachment/4746161/+files/Screenshot%20from%202016-09-22%2011-00-48.png

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

Title:
  Some app screenshots wrongly stretched in Ubuntu version of Gnome
  Software

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Looking at Thunar in Gnome Software, the Ubuntu version of GS
  stretches the screenshot, making it look ugly. Upstream apparently
  doesn't do this and uses grey letterboxing. (See attached
  screenshots.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 22 12:02:12 2016
  InstallationDate: Installed on 2014-04-07 (899 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (49 days ago)

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

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

[Desktop-packages] [Bug 1603898] Re: DNS resolution fails when using VPN and routing all traffic over it

[Stuart Bishop]

I see this with IPv6 disabled completely on the laptop:

$ cat /etc/sysctl.d/99-noipv6.conf 
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1

I can confirm that both ipv4 and ipv6 settings have both 'Use this
connection only for resources on its network' and 'Ignore automatically
obtained routes' disabled, and when I try connecting the ipv6 method is
'ignore'.

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

Title:
  DNS resolution fails when using VPN and routing all traffic over it

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Xenial:
  Confirmed

Bug description:
  When using our company VPN, the Network Manager configured dnsmasq
  ends up in a weird state where its unable to answer queries because
  it's (incorrectly) sending them to 127.0.0.1:53 where nothing is
  listening.

  | root@ornery:~# nmcli con show 'Canonical UK - All Traffic' | grep -i dns
  | ipv4.dns:
  | ipv4.dns-search:
  | ipv4.dns-options:   (default)
  | ipv4.ignore-auto-dns:   no
  | ipv6.dns:
  | ipv6.dns-search:
  | ipv6.dns-options:   (default)
  | ipv6.ignore-auto-dns:   no
  | IP4.DNS[1]: 10.172.192.1
  | root@ornery:~# ps auxfw | grep [4]035
  | nobody4035  0.0  0.0  52872  1620 ?SJun29   6:39  \_ 
/usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces 
--pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 
--cache-size=0 --proxy-dnssec 
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq 
--conf-dir=/etc/NetworkManager/dnsmasq.d
  | root@ornery:~# 

  Querying the DNS server provided by the VPN connection works; querying
  dnsmasq doesn't:

  | root@ornery:~# dig +short @10.172.192.1 www.openbsd.org
  | 129.128.5.194
  | root@ornery:~# dig @127.0.1.1 www.openbsd.org
  | 
  | ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @127.0.1.1 www.openbsd.org
  | ; (1 server found)
  | ;; global options: +cmd
  | ;; Got answer:
  | ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 6996
  | ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
  | 
  | ;; QUESTION SECTION:
  | ;www.openbsd.org.   IN  A
  | 
  | ;; Query time: 0 msec
  | ;; SERVER: 127.0.1.1#53(127.0.1.1)
  | ;; WHEN: Mon Jul 18 10:25:48 CEST 2016
  | ;; MSG SIZE  rcvd: 33
  | 
  | root@ornery:~# 

  While running 'dig @127.0.1.1 www.openbsd.org':

  | root@ornery:~# tcpdump -i lo port 53 -v -n
  | tcpdump: listening on lo, link-type EN10MB (Ethernet), capture size 262144 
bytes
  | 10:26:04.728905 IP (tos 0x0, ttl 64, id 56577, offset 0, flags [none], 
proto UDP (17), length 72)
  | 127.0.0.1.54917 > 127.0.1.1.53: 32273+ [1au] A? www.openbsd.org. (44)
  | 10:26:04.729001 IP (tos 0x0, ttl 64, id 49204, offset 0, flags [DF], proto 
UDP (17), length 61)
  | 127.0.1.1.53 > 127.0.0.1.54917: 32273 Refused$ 0/0/0 (33)

  | root@ornery:~# netstat -anp | grep 127.0.[01].1:53
  | tcp0  0 127.0.1.1:530.0.0.0:*   LISTEN  
4035/dnsmasq
  | udp0  0 127.0.1.1:530.0.0.0:*   
4035/dnsmasq
  | root@ornery:~# 

  You can see below a) that dnsmasq thinks it is configured to use a DNS
  server provided by the VPN, and/but that b) it tries to answer a non
  local query like www.openbsd.org locally.

  | root@ornery:~# kill -USR1 4035; tail /var/log/syslog | grep dnsmasq
  | Jul 18 09:29:22 ornery dnsmasq[4035]: time 1468830562
  | Jul 18 09:29:22 ornery dnsmasq[4035]: cache size 0, 0/0 cache insertions 
re-used unexpired cache entries.
  | Jul 18 09:29:22 ornery dnsmasq[4035]: queries forwarded 1880976, queries 
answered locally 375041
  | Jul 18 09:29:22 ornery dnsmasq[4035]: queries for authoritative zones 0
  | Jul 18 09:29:22 ornery dnsmasq[4035]: server 10.172.192.1#53: queries sent 
792, retried or failed 0
  | root@ornery:~# dig +short @127.0.1.1 www.openbsd.org
  | root@ornery:~# kill -USR1 4035; tail /var/log/syslog | grep dnsmasq
  | Jul 18 09:29:22 ornery dnsmasq[4035]: queries for authoritative zones 0
  | Jul 18 09:29:22 ornery dnsmasq[4035]: server 10.172.192.1#53: queries sent 
792, retried or failed 0
  | Jul 18 09:29:37 ornery dnsmasq[4035]: time 1468830577
  | Jul 18 09:29:37 ornery dnsmasq[4035]: cache size 0, 0/0 cache insertions 
re-used unexpired cache entries.
  | Jul 18 09:29:37 ornery dnsmasq[4035]: queries forwarded 1880976, queries 
answered locally 375042
  | Jul 18 09:29:37 ornery dnsmasq[4035]: queries for authoritative zones 0
  | Jul 18 09:29:37 ornery dnsmasq[4035]: server 10.172.192.1#53: queries sent 
792, retried or failed 0
  | root@ornery:~# 

  This is on Ubuntu 16.04, with the following packages:

  | james@ornery:~$ 

[Desktop-packages] [Bug 1581782] Re: Printed filed are incomplete (missing all text, some images) in evince but not flpsed

[Stuart Langridge]

** Attachment added: "Pictures of failing and successful print of same PDF"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1581782/+attachment/4662788/+files/IMG_20160514_104358.jpg

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

Title:
  Printed filed are incomplete (missing all text, some images) in evince
  but not flpsed

Status in evince package in Ubuntu:
  New

Bug description:
  When I try to print PDFs from evince, the resulting printed page
  contains only the first header image (if any) of the PDF and none of
  the other images or text.

  Additional information:

  1. printing text from other non-PDF applications, such as LibreOffice Writer, 
works fine
  2. printing the same PDF from flpsed works fine
  3. printing the same PDF from xournal shows the same problem

  This suggests that the issue is not specific to evince but is
  something lower-level, but I don't know which lower-level component
  would be the problem.

  Since printing works fine from some places I don't believe this is a
  printer problem, but if it helps my printer is a networked Kyocera
  Mita FS-1010. I have tried using both the "Kyocera FS-1020
  Foomatic/Postscript [en]" driver and the "recommended" "Kyocera Mita
  FS-1010 [en]" driver and the same problem is evident.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu10.2
  ProcVersionSignature: Ubuntu 3.13.0-86.130-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-86-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat May 14 10:39:09 2016
  InstallationDate: Installed on 2014-04-07 (768 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: evince
  UpgradeStatus: Upgraded to trusty on 2014-04-25 (749 days ago)

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

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

[Desktop-packages] [Bug 1581782] [NEW] Printed filed are incomplete (missing all text, some images) in evince but not flpsed

[Stuart Langridge]

Public bug reported:

When I try to print PDFs from evince, the resulting printed page
contains only the first header image (if any) of the PDF and none of the
other images or text.

Additional information:

1. printing text from other non-PDF applications, such as LibreOffice Writer, 
works fine
2. printing the same PDF from flpsed works fine
3. printing the same PDF from xournal shows the same problem

This suggests that the issue is not specific to evince but is something
lower-level, but I don't know which lower-level component would be the
problem.

Since printing works fine from some places I don't believe this is a
printer problem, but if it helps my printer is a networked Kyocera Mita
FS-1010. I have tried using both the "Kyocera FS-1020
Foomatic/Postscript [en]" driver and the "recommended" "Kyocera Mita
FS-1010 [en]" driver and the same problem is evident.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: evince 3.10.3-0ubuntu10.2
ProcVersionSignature: Ubuntu 3.13.0-86.130-generic 3.13.11-ckt39
Uname: Linux 3.13.0-86-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CurrentDesktop: Unity
Date: Sat May 14 10:39:09 2016
InstallationDate: Installed on 2014-04-07 (768 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: evince
UpgradeStatus: Upgraded to trusty on 2014-04-25 (749 days ago)

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


** Tags: amd64 apport-bug trusty

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

Title:
  Printed filed are incomplete (missing all text, some images) in evince
  but not flpsed

Status in evince package in Ubuntu:
  New

Bug description:
  When I try to print PDFs from evince, the resulting printed page
  contains only the first header image (if any) of the PDF and none of
  the other images or text.

  Additional information:

  1. printing text from other non-PDF applications, such as LibreOffice Writer, 
works fine
  2. printing the same PDF from flpsed works fine
  3. printing the same PDF from xournal shows the same problem

  This suggests that the issue is not specific to evince but is
  something lower-level, but I don't know which lower-level component
  would be the problem.

  Since printing works fine from some places I don't believe this is a
  printer problem, but if it helps my printer is a networked Kyocera
  Mita FS-1010. I have tried using both the "Kyocera FS-1020
  Foomatic/Postscript [en]" driver and the "recommended" "Kyocera Mita
  FS-1010 [en]" driver and the same problem is evident.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu10.2
  ProcVersionSignature: Ubuntu 3.13.0-86.130-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-86-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat May 14 10:39:09 2016
  InstallationDate: Installed on 2014-04-07 (768 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: evince
  UpgradeStatus: Upgraded to trusty on 2014-04-25 (749 days ago)

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

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

[Desktop-packages] [Bug 1434986] Re: Not working network connection after boot

[Stuart Gillies]

I'm using the latest 16.04 beta, up to date. When I reboot, the wifi
does not work, I think because it is not detected. When I replug the
little USB wifi thingy, it then does work, though the signal strength
indication is very low (no bars) even though another device alongside is
seeing full strength.  The usb thing worked fine on 14.04. So hotplug
sort-of works but not at reboot time.

I also find that every second reboot the display just shows me a small
white shape, approx a 2cm square but irregular.  Fixed by a further
reboot.

Sorry if this should go some where else, I could not find where so
perhaps the moderator could move it?

thanks

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

Title:
  Not working network connection after boot

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Directly after boot the network connections are not working. I am
  connected and have an IP address, but I cannot establish a connection
  with any Internet server.

  I have the impression it is related to thee DNS lookup, which waits
  forever for a result.

  Cycling the connection (disconnect->reconnect) seems to fix the
  problem for some time.

  I am reporting this against network-manager, but I am not sure if it is 
directly in network manager or if it is systemd related.
  With 14.10 everything worked perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 22 12:38:26 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-30 (50 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.26 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.29
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-02-16T00:14:50.662693
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Kabelnetzwerkverbindung 1  4a581685-6002-4401-a993-49aa649667eb  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   wlan0   wifi  connected  /org/freedesktop/NetworkManager/Devices/1  
4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1085706] Re: pam_ecryptfs: seteuid error

[Stuart]

when blueproximity issues a gnome-screensaver-command -d to unlock the
screen

Mar 10 12:54:55 T420 blueproximity[10821]: screen is unlocked
Mar 10 12:54:55 T420 compiz: pam_ecryptfs: seteuid error

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

Title:
  pam_ecryptfs: seteuid error

Status in eCryptfs:
  Confirmed
Status in GNOME Screensaver:
  New
Status in ecryptfs-utils package in Ubuntu:
  Triaged
Status in gnome-screensaver package in Ubuntu:
  Triaged
Status in plasma-workspace package in Ubuntu:
  Confirmed
Status in gnome-screensaver package in Debian:
  New

Bug description:
  I get this error message in the syslog when I authenticate succesfully
  in the screensaver.

  ---
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  DistroRelease: Ubuntu 12.10
  EcryptfsInUse: Yes
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 600
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationDate: Installed on 2012-06-13 (172 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  Package: gnome-screensaver 3.6.0-0ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
  Tags:  quantal running-unity
  Uname: Linux 3.5.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1555396] [NEW] prolems since installing XFCE

[Jan Stuart Bogusz]

Public bug reported:

Moved from 13 install to 14.04 with x package launching gone wrong  jre
and cant get on wifi since also virgin renewed braodband to their
wireless

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-81.125-generic 3.13.11-ckt35
Uname: Linux 3.13.0-81-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Mar 10 00:40:25 2016
DistUpgraded: 2015-03-20 21:21:55,400 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Sony Corporation Device [104d:9045]
   Subsystem: Sony Corporation Device [104d:9045]
InstallationDate: Installed on 2013-11-04 (856 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
MachineType: Sony Corporation VGN-NS30E_S
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-81-generic 
root=UUID=ed93e881-2d1e-4946-be4b-ea65464345b4 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2015-03-20 (355 days ago)
dmi.bios.date: 08/26/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R2030Y3
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR2030Y3:bd08/26/2009:svnSonyCorporation:pnVGN-NS30E_S:pvrC601HGS5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VGN-NS30E_S
dmi.product.version: C601HGS5
dmi.sys.vendor: Sony Corporation
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Wed Mar  9 20:42:49 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.1-0ubuntu2.7

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


** Tags: apport-bug i386 trusty 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/1555396

Title:
  prolems since installing XFCE

Status in xorg package in Ubuntu:
  New

Bug description:
  Moved from 13 install to 14.04 with x package launching gone wrong
  jre  and cant get on wifi since also virgin renewed braodband to their
  wireless

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-81.125-generic 3.13.11-ckt35
  Uname: Linux 3.13.0-81-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Mar 10 00:40:25 2016
  DistUpgraded: 2015-03-20 21:21:55,400 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Device [104d:9045]
 Subsystem: Sony Corporation Device [104d:9045]
  InstallationDate: Installed on 2013-11-04 (856 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MachineType: Sony Corporation VGN-NS30E_S
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-81-generic 
root=UUID=ed93e881-2d1e-4946-be4b-ea65464345b4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2015-03-20 (355 days ago)
  dmi.bios.date: 08/26/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R2030Y3
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  

[Desktop-packages] [Bug 1382774] Re: Postgresql installation for MAAS fails on locales missing language packs

[Stuart Bishop]

Consider destroying the cluster created by package installation (or
inhibiting its creation), and calling pg_createcluster yourself with the
'--data-checksums' option available in PG 9.3. This will allow
PostgreSQL to detect corrupted files and fail appropriately.

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

Title:
  Postgresql installation for MAAS fails on locales missing language
  packs

Status in MAAS:
  Triaged
Status in dbconfig-common package in Ubuntu:
  Invalid
Status in maas package in Ubuntu:
  Confirmed
Status in postgresql-common package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 14.04 with all updates as of time of the writing.

  MAAS - 1.5.4+bzr2294-0ubuntu1.1

  # apt-get install maas
  ...
  Setting up maas-dns (1.5.4+bzr2294-0ubuntu1.1) ...
   * Stopping domain name service... bind9  

   waiting for pid 29580 to 
die


[ OK ]
   * Starting domain name service... bind9  

[ OK ] 
  Setting up maas-region-controller (1.5.4+bzr2294-0ubuntu1.1) ...
  locale: Cannot set LC_ALL to default locale: No such file or directory
  Considering dependency proxy for proxy_http:
  Module proxy already enabled
  Module proxy_http already enabled
  Module expires already enabled
  Module wsgi already enabled
  rsyslog stop/waiting
  rsyslog start/running, process 32763
  squid-deb-proxy stop/waiting
  squid-deb-proxy start/running, process 349
   * Restarting message broker rabbitmq-server  

[ OK ] 
  Creating user "maas_longpoll" ...
  ...done.
  Creating vhost "/maas_longpoll" ...
  ...done.
  Setting permissions for user "maas_longpoll" in vhost "/maas_longpoll" ...
  ...done.
  Creating user "maas_workers" ...
  ...done.
  Creating vhost "/maas_workers" ...
  ...done.
  Setting permissions for user "maas_workers" in vhost "/maas_workers" ...
  ...done.
   * No PostgreSQL clusters exist; see "man pg_createcluster"
  dbconfig-common: writing config to 
/etc/dbconfig-common/maas-region-controller.conf

  Creating config file /etc/dbconfig-common/maas-region-controller.conf with 
new version
  unable to connect to postgresql server.
  error encountered creating user:
  psql: could not connect to server: No such file or directory Is the server 
running locally and accepting connections on Unix domain socket 
"/var/run/postgresql/.s.PGSQL.5432"?
  /usr/bin/locale: Cannot set LC_ALL to default locale: No such file or 
directory

  Here's the environment:
  # export
  declare -x HOME="/root"
  declare -x LANG="en_US.UTF-8"
  declare -x LANGUAGE="en_US:en"
  declare -x LC_ADDRESS="hr_HR.UTF-8"
  declare -x LC_IDENTIFICATION="hr_HR.UTF-8"
  declare -x LC_MEASUREMENT="hr_HR.UTF-8"
  declare -x LC_MONETARY="hr_HR.UTF-8"
  declare -x LC_NAME="hr_HR.UTF-8"
  declare -x LC_NUMERIC="hr_HR.UTF-8"
  declare -x LC_PAPER="hr_HR.UTF-8"
  declare -x LC_TELEPHONE="hr_HR.UTF-8"
  declare -x LC_TIME="hr_HR.UTF-8"
  declare -x LESSCLOSE="/usr/bin/lesspipe %s %s"
  declare -x LESSOPEN="| /usr/bin/lesspipe %s"
  declare -x LOGNAME="root"
  declare -x 
LS_COLORS="rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lz=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=0
 

[Desktop-packages] [Bug 1451944] Re: Gnome-terminal in Ubuntu Unity shrinks to minimum size

[Stuart Campbell]

This still seems to be a problem for 15.10 as well.

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

Title:
  Gnome-terminal in Ubuntu Unity shrinks to minimum size

Status in GNOME Terminal:
  Confirmed
Status in GNOME Themes Standard:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  When I open a terminal in Ubuntu 15.04, it shrinks to 1 character by 1
  character. I can use the corner resizer to make the window bigger, but
  it immediately shrinks to 1x1. There are a few x,y combinations that
  allow the window to stay at the desired size, but if you're off by a
  pixel, the window shrinks to 1x1.

  There is another question (http://askubuntu.com/questions/423733
  /gnome-terminal-in-kubuntu-shrinks-to-minimum-size), Gnome-terminal in
  Kubuntu shrinks to minimum size, that is basically the same thing, but
  in KDE. I tried to follow the instructions:

  In KDE, go to System Settings. Return to the overview if you are
  not already there. In the Workspace Appearance and Behavior section,
  click Window Behavior. In the area to the left, click the Window Rules
  icon.

  but, there is no Workspace Appearance and Behavior section. I couldn't
  find a similar setting in ccsm, gnome-tweak-tool or unity-tweak-tool.

  % dpkg-query --show compiz
  compiz1:0.9.12.1+15.04.20150410.1-0ubuntu1
  % dpkg-query --show unity
  unity 7.3.2+15.04.20150420-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-terminal 3.14.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May  5 09:59:55 2015
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2013-05-02 (732 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to vivid on 2015-04-26 (8 days ago)

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

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

[Desktop-packages] [Bug 1295247] Re: Cheese says "There was an error playing video from webcam"

[Stuart Campbell]

Same error - still doesn't work on Wily.

guvcview works fine, cheese and skype do not work.

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

Title:
  Cheese says "There was an error playing video from webcam"

Status in cheese package in Ubuntu:
  Confirmed
Status in libjpeg-turbo package in Ubuntu:
  Confirmed

Bug description:
  Whenever I open Cheese in Ubuntu 14.04 beta 1 (Unity), my webcam's light once 
turns on, then it turns off and Cheese turns black, written "There was an error 
playing video from webcam". This never happened in any previous versions of 
Ubuntu. 
  The problem is reproducible.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cheese 3.10.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic i686
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Mar 20 22:29:57 2014
  InstallationDate: Installed on 2014-03-20 (0 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140225)
  SourcePackage: cheese
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1457438] [NEW] files not shown when known to exist

[Stuart Gillies]

Public bug reported:

When using dia I saved some .png images, as I had done before with the
same names.  Going to nautilus in order to select those images, I find
that they are not listed, yet the dia save dialogue does show them.
Reloading did not find them. See attached screenshot, which shows both
the nautilus window after a reload and the dia dialogue.

Later, opening a new nautilus window did find the files.

So, why did they not show when I first looked?  I have observed this
problem before but did not keep records. This time I thought it
worthwhile.

Files are:
timetrial_duties2.png
regatta_duties2.png

I'm using a fully up-to-date 14.04 on an AMD 64 motherboard and Dia-
gnome 0.97.2

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

** Attachment added: Screenshot from 2015-05-21 11:57:02.png
   
https://bugs.launchpad.net/bugs/1457438/+attachment/4401648/+files/Screenshot%20from%202015-05-21%2011%3A57%3A02.png

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

Title:
  files not shown when known to exist

Status in nautilus package in Ubuntu:
  New

Bug description:
  When using dia I saved some .png images, as I had done before with the
  same names.  Going to nautilus in order to select those images, I find
  that they are not listed, yet the dia save dialogue does show them.
  Reloading did not find them. See attached screenshot, which shows both
  the nautilus window after a reload and the dia dialogue.

  Later, opening a new nautilus window did find the files.

  So, why did they not show when I first looked?  I have observed this
  problem before but did not keep records. This time I thought it
  worthwhile.

  Files are:
  timetrial_duties2.png
  regatta_duties2.png

  I'm using a fully up-to-date 14.04 on an AMD 64 motherboard and Dia-
  gnome 0.97.2

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

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

[Desktop-packages] [Bug 1438336] [NEW] Steam not found error

[Stuart Bishop]

Public bug reported:

Open software center, and search for 'steam' using the top right search
box. The results list the 'Steam' package first on the list, but
clicking on this package displays an error page - 'Not found. There
isn't a software package called steam in your current software
sources'.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: software-center 13.10-0ubuntu6
ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
Uname: Linux 3.19.0-10-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.16.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Mar 31 00:52:42 2015
InstallationDate: Installed on 2015-03-13 (17 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
PackageArchitecture: all
SourcePackage: software-center
UpgradeStatus: Upgraded to vivid on 2015-03-16 (14 days ago)

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


** Tags: amd64 apport-bug third-party-packages vivid

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

Title:
  Steam not found error

Status in software-center package in Ubuntu:
  New

Bug description:
  Open software center, and search for 'steam' using the top right
  search box. The results list the 'Steam' package first on the list,
  but clicking on this package displays an error page - 'Not found.
  There isn't a software package called steam in your current software
  sources'.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: software-center 13.10-0ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 31 00:52:42 2015
  InstallationDate: Installed on 2015-03-13 (17 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  PackageArchitecture: all
  SourcePackage: software-center
  UpgradeStatus: Upgraded to vivid on 2015-03-16 (14 days ago)

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

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

[Desktop-packages] [Bug 1401160] Re: nm-applet not shows icon at system tray in 14.10

[Stuart]

I get this on conneting...

$ nmcli con up id bunyip2

(process:15534): GLib-GObject-WARNING **:
/build/buildd/glib2.0-2.42.1/./gobject/gsignal.c:3101: signal id '11' is
invalid for instance '0x22f31d0'

But it seems to all work ok

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

Title:
  nm-applet not shows icon at system tray in 14.10

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

Bug description:
  New installation of Ubuntu 14.10

  Toshiba P50t

  nm-applet doesn't  shows in system tray.

   sudo nm-applet 
  nm-applet-Message: using fallback from indicator to GtkStatusIcon

  (nm-applet:5573): GLib-GObject-WARNING **:
  /build/buildd/glib2.0-2.42.1/./gobject/gsignal.c:3101: signal id '207'
  is invalid for instance '0x1c9bd40'

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager-gnome 0.9.8.8-0ubuntu7
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Dec 10 16:53:34 2014
  ExecutablePath: /usr/bin/nm-applet
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-11-29 (11 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  IpRoute:
   default via 192.168.123.1 dev wlan0  proto static 
   192.168.123.0/24 dev wlan0  proto kernel  scope link  src 192.168.123.107  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Conexión cableada 1   9685b027-3ddc-4cbd-a053-f3b85e4accf5   
802-3-ethernet1418226251   mié 10 dic 2014 16:44:11 CET   yes   
no /org/freedesktop/NetworkManager/Settings/2
   Asimov 1  39cc730a-8e30-4770-a603-429c600c678a   
802-11-wireless   1418226551   mié 10 dic 2014 16:49:11 CET   yes   
no /org/freedesktop/NetworkManager/Settings/1
   Asimovdb5db932-43c6-492b-b4b9-60da58a2c0c1   
802-11-wireless   1418226190   mié 10 dic 2014 16:43:10 CET   yes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Desktop-packages] [Bug 1072206] Re: [nvidia] Window content is black or transparent

[Stuart Gillies]

I have started to get this on my 14.04 double-header nvidia amd64
system.  I can't say what events cause it, but moving a window generally
fixes it until the next time.  I don't need to have a lot of windows
open to see it.

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

Title:
  [nvidia] Window content is black or transparent

Status in Compiz:
  Confirmed
Status in NVIDIA Drivers Ubuntu:
  Confirmed
Status in Unity:
  Confirmed
Status in “compiz” package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 12.10 64bit (updated from 12.04) / NVIDIA GeForce 8 proprietary
  driver.

  This bug happens to me from 12.04 from some update I think.
  It appears mostly when I open a new application and only ocassionally.
  As temporary solution creating some other event like opening Unity dash or 
opening some next window, etc. fix it. Then window content is refreshed and I 
can see all correctly.
  Same with stable and experimental nvidia drivers.

  Screenshot of this bug is attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] je adresářem: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.48  Sun Sep  9 20:22:27 
PDT 2012
   GCC version:  gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Sat Oct 27 23:00:14 2012
  DistUpgraded: 2012-10-23 19:34:29,842 DEBUG enabling apt cron job
  DistroCodename: quantal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-experimental-304, 304.48, 3.5.0-17-generic, x86_64: installed
   virtualbox, 4.1.18, 3.2.0-32-generic, x86_64: installed
   virtualbox, 4.1.18, 3.5.0-17-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation G92 [GeForce 8800 GT] [10de:0611] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Giga-byte Technology Device [1458:3468]
  InstallationDate: Installed on 2012-08-29 (59 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328)
  JockeyStatus:
   kmod:nvidia_experimental_304 - nvidia_experimental_304 (Proprietary, 
Enabled, Not in use)
   kmod:nvidia_173 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
   kmod:nvidia_current - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:nvidia_173_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:nvidia_current_updates - NVIDIA binary Xorg driver, kernel module and 
VDPAU library (Proprietary, Disabled, Not in use)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=3ae94b68-4a0c-4633-aec7-b4ed25a23003 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to quantal on 2012-10-23 (4 days ago)
  XorgConf:
   Section Device
Identifier  Default Device
Option  NoLogoTrue
   EndSection
  dmi.bios.date: 05/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0208
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M LX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0208:bd05/26/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H61-MLX:rvrRevx.0x: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.8.4-0ubuntu3
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  

[Desktop-packages] [Bug 1352000] [NEW] Screen repeatedly goes black, returns to normal after a couple of seconds

[Stuart Langridge]

Public bug reported:

Running 14.04. My screen (an external monitor, connected to a desktop
computer) has started going black and then returning back to normal a
couple of seconds later. This happens every few minutes. dmesg shows
lines:

[ 9241.255109] HDMI: ELD buf size is 0, force 128
[ 9241.255132] HDMI: invalid ELD data byte 0

There does not seem to be anything relevant being added to Xorg.0.log.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sun Aug  3 22:00:36 2014
DistUpgraded: 2014-04-25 18:09:11,162 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:8534]
InstallationDate: Installed on 2014-04-07 (118 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1)
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed 
root=UUID=ad1b3110-ee9a-4dac-839d-604080e0020d ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2014-04-25 (100 days ago)
dmi.bios.date: 12/13/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1707
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z87-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: PCS
dmi.chassis.type: 3
dmi.chassis.vendor: PC SPECIALIST
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1707:bd12/13/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-A:rvrRev1.xx:cvnPCSPECIALIST:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Sun Aug  3 19:24:59 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   10147 
 vendor ACI
xserver.version: 2:1.15.1-0ubuntu2

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


** Tags: amd64 apport-bug compiz-0.9 trusty 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/1352000

Title:
  Screen repeatedly goes black, returns to normal after a couple of
  seconds

Status in “xorg” package in Ubuntu:
  New

Bug description:
  Running 14.04. My screen (an external monitor, connected to a desktop
  computer) has started going black and then returning back to normal a
  couple of seconds later. This happens every few minutes. dmesg shows
  lines:

  [ 9241.255109] HDMI: ELD buf size is 0, force 128
  [ 9241.255132] HDMI: invalid ELD data byte 0

  There does not seem to be anything relevant being added to Xorg.0.log.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Aug  3 22:00:36 2014
  DistUpgraded: 2014-04-25 18:09:11,162 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: 

[Desktop-packages] [Bug 1293711] Re: Remmina Lockups in 14.04 are Harder To Kill

[Stuart]

To add to this. Don't know if it's relevant but I only run into this
problem when I SSH into another local machine, I also use Remmina over
SSH, related?

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

Title:
  Remmina Lockups in 14.04 are Harder To Kill

Status in “remmina” package in Ubuntu:
  Confirmed

Bug description:
  Remmina has always locked up for me in previous versions of Ubuntu.

  Previously, when this would happen, I could right-click on its
  application launcher and select quit. This would kill Remmina, and
  then I could relaunch it and it would work fine after that.

  In Ubuntu 14.04, when this happens, I can not exit out or quit
  Remmina. Instead it requires me to pull up System Monitor and click
  the End Process button.

  Like I said, Remmina has always locked up for me from time to time,
  but in 14.04 it is just harder to kill it when these lockups occur.

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

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

[Desktop-packages] [Bug 253167] Re: Rhythmbox sort by Album Artist for guest/compilations

[Stuart]

Also BUMPING  but I'm guessing this is being ignored.

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

Title:
  Rhythmbox sort by Album Artist for guest/compilations

Status in The Rhythmbox Music Management Application:
  Confirmed
Status in “rhythmbox” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: rhythmbox

  For guest artists on an album or compilations Apple allows definition
  of an album artist and artist for each track.  Rhythmnbox only allows
  browsing by track artists so many artists appear listed with only one
  track.

  Example, Red Book by Texas:

  1. 036 - Texas
  2. Getaway - Texas
  3. Can't Resist - Texas
  4. What About Us - Texas
  5. Cry - Texas
  6. Sleep - Texas featuring Paul Buchanan
  7. Get Down Tonight - Texas
  8. Nevermind - Texas
  9. Bad Weather - Texas
  10. Master Thief - Texas
  11. Just Holding On - Texas
  12. Red Book  - Texas

  The sixth track has artist Texas featuring Paul Buchanan whilst all
  others are Texas.

  I want to browse by album artist selecting Texas and seeing all 12
  tracks on the album, not just the 11 that match.

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

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

[Desktop-packages] [Bug 1293711] Re: Remmina Lockups in 14.04 are Harder To Kill

[Stuart]

Ran into this problem myself, using top I wasn't able to identify
Remmina to kill the process either, I did find it as per your
instructions in Monitor.

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

Title:
  Remmina Lockups in 14.04 are Harder To Kill

Status in “remmina” package in Ubuntu:
  Confirmed

Bug description:
  Remmina has always locked up for me in previous versions of Ubuntu.

  Previously, when this would happen, I could right-click on its
  application launcher and select quit. This would kill Remmina, and
  then I could relaunch it and it would work fine after that.

  In Ubuntu 14.04, when this happens, I can not exit out or quit
  Remmina. Instead it requires me to pull up System Monitor and click
  the End Process button.

  Like I said, Remmina has always locked up for me from time to time,
  but in 14.04 it is just harder to kill it when these lockups occur.

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

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

[Desktop-packages] [Bug 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates

[Stuart Gillies]

Well I now have BT working in A2DP mode. Hopefully it will stay working.
There was never any problem pairing or connecting, just no sound would
come out and the sound settings screen did not offer any choices.

So, once paired and pulseaudio -k issued (but I don't know if that is
needed or not):

In the Sound Settings window, the headset is visible but does not offer
any options to choose a profile.

In bluetooth settings, pairing is shown but not profiles

However, found by accident, right-clicking on the entry in the Blueman
screen offers the option to select an audio profile. This was set to
'none' by default (why I cannot imagine). Setting it to High Fidelity
fixed the problem immediately.

Why have default settings that cannot produce the output that every user
is going to need?  Weird.  And why have both sound settings and
bluetooth settings screens, and yet the crucial function is on a blueman
screen that does not come up when looking at the settings?  Bluetooth
settings and blueman should be merged.

There still remains the problem that the sound settings screen does not
allow the profile to be selected, though it did in 12.04.

The other problem of course is that there are no definitive and reliable
user functional instructions for this (or indeed most of Ubuntu) and
major searching of individual users problems and attempted fixes is
needed to find clues. 14.04 is an LTS release and all this stuff should
'just work'. Using Ubuntu is more like a research project than using a
working system.

I appreciate that lots of people give up their effort to develop Ubuntu
and other distros, and that is appreciated. But things that work (as all
this did in 12.04) should not be tinkered with until they then fail.

Now I feel better.

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

Title:
  [Bluetooth + 14.04] Bluetooth headsets are not working after last
  couple of updates

Status in “blueman” package in Ubuntu:
  Confirmed
Status in “gnome-bluetooth” package in Ubuntu:
  Confirmed
Status in “pulseaudio” package in Ubuntu:
  Invalid

Bug description:
  Hi,

  I found a bug in Ubuntu 14.04 !

  I tried to pair a bluetooth stereo headset (A2DP compatible). The
  pairing process goes well, but after that I can't select it on the
  audio preferences.

  When I select it, it only shows the last selected item options and don't do 
anything. (he should switch to the headset output).
  I must mention that it worked very well on Ubuntu 12.04.

  This bug can be in the bluetooth stack or in unity-control-center or
  maybe pulseaudio. I actually have no idea.

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

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

[Desktop-packages] [Bug 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates

[Stuart Gillies]

Bluetooth working well for a headset on 12.04, not working on 14.04,
either as new install or as upgrade. It pairs normally, but on one
machine (new install) does not appear in sound settings, on the other it
appears but in neither case does it switch sound from speakers to the
headset when on.

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

Title:
  [Bluetooth + 14.04] Bluetooth headsets are not working after last
  couple of updates

Status in “blueman” package in Ubuntu:
  Confirmed
Status in “gnome-bluetooth” package in Ubuntu:
  Confirmed
Status in “pulseaudio” package in Ubuntu:
  Invalid

Bug description:
  Hi,

  I found a bug in Ubuntu 14.04 !

  I tried to pair a bluetooth stereo headset (A2DP compatible). The
  pairing process goes well, but after that I can't select it on the
  audio preferences.

  When I select it, it only shows the last selected item options and don't do 
anything. (he should switch to the headset output).
  I must mention that it worked very well on Ubuntu 12.04.

  This bug can be in the bluetooth stack or in unity-control-center or
  maybe pulseaudio. I actually have no idea.

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

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

[Desktop-packages] [Bug 1308105] Re: Xfce resets TV mode to NULL when power cycled

[Stuart Matthews]

This issue also affects Gigabyte GA-EG45M-UD2H motherboard with Intel
GMA X4500HD integrated graphics.  Fresh install of mythbuntu 14.04.
13.10 was not affected.

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

Title:
  Xfce resets TV mode to NULL when power cycled

Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
  Confirmed
Status in “nvidia-graphics-drivers” package in Ubuntu:
  Invalid
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Invalid
Status in “xfce4-settings” package in Ubuntu:
  Confirmed

Bug description:
  I had an HTPC with Mythbuntu 12.04 installed.  Upon upgrading a new
  behavior that if the TV is power cycled it no longer detects a link
  with the HTPC.

  When this happens I can find in the xorg log that there is an
  accompanying log item:

  [ 39829.509] (II) NVIDIA(0): Setting mode NULL

  After debugging with NVIDIA at
  https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being-
  detected/ we've deteremined it's a X client that reacts to the RANDR
  events causing the mode to be set to NULL.

  Working through the list in an Xfce environment, the culprit is
  xfsettingsd.  If xfsettingsd is running, it causes the TV to come up
  in a NULL mode.  If it's killed, it remains in the mode it was
  previously running in.

  
  Until this is fixed, this behavior can be worked around with a simple shell 
script:
  ==
  #!/bin/sh
  #Fix TV state when HDMI link is lost.
  #By Mario Limonciello supe...@ubuntu.com

  OUTPUT=HDMI-0
  BAD_MODE=1280x720
  GOOD_MODE=1920x1080

  for MODE in $BAD_MODE $GOOD_MODE; do
   DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE
   sleep 2
  done
  ==

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

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

[Desktop-packages] [Bug 949782] Re: No way to disable start-up sound

[Stuart Bishop]

Linked to unity-control-center for a checkbox and user happiness.

** Also affects: unity-control-center (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  No way to disable start-up sound

Status in Unity Greeter:
  Fix Released
Status in “unity-control-center” package in Ubuntu:
  New
Status in “unity-greeter” package in Ubuntu:
  Fix Released
Status in “unity-control-center” source package in Precise:
  New
Status in “unity-greeter” source package in Precise:
  Fix Released

Bug description:
  There doesn't appear to be a way to disable the lightdm start-up sound
  when lightdm first loads.

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

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

[Desktop-packages] [Bug 1135419] Re: replaygain plugin fails to load

[Stuart Bishop]

It loads fine in Trusty.

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

Title:
  replaygain plugin fails to load

Status in “rhythmbox” package in Ubuntu:
  Incomplete

Bug description:
  With a fresh raring install, I am unable to activate the replaygain
  plugin in rhythmbox. The following is emitted to the console:

  Unable to open ~/.mtpz-data for reading, MTPZ disabled.Traceback (most recent 
call last):
File /usr/lib/rhythmbox/plugins/replaygain/replaygain.py, line 33, in 
module
  from player import ReplayGainPlayer
File /usr/lib/rhythmbox/plugins/replaygain/player.py, line 31, in module
  gi.require_version(Gst, 0.11)
File /usr/lib/python2.7/dist-packages/gi/__init__.py, line 65, in 
require_version
  (namespace, loaded_version))
  ValueError: Namespace Gst is already loaded with version 1.0

  (rhythmbox:29180): libpeas-WARNING **: Error loading plugin
  'replaygain'

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: rhythmbox-plugins 2.98-0ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
  Uname: Linux 3.8.0-7-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Thu Feb 28 15:29:45 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-02-26 (2 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130225)
  MarkForUpload: True
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1281419] Re: Failure to mount NTFS partition confusing and unhelpful

[Stuart Bishop]

** Package changed: ubuntu = nautilus (Ubuntu)

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

Title:
  Failure to mount NTFS partition confusing and unhelpful

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  While it is well known to developers what the following error message
  means, it is terrifying and not suitable for most end users:

  Error mounting /dev/sda2 at /media/stub/0123456789ABCDEF: Command-line `mount 
-t ntfs -o 
uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177 
/dev/sda2 /media/stub/0123456789ABCDEF' exited with non-zero exit status 
14: Windows is hibernated, refused to mount.
  Failed to mount '/dev/sda2': Operation not permitted
  The NTFS partition is in an unsafe state. Please resume and shutdown
  Windows fully (no hibernation or fast restarting), or mount the volume
  read-only with the 'ro' mount option.

  Ubuntu needs  a clearer dialog with the user without the techno babble
  (and no 'unsafe' - this is perfectly normal). In addition, if an
  acceptable solution is to 'mount the volume read-only with the 'ro'
  mount option, then a mechanism to actually do this should be provided.

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

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

[Desktop-packages] [Bug 582547] Re: monitor name in display preferences is corrupt

[stuart]

Hi Christophher, Unfortunately I no longer have any of the pieces of
hardware I saw this problem on. So I can't really help any longer on
this one. I'm not seeing it with current hardware.

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

Title:
  monitor name in display preferences is corrupt

Status in “xserver-xorg-video-ati” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xorg

  Problem stated with Lucid.
  The monitor name in display preferences is corrupt containing graphics 
characters and some part of the correct name. 
  On a T60 with Radeon X1400 adapter.
  Multiple monitors tested.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: xorg 1:7.5+5ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic i686
  Architecture: i386
  Date: Tue May 18 22:48:18 2010
  DkmsStatus: Error: [Errno 2] No such file or directory
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
  MachineType: LENOVO 8741G5G
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic 
root=UUID=f9de54ac-d044-4d34-99a7-6e90b3fa1a5d ro quiet splash
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.utf8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  dmi.bios.date: 07/16/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7IET34WW (1.15 )
  dmi.board.name: 8741G5G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7IET34WW(1.15):bd07/16/2008:svnLENOVO:pn8741G5G:pvrThinkPadT60:rvnLENOVO:rn8741G5G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 8741G5G
  dmi.product.version: ThinkPad T60
  dmi.sys.vendor: LENOVO
  glxinfo: Error: [Errno 2] No such file or directory
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   i686
   kernel: 2.6.32-22-generic

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

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

[Desktop-packages] [Bug 1259005] [NEW] Swiping over SEARCH header in top left of phone Dash does not show search

[Stuart Langridge]

Public bug reported:

On the Ubuntu phone I always try and summon the Search by swiping down
over the word SEARCH in the top left of the Dash. This doesn't work; you
have to tap SEARCH, not swipe over it. The swipe gesture isn't being
used for anything else; perhaps swiping over SEARCH ought to summon the
Search dialog as well as tapping SEARCH?

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

** Package changed: xorg-server (Ubuntu) = unity8 (Ubuntu)

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

Title:
  Swiping over SEARCH header in top left of phone Dash does not show
  search

Status in “unity8” package in Ubuntu:
  New

Bug description:
  On the Ubuntu phone I always try and summon the Search by swiping down
  over the word SEARCH in the top left of the Dash. This doesn't work;
  you have to tap SEARCH, not swipe over it. The swipe gesture isn't
  being used for anything else; perhaps swiping over SEARCH ought to
  summon the Search dialog as well as tapping SEARCH?

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

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

[Desktop-packages] [Bug 1238410] Re: Inconsistent cursor visibility with cursor plugin enabled

[Stuart Bishop]

Per duped Bug #1237218, the manifestation I see of this is that very
occasionally I log in (not having touched the mouse at all so I'm unsure
if it is working on the greeter screen), and I find that there is no
mouse visible in Unity. It is still active, as I can use the invisible
mouse pointer to click on things. Using keyboard navigation to log out
and then logging in again, the problem is probably gone and the mouse
pointer visible again.

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

Title:
  Inconsistent cursor visibility with cursor plugin enabled

Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  On fresh boots the greeter  desktop may have the cursor visible or may not 
until mouse is moved.
  On a log out/in the cursor is almost always invisible until mouse is moved. 
(unless made visible in greeter screen, then visible on Desktop

  This is all  well  good, maybe some intentional aesthetics/design 
(https://bugzilla.gnome.org/show_bug.cgi?id=687791) , however sometimes the 
cursor never becomes visible.
  In that case hitting some keys or context menu can cause it to show, though 
most times a log out is needed.
  (with the removal of ctrl+alt+delete  log out this means most users will 
need to either blindly find the session indicator or hit power button.

  When the g-s-d cursor plugin is disabled then the cursor is always
  visible, it the plugin has no use in an ubuntu session then maybe it
  should be default disabled

  There is also the possibility, particularly on ssd drives,  of a login
  with no session indicator. This occasionally  combines with no visible
  cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.8.5-0ubuntu7
  ProcVersionSignature: Ubuntu 3.11.0-12.18-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Fri Oct 11 00:38:16 2013
  InstallationDate: Installed on 2013-10-03 (8 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131002)
  MarkForUpload: True
  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/1238410/+subscriptions

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