[Desktop-packages] [Bug 2062173] [NEW] Apparmor denies updating namespace with ecryptfs

[Marco Tanner]

Public bug reported:

Noticed on Ubuntu 23.10. Started misbehaving on April 17th 2024.

$ snap info chromium
...
snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
tracking: latest/stable
refresh-date: today at 08:58 CEST
channels:
  latest/stable:123.0.6312.122 2024-04-15 (2821) 168MB -
...


When running chromium, it complains about not being able to open my home dir:
cannot update snap namespace: cannot expand mount entry (none 
$HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist-dir=$HOME 0 
0): cannot use invalid home directory "/home/tannerli": permission denied
snap-update-ns failed with code 1

AppArmor log shows that access to ecryptfs private folder was denied:

Apr 18 13:13:21 hostname kernel: audit: type=1400
audit(1713438801.579:437): apparmor="DENIED" operation="open"
class="file" profile="snap-update-ns.chromium"
name="/home/.ecryptfs/tannerli/.Private/" pid=32412 comm="5"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000


I found out, that, under /var/lib/snapd/apparmor/profiles, while 
snap.chromium.chromium has the line
owner @{HOMEDIRS}/.ecryptfs/*/.Private/ r,

the file snap-update-ns.chromium does _not_ have the line. Adding it and
reloading the profile allows chromium to start again.

I'm nowhere near experienced enough to tell whether this line should be
added by default or something else went wrong on my machine.

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

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

Title:
  Apparmor denies updating namespace with ecryptfs

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Noticed on Ubuntu 23.10. Started misbehaving on April 17th 2024.

  $ snap info chromium
  ...
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: latest/stable
  refresh-date: today at 08:58 CEST
  channels:
latest/stable:123.0.6312.122 2024-04-15 (2821) 168MB -
  ...

  
  When running chromium, it complains about not being able to open my home dir:
  cannot update snap namespace: cannot expand mount entry (none 
$HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist-dir=$HOME 0 
0): cannot use invalid home directory "/home/tannerli": permission denied
  snap-update-ns failed with code 1

  AppArmor log shows that access to ecryptfs private folder was denied:

  Apr 18 13:13:21 hostname kernel: audit: type=1400
  audit(1713438801.579:437): apparmor="DENIED" operation="open"
  class="file" profile="snap-update-ns.chromium"
  name="/home/.ecryptfs/tannerli/.Private/" pid=32412 comm="5"
  requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000

  
  I found out, that, under /var/lib/snapd/apparmor/profiles, while 
snap.chromium.chromium has the line
  owner @{HOMEDIRS}/.ecryptfs/*/.Private/ r,

  the file snap-update-ns.chromium does _not_ have the line. Adding it
  and reloading the profile allows chromium to start again.

  I'm nowhere near experienced enough to tell whether this line should
  be added by default or something else went wrong on my machine.

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


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

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

[Marco Scalone]

Same question. it is a really needed feature

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

Title:
  VPN Connection Failed With 2 Factor Authentication

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

Bug description:
  Hi all,

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

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

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

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

  any help will be appreciated

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


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

[Desktop-packages] [Bug 1790608] Re: [snap] Libreoffice/Firefox do not open files from thunderbird (more general: from /tmp)

[Marco Contenti]

Initially not knowing the cause, I filed this bug report on Thunderbird: 
https://bugzilla.mozilla.org/show_bug.cgi?id=1868956
I think there is a conflict between assumptions on how the /tmp directory can 
be used in Thunderbird and snap. This must be resolved.

** Bug watch added: Mozilla Bugzilla #1868956
   https://bugzilla.mozilla.org/show_bug.cgi?id=1868956

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

Title:
  [snap] Libreoffice/Firefox do not open files from thunderbird (more
  general: from /tmp)

Status in snapd:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I received a document via e-mail in Thunderbird. I have the
  Libreoffice snap package installed. When I want to open the document
  from Thunderbird, I see the Libreoffice splash screen, and then a
  dialog stating "/tmp/mozilla_0/.docx does not exist."

  The same dialog appears when I navigate to the folder in Files and
  want to open it.

  When I copy the file to my desktop, however, I can open it without
  problems.

  I guess the source of the issue is confinement, that the Libreoffice
  snap can only access files from $HOME. But this breaks the case where
  thunderbird creates a temporary copy in /tmp.

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


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

[Desktop-packages] [Bug 2033440] Re: ubuntustudio-installer: error occurred while applying changes

[Marco Frailis]

Thank you for updating the documentation, that's exactly what was misleading.

Just as a feedback: installing manually the metapackages listed in the
ubuntustudio-installer worked fine. The ubuntu-desktop metapackage was
probably automatically uninstalled (it is no more instlled in my
system), but during the manual installation process I did not notice any
removal of other critical system packages. So now I have an Ubuntu
Studio over a Vanilla Ubuntu Gnome, with pulse-audio + jack, and a low
latency kernel.

To me, your answer closes the issue.

Thanks a lot.

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

Title:
  ubuntustudio-installer: error occurred while applying changes

Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-meta source package in Lunar:
  New
Status in ubuntu-meta source package in Mantic:
  New

Bug description:
  
  I have installed successfully the standard Ubuntu 23.04 (on a 500 GB external 
USB drive). Immediately after the installation, I have also installed with apt 
the "ubuntustudio-installer" package.

  In the dialog provided by the ubuntustudio-installer, I have selected
  the following metapackages:

  - linux-lowlatency
  - ubuntustudio-lowlatency-settings
  - ubuntustudio-performance-tweaks
  - ubuntustudio-audio
  - ubuntu-pulseaudio-config

  and pressed "Modify installed Package Selection"

  After a while a "qaptbatch" dialog has appeared with title

  "Commit Error"

  and message

  "An error occurred while applying changes"

  So the installation has failed. Then I have tried to manually install
  each metapackage in the list above with apt and every package was
  installed successfully.

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


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

[Desktop-packages] [Bug 1718931] Re: No VPN autoconnect

[Marco Dal Moro]

it's 2023 and this is still an issue. I'm trying with an ethernet
connection and if I trigger for it to connect automatically with a VPN
then my Ubuntu logs in with neither connected: I have to MANUALLY click
on  WIRED Connection then both connects correctly.

This is incredible.

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

Title:
  No VPN autoconnect

Status in NetworkManager:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Fix Released

Bug description:
  [ Impact ]

  When setting up VPN to auto connect with wifi (done through nm-
  connection-editor) the wifi never manages to connect. However if I
  unselect the auto connect option while it is attempting a reconnection
  then it manages to connect to both (wifi and VPN). Doing the
  connection manually also poses no issues

  [ QA ]

  This is part of the upstream fix:
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  ProblemType: BugDistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 13:15:55 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-09-09 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908)
  IpRoute:
   default via 192.168.0.1 dev wlp6s0 proto static metric 600
   169.254.0.0/16 dev wlp6s0 scope link metric 1000
   192.168.0.0/24 dev wlp6s0 proto kernel scope link src 192.168.0.18 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=trueSourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   wlp6s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
VM5055940   85b8f881-7ed9-477a-9c39-9afb5a40bda9  
/org/freedesktop/NetworkManager/ActiveConnection/1
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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


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

[Desktop-packages] [Bug 1934579] Re: Nautilus crashes when opening places from the dock context menu [SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push()]

[Marco Rolfini]

Bug fixed after updating to jammy-proposed/nautilus/1:42.2-0ubuntu2

Testing procedure:
Booted with Wayland
Reproduced bug (as described in test case above)
Updated to jammy-proposed/nautilus/1:42.2-0ubuntu2
Rebooted with Wayland
Performed test case as above
Already open Nautilus windows remain and window for selected place opens as 
expected

When the updated package will be released?
(The updated package will be released to -updates after the bug(s) fixed by 
this package have been verified and the package has been in -proposed for a 
minimum of 7 days.)

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

Title:
  Nautilus crashes when opening places from the dock context menu
  [SIGSEGV in delete_outdated_error_traps() from
  gdk_x11_display_error_trap_push()]

Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Jammy:
  Fix Committed
Status in nautilus source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

  Nautilus crashes when a bookmarked place is opened from dock icon
  context menu

  [ Test case ]

  1. Open Nautilus (and ensure you've a location in the sidebar bookmarks)
  2. Right-click ubuntu dock nautilus icon
  3. Activate one of the bookmarks
  4. Nautilus should open that location without crashing.

  [ Regression potential ]

  A window may not be raised when opened under wayland.

  ---

  After updating to Ubuntu 21.04, Nautilus crashes every time I try to
  open a second folder by right-clicking on the Nautilus icon in the
  "Favorites" left sidebar (i.e., launch panel) and selecting a
  bookmarked "Places" folder. Normally, this would open a second
  Nautilus window for the selected folder, but instead, any open
  Nautilus windows disappear and no window opens for the selected
  folder. In other words, Nautilus crashes. This did not occur on Ubuntu
  20.10.

  This AskUbuntu post describes the same issue:
  https://askubuntu.com/questions/1344175/nautilus-crashes-when-trying-
  to-open-another-window-by-right-clicking-the-nautil

  If, instead, I right-click the Nautilus icon, select "New Window" and
  then select the desired "Places" folder from the left sidebar of the
  newly opened window, Nautilus does not crash.

  ProblemType: BugDistroRelease: Ubuntu 21.04
  Package: nautilus 1:3.38.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  4 13:36:13 2021
  InstallationDate: Installed on 2020-02-05 (514 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 
(20191017)SourcePackage: nautilus
  UpgradeStatus: Upgraded to hirsute on 2021-06-30 (4 days ago)
  usr_lib_nautilus:
   evince40.1-1
   file-roller   3.38.1-1
   nautilus-extension-gnome-terminal 3.38.1-1ubuntu1
   nautilus-share0.7.3-2ubuntu3

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


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

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

[Marco Scalone]

** Changed in: network-manager-fortisslvpn (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  VPN Connection Failed With 2 Factor Authentication

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

Bug description:
  Hi all,

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

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

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

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

  any help will be appreciated

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


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

[Desktop-packages] [Bug 1971180] [NEW] package libreoffice-style-elementary 1:6.4.7-0ubuntu0.20.04.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it be

[Marco Antonio Cerda Lopez]

Public bug reported:

It doesnt let me update libreoffice or another functions

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libreoffice-style-elementary 1:6.4.7-0ubuntu0.20.04.4
ProcVersionSignature: Ubuntu 5.4.0-107.121-generic 5.4.174
Uname: Linux 5.4.0-107-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.23
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon May  2 11:49:51 2022
DuplicateSignature:
 package:libreoffice-style-elementary:1:6.4.7-0ubuntu0.20.04.4
 Unpacking thunderbird-locale-en-us (1:91.8.1+build1-0ubuntu0.20.04.1) over 
(1:91.7.0+build2-0ubuntu0.20.04.1) ...
 dpkg: error processing package libreoffice-style-elementary (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2019-10-20 (925 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: libreoffice
Title: package libreoffice-style-elementary 1:6.4.7-0ubuntu0.20.04.4 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal need-duplicate-check

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

Title:
  package libreoffice-style-elementary 1:6.4.7-0ubuntu0.20.04.4 failed
  to install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libreoffice package in Ubuntu:
  New

Bug description:
  It doesnt let me update libreoffice or another functions

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-style-elementary 1:6.4.7-0ubuntu0.20.04.4
  ProcVersionSignature: Ubuntu 5.4.0-107.121-generic 5.4.174
  Uname: Linux 5.4.0-107-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon May  2 11:49:51 2022
  DuplicateSignature:
   package:libreoffice-style-elementary:1:6.4.7-0ubuntu0.20.04.4
   Unpacking thunderbird-locale-en-us (1:91.8.1+build1-0ubuntu0.20.04.1) over 
(1:91.7.0+build2-0ubuntu0.20.04.1) ...
   dpkg: error processing package libreoffice-style-elementary (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2019-10-20 (925 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: libreoffice
  Title: package libreoffice-style-elementary 1:6.4.7-0ubuntu0.20.04.4 failed 
to install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1950040] Re: Wayland Screensharing broken in Ubuntu 21.10

[marco]

Firefox 96 deb on 22.04 is broken again.

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

Title:
  Wayland Screensharing broken in Ubuntu 21.10

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in pipewire package in Ubuntu:
  Invalid
Status in xdg-desktop-portal package in Ubuntu:
  Invalid
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed

Bug description:
  Freshly installed Ubuntu 21.10, screen sharing does not work with any
  browser, tested the following options:

  - Firefox snap
  - Firefox deb
  - Chromium snap
  - Chromium flatpak

  Steps to reproduce:

  1. Go to 
https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/#7325517390736006
  2. Select to share the whole desktop in the xdg-desktop-portal
  3. Notice the orange screen share indicator in Gnome-Shell but actually 
nothing is shared in the browser.

  This should be handled high priority since this is a critical feature
  during the pandemic.

  Filed against ubuntu-meta since I don't know exactly which package to
  blame, whether it's pipewire, xdg-desktop portal or some problem
  directely with mutter / gnome-shell, please reassign accordingly.

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


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

[Desktop-packages] [Bug 1906162] Re: Lubuntu 20.04 and 20.10: Libreoffice: font of some dialog-windows is too small

[Marco Aurelio]

Hello, I have the same issue. To be honest work with such small fonts is
tiring.

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

Title:
  Lubuntu 20.04 and 20.10: Libreoffice: font of some dialog-windows is
  too small

Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  in LibreOffice: Tools>Options…: the font of the dialog-window is too small;
  same problem:
  Help>About LibreOffice: the font of the dialog-window is too small;
  it's because the VLC is set to qt5+cairo (this information can be found in: 
Help>About LibreOffice)

  maybe this problem exists for more dialog-windows in LibreOffice;
  this problem does not occur in the open/save-dialog-window (I think, it is 
because the open/save-dialog-window uses the LXQt File Dialog)

  now run those 2 lines on the terminal:
  sudo apt install libreoffice-kf5
  sudo apt remove libreoffice-qt5

  now the VLC is set to gtk3 (this information can be found in: Help>About 
LibreOffice)
  now the font of the dialog-windows is not too small any more;
  so, the problem has got something to do with the package libreoffice-qt5

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Sun Nov 29 15:22:07 2020
  InstallationDate: Installed on 2020-11-19 (9 days ago)
  InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1945342] Re: linux-image-5.4 should be a dependency for nvidia-340 drivers

[Marco Boneff]

** Description changed:

+ This is the first bug i file, so please bear with my inexperience :)
+ 
  nvidia-340 kernel modules are not compatibile with the latest linux
- kernel (5.1* series). So when ubuntu-drivers-common detects and installs
- the nvidia-340 drivers it should also install the latest compatible
- kernel version of the linux 5.4 series.
+ kernel (5.1* series, which are default in the latest 20.04 point
+ releases and following ubuntu releases). So when ubuntu-drivers-common
+ detects and installs the nvidia-340 drivers it should also install the
+ latest compatible kernel version of the linux 5.4 series.
+ 
+ This happened to me when trying to install ubuntu 20.04.3 LTS on an old
+ macbook 6,1 (white unibody macbook). Driver manager suggested nvidia-340
+ for my machine, but installation failed when building kernel modules
+ were incompatibile with the latest linux kernel.
+ 
+ I solved the problem by manually running sudo apt-install --install-
+ recommends linux-generic and by rebooting on an older version of the
+ kernel

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

Title:
  linux-image-5.4 should be a dependency for nvidia-340 drivers

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

Bug description:
  This is the first bug i file, so please bear with my inexperience :)

  nvidia-340 kernel modules are not compatibile with the latest linux
  kernel (5.1* series, which are default in the latest 20.04 point
  releases and following ubuntu releases). So when ubuntu-drivers-common
  detects and installs the nvidia-340 drivers it should also install the
  latest compatible kernel version of the linux 5.4 series.

  This happened to me when trying to install ubuntu 20.04.3 LTS on an
  old macbook 6,1 (white unibody macbook). Driver manager suggested
  nvidia-340 for my machine, but installation failed when building
  kernel modules were incompatibile with the latest linux kernel.

  I solved the problem by manually running sudo apt-install --install-
  recommends linux-generic and by rebooting on an older version of the
  kernel

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


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

[Desktop-packages] [Bug 1945342] [NEW] linux-image-5.4 should be a dependency for nvidia-340 drivers

[Marco Boneff]

Public bug reported:

nvidia-340 kernel modules are not compatibile with the latest linux
kernel (5.1* series). So when ubuntu-drivers-common detects and installs
the nvidia-340 drivers it should also install the latest compatible
kernel version of the linux 5.4 series.

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

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

Title:
  linux-image-5.4 should be a dependency for nvidia-340 drivers

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

Bug description:
  nvidia-340 kernel modules are not compatibile with the latest linux
  kernel (5.1* series). So when ubuntu-drivers-common detects and
  installs the nvidia-340 drivers it should also install the latest
  compatible kernel version of the linux 5.4 series.

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


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

[Desktop-packages] [Bug 1943534] Re: Add kernel version to 'About' page in Settings

[Marco Aurélio Gonçalves Pinto]

I don't have a clue on how to get that information.

All I see is that when I update VirtualBox on Windows 10, the guest
additions CD for Ubuntu guest refers to the kernel version.

Besides that, I am clueless.

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

Title:
  Add kernel version to 'About' page in Settings

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  [08:37:46]  Is it too much to ask that the properties of
  the OS would also show the kernel version?

  
  I have 20.04 LTS.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-gnome-desktop (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 14 08:58:52 2021
  InstallationDate: Installed on 2020-04-23 (508 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: ubuntu-gnome-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1943285] Re: login screen lagging.

[Marco]

I have a similar issue on Ubuntu 20.04 with 1.30.0-0ubuntu4~20.04.1.
Sometimes I enter my password, the screen goes black and I have to log
in another time. Once lightdm didn't start at all.

If such issues occur I have these entries in the journal:
Sep 12 20:03:10 marco-MS-5455 lightdm[1123]: pam_unix(lightdm:auth): Couldn't 
open /etc/securetty: No such file or directory
Sep 12 20:03:12 marco-MS-5455 lightdm[1055]: pam_unix(lightdm-greeter:session): 
session closed for user lightdm
Sep 12 20:03:12 marco-MS-5455 systemd[1]: lightdm.service: Main process exited, 
code=exited, status=1/FAILURE
Sep 12 20:03:12 marco-MS-5455 systemd[1]: lightdm.service: Failed with result 
'exit-code'.
Sep 12 20:03:13 marco-MS-5455 systemd[1]: lightdm.service: Scheduled restart 
job, restart counter is at 1.

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

Title:
  login screen lagging.

Status in lightdm package in Ubuntu:
  New

Bug description:
  After boot or logout, login screen slow to appear, and I cannot type
  in my password for 4 to 5 seconds after login screen has appeared.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu4~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133
  Uname: Linux 5.4.0-84-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Fri Sep 10 21:37:00 2021
  InstallationDate: Installed on 2020-05-05 (493 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  LightdmConfig:
   [Seat:*]
   autologin-guest=false
   greeter-show-manual-login=false
   greeter-session=slick-greeter
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1942074] [NEW] Deja-Dup notifications appear in German

[Marco van Zwetselaar]

Public bug reported:

Thank you for maintaining this useful piece of software.

The issue: notifications from Deja Dup appear in German, whereas my
system and user locale are set to en_GB.  Deja dup's UI language is
correctly English.  It appears to be just the notifications that pop up
which are in German.

This is on a plain vanilla Ubuntu 21.04, with Deja Dup 42.7-1ubuntu1.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: deja-dup 42.7-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
Uname: Linux 5.11.0-31-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 30 14:01:29 2021
InstallationDate: Installed on 2020-11-13 (289 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
SourcePackage: deja-dup
UpgradeStatus: Upgraded to hirsute on 2021-05-07 (115 days ago)
modified.conffile..etc.logrotate.d.apport: [modified]
mtime.conffile..etc.logrotate.d.apport: 2020-11-14T00:02:50.449077

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


** Tags: amd64 apport-bug hirsute

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

Title:
  Deja-Dup notifications appear in German

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Thank you for maintaining this useful piece of software.

  The issue: notifications from Deja Dup appear in German, whereas my
  system and user locale are set to en_GB.  Deja dup's UI language is
  correctly English.  It appears to be just the notifications that pop
  up which are in German.

  This is on a plain vanilla Ubuntu 21.04, with Deja Dup 42.7-1ubuntu1.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: deja-dup 42.7-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 30 14:01:29 2021
  InstallationDate: Installed on 2020-11-13 (289 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to hirsute on 2021-05-07 (115 days ago)
  modified.conffile..etc.logrotate.d.apport: [modified]
  mtime.conffile..etc.logrotate.d.apport: 2020-11-14T00:02:50.449077

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


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

[Desktop-packages] [Bug 1922353] Re: Overview sometimes fails to appear or disappear in gnome-shell 3.38

[Marco van Zwetselaar]

Confirming that gnome-shell 3.38.4-1ubuntu3~21.04.1 resolves the issue.
Thank you for your work, it is much appreciated.

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

Title:
  Overview sometimes fails to appear or disappear in gnome-shell 3.38

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Hirsute:
  Fix Committed
Status in gnome-shell source package in Impish:
  Fix Released

Bug description:
  [Impact]

  Shell overview gets stuck where it's permanently toggled but not
  visible. Only app windows appear in their overview state. Can't
  interact with applications anymore.

  [Test Plan]

  1. Log into GNOME.
  2. Press Super+A
  3. Click on 'Files' and wait till it has launched.
  4. Press the Super key.
  Expect: Can interact with the application window.

  [Where problems could occur]

  Since the patch affects some of the core gnome-shell layout logic,
  anything is possible. Risk has been mitigated by the patch being
  small.

  [Original description]

  When I press the "windows" or "options" or "super" key a list of
  running applications (like alt-tab) and a text window appears. I can
  choose from the running applications or write a command into the text
  window. After I chose an application or press ESC all this disappear
  and I can do my thing.

  Since trying 21.04 sometimes this
  1. does not appear properly - there is no visible text window
  2. does not disappear - despite what I click on or what keys do I press this 
never disappear so I can not use my running applications or start anything new 
even from the menu.

  I have to log out and in to break this.

  Disabling my gnome-shell extensions or using xorg instead of wayland
  does not helps.

  Since upgrading this morning this happens every time I press Super,
  not just occasionally, thus making my desktop unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  2 14:07:39 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-19 (378 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago)

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

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

[Desktop-packages] [Bug 1800043] Re: nautilus cannot write on nfs file share base dir

[Marco]

Hi, I have here exactly the same issue on ubuntu 20.04
can't write to the 1st directory of nfs share in nautilus.
In the terminal window no problem

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

Title:
  nautilus cannot write on nfs file share base dir

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

Bug description:
  I installed Ubuntu 18.04LTS comming from 16.04LTS where I did not have this 
weird problem: If I mount a NFS share from a file server (i.e. Synology DS 418) 
Nautilus is not able to perform any write access to it (write, delete, make new 
directory,...). I can do all of this operations by using shell commands (touch, 
cp, mkdir...) in a terminal window. Also, nautilus can perform these actions if 
I start it with root privileges.
  Even stranger is the following: even though nautilus cannot write into the 
mounted shares it is able to write into its subfolders. This bug seems to 
affect others as well: 
https://askubuntu.com/questions/1000973/nautilus-cannot-write-into-1st-directory-of-a-nfs-share

  Ubuntu version: 18.04.1 LTS - amd64
  Nautilus version: 1:3.26.4-0~ubuntu18.04.1

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

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

[Desktop-packages] [Bug 1920239] Re: Icons in the background when I click on "show applications"

[Marco Giannini]

** Summary changed:

- UBUNTU 21.04: Dash to dock wrong focus
+ Icons in the background when I click on "show applications"

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

Title:
  Icons in the background when I click on "show applications"

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

Bug description:
  Ubuntu Hirsute Hippo (development branch)
  gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1

  BUG
  When I press on "Show applications" on the dock the animation starts and at 
the end I end up with the application icons in the background. The icons are 
partly overlaid by the program preview.

  Video of the bug https://youtu.be/eodtSxRRiNg

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

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

[Desktop-packages] [Bug 1920239] [NEW] UBUNTU 21.04: Dash to dock wrong focus

[Marco Giannini]

Public bug reported:

Ubuntu Hirsute Hippo (development branch)
gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1

BUG
When I press on "Show applications" on the dock the animation starts and at the 
end I end up with the application icons in the background. The icons are partly 
overlaid by the program preview.

Video of the bug https://youtu.be/eodtSxRRiNg

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

** Attachment added: "Schermata da 2021-03-19 17-01-45.png"
   
https://bugs.launchpad.net/bugs/1920239/+attachment/5478314/+files/Schermata%20da%202021-03-19%2017-01-45.png

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

Title:
  UBUNTU 21.04: Dash to dock wrong focus

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

Bug description:
  Ubuntu Hirsute Hippo (development branch)
  gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1

  BUG
  When I press on "Show applications" on the dock the animation starts and at 
the end I end up with the application icons in the background. The icons are 
partly overlaid by the program preview.

  Video of the bug https://youtu.be/eodtSxRRiNg

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

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

[Desktop-packages] [Bug 1885344] Re: nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build (oem 5.6 kernel)

[MARCO RUGIADOSI]

Confirmed, using PPA kelebek333/nvidia-legacy with GeForce GT9600 Linux
5.8.0-36-generic x86_64 ubuntu 20.04 works fine

Thanks Andrea

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

Title:
  nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build
  (oem 5.6 kernel)

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

Bug description:
  Nvidia kernel module fails to build with linux kernel 5.6.0. Exits
  with error code 2.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  linux-image-unsigned-5.6.0-1018-oem:
Installed: 5.6.0-1018.18
Candidate: 5.6.0-1018.18
Version table:
   *** 5.6.0-1018.18 500
  500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-340 340.108-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.6.0-1018-oem
  Date: Sat Jun 27 02:15:51 2020
  DuplicateSignature: 
dkms:nvidia-340:340.108-0ubuntu2:/var/lib/dkms/nvidia-340/340.108/build/nv-drm.c:54:25:
 error: implicit declaration of function ‘drm_pci_init’; did you mean 
‘drm_mm_init’? [-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2020-04-24 (63 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageVersion: 340.108-0ubuntu2
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.3
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1909032] [NEW] No sound through HDMI, option listed even without cable

[Marco Carta]

Public bug reported:

The hdmi audio output option is always in the list (even without the
cable) but it doesn't work

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
Uname: Linux 5.8.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  marco 15714 F pulseaudio
 /dev/snd/controlC1:  marco 15714 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 22 19:06:51 2020
InstallationDate: Installed on 2020-05-21 (215 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
Symptom_Card: Audio interno - HDA Intel HDMI
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  marco 15714 F pulseaudio
 /dev/snd/controlC1:  marco 15714 F pulseaudio
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [X550JD, Intel Generic, Digital Out, HDMI] No sound at all
UpgradeStatus: Upgraded to groovy on 2020-12-22 (0 days ago)
dmi.bios.date: 10/08/2014
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X550JD.303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X550JD
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.:bvrX550JD.303:bd10/08/2014:br4.6:svnASUSTeKCOMPUTERINC.:pnX550JD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X550JD
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-12-21T11:16:00.079207

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


** Tags: amd64 apport-bug groovy

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

Title:
  No sound through HDMI, option listed even without cable

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The hdmi audio output option is always in the list (even without the
  cable) but it doesn't work

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marco 15714 F pulseaudio
   /dev/snd/controlC1:  marco 15714 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 22 19:06:51 2020
  InstallationDate: Installed on 2020-05-21 (215 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Audio interno - HDA Intel HDMI
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marco 15714 F pulseaudio
   /dev/snd/controlC1:  marco 15714 F pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [X550JD, Intel Generic, Digital Out, HDMI] No sound at all
  UpgradeStatus: Upgraded to groovy on 2020-12-22 (0 days ago)
  dmi.bios.date: 10/08/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JD.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JD
  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.:bvrX550JD.303:bd10/08/2014:br4.6:svnASUSTeKCOMPUTERINC.:pnX550JD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X550JD
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-12-21T11:16:00.079207

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

-- 

[Desktop-packages] [Bug 1903446] [NEW] the process gnome-shell stay active for ever, and take 6-7 perc. of resorce, without apparent reason

[marco franzini]

Public bug reported:

it take also 1 Gbyte of memory

I expect not using these resoruces from my cpu.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov  8 23:13:43 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-10-04 (34 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  the process gnome-shell stay active for ever, and take 6-7 perc. of
  resorce, without apparent reason

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  it take also 1 Gbyte of memory

  I expect not using these resoruces from my cpu.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  8 23:13:43 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-04 (34 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1849257] Re: Firefox audio not playing via bluetooth

[Marco Ferretti]

Same here: ubuntu (xfce) 20.04 upgraded from a working 18.04

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

Title:
  Firefox audio not playing via bluetooth

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  When I am playing videos in Youtube, it plays through my laptop
  speakers instead of through the connected bluetooth device. I tried
  that with my USB headset but still audio plays out through my laptop
  speakers. Same for Prime Video. It works fine in Google chrome i.e.
  audio is re-routed through bluetooth speakers.

  I tried switching audio devices and still nothing changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 69.0.3+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ashfaq 1386 F pulseaudio
   /dev/snd/pcmC0D0c:   ashfaq 1386 F...m pulseaudio
   /dev/snd/pcmC0D0p:   ashfaq 1386 F...m pulseaudio
  BuildID: 20191010103742
  Channel: Unavailable
  Date: Tue Oct 22 10:58:03 2019
  ForcedLayersAccel: False
  InstallationDate: Installed on 2019-10-18 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.1.1 dev wlp1s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp1s0 scope link metric 1000 
   192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.57 metric 600
  NoProfiles: True
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Suntory_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.08
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.08:bd11/28/2017:svnAcer:pnSwiftSF314-52:pvrV1.08:rvnKBL:rnSuntory_KL:rvrV1.08:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-52
  dmi.product.sku: 
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[Marco Giovinazzi]

@Hui: thanks for the update :)

@Benny: the issue with pulseaudio and bt sound quality is a neverending
story... e.g.:

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/776

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1838151

I'm considering an USB audio adapter (as someone is suggesting in the
other threads) since it's almost impossible to have a decent
conversation using my laptop and my bt headset...

** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #776
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/776

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[Marco Giovinazzi]

@Hui,

Here's my device:

Bus 003 Device 004: ID 8087:0026 Intel Corp.

Marco.

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[Marco Giovinazzi]

Same problem using Aeropex by AfterShokz (AVRCP) headset on 20.04
(xps9310).

Quick-and-dirty workaround:
- download the 1.190 firmware package 
(http://mirrors.edge.kernel.org/ubuntu/pool/main/l/linux-firmware/linux-firmware_1.190.tar.gz)
- copy the relevant ibt firmware and parameters (sfi, ddc) to 
/usr/lib/firmware/intel (ibt-19-0-4 in my case) - backup of the old files 
highly recommended ;)
- reboot, reconnect.

My headset is now working both in A2DP and HFP/HSP modes.

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)

[Marco Giannini]

The patch seems to work fine on Ubuntu 20.10 too.

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

Title:
  Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly
  on Nvidia)

Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Focal:
  In Progress
Status in mutter source package in Groovy:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME Shell starts with a wrong text size

  
  [ Test case ]

  In a terminal run:
- Xephyr :2

  In another one:
- env DISPLAY=:2 dbus-run-session gnome-shell --x11

  The shell should run in the embedded window, with the correct text
  size, running it again (without closing Xephyr window, but stopping
  the shell execution) should not bigger than expected.

  -- Other test case (hw dependant)

  - Login, ensure that the Shell text size matches the configured one.

  
  [ Regression potential ]

  Initial UI scaling when fractional scaling is enabled is wrong.

  
  [ Workaround ]

  Run on startup:
   - gsettings set org.gnome.desktop.interface scaling-factor \
   $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' 
-f2)

  
  ---

  See also bug 1892521.

  The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04
  causes small text in GNOME Shell menu with  NVIDIA cards.

  With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem 
is after update to the (3.36.4-0ubuntu0.20.04.2).
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.36.4-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-15T17:44:36

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

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

[Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)

[Marco Giannini]

As for Ubuntu 20.10, what is the timing for the arrival of the patch?
Will it take some time after arriving on 20.04 or will they be
contextual? (yes, the bug is also present in the development branch I'm
testing)

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

Title:
  Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly
  on Nvidia)

Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Focal:
  In Progress
Status in mutter source package in Groovy:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME Shell starts with a wrong text size

  
  [ Test case ]

  In a terminal run:
- Xephyr :2

  In another one:
- env DISPLAY=:2 dbus-run-session gnome-shell --x11

  The shell should run in the embedded window, with the correct text
  size, running it again (without closing Xephyr window, but stopping
  the shell execution) should not bigger than expected.

  -- Other test case (hw dependant)

  - Login, ensure that the Shell text size matches the configured one.

  
  [ Regression potential ]

  Initial UI scaling when fractional scaling is enabled is wrong.

  
  [ Workaround ]

  Run on startup:
   - gsettings set org.gnome.desktop.interface scaling-factor \
   $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' 
-f2)

  
  ---

  See also bug 1892521.

  The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04
  causes small text in GNOME Shell menu with  NVIDIA cards.

  With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem 
is after update to the (3.36.4-0ubuntu0.20.04.2).
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.36.4-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-15T17:44:36

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

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

[Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)

[Marco Giannini]

For now it seems to work, no problems have emerged after the update.

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

Title:
  Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly
  on Nvidia)

Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Focal:
  In Progress
Status in mutter source package in Groovy:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME Shell starts with a wrong text size

  
  [ Test case ]

  In a terminal run:
- Xephyr :2

  In another one:
- env DISPLAY=:2 dbus-run-session gnome-shell --x11

  The shell should run in the embedded window, with the correct text
  size, running it again (without closing Xephyr window, but stopping
  the shell execution) should not bigger than expected.

  -- Other test case (hw dependant)

  - Login, ensure that the Shell text size matches the configured one.

  
  [ Regression potential ]

  Initial UI scaling when fractional scaling is enabled is wrong.

  
  [ Workaround ]

  Run on startup:
   - gsettings set org.gnome.desktop.interface scaling-factor \
   $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' 
-f2)

  
  ---

  See also bug 1892521.

  The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04
  causes small text in GNOME Shell menu with  NVIDIA cards.

  With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem 
is after update to the (3.36.4-0ubuntu0.20.04.2).
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.36.4-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-15T17:44:36

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

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

[Desktop-packages] [Bug 1892440] Re: [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards

[Marco Giannini]

Same problema with same workaround

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

Title:
  [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu
  20.04 with nvidia cards

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04
  causes small text in GNOME Shell menu with  NVIDIA cards.

  With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem 
is after update to the (3.36.4-0ubuntu0.20.04.2).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.36.4-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-15T17:44:36

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

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

[Desktop-packages] [Bug 1892404] [NEW] busted scale with lowercase characters

[Marco Giannini]

Public bug reported:

UI resolution busted after updating to mutter 3.36.4-0ubuntu0.20.04.2
The writing in the top bar is too small. The bug also shows up on the login 
screen. To reset I have to change the UI scale factor and then reapply the 100% 
one

Ubuntu 20.04.x LTS
NVIDIA 440.x

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

** Attachment added: "photo_2020-08-20_20-07-12.jpg"
   
https://bugs.launchpad.net/bugs/1892404/+attachment/5403214/+files/photo_2020-08-20_20-07-12.jpg

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

Title:
  busted scale with lowercase characters

Status in mutter package in Ubuntu:
  New

Bug description:
  UI resolution busted after updating to mutter 3.36.4-0ubuntu0.20.04.2
  The writing in the top bar is too small. The bug also shows up on the login 
screen. To reset I have to change the UI scale factor and then reapply the 100% 
one

  Ubuntu 20.04.x LTS
  NVIDIA 440.x

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

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

[Desktop-packages] [Bug 1876491] Re: Ubuntu 20.04 Freezes

[Marco]

Hi! I'm experiencing exactly the same problem. I've added the package
name. Hope someone can help me/us

** Package changed: linux (Ubuntu) => gdm3 (Ubuntu)

** 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/1876491

Title:
  Ubuntu 20.04 Freezes

Status in gdm3 package in Ubuntu:
  New

Bug description:
  I am running into full system freezes while using 20.04, i did a clean 
install and the issue is still there it will randomly freeze the whole system 
sometimes the mouse pointer is moving. 
  Ends up hard resetting by holding the power button to restart the pc.
  I am using AMD Ryzen 5 2500U , and while it boots up it has showed some gpu 
error while booting ubuntu. Some error realating to kernel is showed ,  amd gpu 
kernel  like that. So i think its kernel related issue.

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

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

[Desktop-packages] [Bug 1877401] [NEW] The Italian translation is not complete

[Marco]

Public bug reported:

The Italian translation in the version 3.36.0 in Ubuntu 20.04 LTS is not
complete. Some items in the menu are shown in English, like "Right to
Left Document" and "Properties".

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

** Description changed:

- The Italian translation in the version 3.36 in Ubuntu 20.04 LTS is not
+ The Italian translation in the version 3.36.0 in Ubuntu 20.04 LTS is not
  complete. Some items in the menu are shown in English, like "Right to
  Left Document" and "Properties".

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

Title:
  The Italian translation is not complete

Status in evince package in Ubuntu:
  New

Bug description:
  The Italian translation in the version 3.36.0 in Ubuntu 20.04 LTS is
  not complete. Some items in the menu are shown in English, like "Right
  to Left Document" and "Properties".

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

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

[Desktop-packages] [Bug 1877402] [NEW] The Italian translation is not complete

[Marco]

Public bug reported:

The Italian translation is not complete. Some items in the version
3.36.0 in Ubuntu 20.04 LTS are shown in English, like "Scan", "Single
Page", "Text", "Image", "Print" and others.

** Affects: simple-scan (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  The Italian translation is not complete

Status in simple-scan package in Ubuntu:
  New

Bug description:
  The Italian translation is not complete. Some items in the version
  3.36.0 in Ubuntu 20.04 LTS are shown in English, like "Scan", "Single
  Page", "Text", "Image", "Print" and others.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1877402/+subscriptions

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

[Desktop-packages] [Bug 1876696] [NEW] Install button still actionable when snap install in progress

[Marco Boneff]

Public bug reported:

When installing a new snap from gnome-software, the "install" button
remains clickable while installing is in progress. If you press the
button once again, the store returns an error "Impossible to install
«%snap_name%»: snap "%snap_name%" has "install-snap" change in
progress".

Test Case
1. Open GNOME Software
2. Select a snap and click on the install button
3. Click again on the same button

Expected result:
- When the button "Install" is clicked once, it should become inactive (change 
color and not be clickable anymore).
- the label on the button should change showing something like "install in 
progress"
- (Desired, not forcefully required) A progress bar should indicate that 
something is happening

Observed result:
Install button is always active and clickable.
When the "install" button clicked , gnome-software returns the error 
"Impossible to install «%snap_name%»: snap "%snap_name%" has "install-snap" 
change in progress

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

** Description changed:

  When installing a new snap from gnome-software, the "install" button
  remains clickable while installing. If you press the button once again,
- the store returns says install-snap change is in progress.
+ the store returns an error "Impossible to install «%snap_name%»: snap
+ "%snap_name%" has "install-snap" change in progress".
  
  Test Case
  1. Open GNOME Software
  2. Select a snap and click on the install button
  3. Click again on the same button
  
  Expected result:
  - When the button "Install" is clicked once, it should become inactive 
(change color and not be clickable anymore).
  - the label on the button should change showing something like "install in 
progress"
  - (Desired, not forcefully required) A progress bar should indicate that 
something is happening
  
  Observed result:
  Install button is always active and clickable.
  When the "install" button clicked , gnome-software returns the error 
"Impossible to install «%snap_name%»: snap "%snap_name%" has "install-snap" 
change in progress

** Description changed:

  When installing a new snap from gnome-software, the "install" button
- remains clickable while installing. If you press the button once again,
- the store returns an error "Impossible to install «%snap_name%»: snap
- "%snap_name%" has "install-snap" change in progress".
+ remains clickable while installing is in progress. If you press the
+ button once again, the store returns an error "Impossible to install
+ «%snap_name%»: snap "%snap_name%" has "install-snap" change in
+ progress".
  
  Test Case
  1. Open GNOME Software
  2. Select a snap and click on the install button
  3. Click again on the same button
  
  Expected result:
  - When the button "Install" is clicked once, it should become inactive 
(change color and not be clickable anymore).
  - the label on the button should change showing something like "install in 
progress"
  - (Desired, not forcefully required) A progress bar should indicate that 
something is happening
  
  Observed result:
  Install button is always active and clickable.
  When the "install" button clicked , gnome-software returns the error 
"Impossible to install «%snap_name%»: snap "%snap_name%" has "install-snap" 
change in progress

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

Title:
  Install button still actionable when snap install in progress

Status in gnome-software package in Ubuntu:
  New

Bug description:
  When installing a new snap from gnome-software, the "install" button
  remains clickable while installing is in progress. If you press the
  button once again, the store returns an error "Impossible to install
  «%snap_name%»: snap "%snap_name%" has "install-snap" change in
  progress".

  Test Case
  1. Open GNOME Software
  2. Select a snap and click on the install button
  3. Click again on the same button

  Expected result:
  - When the button "Install" is clicked once, it should become inactive 
(change color and not be clickable anymore).
  - the label on the button should change showing something like "install in 
progress"
  - (Desired, not forcefully required) A progress bar should indicate that 
something is happening

  Observed result:
  Install button is always active and clickable.
  When the "install" button clicked , gnome-software returns the error 
"Impossible to install «%snap_name%»: snap "%snap_name%" has "install-snap" 
change in progress

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

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

[Desktop-packages] [Bug 1875216] Re: [snap] chrome-gnome-shell extension fails to detect native host connector

[Marco Evangelisti Crespo]

Just found connection issue also with KeePassHttp-Connector.

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

Title:
  [snap] chrome-gnome-shell extension fails to detect native host
  connector

Status in firefox package in Ubuntu:
  New

Bug description:
  I am on Ubuntu 20.04 and snap Firefox 75.0-3.

  I keep getting "Although GNOME Shell integration extension is running,
  native host connector is not detected. Refer documentation for
  instructions about installing connector."

  Of course, I have already done "sudo apt-get install chrome-gnome-
  shell" and I am confident that the installation went well because
  Gnome shell integration works just fine if I use it on deb-Chrome.

  The issue should then be related to Firefox snap for Ubuntu. In add-on
  preferences, I get "Your native host connector does not support check
  for GNOME Shell extensions updates. Probably python-requests package
  is missing."

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

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

[Desktop-packages] [Bug 1875216] [NEW] [snap] chrome-gnome-shell extension fails to detect native host connector

[Marco Evangelisti Crespo]

Public bug reported:

I am on Ubuntu 20.04 and snap Firefox 75.0-3.

I keep getting "Although GNOME Shell integration extension is running,
native host connector is not detected. Refer documentation for
instructions about installing connector."

Of course, I have already done "sudo apt-get install chrome-gnome-shell"
and I am confident that the installation went well because Gnome shell
integration works just fine if I use it on deb-Chrome.

The issue should then be related to Firefox snap for Ubuntu. In add-on
preferences, I get "Your native host connector does not support check
for GNOME Shell extensions updates. Probably python-requests package is
missing."

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

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

Title:
  [snap] chrome-gnome-shell extension fails to detect native host
  connector

Status in firefox package in Ubuntu:
  New

Bug description:
  I am on Ubuntu 20.04 and snap Firefox 75.0-3.

  I keep getting "Although GNOME Shell integration extension is running,
  native host connector is not detected. Refer documentation for
  instructions about installing connector."

  Of course, I have already done "sudo apt-get install chrome-gnome-
  shell" and I am confident that the installation went well because
  Gnome shell integration works just fine if I use it on deb-Chrome.

  The issue should then be related to Firefox snap for Ubuntu. In add-on
  preferences, I get "Your native host connector does not support check
  for GNOME Shell extensions updates. Probably python-requests package
  is missing."

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

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

[Desktop-packages] [Bug 1873719] [NEW] Relatar

[marco antonio da silva]

Public bug reported:

Relatar erro na execução Linux

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
Uname: Linux 4.15.0-96-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sun Apr 19 23:33:32 2020
DistUpgraded: 2020-04-18 10:05:27,584 DEBUG icon theme changed, re-reading
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 intel-hid, 3.1, 4.4.0-177-generic, x86_64: installed
 oem-wifi-ath9k-msi, 1, 4.4.0-177-generic, x86_64: installed
 oem-wifi-qualcomm-ath10k-lp1734600-4.4, 4.1, 4.4.0-177-generic, x86_64: 
installed
 radeon-si, 1a, 4.4.0-38-generic, x86_64: built
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:078c]
InstallationDate: Installed on 2019-08-18 (246 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
MachineType: Dell Inc. Inspiron 15-3567
ProcEnviron:
 LANGUAGE=pt_BR:
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic 
root=UUID=10e0a602-865d-4c14-bc06-438dbffafffc ro locale=pt_BR alx.enable_wol=1 
mem_sleep_default=deep alx.enable_wol=1 mem_sleep_default=deep quiet splash 
vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2020-04-18 (1 days ago)
dmi.bios.date: 07/17/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.6.0
dmi.board.name: 06J0HF
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.0:bd07/17/2018:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn06J0HF:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 15-3567
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Sat Apr 18 01:24:06 2020
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   29164 
 vendor AUO
xserver.version: 2:1.18.4-0ubuntu0.8

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


** Tags: amd64 apport-bug bionic 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/1873719

Title:
  Relatar

Status in xorg package in Ubuntu:
  New

Bug description:
  Relatar erro na execução Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  Uname: Linux 4.15.0-96-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Apr 19 23:33:32 2020
  DistUpgraded: 2020-04-18 10:05:27,584 DEBUG icon theme changed, re-reading
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   intel-hid, 3.1, 4.4.0-177-generic, x86_64: installed
   oem-wifi-ath9k-msi, 1, 4.4.0-177-generic, x86_64: installed
   oem-wifi-qualcomm-ath10k-lp1734600-4.4, 4.1, 4.4.0-177-generic, x86_64: 
installed
   radeon-si, 1a, 4.4.0-38-generic, x86_64: built
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:078c]
  InstallationDate: Installed on 2019-08-18 (246 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Inspiron 

[Desktop-packages] [Bug 1870740] [NEW] Refresh Rate

[Vasile Marco]

Public bug reported:

Hi.After i installed my video card i did some display changes like Scale
and Refresh Rate.After i changed Refresh Rate from 30 to 50 & 59 it
crush .I reinstalled 3 times ubuntu because my monitor was no signal
receive from  I use Samsung Led TV with 60 Hz Refresh Rate.Sorry
from my english

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:03:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr  4 11:06:23 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 440.64, 5.4.0-21-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GM204 [GeForce GTX 970] 
[1462:3160]
InstallationDate: Installed on 2020-04-04 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
MachineType: MSI MS-7885
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=b8f882ee-4da2-404b-b880-6142322cc80d ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/19/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P.50
dmi.board.asset.tag: Default string
dmi.board.name: X99A RAIDER (MS-7885)
dmi.board.vendor: MSI
dmi.board.version: 5.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 5.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP.50:bd07/19/2016:svnMSI:pnMS-7885:pvr5.0:rvnMSI:rnX99ARAIDER(MS-7885):rvr5.0:cvnMSI:ct3:cvr5.0:
dmi.product.family: Default string
dmi.product.name: MS-7885
dmi.product.sku: Default string
dmi.product.version: 5.0
dmi.sys.vendor: MSI
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal 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/1870740

Title:
  Refresh Rate

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi.After i installed my video card i did some display changes like
  Scale and Refresh Rate.After i changed Refresh Rate from 30 to 50 & 59
  it crush .I reinstalled 3 times ubuntu because my monitor was no
  signal receive from  I use Samsung Led TV with 60 Hz Refresh
  Rate.Sorry from my english

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:03:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 11:06:23 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) 

[Desktop-packages] [Bug 1868332] Re: Scrolling jumps after switching windows

[Marco Gellecanao]

Thank you for the response. Also, this bug actually applies regardless
of what apps I am using, and I was just using Chrome as an example.

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

Title:
  Scrolling jumps after switching windows

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  The bug has to do with mouse scrolling and switching windows; I do not
  know which package it is part of.

  The problem arises when I have two windows of two different
  applications open, such as Google Chrome and a text editor. To
  reproduce the error, I have Google Chrome open initially, then I
  switch tabs (using the shortcut Alt-Tab) to the text editor, then
  scroll around on the text editor. When I Alt-Tab back to Google
  Chrome, my first scroll leads to the page jumping by a large amount
  either up or down before resuming regular mouse scrolling. It is only
  this initial scroll after switching tabs that jumps like this. It also
  happens regardless of whether I use a mouse or the touch pad.

  I also notice, given the same scenario, if I scroll up on the text
  editor, the Google Chrome initial scroll jump will be upward. If I
  scroll down on the text editor, the Chrome jump will be downward. If I
  scroll a lot in the text editor, the Chrome jump will be large. If I
  scroll a small amount in the text editor, the Chrome jump will be
  small.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 20 17:17:39 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b9]
  InstallationDate: Installed on 2020-01-26 (54 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=7cfa547e-7b38-4467-9a1c-5f581ce738c1 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.24
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.43
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.24:bd01/07/2019:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.43:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.product.sku: 1WU65AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1860899] Re: Add extra information to tabs in folders

[Marco Aurélio Gonçalves Pinto]

Hello!

See the attachment.

Right-clicking on a folder tab in Windows allows to add/remove tabs.

See the tab for the video time and it is also possible for the
resolution but I wasn't able to make it appear.

** Attachment added: "windows10_folder_properties_20200127.png"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1860899/+attachment/5323317/+files/windows10_folder_properties_20200127.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/1860899

Title:
  Add extra information to tabs in folders

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Windows 10 allows to select in the tabs to show the resolution and
  length of the video/audio files.

  Could something similar be implemented in Ubuntu?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.4-0~ubuntu18.04.4
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 26 08:33:44 2020
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'244'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x541+102+146'"
  InstallationDate: Installed on 2020-01-07 (18 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1860899] [NEW] Add extra information to tabs in folders

[Marco Aurélio Gonçalves Pinto]

Public bug reported:

Windows 10 allows to select in the tabs to show the resolution and
length of the video/audio files.

Could something similar be implemented in Ubuntu?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.4-0~ubuntu18.04.4
ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-26-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 26 08:33:44 2020
GsettingsChanges:
 b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'244'
 b'org.gnome.nautilus.window-state' b'geometry' b"'890x541+102+146'"
InstallationDate: Installed on 2020-01-07 (18 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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

Title:
  Add extra information to tabs in folders

Status in nautilus package in Ubuntu:
  New

Bug description:
  Windows 10 allows to select in the tabs to show the resolution and
  length of the video/audio files.

  Could something similar be implemented in Ubuntu?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.4-0~ubuntu18.04.4
  ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 26 08:33:44 2020
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'244'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x541+102+146'"
  InstallationDate: Installed on 2020-01-07 (18 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1857027] Re: Bytes are not correctly converted to GygaBytes

[marco]

Oh interesting!.

Always thought it should have been this way, but I thought it wasn't
standard.

Thanks!

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

Title:
  Bytes are not correctly converted to GygaBytes

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  6,230,444,800 bytes, are converted to 6.2GB, instead of 5.80GB

  This happens in the *folder view* and in the properties of the file

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.4-0~ubuntu18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 19 11:12:55 2019
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2019-01-31 (321 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1857027] [NEW] Bytes are not correctly converted to GygaBytes

[marco]

Public bug reported:

6,230,444,800 bytes, are converted to 6.2GB, instead of 5.80GB

This happens in the *folder view* and in the properties of the file

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.4-0~ubuntu18.04.4
ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Dec 19 11:12:55 2019
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2019-01-31 (321 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug bionic

** Attachment added: "Screenshot from 2019-12-19 11-21-32.png"
   
https://bugs.launchpad.net/bugs/1857027/+attachment/5314052/+files/Screenshot%20from%202019-12-19%2011-21-32.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/1857027

Title:
  Bytes are not correctly converted to GygaBytes

Status in nautilus package in Ubuntu:
  New

Bug description:
  6,230,444,800 bytes, are converted to 6.2GB, instead of 5.80GB

  This happens in the *folder view* and in the properties of the file

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.4-0~ubuntu18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 19 11:12:55 2019
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2019-01-31 (321 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1687436] Re: cupsd uses 100% CPU

[Marco Gaiarin]

I can confirm that.

CUPS got 100% CPU in an environment where i've some KONICA-MINOLTA MFP,
and i've the same errors in logs:

W [02/Aug/2019:13:01:21 +0200] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'Konica_Minolta_BizHub_C224e_vdmsv1-Gray..\' already exists
W [02/Aug/2019:13:01:21 +0200] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'Konica_Minolta_BizHub_C224e_vdmsv1-CMYK..\' already exists
W [02/Aug/2019:13:01:27 +0200] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'Konica_Minolta_BizHub_C454e_vdmsv1-Gray..\' already exists
W [02/Aug/2019:13:01:27 +0200] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'Konica_Minolta_BizHub_C454e_vdmsv1-CMYK..\' already exists
W [02/Aug/2019:13:01:33 +0200] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'Konica_Minolta_BizHub_C458_vdmsv1-Gray..\' already exists
W [02/Aug/2019:13:01:33 +0200] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'Konica_Minolta_BizHub_C458_vdmsv1-CMYK..\' already exists

Note that i move my PC between at least 3 environment (home, work site
1, work site 2) with similar configuration, and only on 'site 1' (where
i've KONICA-MINOLTA MFP i got 100% CPU.

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

Title:
  cupsd uses 100% CPU

Status in cups-filters package in Ubuntu:
  Fix Released

Bug description:
  cupsd constantly uses 100% of CPU (one core) when cups-browsed is
  running too. Network printer queues are autodetected and available.
  Printer listing is usually delayed by approx. 30s.

  lsb_release -rd:
  Description:  Ubuntu 17.04
  Release:  17.04

  apt-cache policy cups
  cups:
Installed: 2.2.2-1ubuntu1
Candidate: 2.2.2-1ubuntu1
Version table:
   *** 2.2.2-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  apt-cache policy cups-browsed
  cups-browsed:
Installed: 1.13.4-1ubuntu1
Candidate: 1.13.4-1ubuntu1
Version table:
   *** 1.13.4-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1687436/+subscriptions

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

[Desktop-packages] [Bug 1778069] Re: [xfce] nautilus don't open files if set as default file manager

[Marco Lopilato]

Will the fix be released for 18.04 also? Thx

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

Title:
  [xfce] nautilus don't open files if set as default file manager

Status in Exo:
  Fix Released
Status in exo package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Invalid
Status in xubuntu-default-settings package in Ubuntu:
  Fix Released
Status in nautilus package in Debian:
  New

Bug description:
  If Nautilus is set as the preferred file manager with exo-preferred-
  applications, it no longer opens files. It opens only directories,
  .desktop files and executable files. Trying to open a file, be using
  Enter or with double mouse click, as a text file or a video makes
  Nautilus window blink for a instant and nothing happens. To be able to
  open the files, it's needed to choose to open with another application
  and then choose the application.

  Once Nautilus is unset as the default file manager (Thunar is chosen,
  for example), it starts to work fine again, opening files properly.

  Nautilus' Debian Sid version do not have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  Uname: Linux 4.17.2-041702-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jun 21 10:55:41 2018
  InstallationDate: Installed on 2017-06-13 (372 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (244 days ago)
  usr_lib_nautilus: dropbox 2015.10.28

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

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

[Desktop-packages] [Bug 1785644] Re: Squared number (N^2) of copies printed

[Marco Simondo]

Good morning

We are experiencing on Ubuntu 18.04 with CUPS 2.2.7 this strange problem.
We use Ubuntu 18.04 clients to print to raw queues on a Ubuntu 18.04 server.
We do this for print accounting and control in our application.

We do many many tests, on Ubuntu 18.04, Kubuntu 18.04, Ubuntu 19.04, and
to finish, on Debian 9 (with CUPS 2.2.1)

For our testing, we create a printer called MYREMOTEPRINTER .
This is the name of the raw queue on server and, to keep it simple, the name of 
the printer for the clients.

Each time we print a document (from Firefox, evince, and many others 
applications), asking 2 ou more copies, we get 2^2, or 3^3 and so on copies.
Same behaviour if we print from command line ("lp -d MYREMOTEPRINTER -n 2 
MyDocument.PDF").

A document of 3 pages, 2 copies, will generate 3 * 2^2 pages = 12 pages instead 
of 6.
And if you want to print just a unique page, 10 copies, you will get 100 pages !

This problem did not exist on Ubuntu 14.04 with CUPS 1.7.2

The same problem has been opened (and closed, without any explanations) on 
GitHub here :
https://github.com/apple/cups/issues/5015
(were I posted too this comment)

We discovered also that if we declare the remote printer as :
  lpd://REMOTESERVER/MYREMOTEPRINTER
instead of
  ipp://REMOTESERVER/printers/MYREMOTEPRINTER

(and declare cups-ldp in inetd.conf, of course) problem is not present.

This doesn't seem just an Ubuntu bug (Debian has same problem), but if
it is a CUPS problem, I don't understand why it has been closed by its
developer.

Do you think this bug could be solved in current Ubuntu 18.04 LTS ?

Best regards
Marco

** Bug watch added: github.com/apple/cups/issues #5015
   https://github.com/apple/cups/issues/5015

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

Title:
  Squared number (N^2) of copies printed

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  I wanted to print 4 copies of a 3-pages document (12 pages total) and
  instead 16 copies (48 pages) were printed.

  Using latest Ubuntu with all updates, Gnome Shell on Xorg, I opened a
  PDF file in Evince 3.28.2-1, clicked "Print", clicked "+" button
  several times to increase the number of copies to 4, and sent it
  printing on Xerox_AltaLink_C8030. That network printer was previously
  auto-detected with default drivers.

  access_log only has one line at that time:
  localhost - - [06/Aug/2018:16:28:14 +0200] "POST 
/printers/Xerox_AltaLink_C8030 HTTP/1.1" 200 64269 Print-Job successful-ok

  error_log doesn’t have anything related.

  I am attaching the print job captured per
  https://wiki.ubuntu.com/DebuggingPrintingProblems#Capturing_print_job_data

  On the cups page with completed jobs
  http://localhost:631/printers/Xerox_AltaLink_C8030?which_jobs=completed
  the amount of pages is shown as "48".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  6 16:12:58 2018
  InstallationDate: Installed on 2018-05-02 (96 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lpstat:
   device for Lexmark_M3150_10_: ipp://ET0021B7C1D744.local:631/ipp/print
   device for WorkCentre-7120: socket://10.2.20.114
   device for Xerox_AltaLink_C8030: ipp://XRX9C934E98F100.local:631/ipp/print
   device for Xerox_VersaLink_C505_8c_ab_2c_4_: 
ipps://XC8cab2c.local:631/ipp/print
   device for Xerox_VersaLink_C505_8c_ab_50_7_: 
ipps://XC8cab50.local:631/ipp/print
  MachineType: Dell Inc. OptiPlex 7020
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox_VersaLink_C505_8c_ab_50_7_.ppd', 
'/etc/cups/ppd/Xerox_AltaLink_C8030.ppd', 
'/etc/cups/ppd/Xerox_VersaLink_C505_8c_ab_2c_4_.ppd', 
'/etc/cups/ppd/WorkCentre-7120.ppd', '/etc/cups/ppd/Lexmark_M3150_10_.ppd'] 
failed with exit code 2: grep: 
/etc/cups/ppd/Xerox_VersaLink_C505_8c_ab_50_7_.ppd: Permission denied
   Xerox_AltaLink_C8030: AltaLink C8030
   grep: /etc/cups/ppd/Xerox_VersaLink_C505_8c_ab_2c_4_.ppd: Permission denied
   grep: /etc/cups/ppd/WorkCentre-7120.ppd: Permission denied
   grep: /etc/cups/ppd/Lexmark_M3150_10_.ppd: Permission denied
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/fish
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=3fd92192-fa04-40ea-ac71-f1dff8e153f7 ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 02YYK5
  dmi.board.vendo

[Desktop-packages] [Bug 1825710] Re: Remove "Application is ready" notification

[Marco Aurélio Gonçalves Pinto]

This window that keeps appearing is very annoying.

Can't a setting be created in the OS with a CheckBox gadget to
enable/disable the warning?

"blah blah is ready" is very annoying.

:-(


** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825710/+attachment/5270401/+files/VirtualBox_Ubuntu%2018.04.2%20LTS%20x64%20%28PureBasic%29%20-%202019-06-12.png

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

Title:
  Remove "Application is ready" notification

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The "Application is ready" notification is pointless, really. Say, I
  click on the open downloads folder button in Firefox and GNOME Shell
  gives me a notification saying "Application is ready" but doesn't open
  the notification. I'm totally expecting an app to open because I
  actively initiated it.

  As a workaround, I'm using a GNOME extensions "Focus my Window" which
  removes the "Application is ready" message and focuses the app window
  automatically. However, this cannot be treated as a solution.

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

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

[Desktop-packages] [Bug 49348] Re: List view in Nautilus does not allow dragging a selection by mouse

[Marco Aurélio Gonçalves Pinto]

Ubuntu 19.04 behaviour

** Attachment added: "Ubuntu 19.04 behaviour"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/49348/+attachment/5261179/+files/ub1904_drag_mouse_20190503.mp4

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

Title:
  List view in Nautilus does not allow dragging a selection by mouse

Status in GTK+:
  New
Status in Nautilus:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  When viewing files in Nautilus one can drag a rectangle around them to
  mark certain files. This is not possible in the list view of Nautilus
  even though there is usually a large white space in folders with few
  files that can make a user believe that dragging with the mouse there
  would produce the same rectangle as in icon view. I do it all the time
  by habit, and it is very annoying.

  Proposal:
  * Make it possible to drag a rectangle in list view. The problem is that 
starting to drag on a list item moves that item. Konqueror has solved this that 
you have to drag on the item name itself to move, else a rectangle marquee is 
started. Personally I find this quite efficient but may be annoying for less 
experienced users...

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

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

[Desktop-packages] [Bug 49348] Re: List view in Nautilus does not allow dragging a selection by mouse

[Marco Aurélio Gonçalves Pinto]

Here are two video captures, one in Windows 10 and other in Ubuntu
19.04.


** Attachment added: "Windows 10 behaviour"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/49348/+attachment/5261178/+files/win10_drag_mouse_20190503.mp4

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

Title:
  List view in Nautilus does not allow dragging a selection by mouse

Status in GTK+:
  New
Status in Nautilus:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  When viewing files in Nautilus one can drag a rectangle around them to
  mark certain files. This is not possible in the list view of Nautilus
  even though there is usually a large white space in folders with few
  files that can make a user believe that dragging with the mouse there
  would produce the same rectangle as in icon view. I do it all the time
  by habit, and it is very annoying.

  Proposal:
  * Make it possible to drag a rectangle in list view. The problem is that 
starting to drag on a list item moves that item. Konqueror has solved this that 
you have to drag on the item name itself to move, else a rectangle marquee is 
started. Personally I find this quite efficient but may be annoying for less 
experienced users...

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

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

[Desktop-packages] [Bug 1774957] Re: Network icons in status menu disappearing

[Marco Ferretti]

Following up on #30 and #29 I can confirm that ubuntu 18.04.2 is working
fine with the patch from comment #23

Thanks a lot for the support !

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

Title:
  Network icons in status menu disappearing

Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Disco:
  Invalid

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

  ---

  Ever since the update to Ubuntu 18.04 I'm having issues with the
  status menu at the top right of the screen.

  Normally you'd have a wired network connection icon displayed at the top 
without opening the menu. In my case it is not displayed half of the time. In 
the menu list no icon nor label is displayed for the wired connection menu item.
  When talking about half of the time it means that I can randomly make it 
display again when removing the USB network adapter and reconnecting it e.g.
  This does not work reliably though.

  When connecting to a VPN, normally you'd get an additional icon at the
  top. This is not the case any more, nor does the switch behind an
  activated VPN turns change to an active state. The result is that you
  can activate a VPN using the switch, but you can verify that it is
  activated, nor can you de-active the VPN through the menu. This does
  change in settings though.

  Wireless settings are no longer displayed in the menu at all. So no
  way to activate it or connect to a specific network.

  I tried reconfiguring (dpkg-reconfigure) gnome-shell as well as
  network-manager-gnome, to no avail.

  Attached you'll find a screenshot illustrating the issue. You'll see
  two icons missing to the left of the volume icon, as well as the
  wireless menu missing completely and no icon and text label for the
  wired connection menu item.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  4 10:47:05 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-07 (604 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (3 days ago)

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

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

[Desktop-packages] [Bug 1774957] Re: Network icons in status menu disappearing

[Marco Ferretti]

Hi Daniel,

will install the patch later today and let you know.

Thanks for pointing me to a possible solution (I completely missed it).

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

Title:
  Network icons in status menu disappearing

Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Disco:
  Invalid

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

  ---

  Ever since the update to Ubuntu 18.04 I'm having issues with the
  status menu at the top right of the screen.

  Normally you'd have a wired network connection icon displayed at the top 
without opening the menu. In my case it is not displayed half of the time. In 
the menu list no icon nor label is displayed for the wired connection menu item.
  When talking about half of the time it means that I can randomly make it 
display again when removing the USB network adapter and reconnecting it e.g.
  This does not work reliably though.

  When connecting to a VPN, normally you'd get an additional icon at the
  top. This is not the case any more, nor does the switch behind an
  activated VPN turns change to an active state. The result is that you
  can activate a VPN using the switch, but you can verify that it is
  activated, nor can you de-active the VPN through the menu. This does
  change in settings though.

  Wireless settings are no longer displayed in the menu at all. So no
  way to activate it or connect to a specific network.

  I tried reconfiguring (dpkg-reconfigure) gnome-shell as well as
  network-manager-gnome, to no avail.

  Attached you'll find a screenshot illustrating the issue. You'll see
  two icons missing to the left of the volume icon, as well as the
  wireless menu missing completely and no icon and text label for the
  wired connection menu item.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  4 10:47:05 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-07 (604 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (3 days ago)

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

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

[Desktop-packages] [Bug 1774957] Re: Network icons in status menu disappearing

[Marco Ferretti]

p.s.: restarting gnome-shell (with SIGQUIT) works as a temporary patch.

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

Title:
  Network icons in status menu disappearing

Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Disco:
  Invalid

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

  ---

  Ever since the update to Ubuntu 18.04 I'm having issues with the
  status menu at the top right of the screen.

  Normally you'd have a wired network connection icon displayed at the top 
without opening the menu. In my case it is not displayed half of the time. In 
the menu list no icon nor label is displayed for the wired connection menu item.
  When talking about half of the time it means that I can randomly make it 
display again when removing the USB network adapter and reconnecting it e.g.
  This does not work reliably though.

  When connecting to a VPN, normally you'd get an additional icon at the
  top. This is not the case any more, nor does the switch behind an
  activated VPN turns change to an active state. The result is that you
  can activate a VPN using the switch, but you can verify that it is
  activated, nor can you de-active the VPN through the menu. This does
  change in settings though.

  Wireless settings are no longer displayed in the menu at all. So no
  way to activate it or connect to a specific network.

  I tried reconfiguring (dpkg-reconfigure) gnome-shell as well as
  network-manager-gnome, to no avail.

  Attached you'll find a screenshot illustrating the issue. You'll see
  two icons missing to the left of the volume icon, as well as the
  wireless menu missing completely and no icon and text label for the
  wired connection menu item.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  4 10:47:05 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-07 (604 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (3 days ago)

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

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

[Desktop-packages] [Bug 1774957] Re: Network icons in status menu disappearing

[Marco Ferretti]

I am still experiencing the issue on ubuntu 18.04.4 :

dpkg -s gnome-shell
Package: gnome-shell
Status: install ok installed
Priority: optional
Section: universe/gnome
Installed-Size: 7350
Maintainer: Ubuntu Developers 
Architecture: amd64
Version: 3.28.3-0ubuntu0.18.04.4
Provides: notification-daemon, polkit-1-auth-agent
Depends: libatk-bridge2.0-0 (>= 2.5.3), libatk1.0-0 (>= 1.12.4), libc6 (>= 
2.14), libcairo2 (>= 1.14.0), libcanberra-gtk3-0 (>= 0.25), libcanberra0 (>= 
0.2), libcroco3 (>= 0.6.2), libecal-1.2-19 (>= 3.17), libedataserver-1.2-23 (>= 
3.17.2), libgcr-base-3-1 (>= 3.8.0), libgdk-pixbuf2.0-0 (>= 2.22.0), 
libgirepository-1.0-1 (>= 1.35.9), libgjs0-libmozjs-52-0, libgjs0g (>= 1.52.1), 
libglib2.0-0 (>= 2.53.0), libgstreamer1.0-0 (>= 1.4.0), libgtk-3-0 (>= 3.21.6), 
libical3 (>= 3.0.0), libjson-glib-1.0-0 (>= 0.13.2), libmutter-2-0 (>= 3.28.3), 
libnm0 (>= 1.0.0), libpango-1.0-0 (>= 1.14.0), libpangocairo-1.0-0 (>= 1.14.0), 
libpolkit-agent-1-0 (>= 0.99), libpolkit-gobject-1-0 (>= 0.94), 
libpulse-mainloop-glib0 (>= 0.99.1), libpulse0 (>= 0.99.1), libsecret-1-0 (>= 
0.7), libstartup-notification0 (>= 0.11), libsystemd0, libx11-6, libxfixes3, 
evolution-data-server (>= 3.17.2), gir1.2-accountsservice-1.0, gir1.2-atspi-2.0 
(>= 2.9.91), gir1.2-freedesktop, gir1.2-gdesktopenums-3.0 (>= 3.12), 
gir1.2-geoclue-2.0, gir1.2-gcr-3 (>= 3.7.5), gir1.2-gdm-1.0 (>= 3.18.2), 
gir1.2-glib-2.0 (>= 1.45.3), gir1.2-gnomebluetooth-1.0 (>= 3.12.0), 
gir1.2-gnomedesktop-3.0 (>= 3.12.0), gir1.2-gtk-3.0 (>= 3.16), 
gir1.2-gweather-3.0, gir1.2-ibus-1.0 (>= 1.5.2), gir1.2-mutter-2 (>= 3.27.91), 
gir1.2-nm-1.0, gir1.2-nma-1.0, gir1.2-pango-1.0, gir1.2-polkit-1.0, 
gir1.2-rsvg-2.0, gir1.2-soup-2.4 (>= 2.40.1), gir1.2-upowerglib-1.0 (>= 0.99), 
gjs (>= 1.47.90), gnome-settings-daemon (>= 3.16.0), gnome-shell-common (= 
3.28.3-0ubuntu0.18.04.4), ubuntu-wallpapers, gsettings-desktop-schemas (>= 
3.21.3), mutter (>= 3.27.91), python3, libglib2.0-bin (>= 2.53.0)
Recommends: xserver-xorg-legacy, bolt (>= 0.2), gkbd-capplet, 
gnome-control-center, gnome-user-guide, iio-sensor-proxy, unzip, ubuntu-session 
| gnome-session
Suggests: gir1.2-telepathyglib-0.12, gir1.2-telepathylogger-0.2 (>= 0.8.0), 
chrome-gnome-shell, gdm3 (>= 3.10.0.1-3~), gnome-themes-standard-data, 
switcheroo-control
Breaks: gdm3 (<< 3.19.92), gnome-session (<< 3.19)
Conflicts: gnome-screensaver (<< 3.6)
Description: graphical shell for the GNOME desktop
 The GNOME Shell provides core interface functions like switching
 windows, launching applications or see your notifications. It takes
 advantage of the capabilities of modern graphics hardware and
 introduces innovative user interface concepts to provide a
 delightful and easy to use experience. GNOME Shell is the defining
 technology of the GNOME 3 user experience.
Homepage: https://wiki.gnome.org/Projects/GnomeShell
Original-Maintainer: Debian GNOME Maintainers 


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

Title:
  Network icons in status menu disappearing

Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Disco:
  Invalid

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

  ---

  Ever since the update to Ubuntu 18.04 I'm having issues with the
  status menu at the top right of the screen.

  Normally you'd have a wired network connection icon displayed at the top 
without opening the menu. In my case it is not displayed half of the time. In 
the menu list no icon nor label is displayed for the wired connection menu item.
  When talking about half of the time it means that I can randomly make it 
display again when removing the USB network adapter and reconnecting it e.g.
  This does not work reliably though.

  When connecting to a VPN, normally you'd get an additional icon at the
  top. This is not the case any more, nor does the switch behind an
  activated VPN turns change to an active state. The result is that you
  can activate a VPN using the switch, but you can verify that it is
  activated, nor can you de-active the VPN through the menu. This does
  change in settings though.

  Wireless settings are no longer displayed in the menu at all. So no
  way to activate it or connect to a specific network.

  I tried reconfiguring (dpkg-reconfigure) gnome-shell as well as
  network-manager-gnome, to no avail.

  Attached you'll find a screenshot illustrating the issue. You'll see
  two icons missing to the left of the volume icon, as well as the
  wireless menu missing completely and no icon and text label for the
  wired connection menu item.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 

[Desktop-packages] [Bug 1819945] [NEW] nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE()

[Marco Giannini]

Public bug reported:

Ubuntu 19.04 dev
Nautilus 3.31.90-stable

The crash occurred when I clicked the trash can icon on the desktop

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: nautilus 1:3.31.90-1ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 13 18:08:09 2019
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 
InstallationDate: Installed on 2019-02-26 (14 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226)
ProcCmdline: /usr/bin/nautilus --gapplication-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
SegvAnalysis:
 Segfault happened at: 0x557faa5f70d9 :  mov
(%rbx),%rdi
 PC (0x557faa5f70d9) ok
 source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 nautilus_view_get_selection ()
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in nautilus_view_get_selection()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:
 
usr_lib_nautilus:

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


** Tags: amd64 apport-crash disco

** Information type changed from Private to Public

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

Title:
  nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE()

Status in nautilus package in Ubuntu:
  New

Bug description:
  Ubuntu 19.04 dev
  Nautilus 3.31.90-stable

  The crash occurred when I clicked the trash can icon on the desktop

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.31.90-1ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 13 18:08:09 2019
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-02-26 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x557faa5f70d9 :
mov(%rbx),%rdi
   PC (0x557faa5f70d9) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   nautilus_view_get_selection ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in nautilus_view_get_selection()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:
   
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1687436] Re: cupsd uses 100% CPU

[Marco Gaiarin]

I think i'm hitting this bug too.

cups go CPU 100%, until i restart them.

Ubuntu Bionic, cups 2.2.7-1ubuntu2.3, cups-filters 1.20.2-0ubuntu3.

I can safely install disco packages on bionic? There will be some
backports? Or some workaround for bionic.

Thanks.

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

Title:
  cupsd uses 100% CPU

Status in cups-filters package in Ubuntu:
  Fix Released

Bug description:
  cupsd constantly uses 100% of CPU (one core) when cups-browsed is
  running too. Network printer queues are autodetected and available.
  Printer listing is usually delayed by approx. 30s.

  lsb_release -rd:
  Description:  Ubuntu 17.04
  Release:  17.04

  apt-cache policy cups
  cups:
Installed: 2.2.2-1ubuntu1
Candidate: 2.2.2-1ubuntu1
Version table:
   *** 2.2.2-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  apt-cache policy cups-browsed
  cups-browsed:
Installed: 1.13.4-1ubuntu1
Candidate: 1.13.4-1ubuntu1
Version table:
   *** 1.13.4-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1687436/+subscriptions

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

[Desktop-packages] [Bug 1813542] [NEW] launcher is available on locked screen

[Marco Tanner]

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

Public bug reported:

The launcher bar is accessible to me even though the screen is locked. I
was able to take a screenshot via right-clicking the Shutter icon and
selecting 'Capture the entire screen'. See attachment. I'm able to
launch new applications via launcher and close open ones. (New windows
aren't shown, but are open after unlocking).

Re-locking yields the same situation again. I have yet to reboot to see
if the problem persists.

The expectation is that the launcher bar is not available whilst the
screen is locked.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdm3 3.28.3-0ubuntu18.04.3
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 28 10:05:38 2019
InstallationDate: Installed on 2018-04-20 (282 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180420)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gdm3 (Ubuntu)
 Importance: High
 Status: New


** Tags: amd64 apport-bug bionic

** Attachment added: "Screenshot of bad behaviour"
   
https://bugs.launchpad.net/bugs/1813542/+attachment/5233169/+files/Workspace%201_167.png

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

Title:
  launcher is available on locked screen

Status in gdm3 package in Ubuntu:
  New

Bug description:
  The launcher bar is accessible to me even though the screen is locked.
  I was able to take a screenshot via right-clicking the Shutter icon
  and selecting 'Capture the entire screen'. See attachment. I'm able to
  launch new applications via launcher and close open ones. (New windows
  aren't shown, but are open after unlocking).

  Re-locking yields the same situation again. I have yet to reboot to
  see if the problem persists.

  The expectation is that the launcher bar is not available whilst the
  screen is locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 28 10:05:38 2019
  InstallationDate: Installed on 2018-04-20 (282 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180420)
  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/1813542/+subscriptions

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

[Desktop-packages] [Bug 1812279] [NEW] The ubuntu dock (ubuntu-dock-extension) appears when the screen lock is activated, enabling the access to the applications.

[Marco Furlan]

Public bug reported:

The problem is the same as reported in https://github.com/micheleg/dash-
to-dock/issues/649.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.1
Uname: Linux 4.16.3-041603-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 17 21:35:02 2019
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-osp1-20150720-0
InstallationDate: Installed on 2016-07-25 (906 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
PackageArchitecture: all
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: Upgraded to bionic on 2018-07-18 (183 days ago)

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


** Tags: amd64 apport-bug bionic

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

Title:
  The ubuntu dock (ubuntu-dock-extension) appears when the screen lock
  is activated, enabling the access to the applications.

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

Bug description:
  The problem is the same as reported in https://github.com/micheleg
  /dash-to-dock/issues/649.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.1
  Uname: Linux 4.16.3-041603-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 17 21:35:02 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  InstallationDate: Installed on 2016-07-25 (906 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to bionic on 2018-07-18 (183 days ago)

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

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

[Desktop-packages] [Bug 1806983] Re: desktop environment resumes badly when resuming from suspend mode

[Marco]

Yes, I'm using some extensions. I'll try to deactivate them all and
report if issue exists anymore.

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

Title:
  desktop environment resumes badly when resuming from suspend mode

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

Bug description:
  I've a problem when resuming from suspend mode and try to unlock my
  pc.

  Expected Behavior:

  Interface shows correctly after resuming from suspend mode.

  Real Behavior:

  Interface shows badly after resume PC from suspend.
  unlock interface doesn't shows at all; instead of it, desktop (or last 
application) is shown.

  Have to re-suspend PC and re-resume, so the unlock interface is showed
  but application's bar shows like pc is still locked, so it doesn't
  show real opened applications.

  "resize and move windows" shortcuts doesn't work either.

  How to reproduce bug:

  Go to suspend mode, resume. mostly the bug doesn't appear, but
  sometimes yes.

  Distro Description: Ubuntu 18.10

Installed: 3.30.1-1ubuntu5
Candidate:  3.30.1-1ubuntu5
Version Table:
   *** 3.30.1-1ubuntu5 500
  500 http://it.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.1-1ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  5 20:16:03 2018
  InstallationDate: Installed on 2017-10-21 (410 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (46 days ago)
  mtime.conffile..etc.gdm3.Init.Default: 2017-11-21T14:48:20.846402
  mtime.conffile..etc.gdm3.custom.conf: 2018-10-20T16:29:04.442996

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

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

[Desktop-packages] [Bug 1807704] [NEW] chromium browser crashe when saving image with name and when trying to export bookmarks

[Marco]

Public bug reported:

On ubuntu 16,04 since a couple of weeks chromium browser crashes when
saving image with name  and when trying to export bookmarks.

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

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

Title:
  chromium browser crashe when saving image with name  and when trying
  to export bookmarks

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  On ubuntu 16,04 since a couple of weeks chromium browser crashes when
  saving image with name  and when trying to export bookmarks.

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

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

[Desktop-packages] [Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking

[Marco]

My report (1806983) is slightly different and more problematic: when the bug 
occurs, the interface, the app bar now keeps beeing buggy until I reboot and 
the unlock interface doesn't shows at all even if I re-put on suspend and 
re-resume.
I had the "desktop showed for one second" bug but it this case I have the "lock 
screen not showed at all" one

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

Title:
  Screen contents revealed briefly on resume, before even unlocking

Status in GNOME Shell:
  In Progress
Status in Ubuntu GNOME:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Xenial:
  Fix Released
Status in gnome-shell package in Debian:
  Confirmed

Bug description:
  [Impact]

  When lock is enabled, the screen doesn't get blank/covered by
  lockscreen before suspending, thus on early resume the content might
  be shown.

  Video showing the bug: https://youtu.be/dDOgtK1MldI

  Reproduced on Ubuntu 2015.10, Ubuntu 2014.04

  [Test case]

  1. Work on highly secret files
  2. Close the lid of your laptop and go have a break
  3. Anyone who opens the lid of the laptop can see the secret files for a half 
second before the lock screen appears

  [Possible Regression]

  Content on screen isn't painted anymore and screen stays black.

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

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

[Desktop-packages] [Bug 1806983] [NEW] desktop environment resumes badly when resuming from suspend mode

[Marco]

Public bug reported:

I've a problem when resuming from suspend mode and try to unlock my pc.

Expected Behavior:

Interface shows correctly after resuming from suspend mode.

Real Behavior:

Interface shows badly after resume PC from suspend.
unlock interface doesn't shows at all; instead of it, desktop (or last 
application) is shown.

Have to re-suspend PC and re-resume, so the unlock interface is showed
but application's bar shows like pc is still locked, so it doesn't show
real opened applications.

"resize and move windows" shortcuts doesn't work either.

How to reproduce bug:

Go to suspend mode, resume. mostly the bug doesn't appear, but sometimes
yes.

Distro Description: Ubuntu 18.10

  Installed: 3.30.1-1ubuntu5
  Candidate:  3.30.1-1ubuntu5
  Version Table:
 *** 3.30.1-1ubuntu5 500
500 http://it.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gdm3 3.30.1-1ubuntu5
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec  5 20:16:03 2018
InstallationDate: Installed on 2017-10-21 (410 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: Upgraded to cosmic on 2018-10-20 (46 days ago)
mtime.conffile..etc.gdm3.Init.Default: 2017-11-21T14:48:20.846402
mtime.conffile..etc.gdm3.custom.conf: 2018-10-20T16:29:04.442996

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


** Tags: amd64 apport-bug cosmic

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

Title:
  desktop environment resumes badly when resuming from suspend mode

Status in gdm3 package in Ubuntu:
  New

Bug description:
  I've a problem when resuming from suspend mode and try to unlock my
  pc.

  Expected Behavior:

  Interface shows correctly after resuming from suspend mode.

  Real Behavior:

  Interface shows badly after resume PC from suspend.
  unlock interface doesn't shows at all; instead of it, desktop (or last 
application) is shown.

  Have to re-suspend PC and re-resume, so the unlock interface is showed
  but application's bar shows like pc is still locked, so it doesn't
  show real opened applications.

  "resize and move windows" shortcuts doesn't work either.

  How to reproduce bug:

  Go to suspend mode, resume. mostly the bug doesn't appear, but
  sometimes yes.

  Distro Description: Ubuntu 18.10

Installed: 3.30.1-1ubuntu5
Candidate:  3.30.1-1ubuntu5
Version Table:
   *** 3.30.1-1ubuntu5 500
  500 http://it.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.1-1ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  5 20:16:03 2018
  InstallationDate: Installed on 2017-10-21 (410 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (46 days ago)
  mtime.conffile..etc.gdm3.Init.Default: 2017-11-21T14:48:20.846402
  mtime.conffile..etc.gdm3.custom.conf: 2018-10-20T16:29:04.442996

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

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

[Desktop-packages] [Bug 1805503] [NEW] Files and folders search doesn't work properly with Nautilus 3.30 from the GNOME 3 Staging PPA

[Marco]

Public bug reported:

On my Ubuntu 18.10 I upgraded Nautilus from the GNOME 3 Staging PPA. But
with Nautilus 3.30, when I try to search my files and my folders from
the activity view, I almost never get results. With Nautilus 3.26 the
files and folders search works flawlessly, but with Nautilus 3.30 does
not work properly neither with Tracker 2.0.3 nor with Tracker 2.1.3 from
the GNOME 3 Staging PPA.

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

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


** Tags: files folders nautilus search tracker

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

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

Title:
  Files and folders search doesn't work properly with Nautilus 3.30 from
  the GNOME 3 Staging PPA

Status in nautilus package in Ubuntu:
  New
Status in tracker package in Ubuntu:
  New

Bug description:
  On my Ubuntu 18.10 I upgraded Nautilus from the GNOME 3 Staging PPA.
  But with Nautilus 3.30, when I try to search my files and my folders
  from the activity view, I almost never get results. With Nautilus 3.26
  the files and folders search works flawlessly, but with Nautilus 3.30
  does not work properly neither with Tracker 2.0.3 nor with Tracker
  2.1.3 from the GNOME 3 Staging PPA.

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

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

[Desktop-packages] [Bug 1798012] [NEW] package ppp 2.4.7-1+2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Marco Gomes]

Public bug reported:

Failure during upgrade

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ppp 2.4.7-1+2ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155
Uname: Linux 4.4.0-138-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Tue Oct 16 00:57:59 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.28
SourcePackage: ppp
Title: package ppp 2.4.7-1+2ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2018-10-16 (0 days ago)
mtime.conffile..etc.init.d.pppd-dns: 2014-11-25T19:42:39
mtime.conffile..etc.ppp.options: 2014-11-25T19:43:02

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


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

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

Title:
  package ppp 2.4.7-1+2ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in ppp package in Ubuntu:
  New

Bug description:
  Failure during upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ppp 2.4.7-1+2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155
  Uname: Linux 4.4.0-138-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Tue Oct 16 00:57:59 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.28
  SourcePackage: ppp
  Title: package ppp 2.4.7-1+2ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-10-16 (0 days ago)
  mtime.conffile..etc.init.d.pppd-dns: 2014-11-25T19:42:39
  mtime.conffile..etc.ppp.options: 2014-11-25T19:43:02

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

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

[Desktop-packages] [Bug 1797553] Re: file-roller extract and replace does not replace

[Marco van Zwetselaar]

Sorry about that, this is 18.04 bionic.  Have tagged the bug.

** Tags added: bionic

** Description changed:

  When extracting a file over an existing file, clicking "Replace" in the
  dialog that asks to confirm overwriting a file, does not replace the
  file.
  
- Reproduce: 
+ Reproduce:
  - Open any archive (I've tested zip and 7z)
  - Right click a file and extract
  - Edit the extracted file so you can see that it will not be replaced
- - Right click the and extract the file again, to the same file name
+ - Right click and extract the file again, to the same file name
  - In the dialog asking whether to replace the file, click "Replace".
- - File confirms extraction, however the file was *not* replaced by the copy 
from the archive
+ - File roller confirms extraction, however the file was *not* replaced by the 
copy from the archive

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

Title:
  file-roller extract and replace does not replace

Status in file-roller package in Ubuntu:
  Incomplete

Bug description:
  When extracting a file over an existing file, clicking "Replace" in
  the dialog that asks to confirm overwriting a file, does not replace
  the file.

  Reproduce:
  - Open any archive (I've tested zip and 7z)
  - Right click a file and extract
  - Edit the extracted file so you can see that it will not be replaced
  - Right click and extract the file again, to the same file name
  - In the dialog asking whether to replace the file, click "Replace".
  - File roller confirms extraction, however the file was *not* replaced by the 
copy from the archive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1797553/+subscriptions

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

[Desktop-packages] [Bug 1797553] [NEW] file-roller extract and replace does not replace

[Marco van Zwetselaar]

Public bug reported:

When extracting a file over an existing file, clicking "Replace" in the
dialog that asks to confirm overwriting a file, does not replace the
file.

Reproduce: 
- Open any archive (I've tested zip and 7z)
- Right click a file and extract
- Edit the extracted file so you can see that it will not be replaced
- Right click the and extract the file again, to the same file name
- In the dialog asking whether to replace the file, click "Replace".
- File confirms extraction, however the file was *not* replaced by the copy 
from the archive

** Affects: file-roller (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  file-roller extract and replace does not replace

Status in file-roller package in Ubuntu:
  New

Bug description:
  When extracting a file over an existing file, clicking "Replace" in
  the dialog that asks to confirm overwriting a file, does not replace
  the file.

  Reproduce: 
  - Open any archive (I've tested zip and 7z)
  - Right click a file and extract
  - Edit the extracted file so you can see that it will not be replaced
  - Right click the and extract the file again, to the same file name
  - In the dialog asking whether to replace the file, click "Replace".
  - File confirms extraction, however the file was *not* replaced by the copy 
from the archive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1797553/+subscriptions

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

[Desktop-packages] [Bug 1791673] [NEW] Sound - no output device

[Marco]

Public bug reported:

I don't understand if this is a problem of pulseaudio or what.
I don't get any sound output and the GUI Sound doesn't show any output device. 
However, the sound card module is installed:

$ lsmod | grep snd_hda_intel
snd_hda_intel  40960  6
snd_hda_codec 126976  3 
snd_hda_intel,snd_hda_codec_generic,snd_hda_codec_realtek
snd_hda_core   81920  4 
snd_hda_intel,snd_hda_codec,snd_hda_codec_generic,snd_hda_codec_realtek
snd_pcm98304  4 
snd_hda_intel,snd_hda_codec,snd_usb_audio,snd_hda_core
snd81920  33 
snd_hda_intel,snd_hwdep,snd_seq,snd_hda_codec,snd_usb_audio,snd_timer,thinkpad_acpi,snd_rawmidi,snd_hda_codec_generic,snd_usbmidi_lib,snd_seq_device,snd_hda_codec_realtek,snd_pcm

The audio device is detected:

$ lspci -nnk | grep -A2 Audio
00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-H HD Audio 
[8086:a170] (rev 31)
 Subsystem: Lenovo Sunrise Point-H HD Audio [17aa:222e]
 Kernel driver in use: snd_hda_intel
 Kernel modules: snd_hda_intel

For reference, I am running Ubuntu 18.04.1 LTS, with pulseaudio
1:11.1-1ubuntu7.1, and this is my alsa-base.conf:

# autoloader aliases
install sound-slot-0 /sbin/modprobe snd-card-0
install sound-slot-1 /sbin/modprobe snd-card-1
install sound-slot-2 /sbin/modprobe snd-card-2
install sound-slot-3 /sbin/modprobe snd-card-3
install sound-slot-4 /sbin/modprobe snd-card-4
install sound-slot-5 /sbin/modprobe snd-card-5
install sound-slot-6 /sbin/modprobe snd-card-6
install sound-slot-7 /sbin/modprobe snd-card-7

# Cause optional modules to be loaded above generic modules
install snd /sbin/modprobe --ignore-install snd $CMDLINE_OPTS && { 
/sbin/modprobe --quiet --use-blacklist snd-ioctl32 ; /sbin/modprobe --quiet 
--use-blacklist snd-seq ; }
#
# Workaround at bug #499695 (reverted in Ubuntu see LP #319505)
install snd-pcm /sbin/modprobe --ignore-install snd-pcm $CMDLINE_OPTS && { 
/sbin/modprobe --quiet --use-blacklist snd-pcm-oss ; : ; }
install snd-mixer /sbin/modprobe --ignore-install snd-mixer $CMDLINE_OPTS && { 
/sbin/modprobe --quiet --use-blacklist snd-mixer-oss ; : ; }
install snd-seq /sbin/modprobe --ignore-install snd-seq $CMDLINE_OPTS && { 
/sbin/modprobe --quiet --use-blacklist snd-seq-midi ; /sbin/modprobe --quiet 
--use-blacklist snd-seq-oss ; : ; }
#
install snd-rawmidi /sbin/modprobe --ignore-install snd-rawmidi $CMDLINE_OPTS 
&& { /sbin/modprobe --quiet --use-blacklist snd-seq-midi ; : ; }
# Cause optional modules to be loaded above sound card driver modules
install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 $CMDLINE_OPTS 
&& { /sbin/modprobe --quiet --use-blacklist snd-emu10k1-synth ; }
install snd-via82xx /sbin/modprobe --ignore-install snd-via82xx $CMDLINE_OPTS 
&& { /sbin/modprobe --quiet --use-blacklist snd-seq ; }

# Load saa7134-alsa instead of saa7134 (which gets dragged in by it anyway)
install saa7134 /sbin/modprobe --ignore-install saa7134 $CMDLINE_OPTS && { 
/sbin/modprobe --quiet --use-blacklist saa7134-alsa ; : ; }
# Prevent abnormal drivers from grabbing index 0
options bt87x index=-2
options cx88_alsa index=-2
options saa7134-alsa index=-2
options snd-atiixp-modem index=-2
options snd-intel8x0m index=-2
options snd-via82xx-modem index=-2
options snd-usb-audio index=-2
options snd-usb-caiaq index=-2
options snd-usb-ua101 index=-2
options snd-usb-us122l index=-2
options snd-usb-usx2y index=-2
# Ubuntu #62691, enable MPU for snd-cmipci
options snd-cmipci mpu_port=0x330 fm_port=0x388
# Keep snd-pcsp from being loaded as first soundcard
options snd-pcsp index=-2
# Keep snd-usb-audio from beeing loaded as first soundcard
options snd-usb-audio index=-2
options snd-hda-intel model=generic

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 10 14:03:05 2018
InstallationDate: Installed on 2018-08-20 (21 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
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/18/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N1EET78W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20EQS6H100
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO

[Desktop-packages] R: [Bug 1542865] Re: Samsung ML1915 USB printer not detected by cups

[Marco]

Hello,

It's an old issue. I don't know if it was fixed. Anyway you could close
it.

Thanks
Marco

-Messaggio originale-
Da: boun...@canonical.com  Per conto di gf
Inviato: lunedì 20 agosto 2018 18:51
A: mvizz...@gmail.com
Oggetto: [Bug 1542865] Re: Samsung ML1915 USB printer not detected by cups

Hello Marco,
Thank you for submitting this bug and reporting a problem with cups.  You made 
this bug report some time ago and Ubuntu has been updated since then. 
 
Could you confirm that this is no longer a problem and that we can close the 
ticket? 
If it is still a problem, are you still interested in finding a solution to 
this bug? 
If you are, could you let us know, and in the current version, run the 
following (only once): 
apport-collect BUGNUMBER
and upload the updated logs and and any other logs that are relevant for this 
particular issue.  

Thank you again for helping make Ubuntu better. 
G
[Ubuntu Bug Squad volunteer triager]

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

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1542865

Title:
  Samsung ML1915 USB printer not detected by cups

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

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

Title:
  Samsung ML1915 USB printer not detected by cups

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  My printer stopped working. I tried to remove it from installed
  devices, but I'm unable to add it again since it isn't detected
  anymore. Some command outputs:

  tail -f /var/log/syslog:

  Feb  7 15:48:14 piubuntu udev-add-printer: PPD: 
lsb/usr/cupsfilters/textonly.ppd; Status: 3
  Feb  7 15:48:14 piubuntu kernel: [  803.704139] usb 3-2: USB disconnect, 
device number 15
  Feb  7 15:48:14 piubuntu kernel: [  803.704489] usblp0: removed
  Feb  7 15:48:14 piubuntu udev-configure-printer: remove 
/devices/pci:00/:00:1d.1/usb3/3-2
  Feb  7 15:48:22 piubuntu kernel: [  810.984138] audit: type=1400 
audit(1454856502.255:124): apparmor="DENIED" operation="signal" 
profile="/usr/sbin/cupsd" pid=3519 comm="cups-deviced" requested_mask="send" 
denied_mask="send" signal=term peer="unconfined"
  Feb  7 15:48:22 piubuntu kernel: [  810.984160] audit: type=1400 
audit(1454856502.255:125): apparmor="DENIED" operation="signal" 
profile="/usr/sbin/cupsd" pid=3519 comm="cups-deviced" requested_mask="send" 
denied_mask="send" signal=term peer="unconfined"
  Feb  7 15:48:22 piubuntu kernel: [  810.985259] audit: type=1400 
audit(1454856502.255:126): apparmor="DENIED" operation="signal" 
profile="/usr/sbin/cupsd" pid=2084 comm="cupsd" requested_mask="send" 
denied_mask="send" signal=term peer="unconfined"
  Feb  7 15:48:22 piubuntu kernel: [  810.985277] audit: type=1400 
audit(1454856502.255:127): apparmor="DENIED" operation="signal" 
profile="/usr/sbin/cupsd" pid=2084 comm="cupsd" requested_mask="send" 
denied_mask="send" signal=term peer="unconfined"
  Feb  7 15:48:22 piubuntu kernel: [  810.985495] parport0: lp tried to release 
parport when not owner
  Feb  7 15:48:22 piubuntu kernel: [  810.985910] parport0: lp tried to release 
parport when not owner
  Feb  7 15:49:14 piubuntu kernel: [  862.808058] usb 3-2: new full-speed USB 
device number 16 using uhci_hcd
  Feb  7 15:49:14 piubuntu kernel: [  862.983104] usb 3-2: New USB device 
found, idVendor=04e8, idProduct=3297
  Feb  7 15:49:14 piubuntu kernel: [  862.983115] usb 3-2: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
  Feb  7 15:49:14 piubuntu kernel: [  862.983122] usb 3-2: Product: ML-191x 
252x Series
  Feb  7 15:49:14 piubuntu kernel: [  862.983128] usb 3-2: Manufacturer: 
Samsung Electronics Co., Ltd.
  Feb  7 15:49:14 piubuntu kernel: [  862.983134] usb 3-2: SerialNumber: 
Z2L9BKEZ600533N.
  Feb  7 15:49:14 piubuntu kernel: [  862.990262] usblp 3-2:1.0: usblp0: USB 
Bidirectional printer dev 16 if 0 alt 0 proto 2 vid 0x04E8 pid 0x3297
  Feb  7 15:49:14 piubuntu mtp-probe: checking bus 3, device 16: 
"/sys/devices/pci:00/:00:1d.1/usb3/3-2"
  Feb  7 15:49:14 piubuntu mtp-probe: bus: 3, device: 16 was not an MTP device
  Feb  7 15:49:14 piubuntu udev-configure-printer: add 
/devices/pci:00/:00:1d.1/usb3/3-2
  Feb  7 15:49:14 piubuntu udev-configure-printer: device devpath is 
/devices/pci:00/:00:1d.1/usb3/3-2
  Feb  7 15:49:14 piubuntu udev-configu

[Desktop-packages] [Bug 847001] Re: Adjusting display brightness is very slow on several Dell laptops

[Marco van Zwetselaar]

Added gnome-shell to affected packages, as the issue is independent of
gnome-power-manager.

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

Title:
  Adjusting display brightness is very slow on several Dell laptops

Status in gnome-power-manager package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Changing the brightness via FN key combination or via the brightness applet 
is very slow.
  the CPUs don't seem to go to 100%, but the adjustment process seems 
relatively slow.
  The mouse cursor is also sluggish.
  Reinstalled the OS twice, but not because of this issue and the problem seems 
to persist.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-power-manager 2.32.0-2ubuntu2.1
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  Architecture: amd64
  Date: Sun Sep 11 15:29:02 2011
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GnomeSessionSuspendInhibited: No
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
  MachineType: Dell Inc. Latitude E5410
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic 
root=UUID=0dfaacc9-c19d-425b-963d-dabb87ae18bc ro quiet splash vt.handoff=7
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 05C67D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd01/28/2011:svnDellInc.:pnLatitudeE5410:pvr0001:rvnDellInc.:rn05C67D:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5410
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 847001] Re: Adjusting display brightness is very slow on several Dell laptops

[Marco van Zwetselaar]

Adding some more information. Running the following as root in a gnome
terminal:

   SYSFILE=/sys/class/backlight/intel_backlight/brightness
   OLD_VAL=$(cat $SYSFILE)
   NEW_VAL=$((OLD_VAL + 100))

   T0=$(date +%N)
   time echo $NEW_VAL  | tee $SYSFILE
   T1=$(date +%N)

   echo "Total time (millis): $(((T1 - T0)/1000))"

Gives the following:

   real0m0.002s
   user0m0.002s
   sys 0m0.001s
   Total time (millis): 3502

In other words, the write to sysfs returns in 2ms (and indeed,
brightness changes instantly), but it takes 3502ms for control to get
back to the prompt.

During that time, the system seems to hang, but keypresses are
collected: they are all echoed to the terminal right after the command
returns.  So the question then is: where are the 3 seconds spent?

I'm happy to experiment if someone has instructions.

** Also 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-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/847001

Title:
  Adjusting display brightness is very slow on several Dell laptops

Status in gnome-power-manager package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Changing the brightness via FN key combination or via the brightness applet 
is very slow.
  the CPUs don't seem to go to 100%, but the adjustment process seems 
relatively slow.
  The mouse cursor is also sluggish.
  Reinstalled the OS twice, but not because of this issue and the problem seems 
to persist.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-power-manager 2.32.0-2ubuntu2.1
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  Architecture: amd64
  Date: Sun Sep 11 15:29:02 2011
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GnomeSessionSuspendInhibited: No
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
  MachineType: Dell Inc. Latitude E5410
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic 
root=UUID=0dfaacc9-c19d-425b-963d-dabb87ae18bc ro quiet splash vt.handoff=7
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 05C67D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd01/28/2011:svnDellInc.:pnLatitudeE5410:pvr0001:rvnDellInc.:rn05C67D:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5410
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 847001] Re: Adjusting display brightness is very slow on several Dell laptops

[Marco van Zwetselaar]

Bug reappeared in 18.04.

Dell Precision M4800, running the standard Ubuntu Gnome shell desktop
(on Xorg), Intel Graphics.  No issues in 16.04 (or perhaps a tiny
delay?), but unworkable in 18.04.

Both Fn-Up/Down and `echo value | sudo tee brightness` exhibit the delay
(~2-3 seconds normally). Notable is that the brightness seems to change
*immediately* after echoing into sysfs, so all the delay occurs in the
return of the call back to the prompt.

In /sys/class/backlight I have only intel_backlight. No difference with
or without Backlight option in xorg.conf, nor with the
acpi_backlight=vendor kernel param.

Also notable: when performing the brightness change in a virtual
terminal, it is *instantaneous*.  The issue only occurs in the graphical
VT running the desktop environment.

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

Title:
  Adjusting display brightness is very slow on several Dell laptops

Status in gnome-power-manager package in Ubuntu:
  Confirmed

Bug description:
  Changing the brightness via FN key combination or via the brightness applet 
is very slow.
  the CPUs don't seem to go to 100%, but the adjustment process seems 
relatively slow.
  The mouse cursor is also sluggish.
  Reinstalled the OS twice, but not because of this issue and the problem seems 
to persist.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-power-manager 2.32.0-2ubuntu2.1
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  Architecture: amd64
  Date: Sun Sep 11 15:29:02 2011
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GnomeSessionSuspendInhibited: No
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
  MachineType: Dell Inc. Latitude E5410
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic 
root=UUID=0dfaacc9-c19d-425b-963d-dabb87ae18bc ro quiet splash vt.handoff=7
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 05C67D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd01/28/2011:svnDellInc.:pnLatitudeE5410:pvr0001:rvnDellInc.:rn05C67D:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5410
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1763978] Re: nvidia-prime-boot.service: Main process exited, code=exited, status=2/INVALIDARGUMENT

[Marco Corsi]

Hi, any solution? Same problem with kernel 4.15.0-30-generic

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

Title:
  nvidia-prime-boot.service: Main process exited, code=exited,
  status=2/INVALIDARGUMENT

Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  Since this week (i believe April 9th) Nvidia-prime isn't working for
  me.

  Running:
  Distributor ID:   Ubuntu
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  Codename: bionic

  Nvidia-prime version:

  Nvidia-prime version:
Installed: 0.8.7
Candidate: 0.8.7
Version table:
   *** 0.8.7 500

  Error code:
  apr 14 11:56:33 Precision-7510 systemd[1]: nvidia-prime-boot.service: Main 
process exited, code=exited, status=2/INVALIDARGUMENT

  apr 14 11:56:33 Precision-7510 systemd[1]: nvidia-prime-boot.service:
  Failed with result 'exit-code'.

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

-- 
Mailing list: https://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 1646455] Re: Unacceptably slow performance in Thunderbird

[Marco Righi]

I would like close it without specify one of this answer



New
Incomplete
Opinion
Invalid
Confirmed
In Progress
Fix Committed
Fix Released


please can you add simply close? I do not know if someone fixed the bug.

To resolve the problem I deleted configuration files and I reconfigure
thunderbird with a minimal set of accounts.

thank you for your work.

best
Marco

On 14/07/2018 19:49, Wolf Rogner wrote:
> This issue has been resolved long time ago.
> 
> Thanks for asking and please close the issue.
> 
> Wolf Rogner
> 
> 
> On 2018-07-14 18:45, gf wrote:
>> Hello Wolf,
>> Thank you for submitting this bug and reporting a problem with slow 
>> performance in Thunderbird.  You made this bug report in 2016 and there have 
>> been several versions of Ubuntu and Thunderbird since then. 
>>
>> Could you confirm that this is no longer a problem and that we can close the 
>> ticket? 
>> If it is still a problem, are you still interested in finding a solution to 
>> this bug? 
>> If you are, could you run the following (only once):
>> apport-collect BUGNUMBER
>> and upload the updated logs and and any other logs that are relevant for 
>> this particular issue. 
>>
>> Thank you again for helping make Ubuntu and Thunderbird better. 
>> G
>>
>> ** Changed in: thunderbird (Ubuntu)
>>Status: New => Incomplete
>>
> 

-- 
--
Think Marco, think different

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

Title:
  Unacceptably slow performance in Thunderbird

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  Starting with 16.10 Thunderbirds startup time became agonizingly slow
  From less than 3 seconds (to the blank window) and less than 7 seconds (to 
accepting input) 
  to 17 seconds (blank window) and 28 seconds (to accepting input)
  [same machine, same plugins]

  Now, with the update to 45.5.1 sending an email increase the time from
  pressing send to the disappearance of the window from 1 second to more
  than 9 seconds (on average).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: thunderbird 1:45.5.1+build1-0ubuntu0.16.10.1
  ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6
  Uname: Linux 4.8.0-28-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wolf   2669 F pulseaudio
   /dev/snd/controlC0:  wolf   2669 F pulseaudio
  BuildID: 20161130102337
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Thu Dec  1 11:57:31 2016
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   Enigmail - {847b3a00-7ab1-11d4-8f02-006008948af5}
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Deutsch (DE) Language Pack - langpack...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2016-10-22 (40 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
   default via 10.1.0.254 dev wlp4s0  proto static  metric 600 
   10.0.0.0/8 dev wlp4s0  proto kernel  scope link  src 10.1.0.168  metric 600 
   169.254.0.0/16 dev wlp4s0  scope link  metric 1000 
   172.16.220.0/24 dev vmnet1  proto kernel  scope link  src 172.16.220.1 
   192.168.68.0/24 dev vmnet8  proto kernel  scope link  src 192.168.68.1
  MostRecentCrashID: bp-09b01898-5a57-4940-bf7b-9ce882161021
  PrefSources:
   prefs.js
   
[Profile]/extensions/{25cf5f06-b211-4df3-9d5a-c0ab253a5561}.xpi:defaults/preferences.js
   
[Profile]/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
   
/usr/lib/thunderbird/extensions/{a62ef8ec-5fdc-40c2-873c-223b8a6925cc}/defaults/preferences/preferences.js
   
/usr/lib/thunderbird/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
  Profiles: Profile0 (Default) - LastVersion=45.5.1/20161130102337 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  SubmittedCrashIDs:
   bp-09b01898-5a57-4940-bf7b-9ce882161021
   bp-57849896-c2e9-45b1-9cbf-0bf392160823
   bp-47c994ab-4894-4453-a743-08c592160525
   bp-407af357-4517-4945-a8da-f0d482151002
   bp-b1c86d9c-9939-42a2-af8d-f9e6c2150903
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP101.88Z.00EE.B03.1212211437
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-C3EC7CD22292981F
  dmi.board.vendor: Apple Inc.
  dmi.bo

[Desktop-packages] [Bug 1779846] Re: Pressing Alt+Backslash locks up all windows (no focus)

[Marco Gaiarin]

> First, please try removing these shell extensions:

A-Ha! Sorry, i've played with some extensions and never minded about
them.

I've disabled (it suffices, it was not needed to uninstall them)
'system-monitor' and 'windows-alt-tab' and problem desappear.

Many thanks and sorry for that bug report!

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

Title:
  Pressing Alt+Backslash locks up all windows (no focus)

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I've recently switched from 16.04/Unity to 18.04/Gnome3, with new
  hardware (a Lenovo Thinkpad T470s) used mostly with a docking station
  and external keyboard.

  I do heavily use of in-workspace windows switch (eg, Alt+Esc) and i've found 
that every time i press Alt+Backslash (in Italian keyboard layout Backslash is 
all left, between TAB and Esc keys) my session ''lock up'': i can switch 
between windows, i can use the gnome shell and the top bar (status bar?), i can 
even run other application (via Alt+F2 or gnome shell menu) but every window 
(old or new) are ''locked'', like there's no focus: no keyboard nor mouse 
interaction is possible.
  Application are not 'locked', they continue to run, but there's no way to 
interact with them.

  I can also lock the screen, or put the system in standby: i can awaken
  from that, insert the password but still no focus on windows.

  The only solution: logout.

  I've also tried to define a keyboard shortcut to map Alt+Backslash,
  but... gnome keyboard configurator locks as every other window when i
  press the keys.

  Please, help me at least to disable that 'killer' keyboard shortcut!
  ;-)

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  3 12:16:18 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['system-moni...@paradoxxx.zero.gmail.com', 
'workspace-g...@mathematical.coffee.gmail.com', 'windows-alt-...@tglman.org']"
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-05-25 (38 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1779846] [NEW] Pressing Alt+Backslash locks up all windows (no focus)

[Marco Gaiarin]

Public bug reported:

I've recently switched from 16.04/Unity to 18.04/Gnome3, with new
hardware (a Lenovo Thinkpad T470s) used mostly with a docking station
and external keyboard.

I do heavily use of in-workspace windows switch (eg, Alt+Esc) and i've found 
that every time i press Alt+Backslash (in Italian keyboard layout Backslash is 
all left, between TAB and Esc keys) my session ''lock up'': i can switch 
between windows, i can use the gnome shell and the top bar (status bar?), i can 
even run other application (via Alt+F2 or gnome shell menu) but every window 
(old or new) are ''locked'', like there's no focus: no keyboard nor mouse 
interaction is possible.
Application are not 'locked', they continue to run, but there's no way to 
interact with them.

I can also lock the screen, or put the system in standby: i can awaken
from that, insert the password but still no focus on windows.

The only solution: logout.

I've also tried to define a keyboard shortcut to map Alt+Backslash,
but... gnome keyboard configurator locks as every other window when i
press the keys.

Please, help me at least to disable that 'killer' keyboard shortcut! ;-)

Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul  3 12:16:18 2018
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'enabled-extensions' 
b"['system-moni...@paradoxxx.zero.gmail.com', 
'workspace-g...@mathematical.coffee.gmail.com', 'windows-alt-...@tglman.org']"
 b'org.gnome.shell' b'command-history' redacted by apport
 b'org.gnome.shell' b'favorite-apps' redacted by apport
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2018-05-25 (38 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Pressing Alt+Backslash locks up all windows (no focus)

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I've recently switched from 16.04/Unity to 18.04/Gnome3, with new
  hardware (a Lenovo Thinkpad T470s) used mostly with a docking station
  and external keyboard.

  I do heavily use of in-workspace windows switch (eg, Alt+Esc) and i've found 
that every time i press Alt+Backslash (in Italian keyboard layout Backslash is 
all left, between TAB and Esc keys) my session ''lock up'': i can switch 
between windows, i can use the gnome shell and the top bar (status bar?), i can 
even run other application (via Alt+F2 or gnome shell menu) but every window 
(old or new) are ''locked'', like there's no focus: no keyboard nor mouse 
interaction is possible.
  Application are not 'locked', they continue to run, but there's no way to 
interact with them.

  I can also lock the screen, or put the system in standby: i can awaken
  from that, insert the password but still no focus on windows.

  The only solution: logout.

  I've also tried to define a keyboard shortcut to map Alt+Backslash,
  but... gnome keyboard configurator locks as every other window when i
  press the keys.

  Please, help me at least to disable that 'killer' keyboard shortcut!
  ;-)

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  3 12:16:18 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['system-moni...@paradoxxx.zero.gmail.com', 
'workspace-g...@mathematical.coffee.gmail.com', 'windows-alt-...@tglman.org']"
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-05-25 (38 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 

[Desktop-packages] [Bug 1777318] [NEW] GDM3 completely ignore pam_group

[Marco Gaiarin]

Public bug reported:

I'm using some ubuntu machine in a network where users data came from
LDAP.

I've setup PAM/NSS to use LDAP account and all works as expected.
Apart assigning local group to users, via pam_group.

I've added to /etc/pam.d/common-auth (to the end):
 authoptionalpam_group.so

and added to /etc/security/group.conf:
 *; *; %sysops; Al-2400; 
adm,sudo,admin,dip,cdrom,floppy,plugdev,lpadmin,sambashare

but groups are not added as expected, i'm not in 'admin' or 'sudo' group
(eg, i cannot do administrative tasks) and if i fire up a terminal:

 gaio@dora:~$ id
 uid=1000(gaio) gid=1001(casa) gruppi=1001(casa),1000(sysops),1003(bbs)

note that group assignment works, eg:

 gaio@dora:~$ ssh localhost
 gaio@localhost's password: 
 Welcome to Ubuntu 18.04 LTS (GNU/Linux 4.15.0-23-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management: https://landscape.canonical.com
 * Support:https://ubuntu.com/advantage


 * Canonical Livepatch is available for installation.
   - Reduce system reboots and improve kernel security. Activate at:
 https://ubuntu.com/livepatch

 0 pacchetti possono essere aggiornati.
 0 sono aggiornamenti di sicurezza.

 Last login: Sun Jun 17 14:36:50 2018 from 127.0.0.1
 gaio@dora:~$ id 
 uid=1000(gaio) gid=1001(casa)  
gruppi=1001(casa),4(adm),24(cdrom),25(floppy),27(sudo),30(dip),46(plugdev),116(lpadmin),126(sambashare),1000(sysops),1003(bbs)

Previous LTS (16.04) with LightDM works as expected. This bug seems very
similar to #880104 .

Thanks.

** Affects: gdm3 (Ubuntu)
 Importance: Undecided
 Status: 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/1777318

Title:
  GDM3 completely ignore pam_group

Status in gdm3 package in Ubuntu:
  New

Bug description:
  I'm using some ubuntu machine in a network where users data came from
  LDAP.

  I've setup PAM/NSS to use LDAP account and all works as expected.
  Apart assigning local group to users, via pam_group.

  I've added to /etc/pam.d/common-auth (to the end):
   authoptionalpam_group.so

  and added to /etc/security/group.conf:
   *; *; %sysops; Al-2400; 
adm,sudo,admin,dip,cdrom,floppy,plugdev,lpadmin,sambashare

  but groups are not added as expected, i'm not in 'admin' or 'sudo'
  group (eg, i cannot do administrative tasks) and if i fire up a
  terminal:

   gaio@dora:~$ id
   uid=1000(gaio) gid=1001(casa) gruppi=1001(casa),1000(sysops),1003(bbs)

  note that group assignment works, eg:

   gaio@dora:~$ ssh localhost
   gaio@localhost's password: 
   Welcome to Ubuntu 18.04 LTS (GNU/Linux 4.15.0-23-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

  
   * Canonical Livepatch is available for installation.
 - Reduce system reboots and improve kernel security. Activate at:
   https://ubuntu.com/livepatch

   0 pacchetti possono essere aggiornati.
   0 sono aggiornamenti di sicurezza.

   Last login: Sun Jun 17 14:36:50 2018 from 127.0.0.1
   gaio@dora:~$ id 
   uid=1000(gaio) gid=1001(casa)  
gruppi=1001(casa),4(adm),24(cdrom),25(floppy),27(sudo),30(dip),46(plugdev),116(lpadmin),126(sambashare),1000(sysops),1003(bbs)

  Previous LTS (16.04) with LightDM works as expected. This bug seems
  very similar to #880104 .

  Thanks.

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

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

[Desktop-packages] [Bug 1774121] Re: affects ubuntu/thunderbird

[marco masetti]

** Description changed:

  Good day,
  
  I'd like to report a bug in Thunderbird 52.8.0 (64 bit). I use ubuntu
  18.04 LTS with Gnome 3.28.1.
  
affects ubuntu/thunderbird
  
  When i need to save all attachments in one mail into a directory and i
  right click into the attachment and select "save all files" the green
  button is displayed as "open" instead of "save" but the action of saving
  is performed correctly.
  
  Kind regards
  
  
  -- 
  Marco Masetti
- office: +39051370744
- mobile/whatsapp/wechat: +393391379191
- skype: masettimarco

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

Title:
  affects ubuntu/thunderbird

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Good day,

  I'd like to report a bug in Thunderbird 52.8.0 (64 bit). I use ubuntu
  18.04 LTS with Gnome 3.28.1.

affects ubuntu/thunderbird

  When i need to save all attachments in one mail into a directory and i
  right click into the attachment and select "save all files" the green
  button is displayed as "open" instead of "save" but the action of saving
  is performed correctly.

  Kind regards

  
  -- 
  Marco Masetti

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

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

[Desktop-packages] [Bug 1774121] [NEW] affects ubuntu/thunderbird

[marco masetti]

Public bug reported:

Good day,

I'd like to report a bug in Thunderbird 52.8.0 (64 bit). I use ubuntu
18.04 LTS with Gnome 3.28.1.

  affects ubuntu/thunderbird

When i need to save all attachments in one mail into a directory and i
right click into the attachment and select "save all files" the green
button is displayed as "open" instead of "save" but the action of saving
is performed correctly.

Kind regards


-- 
Marco Masetti
office: +39051370744
mobile/whatsapp/wechat: +393391379191
skype: masettimarco

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

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

Title:
  affects ubuntu/thunderbird

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Good day,

  I'd like to report a bug in Thunderbird 52.8.0 (64 bit). I use ubuntu
  18.04 LTS with Gnome 3.28.1.

affects ubuntu/thunderbird

  When i need to save all attachments in one mail into a directory and i
  right click into the attachment and select "save all files" the green
  button is displayed as "open" instead of "save" but the action of saving
  is performed correctly.

  Kind regards

  
  -- 
  Marco Masetti
  office: +39051370744
  mobile/whatsapp/wechat: +393391379191
  skype: masettimarco

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

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

[Desktop-packages] [Bug 1768587] Re: [Regression] Reverse vnc protocol is missing in Remmina 1.2.0-rcgit.29+dfsg-1 (Ubuntu 18.04 - bionic)

[Marco Menardi]

Seems that has been resolved upstream with 1.2.30+dfsg-1
https://github.com/FreeRDP/Remmina/issues/1538
and right now my Debian sid has upgraded remmina to that version and it works 
again!
Hope Ubuntu maintainers will "backport" to 18.04 soon.

** Bug watch added: Remmina Issues #1538
   https://github.com/FreeRDP/Remmina/issues/1538

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

Title:
  [Regression] Reverse vnc protocol is missing in Remmina
  1.2.0-rcgit.29+dfsg-1 (Ubuntu 18.04 - bionic)

Status in remmina package in Ubuntu:
  New

Bug description:
  [Regression] Reverse VNC (VNCI) protocol is missing in Remmina
  1.2.0-rcgit.29+dfsg-1 (Ubuntu 18.04 - bionic), but is available in all
  older Ubuntu and official remmina-ppa-team PPA releases, including
  1.2.0-rcgit-27 and older versions from ppa:remmina-ppa-team/remmina-
  next

  AFAIK latest release with Reverse VNC (VNCI) protocol is remmina -
  1.2.0-rcgit-27-0~remmina201802142316.r566cdf6.dd516ac4~ubuntu16.04.1 ,
  see https://launchpad.net/~baltix-
  members/+archive/ubuntu/ppa/+packages?field.name_filter=remmina

  Steps to reproduce:

  1. Install remmina-plugin-vnc package and open Remmina app
  2. Press + button on the top left side
  3. Open "Protocol" dropdown list in newly appeared "Remote Desktop 
Preference" window
  4. Notice, that "Reverse VNC (VNCI)" is missing from "Protocol" dropdown list

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

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

[Desktop-packages] [Bug 1768587] Re: [Regression] Reverse vnc protocol is missing in Remmina 1.2.0-rcgit.29+dfsg-1 (Ubuntu 18.04 - bionic)

[Marco Menardi]

I can confirm, and I can add that affects Debian Sid (unstable) too
(remmina 1.2.0-rcgit.29+dfsg-1)

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

Title:
  [Regression] Reverse vnc protocol is missing in Remmina
  1.2.0-rcgit.29+dfsg-1 (Ubuntu 18.04 - bionic)

Status in remmina package in Ubuntu:
  New

Bug description:
  [Regression] Reverse VNC (VNCI) protocol is missing in Remmina
  1.2.0-rcgit.29+dfsg-1 (Ubuntu 18.04 - bionic), but is available in all
  older Ubuntu and official remmina-ppa-team PPA releases, including
  1.2.0-rcgit-27 and older versions from ppa:remmina-ppa-team/remmina-
  next

  AFAIK latest release with Reverse VNC (VNCI) protocol is remmina -
  1.2.0-rcgit-27-0~remmina201802142316.r566cdf6.dd516ac4~ubuntu16.04.1 ,
  see https://launchpad.net/~baltix-
  members/+archive/ubuntu/ppa/+packages?field.name_filter=remmina

  Steps to reproduce:

  1. Install remmina-plugin-vnc package and open Remmina app
  2. Press + button on the top left side
  3. Open "Protocol" dropdown list in newly appeared "Remote Desktop 
Preference" window
  4. Notice, that "Reverse VNC (VNCI)" is missing from "Protocol" dropdown list

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

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

[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

[Marco Bortoli]

Brother MFC-J480DW, printer ok, scanner doesn't work in Ubuntu 18.04,
fresh installation yesterday. I use simple scan, scanner is not found.
Scanner works fine with 16.04. In brother folder,
brscan4-04.4-3.amd64.deb, libsane-common version 1.0.27-1
experimental3ubuntu 2. If you find the way to solve this problem


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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Many scanners can no more be used since sane has changed something:
  The 3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.

  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
   - Epson Perfection V33

  It is to note that the probability that the scanner manufacturers fix
  things others broke is below 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

[Marco Venturini]

Xubuntu 18.04 lts, it looks like it's still not fixed

cat /proc/asound/cards

 0 [Audio  ]: HdmiLpeAudio - Intel HDMI/DP LPE Audio
  Intel HDMI/DP LPE Audio

uname -a

Linux marco-E200HA 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Thanks

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1756783] Re: Problems at display the second monitor

[Marco]

Yes, to get both screen working... I need to boot with only the Display Port 
connected!
If I boot with both ports connected only the DVI one gets detected.

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

Title:
  Problems at display the second monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  I had a problem where my monitor connected to the Display Port didn't
  work but the monitor at the DVI Port was working fine.

  The only way I manage to get the Display Monitor working was to boot
  with only this monitor connected and after the Desktop was loaded I
  could connect the DVI Port and it would work fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  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: Mon Mar 19 00:55:50 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:67df] (rev c7) (prog-if 
00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e347]
  InstallationDate: Installed on 2018-03-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic.efi.signed 
root=UUID=b539d681-84bf-4093-b7db-2cc19cdd469e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FD
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-DS3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFD:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-DS3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.85-5~x~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.6-2~x~padoka0
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.6-2~x~padoka0
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Mar 19 00:33:07 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: amdgpu

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

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

[Desktop-packages] [Bug 1756783] [NEW] Problems at display the second monitor

[Marco]

Public bug reported:

I had a problem where my monitor connected to the Display Port didn't
work but the monitor at the DVI Port was working fine.

The only way I manage to get the Display Monitor working was to boot
with only this monitor connected and after the Desktop was loaded I
could connect the DVI Port and it would work fine.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
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: Mon Mar 19 00:55:50 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:67df] (rev c7) (prog-if 00 
[VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e347]
InstallationDate: Installed on 2018-03-19 (0 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic.efi.signed 
root=UUID=b539d681-84bf-4093-b7db-2cc19cdd469e ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/26/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FD
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 970A-DS3P
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFD:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-DS3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.85-5~x~padoka0
version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.6-2~x~padoka0
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.6-2~x~padoka0
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Mon Mar 19 00:33:07 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: amdgpu

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


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

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

Title:
  Problems at display the second monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  I had a problem where my monitor connected to the Display Port didn't
  work but the monitor at the DVI Port was working fine.

  The only way I manage to get the Display Monitor working was to boot
  with only this monitor connected and after the Desktop was loaded I
  could connect the DVI Port and it would work fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  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: Mon Mar 19 00:55:50 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:67df] (rev c7) (prog-if 
00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e347]
  InstallationDate: Installed on 2018-03-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: 

[Desktop-packages] [Bug 1756066] Re: [FFe] Amarok 2.9.0 for Bionic

[Marco Parillo]

https://irclogs.ubuntu.com/2018/03/14/%23kubuntu-devel.html#t17:07

[17:07]   could people please test amarok 2.9.0 in 
ppa:kubuntu-ppa/staging-misc please
[17:09]   not even slighy suggesting shipping that kde4 
version as our default, but having the new bugfix release in the repos as a 
fallback would look good

...

[20:13]  I added ppa:kubuntu-ppa/staging-misc please, and 
successfully installed amarok 2.9.0. It brought in a bunch of dependencies, and 
when I ran the program, I successfully played Art of Nations.
[20:15]  I was able to go to cool streams, and play something, and a 
Wikipedia link was displayed
[21:56]  mparillo: thanks

** Description changed:

  Amarok have released a first non-beta version since 2013.
  
  We currently have 2.8.0 in the archive.
  
  Announcement and changes since the 2015 beta:
  https://amarok.kde.org/en/node/888
  
  Nearly all bug fixes.
  
  Announcement and changes 2.8.0 -> 2.8.90 (beta) we did not ship:
  https://amarok.kde.org/en/node/887
  
  The new features seem to work: e.g: ascii analyser
  https://i.imgur.com/OUC99mi.png
  
  Valorie Zimmerman of KDE's Team Amarok reported successful testing with
  the staged build in ppa:kubuntu-ppa/staging-misc
  
  Should also fix the current archive FTBFS on s390x
  
- I would not that due to lack of upstream releases and an unfinished
+ I would note that due to lack of upstream releases and an unfinished
  Qt5/KF5 port, Kubuntu has switched to the Qt5 app Cantata for our
  default. The Qt4 Amarok has become an unseeded (iso or meta) leaf
  package for us at the moment. However it is still very popular, so would
  be great to get this mostly bugfix release into the bionic repos.

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

Title:
  [FFe] Amarok 2.9.0 for Bionic

Status in amarok package in Ubuntu:
  New
Status in amarok source package in Bionic:
  New

Bug description:
  Amarok have released a first non-beta version since 2013.

  We currently have 2.8.0 in the archive.

  Announcement and changes since the 2015 beta:
  https://amarok.kde.org/en/node/888

  Nearly all bug fixes.

  Announcement and changes 2.8.0 -> 2.8.90 (beta) we did not ship:
  https://amarok.kde.org/en/node/887

  The new features seem to work: e.g: ascii analyser
  https://i.imgur.com/OUC99mi.png

  Valorie Zimmerman of KDE's Team Amarok reported successful testing
  with the staged build in ppa:kubuntu-ppa/staging-misc

  Should also fix the current archive FTBFS on s390x

  I would note that due to lack of upstream releases and an unfinished
  Qt5/KF5 port, Kubuntu has switched to the Qt5 app Cantata for our
  default. The Qt4 Amarok has become an unseeded (iso or meta) leaf
  package for us at the moment. However it is still very popular, so
  would be great to get this mostly bugfix release into the bionic
  repos.

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

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

[Desktop-packages] [Bug 1756066] Re: [FFe] Amarok 2.9.0 for Bionic

[Marco Parillo]

https://irclogs.ubuntu.com/2018/03/14/%23kubuntu-council.txt

[17:07]   could people please test amarok 2.9.0 in 
ppa:kubuntu-ppa/staging-misc please
[17:08]   valorie: ^^^
[20:47]  
[20:47]  I probably should purge it if I have it on this machine first 
though
[20:48]  right?
[20:48]  acheronuk: ^^^
[21:56]  It's a new version so upgrade should be ok
[22:09]  ah, ok
[22:09]  and yeah I have ppa-purge so it should be find
[22:09]  in a min
[22:31]  uh, how do I upgrade amarok and not everything else?
[22:31]  I specified amarok but it wants to upgrade lots of other 
stuff which I prefer not to do right now
[22:32]  ah, only-upgrade
[22:32]  got it
[22:33]  hmmm, maybe I need it all
[22:35]  going for it
[23:36]  ok, it's running, but it lost track of my music collection -- 
might not have set that up after I moved my music off the SSD and onto the HD 
on this machine

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

Title:
  [FFe] Amarok 2.9.0 for Bionic

Status in amarok package in Ubuntu:
  New
Status in amarok source package in Bionic:
  New

Bug description:
  Amarok have released a first non-beta version since 2013.

  We currently have 2.8.0 in the archive.

  Announcement and changes since the 2015 beta:
  https://amarok.kde.org/en/node/888

  Nearly all bug fixes.

  Announcement and changes 2.8.0 -> 2.8.90 (beta) we did not ship:
  https://amarok.kde.org/en/node/887

  The new features seem to work: e.g: ascii analyser
  https://i.imgur.com/OUC99mi.png

  Valorie Zimmerman of KDE's Team Amarok reported successful testing
  with the staged build in ppa:kubuntu-ppa/staging-misc

  Should also fix the current archive FTBFS on s390x

  I would note that due to lack of upstream releases and an unfinished
  Qt5/KF5 port, Kubuntu has switched to the Qt5 app Cantata for our
  default. The Qt4 Amarok has become an unseeded (iso or meta) leaf
  package for us at the moment. However it is still very popular, so
  would be great to get this mostly bugfix release into the bionic
  repos.

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

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

[Desktop-packages] [Bug 1572244] Re: Kubuntu requires that the WiFi password be entered twice before WiFi can be used

[Marco Parillo]

Fix verified (originally posted to:
https://phabricator.kde.org/T7981#132629):

I zsynced kubuntu-ci-stable-bionic-amd64.iso.zsync
I dd'd the ISO to a usb thumb drive
I booted the thumb drive
I saw the WEP network, selected it, and entered the key all in Network Manager 
from the tray.
I did NOT get the pop-up to re-enter the WEP password.

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

Title:
  Kubuntu requires that the WiFi password be entered twice before WiFi
  can be used

Status in casper package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in plasma-nm package in Ubuntu:
  Confirmed
Status in casper source package in Bionic:
  Confirmed
Status in network-manager source package in Bionic:
  Fix Released
Status in plasma-nm source package in Bionic:
  Confirmed

Bug description:
  Kubuntu 16.04 ISO number 20160417.1 Xenial Final
  Bug reported against network-manager 
  Every time I tried the live Kubuntu 16.04 image on a Lenovo t420 laptop it 
requires to enter the wifi password twice before I can use the wifi. Once from 
the network icon panel, then second time a prompt on the desktop to enter the 
wifi password.

  I do not know if this is typical behavior of Kubuntu since I usually use GTK 
base desktops.
  I guess network-manager is the right package to file this report against.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.373
  CurrentDesktop: KDE
  Date: Tue Apr 19 16:48:02 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.77.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.77.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.77.128  
metric 600
  LiveMediaBuild: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  802-11-wireless  
1461084315  Tue 19 Apr 2016 04:45:15 PM UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp3s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/3 
   Wired connection 1  4957fbd0-8ffa-4de8-aa18-275e6dfdcd9e  802-3-ethernet   
1461077415  Tue 19 Apr 2016 02:50:15 PM UTC  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  no  --  --
 --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  
--  ----
  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/ubuntu/+source/casper/+bug/1572244/+subscriptions

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

[Desktop-packages] [Bug 1300215] Re: Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory

[Marco Schmidt]

After some further investigation, I learned, that there are two APIs for this. 
1. VA-API: for Intel with the tool: vainfo
2. VDPAU-API: for others with the tool: vdpauinfo

and there is the libvdpau-va-gl which translates VDPAU-API to VA-API. 
Setting VDPAU_DRIVER uses this library and this library uses 
"i965_drv_video.so" as VA-API backend.
According to the README.Debian of "i965-va-driver" it should be able to 
hw-accelerate MPEG-2

Codecs:
--

H.264   D   ILK+
H.264   E   SNB+
MPEG-2  D   CTG+
VC-1D   SNB+

Seems that this is not working as expected.
The "vainfo" uses "i965_drv_video.so", too. And it notes that MPEG2 is 
supported: 
vainfo: Supported profile and entrypoints
  VAProfileMPEG2Simple: VAEntrypointVLD
  VAProfileMPEG2Main  : VAEntrypointVLD

Unfortunately this means, that we are in the wrong package for this
"Bug" (I assume Intel changed something in driver).

References: 
https://wiki.archlinux.org/index.php/Hardware_video_acceleration

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

Title:
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared
  object file: No such file or directory

Status in libvdpau package in Ubuntu:
  Triaged
Status in libvdpau-va-gl package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in vdr-plugin-xineliboutput package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Invalid
Status in xine-ui package in Ubuntu:
  Confirmed
Status in libvdpau package in Debian:
  New

Bug description:
  This has been bothering me at least since precise (although there the
  missing link went to libvdpau_nvidia.so which was all the more
  mysterious since I do not own NVIDIA hardware).  In numerous cases do
  I get a warning that libvdpau_i965.so is being tried to be accessed
  but it fails.  I also can't find that file anywhere on my system or in
  the Ubuntu repository.  I tried poking around with ldd to find out
  where the call to that lib comes from but so far unsuccessful.

  $ vdpauinfo
  display: :0   screen: 0
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object 
file: No such file or directory
  Error creating VDPAU device: 1

  libvdpau1:i386 is version 0.7-1 and vdpauinfo is 0.1-1

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

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

[Desktop-packages] [Bug 1300215] Re: Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory

[Marco Schmidt]

In xenial after upgrade to hwe-16.04 the missing library is showing up
in kaffein.

Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: 
No such file or directory
vo_vdpau: Can't create vdp device : No vdpau implementation.

Setting VDPAU_DRIVER to va_gl removes the missing-library error, but due
to missing MPEG2 decode support the DVB-T stream is not played.

MPEG2_SIMPLE   --- not supported ---
MPEG2_MAIN --- not supported ---

Any hint, how to get DVB-T stream on the screen?

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

Title:
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared
  object file: No such file or directory

Status in libvdpau package in Ubuntu:
  Triaged
Status in libvdpau-va-gl package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in vdr-plugin-xineliboutput package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Invalid
Status in xine-ui package in Ubuntu:
  Confirmed
Status in libvdpau package in Debian:
  New

Bug description:
  This has been bothering me at least since precise (although there the
  missing link went to libvdpau_nvidia.so which was all the more
  mysterious since I do not own NVIDIA hardware).  In numerous cases do
  I get a warning that libvdpau_i965.so is being tried to be accessed
  but it fails.  I also can't find that file anywhere on my system or in
  the Ubuntu repository.  I tried poking around with ldd to find out
  where the call to that lib comes from but so far unsuccessful.

  $ vdpauinfo
  display: :0   screen: 0
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object 
file: No such file or directory
  Error creating VDPAU device: 1

  libvdpau1:i386 is version 0.7-1 and vdpauinfo is 0.1-1

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

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

[Desktop-packages] [Bug 1752681] Re: wireless disconnect

[Marco Giannini]

In my case it works also by setting the IPV6 to "Automatic, address only".
Try like this. Turn off the connection, set it to Automatich, address only or 
"Ignore" and then re-enable the connection. In my case this procedure works 
(see attachment)

** Attachment added: "Istantanea_2018-03-06_19-03-28.png"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1752681/+attachment/5070976/+files/Istantanea_2018-03-06_19-03-28.png

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

Title:
  wireless disconnect

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  There are many problems reported about random and quick
  disconnect/reconnect of the wireless connection in ubuntu. Some say,
  disabling the ipv6 is the solution but it isn't!

  I really do want to find a way to debug what happens that the wireless
  connection drops randomly. But I couldn't find a tool for that.

  The output of the following commands are attached:
  uname -a
  ifconfig
  cat /proc/sys/net/ipv6/conf/all/disable_ipv6
  iwconfig
  lsmod
  dmesg

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

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

[Desktop-packages] [Bug 1752681] Re: wireless disconnect

[Marco Giannini]

I encounter the same problem with the daily Xubuntu 18.04 and Ubuntu MATE 18.04 
of March 5, 2018. The connection via ethernet cable does not work unless I 
disable the ipv6.
In practice I have to set the Method to Ignore in IPV6 Settings to navigate.

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

Title:
  wireless disconnect

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  There are many problems reported about random and quick
  disconnect/reconnect of the wireless connection in ubuntu. Some say,
  disabling the ipv6 is the solution but it isn't!

  I really do want to find a way to debug what happens that the wireless
  connection drops randomly. But I couldn't find a tool for that.

  The output of the following commands are attached:
  uname -a
  ifconfig
  cat /proc/sys/net/ipv6/conf/all/disable_ipv6
  iwconfig
  lsmod
  dmesg

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

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

[Desktop-packages] [Bug 1707451] Re: udisksd crashed with SIGSEGV in g_mutex_lock()

[Marco Giannini]

Same issue on daily 19/02/2018 of Ubuntu 18.04 (fresh install)

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

Title:
  udisksd crashed with SIGSEGV in g_mutex_lock()

Status in udisks:
  New
Status in udisks2 package in Ubuntu:
  Triaged

Bug description:
  Showed up after login

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: udisks2 2.6.5-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sun Jul 30 00:35:31 2017
  ExecutablePath: /usr/lib/udisks2/udisksd
  InstallationDate: Installed on 2017-06-22 (37 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170622)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcCmdline: /usr/lib/udisks2/udisksd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic.efi.signed 
root=UUID=44b31662-d2ab-443b-9546-86d022d8de0d ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f4900fb5c65 :   lock xadd 
%eax,(%rdi)
   PC (0x7f4900fb5c65) ok
   source "%eax" ok
   destination "(%rdi)" (0x3a9d80e262617474) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: udisks2
  StacktraceTop:
   g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   main ()
  Title: udisksd crashed with SIGSEGV in g_mutex_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/12/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.40
  dmi.board.name: Z87 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd04/12/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 1749822] [NEW] package libvorbisenc2:amd64 1.3.5-3ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting c

[Marco Vronik]

Public bug reported:

after installing pdfsam from the appstore the progam did not start. I
have update ubuntu in terminal and I have got the error. I have removed
and reinstalled the program but no solution. Check the issue on forums
and try the solution. The problem maintain the same

Earlier today I have installed dropbox but this is function fine.

Ubuntu 16.04.3 LTS

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libvorbisenc2:amd64 1.3.5-3ubuntu0.1
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
AptOrdering:
 libvorbis0a: Install
 libvorbis0a: Configure
 libvorbisenc2: Configure
 libvorbisfile3: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Feb 15 22:05:56 2018
DuplicateSignature:
 package:libvorbisenc2:amd64:1.3.5-3ubuntu0.1
 Setting up libvorbis0a:amd64 (1.3.5-3ubuntu0.1) ...
 dpkg: error processing package libvorbisenc2:amd64 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2018-01-11 (35 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.25
SourcePackage: libvorbis
Title: package libvorbisenc2:amd64 1.3.5-3ubuntu0.1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libvorbisenc2:amd64 1.3.5-3ubuntu0.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libvorbis package in Ubuntu:
  New

Bug description:
  after installing pdfsam from the appstore the progam did not start. I
  have update ubuntu in terminal and I have got the error. I have
  removed and reinstalled the program but no solution. Check the issue
  on forums and try the solution. The problem maintain the same

  Earlier today I have installed dropbox but this is function fine.

  Ubuntu 16.04.3 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libvorbisenc2:amd64 1.3.5-3ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  AptOrdering:
   libvorbis0a: Install
   libvorbis0a: Configure
   libvorbisenc2: Configure
   libvorbisfile3: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Feb 15 22:05:56 2018
  DuplicateSignature:
   package:libvorbisenc2:amd64:1.3.5-3ubuntu0.1
   Setting up libvorbis0a:amd64 (1.3.5-3ubuntu0.1) ...
   dpkg: error processing package libvorbisenc2:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-01-11 (35 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: libvorbis
  Title: package libvorbisenc2:amd64 1.3.5-3ubuntu0.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1676547] Re: No network connectivity (NIC unmanaged) after upgrade

[Marco Bianchi]

I do not have /etc/netplan directory on my ubuntu 14.04? Marco

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

Title:
  No network connectivity (NIC unmanaged) after upgrade

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Yakkety:
  Fix Released
Status in network-manager source package in Zesty:
  Fix Released

Bug description:
  Impact
  --
  When upgrading from Xenial (with all updates installed) to Yakkety/Zesty you 
will boot to a system without networking - sad!

  Test Case
  -
  1) Boot a xenial desktop system
  2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed
  3) Upgrade to yakkety or zesty
  3.5) Enable -proposed and download the new version of n-m "apt-get download 
network-manager"
  4) Reboot
  5) Observe you have no network

  If you install the version of network-manager from yakkety-proposed
  and then reboot you should have a network connection.

  1) Boot a xenial desktop system.
  2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed.
  3) Install nplan, configure to set up static network on an ethernet device 
using nplan.
  4) Upgrade to yakkety or zesty
  5) Reboot
  6) Observe that your system is still being managed by networkd rather than 
NetworkManager.

  Regression Potential
  

  Any failure to manage ethernet or wireless devices after upgrade, or
  issues with the use of netplan in conjunction with NetworkManager
  should be investigated as potential regressions. For example, if after
  upgrading, ethernet devices are no longer managed, or if devices that
  should be explicitly ignored by NetworkManager due to existing user
  configuration are now managed, these would indicate a possible
  regression caused by this update.

  Original Description
  

  nplan was installed during the upgrade process but I had no network
  connectivity after upgrading. Apparently, no package wanted to manage
  my ethernet connection.

  ProblemType: BugDistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.10
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Mar 27 11:34:04 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-16 (1531 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  PackageArchitecture: allSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago)
  VarLogDistupgradeTermlog:

  modified.conffile..etc.update-manager.meta-release: [modified]
  mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913

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

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

[Desktop-packages] [Bug 1300215] Re: Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory

[Marco]

A correction to #34

$ vdpauinfo
display: :0   screen: 0
Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: 
No such file or directory
Error creating VDPAU device: 1


$ xine
Questo è xine (X11 gui) - un riproduttore video libero v0.99.9.
(c) 2000-2014 The xine Team.
Failed to open VDPAU backend libvdpau_i965.so: impossibile aprire il file 
oggetto condiviso: File o directory non esistente
vo_vdpau: Can't create vdp device : No vdpau implementation.
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  151 (XVideo)
  Minor opcode of failed request:  17 ()
  Serial number of failed request:  2632
  Current serial number in output stream:  2632

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

Title:
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared
  object file: No such file or directory

Status in libvdpau package in Ubuntu:
  Triaged
Status in libvdpau-va-gl package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in vdr-plugin-xineliboutput package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Invalid
Status in xine-ui package in Ubuntu:
  Confirmed
Status in libvdpau package in Debian:
  New

Bug description:
  This has been bothering me at least since precise (although there the
  missing link went to libvdpau_nvidia.so which was all the more
  mysterious since I do not own NVIDIA hardware).  In numerous cases do
  I get a warning that libvdpau_i965.so is being tried to be accessed
  but it fails.  I also can't find that file anywhere on my system or in
  the Ubuntu repository.  I tried poking around with ldd to find out
  where the call to that lib comes from but so far unsuccessful.

  $ vdpauinfo
  display: :0   screen: 0
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object 
file: No such file or directory
  Error creating VDPAU device: 1

  libvdpau1:i386 is version 0.7-1 and vdpauinfo is 0.1-1

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

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

[Desktop-packages] [Bug 1300215] Re: Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory

[Marco]

Same problem here after a fresh install of Ubuntu 16.04.3 on a Thinkpad
T460

$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated 
Graphics (rev 07)

$ vdpauinfo
display: :0   screen: 0
Failed to open VDPAU backend libvdpau_.so: cannot open shared object file: No 
such file or directory
Error creating VDPAU device: 1

$ ll /usr/lib/x86_64-linux-gnu/vdpau
lrwxrwxrwx 1 root root  25 gen 13 09:41 libvdpau_nouveau.so -> 
libvdpau_nouveau.so.1.0.0
lrwxrwxrwx 1 root root  25 gen 13 09:41 libvdpau_nouveau.so.1 -> 
libvdpau_nouveau.so.1.0.0
lrwxrwxrwx 1 root root  25 gen 13 09:41 libvdpau_nouveau.so.1.0 -> 
libvdpau_nouveau.so.1.0.0
-rw-r--r-- 4 root root 5132328 gen 13 09:41 libvdpau_nouveau.so.1.0.0
lrwxrwxrwx 1 root root  22 gen 13 09:41 libvdpau_r300.so -> 
libvdpau_r300.so.1.0.0
lrwxrwxrwx 1 root root  22 gen 13 09:41 libvdpau_r300.so.1 -> 
libvdpau_r300.so.1.0.0
lrwxrwxrwx 1 root root  22 gen 13 09:41 libvdpau_r300.so.1.0 -> 
libvdpau_r300.so.1.0.0
-rw-r--r-- 4 root root 5132328 gen 13 09:41 libvdpau_r300.so.1.0.0
lrwxrwxrwx 1 root root  22 gen 13 09:41 libvdpau_r600.so -> 
libvdpau_r600.so.1.0.0
lrwxrwxrwx 1 root root  22 gen 13 09:41 libvdpau_r600.so.1 -> 
libvdpau_r600.so.1.0.0
lrwxrwxrwx 1 root root  22 gen 13 09:41 libvdpau_r600.so.1.0 -> 
libvdpau_r600.so.1.0.0
-rw-r--r-- 4 root root 5132328 gen 13 09:41 libvdpau_r600.so.1.0.0
lrwxrwxrwx 1 root root  26 gen 13 09:41 libvdpau_radeonsi.so -> 
libvdpau_radeonsi.so.1.0.0
lrwxrwxrwx 1 root root  26 gen 13 09:41 libvdpau_radeonsi.so.1 -> 
libvdpau_radeonsi.so.1.0.0
lrwxrwxrwx 1 root root  26 gen 13 09:41 libvdpau_radeonsi.so.1.0 -> 
libvdpau_radeonsi.so.1.0.0
-rw-r--r-- 4 root root 5132328 gen 13 09:41 libvdpau_radeonsi.so.1.0.0
lrwxrwxrwx 1 root root  23 feb 19  2016 libvdpau_trace.so.1 -> 
libvdpau_trace.so.1.0.0
-rw-r--r-- 1 root root   55376 feb 19  2016 libvdpau_trace.so.1.0.0

$ xine
Questo è xine (X11 gui) - un riproduttore video libero v0.99.9.
(c) 2000-2014 The xine Team.
Failed to open VDPAU backend libvdpau_.so: impossibile aprire il file oggetto 
condiviso: File o directory non esistente
vo_vdpau: Can't create vdp device : No vdpau implementation.
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  151 (XVideo)
  Minor opcode of failed request:  17 ()
  Serial number of failed request:  2631
  Current serial number in output stream:  2631

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

Title:
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared
  object file: No such file or directory

Status in libvdpau package in Ubuntu:
  Triaged
Status in libvdpau-va-gl package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in vdr-plugin-xineliboutput package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Invalid
Status in xine-ui package in Ubuntu:
  Confirmed
Status in libvdpau package in Debian:
  New

Bug description:
  This has been bothering me at least since precise (although there the
  missing link went to libvdpau_nvidia.so which was all the more
  mysterious since I do not own NVIDIA hardware).  In numerous cases do
  I get a warning that libvdpau_i965.so is being tried to be accessed
  but it fails.  I also can't find that file anywhere on my system or in
  the Ubuntu repository.  I tried poking around with ldd to find out
  where the call to that lib comes from but so far unsuccessful.

  $ vdpauinfo
  display: :0   screen: 0
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object 
file: No such file or directory
  Error creating VDPAU device: 1

  libvdpau1:i386 is version 0.7-1 and vdpauinfo is 0.1-1

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

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

[Desktop-packages] [Bug 1745639] [NEW] package thunderbird 1:52.2.1+build1-0ubuntu0.16.04.1 failed to install/upgrade: unable to securely remove '/target/usr/share/pixmaps.dpkg-tmp': Read-only file sy

[Marco Del Longo]

Public bug reported:

The installation process crashed, that's all I can tell you

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: thunderbird 1:52.2.1+build1-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 Cannot stat file /proc/2350/fd/11: Stale file handle
 Cannot stat file /proc/2350/fd/12: Stale file handle
  USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ubuntu 2202 F pulseaudio
BuildID: 20170626135948
CasperVersion: 1.376.2
Channel: Unavailable
Date: Fri Jan 26 17:51:19 2018
ErrorMessage: unable to securely remove '/target/usr/share/pixmaps.dpkg-tmp': 
Read-only file system
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IpRoute:
 default via 192.168.1.1 dev wlp3s0  proto static  metric 600 
 169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
 192.168.1.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.1.4  metric 
600
LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
NoProfiles: True
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
RunningIncompatibleAddons: False
SourcePackage: thunderbird
Title: package thunderbird 1:52.2.1+build1-0ubuntu0.16.04.1 failed to 
install/upgrade: unable to securely remove 
'/target/usr/share/pixmaps.dpkg-tmp': Read-only file system
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/21/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K56CM.206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K56CM
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.:bvrK56CM.206:bd08/21/2012:svnASUSTeKCOMPUTERINC.:pnK56CM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK56CM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: K56CM
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-package xenial

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

Title:
  package thunderbird 1:52.2.1+build1-0ubuntu0.16.04.1 failed to
  install/upgrade: unable to securely remove '/target/usr/share/pixmaps
  .dpkg-tmp': Read-only file system

Status in thunderbird package in Ubuntu:
  New

Bug description:
  The installation process crashed, that's all I can tell you

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: thunderbird 1:52.2.1+build1-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/2350/fd/11: Stale file handle
   Cannot stat file /proc/2350/fd/12: Stale file handle
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2202 F pulseaudio
  BuildID: 20170626135948
  CasperVersion: 1.376.2
  Channel: Unavailable
  Date: Fri Jan 26 17:51:19 2018
  ErrorMessage: unable to securely remove '/target/usr/share/pixmaps.dpkg-tmp': 
Read-only file system
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.1.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.1.4  metric 
600
  LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Title: package thunderbird 1:52.2.1+build1-0ubuntu0.16.04.1 failed to 
install/upgrade: unable to securely remove 
'/target/usr/share/pixmaps.dpkg-tmp': Read-only file system
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K56CM.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K56CM
  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 

[Desktop-packages] [Bug 1676547] Re: No network connectivity (NIC unmanaged) after upgrade

[Marco Bianchi]

I am truly sorry to say that I have tried many of the recommended
solutions for this problem but to no avail. I am running Ubuntu 16.04 on
a AMD 8-core desktop machine and if I ever ever ever even try to give a
command like sudo apt-get update and apt-get upgrade I inevitably find
myself with an operating system without ethernet connection. I have been
unable to fix that no matter what I have tried so far. I have spent DAYS
reading the blogs and trying to get a fix for this bug. In the end the
only solution I could find so far was to use the original ssd back up
disk to get back to the original system, before the sudo apt-get update
etc commands. Can anyone in this forum or elsewhere explain in a simple
and clear manner how to fix this major issue with ubuntu upgrades?

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

Title:
  No network connectivity (NIC unmanaged) after upgrade

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Yakkety:
  Fix Released
Status in network-manager source package in Zesty:
  Fix Released

Bug description:
  Impact
  --
  When upgrading from Xenial (with all updates installed) to Yakkety/Zesty you 
will boot to a system without networking - sad!

  Test Case
  -
  1) Boot a xenial desktop system
  2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed
  3) Upgrade to yakkety or zesty
  3.5) Enable -proposed and download the new version of n-m "apt-get download 
network-manager"
  4) Reboot
  5) Observe you have no network

  If you install the version of network-manager from yakkety-proposed
  and then reboot you should have a network connection.

  1) Boot a xenial desktop system.
  2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed.
  3) Install nplan, configure to set up static network on an ethernet device 
using nplan.
  4) Upgrade to yakkety or zesty
  5) Reboot
  6) Observe that your system is still being managed by networkd rather than 
NetworkManager.

  Regression Potential
  

  Any failure to manage ethernet or wireless devices after upgrade, or
  issues with the use of netplan in conjunction with NetworkManager
  should be investigated as potential regressions. For example, if after
  upgrading, ethernet devices are no longer managed, or if devices that
  should be explicitly ignored by NetworkManager due to existing user
  configuration are now managed, these would indicate a possible
  regression caused by this update.

  Original Description
  

  nplan was installed during the upgrade process but I had no network
  connectivity after upgrading. Apparently, no package wanted to manage
  my ethernet connection.

  ProblemType: BugDistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.10
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Mar 27 11:34:04 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-16 (1531 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  PackageArchitecture: allSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago)
  VarLogDistupgradeTermlog:

  modified.conffile..etc.update-manager.meta-release: [modified]
  mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913

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

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

[Desktop-packages] [Bug 1676547] Re: No network connectivity (NIC unmanaged) after upgrade

[Marco Bianchi]

Also not to mention that even when I use my 16.04 without ever using the
sudo apt-get update command, the wifi network is also not detected by
ubuntu.

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

Title:
  No network connectivity (NIC unmanaged) after upgrade

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Yakkety:
  Fix Released
Status in network-manager source package in Zesty:
  Fix Released

Bug description:
  Impact
  --
  When upgrading from Xenial (with all updates installed) to Yakkety/Zesty you 
will boot to a system without networking - sad!

  Test Case
  -
  1) Boot a xenial desktop system
  2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed
  3) Upgrade to yakkety or zesty
  3.5) Enable -proposed and download the new version of n-m "apt-get download 
network-manager"
  4) Reboot
  5) Observe you have no network

  If you install the version of network-manager from yakkety-proposed
  and then reboot you should have a network connection.

  1) Boot a xenial desktop system.
  2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed.
  3) Install nplan, configure to set up static network on an ethernet device 
using nplan.
  4) Upgrade to yakkety or zesty
  5) Reboot
  6) Observe that your system is still being managed by networkd rather than 
NetworkManager.

  Regression Potential
  

  Any failure to manage ethernet or wireless devices after upgrade, or
  issues with the use of netplan in conjunction with NetworkManager
  should be investigated as potential regressions. For example, if after
  upgrading, ethernet devices are no longer managed, or if devices that
  should be explicitly ignored by NetworkManager due to existing user
  configuration are now managed, these would indicate a possible
  regression caused by this update.

  Original Description
  

  nplan was installed during the upgrade process but I had no network
  connectivity after upgrading. Apparently, no package wanted to manage
  my ethernet connection.

  ProblemType: BugDistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.10
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Mar 27 11:34:04 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-16 (1531 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  PackageArchitecture: allSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago)
  VarLogDistupgradeTermlog:

  modified.conffile..etc.update-manager.meta-release: [modified]
  mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913

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

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

[Desktop-packages] [Bug 1726738] [NEW] package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Miguel Pujante Marco]

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

Public bug reported:

upgrade to 17.10

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: cracklib-runtime 2.9.2-5build1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Tue Oct 24 01:18:27 2017
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2017-01-14 (282 days ago)
InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5
SourcePackage: cracklib2
Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: 
dependency problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago)

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


** Tags: amd64 apport-package artful

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

Title:
  package cracklib-runtime 2.9.2-5build1 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in cracklib2 package in Ubuntu:
  New

Bug description:
  upgrade to 17.10

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: cracklib-runtime 2.9.2-5build1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Tue Oct 24 01:18:27 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-01-14 (282 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: 
dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago)

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

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