[Desktop-packages] [Bug 2062133] Re: Migration to the snap issues

[Pablo Angulo]

As mentioned in
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2056434/comments/15
, if there is not enough free space for copying the .thunderbird folder
to its new snap location, then the migration will not be done,
thunderbird will open as new, and the user will not be notified at all.
Creating a soft link will not do. Moving the folder from ~/.thunberdird
to ~/snap/thunderbird/common/ did work.

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

Title:
  Migration to the snap issues

Status in thunderbird package in Ubuntu:
  In Progress

Bug description:
  After migrating to the snap, I noticed the following:
  - the launcher icon disappeared (I guess it’s because the .desktop file is 
now "thunderbird_thunderbird.desktop"
  - the snap migration took a good 5 minutes on my machine (I guess it’s the 
copy of the email folder), without any feedbacks that something is happening if 
you don’t look at ps output. You don’t have any visual feedback about the 
migration and we should have a progress window (maybe zenity?) to reassure on 
this one time transition
  - all unread emails triggered notification (I guess it’s because the state is 
considered "New") on any folders.
  - I know have 2 15G folders now: ~/snap/thunderbird/common/ and 
~/.thunderbird. I think the latter was the old one which is unused right now 
and it should be cleaned up after the migration to the snap?

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: thunderbird 2:1snap1-0ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 18 09:28:35 2024
  InstallationDate: Installed on 2020-04-24 (1455 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SnapChanges:
   Identifiant  État  DescendancePrêt   
Résumé
   700  Done  2024-04-18T09:06:12+02:00  2024-04-18T09:07:34+02:00  
Installer le paquet Snap "thunderbird"
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2056434] Re: Thunderbird profile not migrated to snap

[Pablo Angulo]

Thanks for your answer, Sebastien. I think you nailed it.
There was not enough free space to copy the profile and the profile was not 
copied.
I had tried to softlink my old profile from .thunderbird info 
snap/thunderbird/common/.thunderbird but that did not work, as I described, and 
it still doesn't.

However, moving the thunderbird profile instead of softlinking did solve
the problem.

The maybe a problem, though, since some people like myself have massive
profiles with years of emails, and users are warned about the root space
they need for the upgrade, but not the space in the home directory.
Specially if several users share the computer.

Regards

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

Title:
  Thunderbird profile not migrated to snap

Status in thunderbird package in Ubuntu:
  Fix Released

Bug description:
  Today's update installed the thunderbird snap and removed the
  thunderbird binary but it did not migrate my thunderbird profile.

  Now I don't have access to any old mails anymore.

  Looking at ~/.thunderbird:

  $ cat profiles.ini 
  [Profile1]
  Name=default
  IsRelative=1
  Path=ao6t0qef.default
  Default=1

  [InstallFDC34C9F024745EB]
  Default=ji04wv64.default-release
  Locked=1

  [Profile0]
  Name=default-release
  IsRelative=1
  Path=ji04wv64.default-release

  [General]
  StartWithLastProfile=1
  Version=2

  
  ji04wv64.default-release is the folder that should have been migrated.

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


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

[Desktop-packages] [Bug 2056434] Re: Thunderbird profile not migrated to snap

[Pablo Angulo]

Hello:
Thunderbird still does not migrate my profile. My system works fine after
```
apt remove thunderbird
snap remove thunderbird
dpkg -i ~/software/thunderbird_115.9.0+build1-0ubuntu0.22.04.1_amd64.deb
```
but thunderbird gets updated every day (unattended-upgrades?, snap refresh?) 
and starts fresh, ignoring my profile. I have tried to delete the 
~/snap/thunderbird folder, but it still does not migrate the profile correctly.
Any ideas?
Regards!

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

Title:
  Thunderbird profile not migrated to snap

Status in thunderbird package in Ubuntu:
  Fix Released

Bug description:
  Today's update installed the thunderbird snap and removed the
  thunderbird binary but it did not migrate my thunderbird profile.

  Now I don't have access to any old mails anymore.

  Looking at ~/.thunderbird:

  $ cat profiles.ini 
  [Profile1]
  Name=default
  IsRelative=1
  Path=ao6t0qef.default
  Default=1

  [InstallFDC34C9F024745EB]
  Default=ji04wv64.default-release
  Locked=1

  [Profile0]
  Name=default-release
  IsRelative=1
  Path=ji04wv64.default-release

  [General]
  StartWithLastProfile=1
  Version=2

  
  ji04wv64.default-release is the folder that should have been migrated.

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


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

[Desktop-packages] [Bug 2060304] [NEW] JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4

[Pablo Catalina]

Public bug reported:

Related to #1988393.

It also affects Jammy and no fix was provided to Jammy.

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

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

Title:
  JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js
  287]: Too many arguments to method Gio.AsyncInitable.init_async:
  expected 3, got 4

Status in gjs package in Ubuntu:
  New

Bug description:
  Related to #1988393.

  It also affects Jammy and no fix was provided to Jammy.

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


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

[Desktop-packages] [Bug 1988393] Re: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4

[Pablo Catalina]

Still seeing the same in recent jammy

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

Title:
  JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js
  287]: Too many arguments to method Gio.AsyncInitable.init_async:
  expected 3, got 4

Status in gjs:
  Fix Released
Status in gjs package in Ubuntu:
  Fix Released

Bug description:
  I'm seeing this in everyone's kinetic logs:

  JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js
  287]: Too many arguments to method Gio.AsyncInitable.init_async:
  expected 3, got 4

  and it appears gjs is the only place where too many arguments are
  provided.

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


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

[Desktop-packages] [Bug 2056668] Re: Thunderbird Snap migration loses user profile

[Pablo Angulo]

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

Hello:

I started with the same proble.

By following that advice:

`ln -s /home/pang/.thunderbird /home/pang/snap/thunderbird/common/`

my profile does appear in the list when I run `thunderbird -P`, but then

 1. I get the following output
```
[GFX1-]: glxtest: libpci missing
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error: 
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error: 
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error: 
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error: 
Can't find profile directory.
console.error: (new UnknownError("IndexedDB: 
thunderbird/url-classifier-skip-urls getLastModified() IndexedDB:   The 
operation failed for reasons unrelated to the database itself and not covered 
by any other error code.", "resource://services-settings/IDBHelpers.jsm", 18))
[GFX1-]: glxtest: libpci missing
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error: 
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error: 
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error: 
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error: 
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error: 
Can't find profile directory.
```
 2. then a popup window appear with the text
```Thunderbird is already running, but is not responding. To use Thunderbird, 
you must first close the existing Thunderbird process, restart your device, or 
use a different profile.```, and an "ok" button

 3. When I click the ok button, the window closes, and thunderbird does
not raise.

Is this the same bug?

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

Title:
  Thunderbird Snap migration loses user profile

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  TL;DR: Snap implementation is FUBAR, how do I get back to a non-SNAP
  version?

  I consider this bug to be Grave since it not only affects thunderbid,
  but also a huge number of depending other services, bug-reporting
  amongst it.

  Thunderbird Snap migration loses user profile

  With the migration from normal deb to snap all and any settings, addons, 
accounts, etc got lost.
  This is a big no-no.


  Architecture: amd64
  Version: 1:115.8.1+build1+snap2

  No LSB modules are available.
  Description:  Ubuntu Noble Numbat (development branch)
  Release:  24.04

  root@kyle:/opt/DATA/media/incoming/tmp# apt-cache policy thunderbird
  thunderbird:
Installed: 1:115.8.1+build1+snap2
Candidate: 1:115.8.1+build1+snap2
Version table:
   *** 1:115.8.1+build1+snap2 500
  500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
  100 /var/lib/dpkg/status
   1:115.8.1+build1-0ubuntu0.23.10.1 500
  500 http://archive.ubuntu.com/ubuntu mantic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu mantic-security/main amd64 
Packages
   1:115.3.1+build1-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages

  neuffer@kyle:~$ ls -la ~/.thunderbird/
  total 28
  drwx--  5 neuffer neuffer 4096 Okt  7  2019  .
  drwxr-x--- 26 neuffer neuffer 4096 Mär 10 11:09  ..
  drwx-- 17 neuffer neuffer 4096 Mär  5 17:50  8ru3o2xn.default
  drwx--  4 neuffer neuffer 4096 Mär  5 15:58 'Crash Reports'
  -rw-rw-r--  1 neuffer neuffer   45 Okt  7  2019  installs.ini
  drwx--  2 neuffer neuffer 4096 Apr  2  2019 'Pending Pings'
  -rw-rw-r--  1 neuffer neuffer  166 Okt  7  2019  profiles.ini
  neuffer@kyle:~$ 


  neuffer@kyle:~$ thunderbird --ProfileManager
  _IceTransSocketINETConnect() no usable address for kyle:44955
  [GFX1-]: glxtest: libpci missing
  ATTENTION: default value of option mesa_glthread overridden by environment.
  ATTENTION: default value of option mesa_glthread overridden by environment.
  ATTENTION: default value of option mesa_glthread overridden by environment.
  [Parent 27516, Main Thread] WARNING: Failed to mkdir 
/home/neuffer/snap/thunderbird/450/.config/ibus/bus: Not a directory: 

[Desktop-packages] [Bug 2043524] Re: audio disappeared after upgrade to Ubuntu 23.10

[Pablo Fontoura]

Same thing  here. Fresh 23.10 installation and no sound. 
My USB headset is working properly.

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

Title:
  audio disappeared after upgrade to Ubuntu 23.10

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except
  there is no audio output on streaming functions. The external
  bluetooth speaker is connected and detected. It is charged and
  responds to testing. Just no sound when playing videos or podcasts.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: pulseaudio 1:16.1+dfsg1-2ubuntu4
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  owner   975 F wireplumber
   /dev/snd/seq:owner   971 F pipewire
  CasperMD5CheckResult: fail
  CurrentDesktop: KDE
  Date: Tue Nov 14 17:50:17 2023
  InstallationDate: Installed on 2023-04-15 (213 days ago)
  InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  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: Upgraded to mantic on 2023-11-09 (5 days ago)
  dmi.bios.date: 07/04/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V3.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-P31/W8 (MS-7788)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7788
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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


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

[Desktop-packages] [Bug 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead

[Pablo Hörtner]

Hi Angel, maybe your sources list needs to be adjusted accordingly? I
have it in the sources:

apt policy gnome-shell-extension-ubuntu-dock
gnome-shell-extension-ubuntu-dock:
  Installed: 87ubuntu1
  Candidate: 87ubuntu1
  Version table:
 87ubuntu2 100
100 http://mirror.easyname.at/ubuntu-archive mantic-proposed/main amd64 
Packages
100 http://mirror.easyname.at/ubuntu-archive mantic-proposed/main i386 
Packages
 *** 87ubuntu1 500
500 http://mirror.easyname.at/ubuntu-archive mantic/main amd64 Packages
500 http://mirror.easyname.at/ubuntu-archive mantic/main i386 Packages
100 /var/lib/dpkg/status

Regarding the bug, I can confirm that by removing the gnome-shell-
extension-ubuntu-dock package I could get rid of those log warnings
(although the ubuntu-desktop-minimal package depends on gnome-shell-
extension-ubuntu-dock).

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

Title:
  Meta.Rectangle is deprecated, use Mtk.Rectangle instead

Status in gnome-shell-extension-tiling-assistant package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-tiling-assistant source package in Mantic:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

  The gnome-shell 45.rc log fills with:

  Meta.Rectangle is deprecated, use Mtk.Rectangle instead

  [ Test case ]

  Run ubuntu with ubuntu extensions enabled (only).
  journalctl /usr/bin/gnome-shell should not contain any reference to 
Meta.Rectangle deprecation

  [ Regression potential ]

  Introspected types are not defined and so extensions may try to use
  undefined code.

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


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

[Desktop-packages] [Bug 2022997] Re: Nautilus does not update view properly when deleting or moving files unless refreshed

[Pablo Herrero Fernández]

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

Sorry about asking this but... How did you upgraded nautilus in Ubuntu
23.04?? Is there any repo that can be added?? Or did you built it from
source?

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

Title:
  Nautilus does not update view properly when deleting or moving files
  unless refreshed

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

Bug description:
  This issue happens in Nautilus 44.0, both on Wayland and X11, and has also 
been noted in upstream Gnome as well:
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/2945

  
  When deleting files, only the file being deleted should be shown as deleted, 
  and when moving files/folders, the file/folder should appear as-is in the 
destination directory.

  However, this is not the case here. When deleting, the file/folder gets 
deleted correctly in the filesystem, but Nautilus does not update the view 
properly. The file being deleted still remains, instead showing another file to 
be deleted and when undoing delete operation via [Ctrl-Z], it shows a duplicate 
of the deleted file/folder.
  This issue persists until you refresh the view [F5], when the view shows up 
correctly.

  Also, when moving files/folders to another directory, the file/folder
  initially shows up as a blank 'text' file named '', until you refresh
  the view, when it shows up correctly.

  It is worth noting that this issue has apparently been fixed in Fedora
  and Arch for a while (see gitlab bug report linked above). Please
  implement the same fixes here in Ubuntu as well.

  System details:
  OS: Ubuntu
  Version: 23.04
  GNOME Version: 44.0
  Kernel: Linux 6.2.0-20-generic

  Package details:
  nautilus:
Installed: 1:44.0-1ubuntu2
Candidate: 1:44.0-1ubuntu2
Version table:
   *** 1:44.0-1ubuntu2 500
  500 http://ae.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: nautilus 1:44.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  6 08:45:58 2023
  GsettingsChanges:
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.preferences' b'show-create-link' b'true'
   b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 549)'
  InstallationDate: Installed on 2023-06-03 (2 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.48.0-1ubuntu1

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


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

[Desktop-packages] [Bug 1988315]

[pablo]

Fixed a long time ago, closing

*** This bug has been marked as a duplicate of bug 2127826 ***

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

Title:
  gnome-shell crashed with SIGABRT
  [Clutter:ERROR:../clutter/clutter/clutter-
  actor.c:11749:clutter_actor_destroy_all_children: assertion failed:
  (self->priv->n_children < prev_n_children)] in
  indicatorStatusIcon.js:317

Status in Ubuntu AppIndicators:
  Fix Released
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator package in Fedora:
  Invalid

Bug description:
  After upgrading to kinetic gnome-shell is crashing on start when using
  wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 31 10:28:31 2022
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-bionic-amd64-20200511-23+sutton-knuth-bionic-amd64+iso
  InstallationDate: Installed on 2020-05-18 (834 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20200511-12:31
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43~beta-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-08-30 (0 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-05-11T08:18:53

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


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

[Desktop-packages] [Bug 1971769] Re: Cheese not running on Ubuntu 22.04 Wayland [Error reading events from display: Protocol error]

[Pablo Catalina]

I have the same problem running Ubuntu 22.04 Wayland.

$ cheese

(cheese:14884): Gdk-WARNING **: 10:23:38.778: Native Windows taller than 65535 
pixels are not supported
Gdk-Message: 10:23:39.260: Error reading events from display: Protocol error



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

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

Title:
  Cheese not running on Ubuntu 22.04 Wayland [Error reading events from
  display: Protocol error]

Status in cheese package in Ubuntu:
  Confirmed

Bug description:
  $ cheese

  (cheese:108091): Gdk-WARNING **: 01:22:35.973: Native Windows taller than 
65535 pixels are not supported
  Gdk-Message: 01:22:36.459: Error reading events from display: Protocol error

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


-- 
Mailing list: https://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 1991507] Re: Monitor does not turn on

[Pablo]

Thanks this solves my problem

El lun, 3 oct 2022 a las 10:00, Daniel van Vugt (<1991...@bugs.launchpad.net>)
escribió:

> Thanks for the bug report. This is probably bug 1968040 so please try
> the workaround mentioned there.
>
>
> ** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
>
> ** Changed in: mutter (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1991507
>
> Title:
>   Monitor does not turn on
>
> Status in mutter package in Ubuntu:
>   Incomplete
>
> Bug description:
>   The main screen does not turn on after the monitors are turned off due
>   to energy saving (there is no video signal). The secondary screen
>   turns on correctly. It doesn't happen every time
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 22.04
>   Package: xorg 1:7.7+23ubuntu2
>   ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
>   Uname: Linux 5.15.0-48-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu82.1
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
>   CasperMD5CheckResult: pass
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Mon Oct  3 09:17:24 2022
>   DistUpgraded: Fresh install
>   DistroCodename: jammy
>   DistroVariant: ubuntu
>   DpkgLog:
>
>   ExtraDebuggingInterest: No
>   GraphicsCard:
>Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA
> controller])
>  Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8299]
>   InstallationDate: Installed on 2022-09-26 (6 days ago)
>   InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
> (20220809.1)
>   Lsusb:
>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 001 Device 003: ID 1c4f:00b0 SiGma Micro USB Optical Mouse
>Bus 001 Device 002: ID 03f0:2b4a HP, Inc Business Slim Keyboard
>Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
> Dongle (HCI mode)
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: HP Z4D06EA#ABE
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=es_ES.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic
> root=UUID=f28d3bdb-0af0-4cbf-a682-38f39118cb88 ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 04/14/2019
>   dmi.bios.release: 2.27
>   dmi.bios.vendor: HP
>   dmi.bios.version: P01 Ver. 02.27
>   dmi.board.name: 8299
>   dmi.board.vendor: HP
>   dmi.board.version: KBC Version 06.21
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: HP
>   dmi.ec.firmware.release: 6.33
>   dmi.modalias:
> dmi:bvnHP:bvrP01Ver.02.27:bd04/14/2019:br2.27:efr6.33:svnHP:pnZ4D06EA#ABE:pvr:rvnHP:rn8299:rvrKBCVersion06.21:cvnHP:ct3:cvr:skuZ4D06EA:
>   dmi.product.family: 103C_53307F HP EliteDesk
>   dmi.product.name: Z4D06EA#ABE
>   dmi.product.sku: Z4D06EA
>   dmi.sys.vendor: HP
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.110-1ubuntu1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>   version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20210115-1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.17-2build1
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1991507/+subscriptions
>
>

--

[image: JIMSPORTS BANNER]

Pablo Luaces
Departamento de desarrollo y nuevas tecnologías
982 286 100 - Ext. 739
pa...@jimsports.com
www.jimsports.com <https://jimsports.com>
[image: Logo Grupo Jim Sports]
[image: Jim Sports Certificates] Grupo Jim Sports
Polígono Industrial Palas de Rei s/n
27200 Palas de Rei - Lugo [image: Whatsapp]
<https://api.whatsapp.com/send?phone=34683408532>[image: Twitter]
<https://twitter.com/GrupoJimSports>[image: Facebook]
<http://www.facebook.com/grupo.jimsports>[image: LinkedIn]
<https://es.linkedin.com/company/grupo-jim-sports>[image: Instagram]
<https://www.instagram.com/softeejimsports/?hl=es>[image: RSS]
<https://jimsports.com/?feed=rss>
Los datos de carácter personal que se incluyen en la presente comunicación
se contienen en los tratamientos de datos personales r

[Desktop-packages] [Bug 1991507] [NEW] Monitor does not turn on

[Pablo]

Public bug reported:

The main screen does not turn on after the monitors are turned off due
to energy saving (there is no video signal). The secondary screen turns
on correctly. It doesn't happen every time

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct  3 09:17:24 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8299]
InstallationDate: Installed on 2022-09-26 (6 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1c4f:00b0 SiGma Micro USB Optical Mouse
 Bus 001 Device 002: ID 03f0:2b4a HP, Inc Business Slim Keyboard
 Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle 
(HCI mode)
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP Z4D06EA#ABE
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=f28d3bdb-0af0-4cbf-a682-38f39118cb88 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/14/2019
dmi.bios.release: 2.27
dmi.bios.vendor: HP
dmi.bios.version: P01 Ver. 02.27
dmi.board.name: 8299
dmi.board.vendor: HP
dmi.board.version: KBC Version 06.21
dmi.chassis.type: 3
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 6.33
dmi.modalias: 
dmi:bvnHP:bvrP01Ver.02.27:bd04/14/2019:br2.27:efr6.33:svnHP:pnZ4D06EA#ABE:pvr:rvnHP:rn8299:rvrKBCVersion06.21:cvnHP:ct3:cvr:skuZ4D06EA:
dmi.product.family: 103C_53307F HP EliteDesk
dmi.product.name: Z4D06EA#ABE
dmi.product.sku: Z4D06EA
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu wayland-session

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

Title:
  Monitor does not turn on

Status in xorg package in Ubuntu:
  New

Bug description:
  The main screen does not turn on after the monitors are turned off due
  to energy saving (there is no video signal). The secondary screen
  turns on correctly. It doesn't happen every time

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  3 09:17:24 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8299]
  InstallationDate: Installed on 2022-09-26 (6 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1c4f:00b0 SiGma Micro USB Optical Mouse
   Bus 001 Device 002: ID 03f0:2b4a HP, Inc Business Slim Keyboard
   Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP Z4D06EA#ABE
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=f28d3bdb-0af0-4cbf-a682-38f39118cb88 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh 

[Desktop-packages] [Bug 1988315]

[pablo]

Just confirmed that updating gnome-shell-extension-appindicator to the
code in the "ubuntu/jammy" branch makes the crash disappear

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

Title:
  gnome-shell crashed with SIGABRT
  [Clutter:ERROR:../clutter/clutter/clutter-
  actor.c:11749:clutter_actor_destroy_all_children: assertion failed:
  (self->priv->n_children < prev_n_children)] in
  indicatorStatusIcon.js:317

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-appindicator package in Fedora:
  Confirmed

Bug description:
  After upgrading to kinetic gnome-shell is crashing on start when using
  wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 31 10:28:31 2022
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-bionic-amd64-20200511-23+sutton-knuth-bionic-amd64+iso
  InstallationDate: Installed on 2020-05-18 (834 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20200511-12:31
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43~beta-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-08-30 (0 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-05-11T08:18:53

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


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

[Desktop-packages] [Bug 1777708] Re: Desktop briefly becomes unresponsive when receiving a keypress from a different device/mapping than the last keypress (in Xorg)

[Pablo Q]

I have checked that the Osvald Lindholm fix works. Thanks bro!

This problem is a real pain in the ass.

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

Title:
  Desktop briefly becomes unresponsive when receiving a keypress from a
  different device/mapping than the last keypress (in Xorg)

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

Bug description:
  I'm running Ubuntu 18.04 and Gnome 3.28.1 with all the latest updates
  from the repos.

  If I connect 2 (or more) keyboards to my computer and type on both at
  the same time, the desktop briefly becomes unresponsive. More
  keypresses increase the time of unresponsiveness.

  E.g. when typing a full sentence in gedit or the terminal, only very
  few characters show up on the screen (I guess up until something is
  pressed on both keyboards at the same time), then everything freezes.
  Then after a while (some seconds), all the characters show up. And the
  desktop becomes responsive again.

  Symptoms: During the freeze, windows stop updating their content. If
  seconds are enabled on the clock at the top middle, these freeze too.
  But I'm still able to move the mouse pointer around during the freeze
  without any problems.

  The back story:

  I got an ergonomic keyboard (R-Go Split Keyboard) yesterday, and
  quickly noticed the issue. But initiallly I thought it was an issue
  with the keyboard, and the problem wasn't that bad. But as I've gotten
  more used to the keyboard since yesterday and started picking up a
  proper typing speed, things got worse.

  The keyboard is technically two separate cabled USB keyboards each
  with only about half of they keys of a normal keyboard (or at least
  that's very much my impression).

  After getting the suspicion that this was a software issue, not a
  hardware issue, I tried typing on my old Logitech keyboard (Unifying
  Receiver) along with one of the R-Go halves: Same issue. Then I tried
  each of the halves without the other (as in "single" keyboard typing):
  No issue. Then I connected another Logitech keyboard (separate UR),
  typed on both Logitechs: Same issue.

  Some further observations:

  1) Nothing of significance in my syslog.
  2) If I drop to a non-graphical shell, there's no problem. I suspect this 
issue is related to X.org or Gnome, but I'm in no position to say anything 
credible about that.
  3) Also no problems when connecting the R-Go keyboard to a Windows or a MacOS 
machine.

  Let me know if there are any logs I can provide or things I can run to
  produce useful debug output.

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


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

[Desktop-packages] [Bug 1065126]

[Pablo-muir]

*** Bug 1731479 has been marked as a duplicate of this bug. ***

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

Title:
  "Always do this from now on" does not work

Status in Mozilla Firefox:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Downloading an unknown file type in Firefox displays a dialog for choosing 
which application to use for opening the file.
  The dialog contains a check box labelled "Always do this action from now on".
  Checking this option does not work: When I download a file of the same type 
next time, the same dialog is displayed again.

  This feature is broken for as long as I can remember (> 10 years).
  It's time it was fixed (or removed).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 15.0.1+build1-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
  Uname: Linux 3.2.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ruediger   2536 F pulseaudio
  BuildID: 20120907231657
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfe22 irq 49'
     Mixer name : 'Analog Devices AD1984'
     Components : 'HDA:11d41984,17aa20bb,00100400'
     Controls  : 32
     Simple ctrls  : 20
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
7KHT24WW-1.08'
     Mixer name : 'ThinkPad EC 7KHT24WW-1.08'
     Components : ''
     Controls  : 1
     Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
     Capabilities: pswitch pswitch-joined penum
     Playback channels: Mono
     Mono: Playback [on]
  Channel: Unavailable
  Date: Wed Oct 10 18:17:44 2012
  EcryptfsInUse: Yes
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  IpRoute:
   default via 172.31.0.1 dev wlan0  proto static
   169.254.0.0/16 dev wlan0  scope link  metric 1000
   172.31.0.0/20 dev wlan0  proto kernel  scope link  src 172.31.9.26  metric 2
  MostRecentCrashID: bp-7716491c-74b4-4213-bbf0-37b512110505
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=15.0.1/20120907231657 (In use)
  RelatedPackageVersions:
   rhythmbox-mozilla 2.96-0ubuntu4.2
   totem-mozilla 3.0.1-0ubuntu21.1
   icedtea-6-plugin  1.2-2ubuntu1.2
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to precise on 2012-04-28 (165 days ago)
  dmi.bios.date: 03/18/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETC9WW (2.29 )
  dmi.board.name: 6457BBG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:svnLENOVO:pn6457BBG:pvrThinkPadT61:rvnLENOVO:rn6457BBG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 6457BBG
  dmi.product.version: ThinkPad T61
  dmi.sys.vendor: LENOVO

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


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

[Desktop-packages] [Bug 1934797] [NEW] Keyboard freeze for several seconds when I switch language (ENG -> ES)

[Pablo Q]

Public bug reported:

Something funny is happening with the mapping of my keyboard when I
switch language. This provokes that the system is frozen for several
seconds.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.9-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
Uname: Linux 5.4.0-77-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul  6 08:45:18 2021
DisplayManager: gdm3
InstallationDate: Installed on 2016-11-20 (1689 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-10-04 (274 days ago)

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


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

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

Title:
  Keyboard freeze for several seconds when I switch language (ENG -> ES)

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Something funny is happening with the mapping of my keyboard when I
  switch language. This provokes that the system is frozen for several
  seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  Uname: Linux 5.4.0-77-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  6 08:45:18 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-11-20 (1689 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-04 (274 days ago)

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

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

[Desktop-packages] [Bug 1926462] [NEW] Typo 'libreoffice-oopslash' in /usr/lib/libreoffice/program/oosplash

[Pablo Hörtner]

Public bug reported:

Affected package: libreoffice-common (1:6.4.7-0ubuntu0.20.04.1, focal-
updates)

While investigating the reason for lot of aa messages flooding my kernel
logs, I noticed a (supposed) typo in the file
/usr/lib/libreoffice/program/oosplash at line 17. I guess 'libreoffice-
oopslash' should be 'libreoffice-oopslash'.

It seems that the issue has already been reported one and a half years ago:
https://listarchives.libreoffice.org/global/users/2019/msg00812.html

Fix: Edit /usr/lib/libreoffice/program/oosplash, systemctl reload-or-
restart apparmor.service, aa-remove-unknown to remove libreoffice-
oopslash aka :-O/

PS: My initial "issue" that is filling up my /var/log/kern.log persists,
but this might be a misconfiguration on my side. :-)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libreoffice-common 1:6.4.7-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.8.0-51.57~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-51-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 28 16:49:54 2021
InstallationDate: Installed on 2018-12-11 (869 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitecture: all
SourcePackage: libreoffice
UpgradeStatus: Upgraded to focal on 2020-10-26 (184 days ago)

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

Title:
  Typo 'libreoffice-oopslash' in /usr/lib/libreoffice/program/oosplash

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Affected package: libreoffice-common (1:6.4.7-0ubuntu0.20.04.1, focal-
  updates)

  While investigating the reason for lot of aa messages flooding my
  kernel logs, I noticed a (supposed) typo in the file
  /usr/lib/libreoffice/program/oosplash at line 17. I guess
  'libreoffice-oopslash' should be 'libreoffice-oopslash'.

  It seems that the issue has already been reported one and a half years ago:
  https://listarchives.libreoffice.org/global/users/2019/msg00812.html

  Fix: Edit /usr/lib/libreoffice/program/oosplash, systemctl reload-or-
  restart apparmor.service, aa-remove-unknown to remove libreoffice-
  oopslash aka :-O/

  PS: My initial "issue" that is filling up my /var/log/kern.log
  persists, but this might be a misconfiguration on my side. :-)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-common 1:6.4.7-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-51.57~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-51-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 28 16:49:54 2021
  InstallationDate: Installed on 2018-12-11 (869 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to focal on 2020-10-26 (184 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-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)

[Pablo Piaggio]

Same problem here. It also affects: 5.8.0-34-generic

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.1 LTS
Release:20.04
Codename:   focal

$ uname -a
Linux vanhalen 5.8.0-34-generic #37~20.04.2-Ubuntu SMP Thu Dec 17 14:53:00 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

Also, this is valid: https://askubuntu.com/questions/969352
/uninstalling-and-then-reinstalling-nvidia-384-kills-colord

In other words the shell bug is still there, however, fixing manually
does not fix the problem, as some header problem stops the creation of
the module.

Any alternative?  nouveau is heating up my system.

Thanks in advance,

-- 
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 1903995] Re: upower report wrong battery percentage for Logitech Unify devices

[Pablo Catalina]

I recharged the mouse, but:

$ solaar show
Unifying Receiver
  Device path  : /dev/hidraw0
  USB id   : 046d:c52b
  Serial   : 23FF9429
Firmware   : 12.10.B0032
Bootloader : 02.15
Other  : AA.AA
  Has 3 paired device(s) out of a maximum of 6.
  Notifications: wireless (0x000100)
  Device activity counters: 1=70, 2=105

  1: Wireless Keyboard K270(unifying)
 Codename : K270(unifying)
 Kind : keyboard
 Wireless PID : 4003
 Protocol : HID++ 2.0
 Polling rate : 20 ms (50Hz)
 Serial number: 1A395FC1
  Firmware: RQK 35.00.B0017
 The power switch is located on the top case.
 Supports 12 HID++ 2.0 features:
 0: ROOT   {}   
 1: FEATURE SET{0001}   
 2: DEVICE FW VERSION  {0003}   
 3: DEVICE NAME{0005}   
 4: BATTERY STATUS {1000}   
 5: unknown:1820   {1820}   hidden
 6: REPROG CONTROLS{1B00}   
 7: WIRELESS DEVICE STATUS {1D4B}   
 8: unknown:1DF0   {1DF0}   hidden
 9: unknown:1DF3   {1DF3}   hidden
10: ENCRYPTION {4100}   
11: KEYBOARD LAYOUT{4520}   
 Has 8 reprogrammable keys:
 0: Play/Pause => Play/Pause
nonstandard
 1: Mute   => Mute  
nonstandard
 2: Volume Down=> Volume Down   
nonstandard
 3: Volume Up  => Volume Up 
nonstandard
 4: MY HOME=> HomePage  
nonstandard, reprogrammable
 5: Mail   => Email 
nonstandard, reprogrammable
 6: SLEEP  => Sleep 
nonstandard, reprogrammable
 7: Calculator => Calculator
nonstandard, reprogrammable
 Battery: 70%, discharging.

  2: Wireless Mouse MX Master
 Codename : MX Master
 Kind : mouse
 Wireless PID : 4071
 Protocol : HID++ 4.5
 Polling rate : 8 ms (125Hz)
 Serial number: F8EBBFD1
Bootloader: BOT 56.10.B0005
  Firmware: MPM 12.10.B0005
  Firmware: MPM 12.10.B0005
 Other: 
 The power switch is located on the base.
 Supports 32 HID++ 2.0 features:
 0: ROOT   {}   
 1: FEATURE SET{0001}   
 2: DEVICE FW VERSION  {0003}   
 3: DEVICE NAME{0005}   
 4: WIRELESS DEVICE STATUS {1D4B}   
 5: RESET  {0020}   
 6: unknown:0021   {0021}   
 7: BATTERY STATUS {1000}   
 8: unknown:1806   {1806}   internal, hidden
 9: CHANGE HOST{1814}   
10: REPROG CONTROLS V4 {1B04}   
11: ADJUSTABLE DPI {2201}   
12: VERTICAL SCROLLING {2100}   
Roller type: 3G
Ratchet per turn: 24
Scroll lines: 0
13: SMART SHIFT{2110}   
14: HIRES WHEEL{2121}   
Multiplier: 8
Has invert
  Normal wheel motion
Has ratchet switch
  Normal wheel mode
High resolution mode
HID notification
15: GESTURE 2  {6501}   
16: unknown:00C2   {00C2}   
17: unknown:1813   {1813}   internal, hidden
18: unknown:1830   {1830}   internal, hidden
19: unknown:1890   {1890}   internal, hidden
20: unknown:1891   {1891}   internal, hidden
21: unknown:18A1   {18A1}   internal, hidden
22: unknown:18C0   {18C0}   internal, hidden
23: unknown:1DF3   {1DF3}   internal, hidden
24: unknown:1E00   {1E00}   hidden
25: unknown:1EB0   {1EB0}   internal, hidden
26: unknown:1803   {1803}   internal, hidden
27: unknown:1861   {1861}   internal, hidden
28: unknown:9001   {9001}   internal, hidden
29: unknown:9200   {9200}   internal, hidden
30: unknown:9202   {9202}   internal, hidden
31: unknown:1805   {1805}   internal, hidden
 Has 8 reprogrammable keys:
 0: LEFT CLICK, default: LeftClick   => 
LEFT CLICK
 mse, pos:0, group:1, gmask:1
 1: RIGHT CLICK   , default: RightClick  => 
RIGHT CLICK   
 mse, pos:0, group:1, gmask:1
 2: MIDDLE BUTTON , default: MiddleMouseButton   => 
MIDDLE BUTTON 
 mse, reprogrammable, divertable, pos:0, group:3, gmask:7
 3: BACK AS BUTTON 4 

[Desktop-packages] [Bug 1903755] Re: removable-media interface missing but useful to access shared profiles

[Pablo Alvarez]

Everything is ok now. Works perfectly.

A lot of thanks.

** Attachment added: "Screenshot from 2020-11-13 09-21-07.png"
   
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1903755/+attachment/5434052/+files/Screenshot%20from%202020-11-13%2009-21-07.png

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

Title:
  removable-media interface missing but useful to access shared profiles

Status in thunderbird package in Ubuntu:
  Fix Released

Bug description:
  ---
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  ---
  thunderbird 74.8.1 - channel lastest/stable
  ---
  I try to connect to an exist profile in a ntfs partition.
  But the "Read/write files on removable storage device option" is missing in 
permissions.
  --
  I can't launch thunderbird with a profile located in a mnt (ntfs partition) 
device.

  Thunderbird does not have auto-connect of removable-media, and i can't
  connect it manually with:

  snap connect thunderbird:removable-media

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

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

[Desktop-packages] [Bug 1903755] Re: removable-media interface missing but useful to access shared profiles

[Pablo Alvarez]

Greatest news.

Tomorrow i'll try the new release and i'll comment here if everything is
fine.

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

Title:
  removable-media interface missing but useful to access shared profiles

Status in thunderbird package in Ubuntu:
  Fix Released

Bug description:
  ---
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  ---
  thunderbird 74.8.1 - channel lastest/stable
  ---
  I try to connect to an exist profile in a ntfs partition.
  But the "Read/write files on removable storage device option" is missing in 
permissions.
  --
  I can't launch thunderbird with a profile located in a mnt (ntfs partition) 
device.

  Thunderbird does not have auto-connect of removable-media, and i can't
  connect it manually with:

  snap connect thunderbird:removable-media

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

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

[Desktop-packages] [Bug 1903995] [NEW] upower report wrong battery percentage for Logitech Unify devices

[Pablo Catalina]

Public bug reported:

The battery percentage reported by upower for Logitech devices connected
using Unify receiver are wrong.  Below are the results for two devices:
Mouse and Keyboard:

* Battery percentages reported by Unify receiver using Solaar:

$ solaar show  | grep -iP "^((  \d: )|(.*batt.*))"
  1: Wireless Keyboard K270(unifying)
 4: BATTERY STATUS {1000}
 Battery: 70%, discharging.
  2: Wireless Mouse MX Master
 7: BATTERY STATUS {1000}
 Battery: 20%, discharging.


* Battery percentages reported by upower:

$ upower -i /org/freedesktop/UPower/devices/keyboard_hidpp_battery_0
  native-path:  hidpp_battery_0
  model:Wireless Keyboard K270
  serial:   4003-1a-39-5f-c1
  power supply: no
  updated:  Thu 12 Nov 2020 13:59:18 CET (119 seconds ago)
  has history:  yes
  has statistics:   yes
  keyboard
present: yes
rechargeable:yes
state:   discharging
warning-level:   none
battery-level:   normal
percentage:  55% (should be ignored)
icon-name:  'battery-low-symbolic'

$ upower -i /org/freedesktop/UPower/devices/mouse_hidpp_battery_1
  native-path:  hidpp_battery_1
  model:Wireless Mouse MX Master
  serial:   4071-f8-eb-bf-d1
  power supply: no
  updated:  Thu 12 Nov 2020 14:03:14 CET (27 seconds ago)
  has history:  yes
  has statistics:   yes
  mouse
present: yes
rechargeable:yes
state:   discharging
warning-level:   low
battery-level:   low
percentage:  10% (should be ignored)
icon-name:  'battery-caution-symbolic'


Basically the difference is big so I'm getting a lot of notifications
related to low battery even if the battery is OK:

* Mouse, upower: 10%real (Solaar): 20%
* Keyboard: upower: 70%real (Solaar): 55%


ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: upower 0.99.11-1build2
ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
Uname: Linux 5.4.0-53-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 12 13:58:35 2020
InstallationDate: Installed on 2020-04-19 (206 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417)
SourcePackage: upower
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.apport.crashdb.conf: 2020-06-17T11:02:56.934699

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


** Tags: amd64 apport-bug focal

** Description changed:

  The battery percentage reported by upower for Logitech devices connected
  using Unify receiver are wrong.  Below are the results for two devices:
  Mouse and Keyboard:
  
- 
  * Battery percentages reported by Unify receiver using Solaar:
  
  $ solaar show  | grep -iP "^((  \d: )|(.*batt.*))"
-   1: Wireless Keyboard K270(unifying)
-  4: BATTERY STATUS {1000}   
-  Battery: 70%, discharging.
-   2: Wireless Mouse MX Master
-  7: BATTERY STATUS {1000}   
-  Battery: 20%, discharging.
+   1: Wireless Keyboard K270(unifying)
+  4: BATTERY STATUS {1000}
+  Battery: 70%, discharging.
+   2: Wireless Mouse MX Master
+  7: BATTERY STATUS {1000}
+  Battery: 20%, discharging.
  
  
  * Battery percentages reported by upower:
+ 
  $ upower -i /org/freedesktop/UPower/devices/keyboard_hidpp_battery_0
-   native-path:  hidpp_battery_0
-   model:Wireless Keyboard K270
-   serial:   4003-1a-39-5f-c1
-   power supply: no
-   updated:  Thu 12 Nov 2020 13:59:18 CET (119 seconds ago)
-   has history:  yes
-   has statistics:   yes
-   keyboard
- present: yes
- rechargeable:yes
- state:   discharging
- warning-level:   none
- battery-level:   normal
- percentage:  55% (should be ignored)
- icon-name:  'battery-low-symbolic'
+   native-path:  hidpp_battery_0
+   model:Wireless Keyboard K270
+   serial:   4003-1a-39-5f-c1
+   power supply: no
+   updated:  Thu 12 Nov 2020 13:59:18 CET (119 seconds ago)
+   has history:  yes
+   has statistics:   yes
+   keyboard
+ present: yes
+ rechargeable:yes
+ state:   discharging
+ warning-level:   none
+ battery-level:   normal
+ percentage:  55% (should be ignored)
+ icon-name:  'battery-low-symbolic'
  
- $ upower -i /org/freedesktop/UPower/devices/mouse_hidpp_battery_1 
-   native-path:  hidpp_battery_1
-   model:Wireless Mouse MX Master
-   serial: 

[Desktop-packages] [Bug 1903755] Re: thunderbird 78.4.1 snap connection missing

[Pablo Alvarez]

Trying to load thunderbird profile in
/mnt/EE66EAC766EA901F/palva/Documents/Thunderbird/ururhyog.default

Profile.ini.:

[General]
StartWithLastProfile=1
Version=2

[Profile1]
Name=default
IsRelative=1
Path=23pjhefu.default

[Profile0]
Name=default-release
IsRelative=1
Path=a30isjck.default-release

[Install9238613B8C3D2579]
Default=/mnt/EE66EAC766EA901F/palva/Documents/Thunderbird/ururhyog.default
Locked=1

[Profile2]
Name=Work
IsRelative=0
Path=/mnt/EE66EAC766EA901F/palva/Documents/Thunderbird/ururhyog.default
Default=1

** Attachment added: "Screenshot from 2020-11-12 09-02-04.png"
   
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1903755/+attachment/5433735/+files/Screenshot%20from%202020-11-12%2009-02-04.png

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

Title:
  thunderbird 78.4.1 snap connection missing

Status in thunderbird package in Ubuntu:
  New

Bug description:
  ---
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  ---
  thunderbird 74.8.1 - channel lastest/stable
  ---
  I try to connect to an exist profile in a ntfs partition.
  But the "Read/write files on removable storage device option" is missing in 
permissions.
  --
  I can't launch thunderbird with a profile located in a mnt (ntfs partition) 
device.

  Thunderbird does not have auto-connect of removable-media, and i can't
  connect it manually with:

  snap connect thunderbird:removable-media

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

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

[Desktop-packages] [Bug 1903755] Re: thunderbird 78.4.1 snap connection missing

[Pablo Alvarez]

I share my journalctl -b 0 log after triggering the issue.

** Attachment added: "logThunderbird.txt"
   
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1903755/+attachment/5433736/+files/logThunderbird.txt

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

Title:
  thunderbird 78.4.1 snap connection missing

Status in thunderbird package in Ubuntu:
  New

Bug description:
  ---
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  ---
  thunderbird 74.8.1 - channel lastest/stable
  ---
  I try to connect to an exist profile in a ntfs partition.
  But the "Read/write files on removable storage device option" is missing in 
permissions.
  --
  I can't launch thunderbird with a profile located in a mnt (ntfs partition) 
device.

  Thunderbird does not have auto-connect of removable-media, and i can't
  connect it manually with:

  snap connect thunderbird:removable-media

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

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

[Desktop-packages] [Bug 1903755] Re: thunderbird 78.4.1 snap connection missing

[Pablo Alvarez]

Could you share you journalctl -b 0 log after triggering the issue?

Today is holiday in Spain (Is a work equipment). Tomorrow i'll share the
log (i hope, because i have install thunderbird manually). I'll try it
tomorrow.

was it working with the snap before we removed the removable-media
interface?

Yes. All was ok.


what type of device is used and how is it mounted? 

A partition in another hard drive. I have an ssd with ubuntu and w10 and
another hard drive with two partitions in ntfs (data and backup).

The data partition was configurated by disk app of ubuntu. Mount at
start up the sistem. Tomorrow send more tecnical information.

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

Title:
  thunderbird 78.4.1 snap connection missing

Status in thunderbird package in Ubuntu:
  New

Bug description:
  ---
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  ---
  thunderbird 74.8.1 - channel lastest/stable
  ---
  I try to connect to an exist profile in a ntfs partition.
  But the "Read/write files on removable storage device option" is missing in 
permissions.
  --
  I can't launch thunderbird with a profile located in a mnt (ntfs partition) 
device.

  Thunderbird does not have auto-connect of removable-media, and i can't
  connect it manually with:

  snap connect thunderbird:removable-media

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

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

[Desktop-packages] [Bug 1903755] Re: thunderbird 78.4.1 snap connection missing

[Pablo Alvarez]

With version 74.8.0 snap thunderbird works fine with the profile in ntfs
partition.

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

Title:
  thunderbird 78.4.1 snap connection missing

Status in thunderbird package in Ubuntu:
  New

Bug description:
  ---
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  ---
  thunderbird 74.8.1 - channel lastest/stable
  ---
  I try to connect to an exist profile in a ntfs partition.
  But the "Read/write files on removable storage device option" is missing in 
permissions.
  --
  I can't launch thunderbird with a profile located in a mnt (ntfs partition) 
device.

  Thunderbird does not have auto-connect of removable-media, and i can't
  connect it manually with:

  snap connect thunderbird:removable-media

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

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

[Desktop-packages] [Bug 1903755] Re: thunderbird 78.4.1 snap connection missing

[Pablo Alvarez]

With version 78.4.0 snap thunderbird works fine with the profile in ntfs
partition.

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

Title:
  thunderbird 78.4.1 snap connection missing

Status in thunderbird package in Ubuntu:
  New

Bug description:
  ---
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  ---
  thunderbird 74.8.1 - channel lastest/stable
  ---
  I try to connect to an exist profile in a ntfs partition.
  But the "Read/write files on removable storage device option" is missing in 
permissions.
  --
  I can't launch thunderbird with a profile located in a mnt (ntfs partition) 
device.

  Thunderbird does not have auto-connect of removable-media, and i can't
  connect it manually with:

  snap connect thunderbird:removable-media

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

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

[Desktop-packages] [Bug 1903755] Re: thunderbird 78.4.1 snap connection missing

[Pablo Alvarez]

Yes. The partition is mounted on startup.

I can access to data in this partition, create folders, files, remove
documents etc.

I have a profile for firefox in this ntfs partition and no problem to
load.

Eventualy i install thunderbird manually to work with email, and cero
problem loading this profile.

With this installation in manual i can create a new profile in this
partition because when launch thunderbird -p, and follow the steps to
create a new profile i can do this in this partition.

With snap installation i can't do this because thunderbird can't access
to this ntfs file system.

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

Title:
  thunderbird 78.4.1 snap connection missing

Status in thunderbird package in Ubuntu:
  New

Bug description:
  ---
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  ---
  thunderbird 74.8.1 - channel lastest/stable
  ---
  I try to connect to an exist profile in a ntfs partition.
  But the "Read/write files on removable storage device option" is missing in 
permissions.
  --
  I can't launch thunderbird with a profile located in a mnt (ntfs partition) 
device.

  Thunderbird does not have auto-connect of removable-media, and i can't
  connect it manually with:

  snap connect thunderbird:removable-media

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

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

[Desktop-packages] [Bug 1903755] [NEW] thunderbird 78.4.1 snap connection missing

[Pablo Alvarez]

Public bug reported:

---
Description:Ubuntu 20.04.1 LTS
Release:20.04
---
thunderbird 74.8.1 - channel lastest/stable
---
I try to connect to an exist profile in a ntfs partition.
But the "Read/write files on removable storage device option" is missing in 
permissions.
--
I can't launch thunderbird with a profile located in a mnt (ntfs partition) 
device.

Thunderbird does not have auto-connect of removable-media, and i can't
connect it manually with:

snap connect thunderbird:removable-media

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

** Attachment added: "Missing last option - Read/write files on removable 
storage devices"
   
https://bugs.launchpad.net/bugs/1903755/+attachment/5433055/+files/Screenshot%20from%202020-11-10%2009-37-48.png

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

Title:
  thunderbird 78.4.1 snap connection missing

Status in thunderbird package in Ubuntu:
  New

Bug description:
  ---
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  ---
  thunderbird 74.8.1 - channel lastest/stable
  ---
  I try to connect to an exist profile in a ntfs partition.
  But the "Read/write files on removable storage device option" is missing in 
permissions.
  --
  I can't launch thunderbird with a profile located in a mnt (ntfs partition) 
device.

  Thunderbird does not have auto-connect of removable-media, and i can't
  connect it manually with:

  snap connect thunderbird:removable-media

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

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

[Desktop-packages] [Bug 1902976] Re: [Acer Aspire E5-432] After boot pulseaudio needs to be restarted

[Pablo Pedrotti]

Uninstalling pipewire fixed the issue. Now both the speakers and the
microphone work properly.

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

Title:
  [Acer Aspire E5-432] After boot pulseaudio needs to be restarted

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After an upgrade pulseaudio does not run properly after boot unless I
  restart the service with the command systemctl --user restart
  pulseaudio. Reinstalling the service with the comand apt-get install
  --reinstall pulseaudio also solves the issue.

  I am currently running Kubuntu 20.10 and the pulseaudio version is
  1:13.99.2-1ubuntu2.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ppedrotti   1572 F pipewire-media-
ppedrotti   5420 F pulseaudio
   /dev/snd/seq:ppedrotti   1567 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Nov  4 23:13:09 2020
  InstallationDate: Installed on 2020-10-17 (18 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (12 days ago)
  dmi.bios.date: 12/07/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Robin_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd12/07/2015:br0.0:efr1.7:svnAcer:pnAspireE5-432:pvrV1.10:rvnAcer:rnRobin_BA:rvrV1.10:cvnAcer:ct10:cvrV1.10:
  dmi.product.family: BSW
  dmi.product.name: Aspire E5-432
  dmi.product.sku: Aspire E5-432
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1902976] [NEW] After boot pulseaudio needs to be restarted

[Pablo Pedrotti]

Public bug reported:

After an upgrade pulseaudio does not run properly after boot unless I
restart the service with the command systemctl --user restart
pulseaudio. Reinstalling the service with the comand apt-get install
--reinstall pulseaudio also solves the issue.

I am currently running Kubuntu 20.10 and the pulseaudio version is
1:13.99.2-1ubuntu2.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: pulseaudio 1:13.99.2-1ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
Uname: Linux 5.8.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ppedrotti   1572 F pipewire-media-
  ppedrotti   5420 F pulseaudio
 /dev/snd/seq:ppedrotti   1567 F pipewire
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Wed Nov  4 23:13:09 2020
InstallationDate: Installed on 2020-10-17 (18 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to groovy on 2020-10-24 (12 days ago)
dmi.bios.date: 12/07/2015
dmi.bios.release: 0.0
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.10
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Robin_BA
dmi.board.vendor: Acer
dmi.board.version: V1.10
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.10
dmi.ec.firmware.release: 1.7
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd12/07/2015:br0.0:efr1.7:svnAcer:pnAspireE5-432:pvrV1.10:rvnAcer:rnRobin_BA:rvrV1.10:cvnAcer:ct10:cvrV1.10:
dmi.product.family: BSW
dmi.product.name: Aspire E5-432
dmi.product.sku: Aspire E5-432
dmi.product.version: V1.10
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug groovy

** Attachment added: "alsa-info.txt"
   
https://bugs.launchpad.net/bugs/1902976/+attachment/5431303/+files/alsa-info.txt

** Attachment removed: "alsa-info.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902976/+attachment/5431303/+files/alsa-info.txt

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

Title:
  After boot pulseaudio needs to be restarted

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After an upgrade pulseaudio does not run properly after boot unless I
  restart the service with the command systemctl --user restart
  pulseaudio. Reinstalling the service with the comand apt-get install
  --reinstall pulseaudio also solves the issue.

  I am currently running Kubuntu 20.10 and the pulseaudio version is
  1:13.99.2-1ubuntu2.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ppedrotti   1572 F pipewire-media-
ppedrotti   5420 F pulseaudio
   /dev/snd/seq:ppedrotti   1567 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Nov  4 23:13:09 2020
  InstallationDate: Installed on 2020-10-17 (18 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (12 days ago)
  dmi.bios.date: 12/07/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Robin_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd12/07/2015:br0.0:efr1.7:svnAcer:pnAspireE5-432:pvrV1.10:rvnAcer:rnRobin_BA:rvrV1.10:cvnAcer:ct10:cvrV1.10:
  dmi.product.family: BSW
  dmi.product.name: Aspire E5-432
  dmi.product.sku: Aspire E5-432
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1902580] Re: [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall pulseaudio after every reboot.

[Pablo Pedrotti]

I also has this issue of losing audio and having to reinstall pulseaudio
to get it back to work. The latest pulseaudio update
(1:13.99.2-1ubuntu2) did not seem to solve the issue.


** Attachment added: "alsa-info"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902580/+attachment/5430501/+files/alsa-info.txt

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

Title:
  [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall
  pulseaudio after every reboot.

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  My Xubuntu 20.10 installation has no sound (Dummy Output) unless I
  reinstall pulseaudio after every reboot.

  pulseaudio does survive a suspend.  Just a hard reset or power cycle
  causes it to fail.

  How I re-install pulseaudio:

  sudo apt-get install --reinstall pulseaudio

  I have tried just killing the pulseaudio service, and letting it
  restart on it's own. It restarts, but no audio. Reinstalling seems to
  do the trick though.

  Thank You,
  Jeff

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Mon Nov  2 13:42:36 2020
  InstallationDate: Installed on 2020-11-02 (0 days ago)
  InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX425IA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX425IA
  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.ec.firmware.release: 3.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX425IA_UM425IA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1740180]

[Pablo-muir]

i was able to reproduce this issue on Nightly 81.0a1 on Ubuntu 18.04,
also on beta 80.0b3 and 79release.

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

Title:
  Firefox stops loading Farmville 2 and hangs.

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  STR: Start Firefox (56 or 57), go to Facebook. Start Farmville 2. 
   Farmville 2 hangs while loading. Never plays. 

  The Adobe Flash Player is properly installed. Has also been re-
  installed. Ditto for FireFox.

  Does not matter if using Ubuntu 16.04 or 17.10.

  Farmville 2 via Facebook in Firefox hangs. Also will not work if run
  from the Zynga URL (the makers of Farmville 2. Other Facebook games
  work well. Try "Pearl's Perils."

  Happy to help with testing if you like. This has been tested on both
  desktops and laptops.

  Thanks,

  Ken Wagner

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.23
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Dec 26 15:59:05 2017
  InstallationDate: Installed on 2017-03-06 (295 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ken2466 F pulseaudio
   /dev/snd/pcmC0D0p:   ken2466 F...m pulseaudio
   /dev/snd/controlC0:  ken2466 F pulseaudio
   /dev/snd/controlC2:  ken2466 F pulseaudio
  BuildID: 20180614184508
  Channel: beta
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-03-28 (94 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IpRoute:
   default via 192.168.0.1 dev enp2s0  proto static  metric 100 
   default via 192.168.1.1 dev wlx7cdd908b43ea  proto static  metric 600 
   169.254.0.0/16 dev wlx7cdd908b43ea  scope link  metric 1000 
   192.168.0.0/24 dev enp2s0  proto kernel  scope link  src 192.168.0.10  
metric 100 
   192.168.1.0/24 dev wlx7cdd908b43ea  proto kernel  scope link  src 
192.168.1.2  metric 600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-61ed5f93-fc76-48cc-8c5e-05d080180530
  Package: firefox 61.0~b14+build1-0ubuntu0.16.04.1 [origin: 
LP-PPA-mozillateam-firefox-next]
  PackageArchitecture: amd64
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources:
   /usr/lib/firefox/defaults/pref/vendor-gre.js
   /usr/lib/firefox/defaults/pref/channel-prefs.js
   prefs.js
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  Profiles: Profile0 (Default) - LastVersion=61.0/20180614184508 (In use)
  RunningIncompatibleAddons: False
  SubmittedCrashIDs:
   bp-61ed5f93-fc76-48cc-8c5e-05d080180530
   bp-481cf9ec-efcd-4900-93aa-4e8940180512
   bp-ad49167e-7776-4ff5-8acc-5adb50180421
   bp-08f026d0-e273-45fb-b355-c70ae0180402
  Tags: xenial third-party-packages beta-channel
  Themes: extensions.sqlite corrupt or missing
  Uname: Linux 4.13.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 LE R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2501:bd04/09/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.: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: To be filled by O.E.M.
  --- 
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64

[Desktop-packages] [Bug 1879287] Re: [nvidia+amdgpu] System sometimes starts with a black screen with Nvidia PRIME setup on Ryzen+Nvidia system (but kernel 5.6.14 works perfectly)

[Juan Pablo]

I have a very similar problem, today I asked a question on ask ubuntu


https://askubuntu.com/questions/1265779/video-issues-with-amd-igpu-and-nvidia-gpu-in-an-aspire-a715-41g-laptop

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

Title:
  [nvidia+amdgpu] System sometimes starts with a black screen with
  Nvidia PRIME setup on Ryzen+Nvidia system (but kernel 5.6.14 works
  perfectly)

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-prime package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  I've recently installed Ubuntu on a laptop that has a Ryzen APU (with
  Vega 8 integrated graphics) and a Nvidia dedicated GPU. The first
  issue that this kind of setup gives on a fresh install is that that
  PRIME render offloading doesn't work, I presume that Ubuntu currently
  sets up hybrid graphics for laptop with Intel+Nvidia, not AMD+Nvidia
  but that's another separate issue. As a workaround I created an Xorg
  configuration (attached in this report) that sets up both GPUs (with
  the appropiate BusIDs), after such configuration is applied the system
  boots fine with AMD integrated graphics being used and the ability to
  switch to Nvidia with PRIME render off-loading.

  The problem comes when I try to use the computer the next day, then it
  gives me a black screen without having the ability to switch to a tty,
  the boot log doesn't throw any errors I just see a black screen after
  Xorg tries to start. I can make it work again by entering in recovery
  mode, logging into a root console and switching between "nvidia" and
  "on-demand" modes using prime-select (I set it up to "on-demand"
  profile after installing Ubuntu).

  For the moment I cannot provide any relevant logs since it's now
  working fine (and I don't remember seeing any errors on Xorg logs),
  also I don't really know where to look for this kind of issues.

  My system information:
  -CPU: AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx
  -GPU: Nvidia GTX 1650 Mobile (TU117M) (Using Nvidia binary driver version 
440.64 from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  -RAM: 8 GB
  -Kubuntu 20.04 LTS (Using KDE Plasma 5.18.4)
  -Xorg 1.20.8-2ubuntu2

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

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

[Desktop-packages] [Bug 1874874] Re: Focal detects wrong driver version 440 for NVIDIA GTX 550

[Pablo Carballo]

nvidia-driver-440 contains some invalid modaliases that cause to be
detected as a valid driver for the wrong card.

** Package changed: ubuntu-drivers-common (Ubuntu) => nvidia-graphics-
drivers-440 (Ubuntu)

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

Title:
  Focal detects wrong driver version 440 for NVIDIA GTX 550

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

Bug description:
  My desktop PC has an NVIDIA GeForce GTX 550 Ti. Just installed Focal 
selecting the option to install 3rd-party drivers during setup process, and 
after the first boot screen resolution is 800x600.
  I verified the detected version of NVIDIA driver and I realized it was 440, 
although correct version is 390. Finally I manually installed proper version 
(390) and now the graphics are working OK.

  This is the output for the command "$ lspci -nn":

  01:00.0 VGA compatible controller: NVIDIA Corporation GF116 [GeForce GTX 550 
Ti] (rev a1)
  01:00.1 Audio device: NVIDIA Corporation GF116 High Definition Audio 
Controller (rev a1)

  
  This is the output for the command "# ubuntu-drivers devices":

  == /sys/devices/pci:00/:00:02.0/:01:00.0 ==
  modalias : pci:v10DEd1244sv1043sd83BEbc03sc00i00
  vendor   : NVIDIA Corporation
  model: GF116 [GeForce GTX 550 Ti]
  driver   : nvidia-driver-435 - distro non-free
  driver   : nvidia-driver-390 - distro non-free
  driver   : nvidia-driver-440 - distro non-free recommended
  driver   : nvidia-340 - distro non-free
  driver   : xserver-xorg-video-nouveau - distro free builtin

  The version 440 is recommended, but it's not correct for this model
  (390 should be recommended instead)

  
  The issue was not present in previous versions (in both 19.10 and 18.04 
driver 390 was recommended correctly)

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

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

[Desktop-packages] [Bug 1884595] [NEW] Bugged 3D display of multimaterial meshes after last Radeon driver update

[Pablo Roldán]

Public bug reported:

After the last driver update for my Radeon HD 7750 Im having viewport
problems in Blender when displaying meshes with multiple materials (see
attached screenshot).

This happens both with both the latest version of Blender snap and the direct 
download from Blender.org
I also have an older version installed and is having the same problem.

It all worked fine before the driver update.

Just in case these are the last lines from running  grep "upgrade " 
/var/log/dpkg.log
:

2020-06-20 00:48:38 upgrade xserver-xorg-legacy-hwe-18.04:amd64 
2:1.20.5+git20191008-0ubuntu1~18.04.1 2:1.20.8-2ubuntu2.1~18.04.1
2020-06-20 00:48:39 upgrade xserver-xorg-core-hwe-18.04:amd64 
2:1.20.5+git20191008-0ubuntu1~18.04.1 2:1.20.8-2ubuntu2.1~18.04.1
2020-06-20 00:48:40 upgrade xserver-xorg-video-amdgpu-hwe-18.04:amd64 
19.0.1-1ubuntu1~18.04.1 19.1.0-1~18.04.1
2020-06-20 00:48:40 upgrade xserver-xorg-video-radeon-hwe-18.04:amd64 
1:19.0.1-1ubuntu1~18.04.1 1:19.1.0-1~18.04.1
2020-06-20 00:48:41 upgrade xserver-xorg-video-ati-hwe-18.04:amd64 
1:19.0.1-1ubuntu1~18.04.1 1:19.1.0-1~18.04.1

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-59-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: Budgie:GNOME
Date: Mon Jun 22 16:31:31 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 openrazer-driver, 2.8.0, 5.3.0-53-generic, x86_64: installed
 openrazer-driver, 2.8.0, 5.3.0-59-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] [1002:683f] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Cape Verde PRO [Radeon HD 7750/8740 / R7 
250E] [1043:0427]
InstallationDate: Installed on 2019-08-03 (324 days ago)
InstallationMedia: Ubuntu-Budgie 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=bf94f108-3b15-444b-a40a-414115dcfedd ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/25/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1107
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H61-M LX3 R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1107:bd02/25/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX3R2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2~18.04.1
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

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


** Tags: amd64 apport-bug bionic corruption ubuntu

** Attachment added: "Screenshot."
   
https://bugs.launchpad.net/bugs/1884595/+attachment/5386190/+files/Captura%20de%20pantalla%20de%202020-06-22%2016-33-04.png

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

Title:
  Bugged 3D display of multimaterial meshes after last Radeon driver
  update

Status in xorg package in Ubuntu:
  New

Bug description:
  After the last driver update for my Radeon HD 7750 Im having viewport
  problems in Blender when displaying meshes with multiple materials
  (see attached screenshot).

  This happens both with both the latest version of Blender snap and the direct 
download from Blender.org
  I also have an older version installed and is having the same problem.

  It all worked fine before the driver update.

  Just in case these are the last lines from running  grep "upgrade " 
/var/log/dpkg.log
  :

  2020-06-20 00:48:38 upgrade xserver-xorg-legacy-hwe-18.04:amd64 
2:1.20.5+git20191008-0ubuntu1~18.04.1 2:1.20.8-2ubuntu2.1~18.04.1
  2020-06-20 00:48:39 upgrade 

[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu 19.10 & 20.04 (see comment 93)

[Pablo San Martín]

Thanks! This fixed it for me! Glad to be able to use Clipboard Indicator
and LibreOffice at the same time again"

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

Title:
  [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu
  19.10 & 20.04 (see comment 93)

Status in LibreOffice:
  Won't Fix
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  [ Test case ]

  1. Use use libreoffice writer/calc
  2. Copy text around
  3. Paste it and ensure it always work

  [ Regression potential ]

  Copy/paste won't work as expected, for non-text types

  -

  
  I use LibreOffice Writer a lot, and I now see this problem very often, i.e. 
many times every day.

  There is some discussion of the problem here:

     https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

     https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

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

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

[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu 19.10 & 20.04 (see comment 93)

[Pablo San Martín]

On Ubuntu 20.04, I had the issue of copy-paste working every other time,
specifically on LibreOffice apps (Writer, Calc and Draw), not in any
other apps (Gedit, Firefox, Thunderbird, etc.) or in the GNOME Shell.

However, disabling the Clipboard Indicator extension fixed this for me.

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

Title:
  [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu
  19.10 & 20.04 (see comment 93)

Status in LibreOffice:
  Won't Fix
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Triaged
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  [ Test case ]

  1. Use use libreoffice writer/calc
  2. Copy text around
  3. Paste it and ensure it always work

  [ Regression potential ]

  Copy/paste won't work as expected, for non-text types

  -

  
  I use LibreOffice Writer a lot, and I now see this problem very often, i.e. 
many times every day.

  There is some discussion of the problem here:

     https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

     https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

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

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

[Desktop-packages] [Bug 1794033] Re: i965: Failed to submit batchbuffer: Bad address

[Pablo A. Garcia]

Previous issue (https://gitlab.freedesktop.org/mesa/mesa/-/issues/1680)
was closed as duplicated of this one.

see https://gitlab.freedesktop.org/mesa/mesa/-/issues/1680#note_328635.

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #2134
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/2134

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #1680
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/1680

** Changed in: mesa
   Status: Fix Released => Unknown

** Changed in: mesa
 Remote watch: gitlab.freedesktop.org/mesa/mesa/issues #1680 => 
gitlab.freedesktop.org/mesa/mesa/-/issues #2134

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

Title:
   i965: Failed to submit batchbuffer: Bad address

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Fedora:
  Unknown

Bug description:
  cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 
  gpu: Intel® HD Graphics 630 (Kaby Lake GT2)
  00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  xserver-xorg-video-intel:
Installed: 2:2.99.917+git20171229-1
Candidate: 2:2.99.917+git20171229-1
  ubuntu: 18.04 LTS bionic
  gnome: 3.28.2
  gdm3:
Installed: 3.28.2-0ubuntu1.4
Candidate: 3.28.2-0ubuntu1.4
  os type: 64 bit
  kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  mesa-va-drivers:
Installed: 18.0.5-0ubuntu0~18.04.1
Candidate: 18.0.5-0ubuntu0~18.04.1

  from syslog:

  Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit 
batchbuffer: Bad address
  Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0" 
   - but 
  (followed by pages upon pages of applications within gnome failing.)

  nothing in kern.log around that time.

  Singular gnome crash, taking down all applications running within it.
  Not yet reproduced. gdm successfully started a new session afterwards.
  Was definitely in a palermoon session on some website or other.

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

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

[Desktop-packages] [Bug 1794033] Re: i965: Failed to submit batchbuffer: Bad address

[Pablo A. Garcia]

Also facing this issue persistently, always when working with little
memory available (as #32).

My system: Dell XPS 13 9370 - Ubuntu 18.04.4 LTS

$ uname -a
Linux charon 5.3.0-51-generic #44~18.04.2-Ubuntu SMP Thu Apr 23 14:27:18 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux


$ journalctl --since=-2w | grep -A1 'Failed to submit batchbuffer'
abr 27 17:17:09 charon org.gnome.Shell.desktop[3359]: i965: Failed to submit 
batchbuffer: Dirección incorrecta
abr 27 17:17:09 charon kernel: mce: CPU3: Core temperature above threshold, cpu 
clock throttled (total events = 2304)
--
abr 27 18:23:14 charon /usr/lib/gdm3/gdm-x-session[3239]: i965: Failed to 
submit batchbuffer: Bad address
abr 27 18:23:14 charon org.gnome.Shell.desktop[3359]: 
[9820:9820:0427/182314.955599:ERROR:chrome_browser_main_extra_parts_x11.cc(62)] 
X IO error received (X server probably went away)
--
abr 27 21:59:47 charon org.gnome.Shell.desktop[24418]: i965: Failed to submit 
batchbuffer: Dirección incorrecta
abr 27 21:59:48 charon org.gnome.Shell.desktop[24418]: 
[20630:20630:0427/215948.650070:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process gpu-process.
--
abr 28 11:32:50 charon /usr/lib/gdm3/gdm-x-session[24313]: i965: Failed to 
submit batchbuffer: Bad address
abr 28 11:32:50 charon dropbox[24681]: dropbox: Fatal IO error 11 (Recurso no 
disponible temporalmente) on X server :0.
--
may 06 11:10:23 charon /usr/lib/gdm3/gdm-x-session[6485]: i965: Failed to 
submit batchbuffer: Bad address
may 06 11:10:23 charon org.gnome.Shell.desktop[6634]: 
[8456:8456:0506/111023.129635:ERROR:gl_surface_presentation_helper.cc(259)] 
GetVSyncParametersIfAvailable() failed for 1 times!
--
may 08 11:07:53 charon /usr/lib/gdm3/gdm-x-session[6255]: i965: Failed to 
submit batchbuffer: Bad address
may 08 11:07:53 charon dropbox[6661]: dropbox: Fatal IO error 11 (Recurso no 
disponible temporalmente) on X server :0.

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

Title:
   i965: Failed to submit batchbuffer: Bad address

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Fedora:
  Unknown

Bug description:
  cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 
  gpu: Intel® HD Graphics 630 (Kaby Lake GT2)
  00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  xserver-xorg-video-intel:
Installed: 2:2.99.917+git20171229-1
Candidate: 2:2.99.917+git20171229-1
  ubuntu: 18.04 LTS bionic
  gnome: 3.28.2
  gdm3:
Installed: 3.28.2-0ubuntu1.4
Candidate: 3.28.2-0ubuntu1.4
  os type: 64 bit
  kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  mesa-va-drivers:
Installed: 18.0.5-0ubuntu0~18.04.1
Candidate: 18.0.5-0ubuntu0~18.04.1

  from syslog:

  Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit 
batchbuffer: Bad address
  Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0" 
   - but 
  (followed by pages upon pages of applications within gnome failing.)

  nothing in kern.log around that time.

  Singular gnome crash, taking down all applications running within it.
  Not yet reproduced. gdm successfully started a new session afterwards.
  Was definitely in a palermoon session on some website or other.

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

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

[Desktop-packages] [Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.

[Pablo Catalina]

I had the same problem with a Thunderbolt audio device and BT. I removed 
.config/pulse and started working fine again.
Not sure if it will fail, but for the moment is working.

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

Title:
  External audio device shows up in the sound output options but the
  sound keeps being emitted from the internal laptop speaker, or none at
  all.

Status in gnome-control-center:
  Unknown
Status in PulseAudio:
  New
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  In Progress
Status in gnome-control-center source package in Focal:
  Invalid
Status in pulseaudio source package in Focal:
  In Progress

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Pulseaudio: 1:13.99.1-1ubuntu1
  Device CID: 201704-25503

  Steps to reproduce:

  1. Connect an audio interface. I tried with BT headphones and speakers as 
well as a USB microphone/output.
  2. Make sure it's the one selected as "Output device"
  3. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  4. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  5. Try to switch back to the BT device and click Test
  -> same result as in step 3

  Tested with 2 different BT devices (one headset and one speaker) as
  well as a USB audio interface (Zoom H2N microphone).

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  I was previously using 19.04 and 19.10 on this device and never
  experienced this kind of issue.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1874874] Re: Focal detects wrong driver version 440 for NVIDIA GTX 550

[Pablo Carballo]

** Description changed:

- My desktop has an NVIDIA GeForce GTX 550 Ti. Just installed Focal and
- now screen resolution is 800x600. I verified the detected version of
- NVIDIA driver and I realized it was 440, but correct version is 390.
- Finally I changed version to 390 and now the graphics are  working OK.
+ My desktop PC has an NVIDIA GeForce GTX 550 Ti. Just installed Focal 
selecting the option to install 3rd-party drivers during setup process, and 
after the first boot screen resolution is 800x600.
+ I verified the detected version of NVIDIA driver and I realized it was 440, 
although correct version is 390. Finally I manually installed proper version 
(390) and now the graphics are working OK.
  
- This issue was not present in previous versions (19.10 and 18.04)
+ This is the output for the command "$ lspci -nn":
+ 
+ 01:00.0 VGA compatible controller: NVIDIA Corporation GF116 [GeForce GTX 550 
Ti] (rev a1)
+ 01:00.1 Audio device: NVIDIA Corporation GF116 High Definition Audio 
Controller (rev a1)
+ 
+ 
+ This is the output for the command "# ubuntu-drivers devices":
+ 
+ == /sys/devices/pci:00/:00:02.0/:01:00.0 ==
+ modalias : pci:v10DEd1244sv1043sd83BEbc03sc00i00
+ vendor   : NVIDIA Corporation
+ model: GF116 [GeForce GTX 550 Ti]
+ driver   : nvidia-driver-435 - distro non-free
+ driver   : nvidia-driver-390 - distro non-free
+ driver   : nvidia-driver-440 - distro non-free recommended
+ driver   : nvidia-340 - distro non-free
+ driver   : xserver-xorg-video-nouveau - distro free builtin
+ 
+ The version 440 is recommended, but it's not correct for this model (390
+ should be recommended instead)
+ 
+ 
+ The issue was not present in previous versions (in both 19.10 and 18.04 
driver 390 was recommended correctly)

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

Title:
  Focal detects wrong driver version 440 for NVIDIA GTX 550

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  My desktop PC has an NVIDIA GeForce GTX 550 Ti. Just installed Focal 
selecting the option to install 3rd-party drivers during setup process, and 
after the first boot screen resolution is 800x600.
  I verified the detected version of NVIDIA driver and I realized it was 440, 
although correct version is 390. Finally I manually installed proper version 
(390) and now the graphics are working OK.

  This is the output for the command "$ lspci -nn":

  01:00.0 VGA compatible controller: NVIDIA Corporation GF116 [GeForce GTX 550 
Ti] (rev a1)
  01:00.1 Audio device: NVIDIA Corporation GF116 High Definition Audio 
Controller (rev a1)

  
  This is the output for the command "# ubuntu-drivers devices":

  == /sys/devices/pci:00/:00:02.0/:01:00.0 ==
  modalias : pci:v10DEd1244sv1043sd83BEbc03sc00i00
  vendor   : NVIDIA Corporation
  model: GF116 [GeForce GTX 550 Ti]
  driver   : nvidia-driver-435 - distro non-free
  driver   : nvidia-driver-390 - distro non-free
  driver   : nvidia-driver-440 - distro non-free recommended
  driver   : nvidia-340 - distro non-free
  driver   : xserver-xorg-video-nouveau - distro free builtin

  The version 440 is recommended, but it's not correct for this model
  (390 should be recommended instead)

  
  The issue was not present in previous versions (in both 19.10 and 18.04 
driver 390 was recommended correctly)

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

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

[Desktop-packages] [Bug 1874874] Re: Focal detects wrong driver version 440 for NVIDIA GTX 550

[Pablo Carballo]

** Tags added: driver

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

Title:
  Focal detects wrong driver version 440 for NVIDIA GTX 550

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  My desktop has an NVIDIA GeForce GTX 550 Ti. Just installed Focal and
  now screen resolution is 800x600. I verified the detected version of
  NVIDIA driver and I realized it was 440, but correct version is 390.
  Finally I changed version to 390 and now the graphics are  working OK.

  This issue was not present in previous versions (19.10 and 18.04)

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

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

[Desktop-packages] [Bug 1874874] Re: Focal detects wrong driver version 440 for NVIDIA GTX 550

[Pablo Carballo]

Set the most probable package.

** Package changed: ubuntu => ubuntu-drivers-common (Ubuntu)

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

Title:
  Focal detects wrong driver version 440 for NVIDIA GTX 550

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  My desktop has an NVIDIA GeForce GTX 550 Ti. Just installed Focal and
  now screen resolution is 800x600. I verified the detected version of
  NVIDIA driver and I realized it was 440, but correct version is 390.
  Finally I changed version to 390 and now the graphics are  working OK.

  This issue was not present in previous versions (19.10 and 18.04)

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

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

[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Pablo Catalina]

I installed Ubuntu 20.04 5 days ago (using the daily iso) and works fine
with Quadro P3200 Mobile and default proprietary drivers installed.

I installed it setting up the user with autologon from the installer.

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01: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  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-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.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-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

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

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

[Desktop-packages] [Bug 1874223] Re: Gnome-Shell search does not work

[Pablo Catalina]

** Attachment added: "journalctl_gnome-shell.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1874223/+attachment/5357870/+files/journalctl_gnome-shell.txt

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

Title:
  Gnome-Shell search does not work

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

Bug description:
  Gnome-shell search does not work.
  When I open the menu using "Meta" key on keyboard, and I write anything, no 
results are displayed.

  I noted errors on gnome-shell journal (see attached logs):

  Received error from D-Bus search provider 
org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: 
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 
“org.gnome.Shell.SearchProvider2” on object at path 
/org/gnome/seahorse/Application
  Wrong number of result metas returned by search provider 
org.gnome.seahorse.Application.desktop: expected 1 but got 0

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30
  Uname: Linux 5.4.0-26-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 22 11:59:54 2020
  InstallationDate: Installed on 2020-04-19 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1874223] [NEW] Gnome-Shell search does not work

[Pablo Catalina]

Public bug reported:

Gnome-shell search does not work.
When I open the menu using "Meta" key on keyboard, and I write anything, no 
results are displayed.

I noted errors on gnome-shell journal (see attached logs):

Received error from D-Bus search provider 
org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: 
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 
“org.gnome.Shell.SearchProvider2” on object at path 
/org/gnome/seahorse/Application
Wrong number of result metas returned by search provider 
org.gnome.seahorse.Application.desktop: expected 1 but got 0

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.1-1ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30
Uname: Linux 5.4.0-26-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 22 11:59:54 2020
InstallationDate: Installed on 2020-04-19 (2 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Gnome-Shell search does not work

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

Bug description:
  Gnome-shell search does not work.
  When I open the menu using "Meta" key on keyboard, and I write anything, no 
results are displayed.

  I noted errors on gnome-shell journal (see attached logs):

  Received error from D-Bus search provider 
org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: 
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 
“org.gnome.Shell.SearchProvider2” on object at path 
/org/gnome/seahorse/Application
  Wrong number of result metas returned by search provider 
org.gnome.seahorse.Application.desktop: expected 1 but got 0

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30
  Uname: Linux 5.4.0-26-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 22 11:59:54 2020
  InstallationDate: Installed on 2020-04-19 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1873768] [NEW] Gnome Network Settings wrong position of texts

[Pablo Catalina]

Public bug reported:

The text boxes of a network connection details is wrong placed and one
text box is over another, see screenshot.

NOTE: 100% scale on display.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.1-1ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-25.29-lowlatency 5.4.30
Uname: Linux 5.4.0-25-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 20 11:14:14 2020
InstallationDate: Installed on 2020-04-19 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot-20200420111445-972x806.png"
   
https://bugs.launchpad.net/bugs/1873768/+attachment/5357078/+files/Screenshot-20200420111445-972x806.png

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

Title:
  Gnome Network Settings wrong position of texts

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

Bug description:
  The text boxes of a network connection details is wrong placed and one
  text box is over another, see screenshot.

  NOTE: 100% scale on display.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-25.29-lowlatency 5.4.30
  Uname: Linux 5.4.0-25-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 20 11:14:14 2020
  InstallationDate: Installed on 2020-04-19 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1873764] [NEW] CUPS Apparmor Error opening /proc/sys/kernel/random/boot_id

[Pablo Catalina]

Public bug reported:

I noted the following messages on a just installed Ubuntu Focal:

$ dmesg | grep cups
[ 1769.505132] audit: type=1400 audit(1587372138.575:3011): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cups-browsed" pid=15230 
comm="cups-browsed" capability=23  capname="sys_nice"
[ 1776.623181] audit: type=1400 audit(1587372145.693:3012): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cups-browsed" pid=15510 
comm="cups-browsed" capability=23  capname="sys_nice"
[ 2040.426033] audit: type=1400 audit(1587372409.494:3013): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2040.426044] audit: type=1400 audit(1587372409.494:3014): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2040.426074] audit: type=1400 audit(1587372409.494:3015): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2040.426092] audit: type=1400 audit(1587372409.494:3016): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2040.426106] audit: type=1400 audit(1587372409.494:3017): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2041.404914] audit: type=1400 audit(1587372410.473:3018): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2041.404920] audit: type=1400 audit(1587372410.473:3019): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2041.404926] audit: type=1400 audit(1587372410.473:3020): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2041.404953] audit: type=1400 audit(1587372410.473:3021): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2041.404963] audit: type=1400 audit(1587372410.473:3022): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2071.925327] audit: type=1400 audit(1587372440.994:3028): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2071.925330] audit: type=1400 audit(1587372440.994:3029): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2071.925337] audit: type=1400 audit(1587372440.994:3030): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2071.925382] audit: type=1400 audit(1587372440.994:3031): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2071.925391] audit: type=1400 audit(1587372440.994:3032): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0


It happened after installing Brother DCPL3550CDW Linux drivers.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cups-daemon 2.3.1-9ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-25.29-lowlatency 5.4.30
Uname: Linux 5.4.0-25-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 20 10:49:08 2020
InstallationDate: Installed on 2020-04-19 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417)
Lpstat: device for DCPL3550CDW: 
dnssd://Brother%20DCP-L3550CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4b66edd
MachineType: LENOVO 20MAS0DF03
Papersize: a4
PpdFiles: DCPL3550CDW: Brother DCP-L3550CDW CUPS
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-lowlatency 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log 

[Desktop-packages] [Bug 1536353] Re: [Regression] Epson's printer driver packages cannot be installed as lsb package is not available anymore

[Rosendo Pablo]

Thank you so much for this information, I have been googling and
searching the net for 2 weeks for an answer of my Epson L800, I couldn't
installed it in Sparkylinux 5, I added the Debian 9 repository and
charm.

One thing that I don't get it to work is the HubiC cloud, it keeps says
"Warning] Can not synchronise /home/qkeybil/Hubic/: Index was outside
the bounds of the array.. Will retry later.

If there is one out there to help, what is going on?

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

Title:
  [Regression] Epson's printer driver packages cannot be installed as
  lsb package is not available anymore

Status in lsb:
  New
Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.

  This SRU will restore the bare minimum of LSB compatibility necessary
  to support known third-party LSB printer driver packages on Ubuntu
  16.04.

  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.

  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land
  before the first 16.04 point release.

  [Test case]
  1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
  2. Install the package and confirm that its dependencies are not satisfiable.
  3. Enable xenial-proposed.
  4. Install the package again and confirm that the dependencies are satisfied.
  5. Verify that 
/opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter 
can be run without errors about missing lsb ld.so or missing libraries.

  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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

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

[Desktop-packages] [Bug 1869592] Re: Lubuntu LXQt - Locale fallback fails

[Pablo César Galdo Regueiro]

Thank you.
I've already submitted a report to the Lubuntu team, via forum.

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

Title:
  Lubuntu LXQt - Locale fallback fails

Status in language-selector package in Ubuntu:
  Invalid

Bug description:
  I have always been a locale-fallback feature user. With Lubuntu 18.04
  LTS I haven't any problem.

  The computer users are fluent in those languages, except in English
  (the default one). If there's a string untranslated in one language,
  it jumps and try to show the string of the next listed language and so
  on.

  In most of the programs the fallback works, but the LXQt menu, some
  details like some dialogs, don't work well, even editing
  /etc/default/locale file:

  LANG="pt_BR.UTF-8"
  LANGUAGE="pt_BR:pt_PT:gl_ES:es_ES:en"
  LC_NUMERIC="pt_PT.UTF-8"
  LC_TIME="pt_PT.UTF-8"
  LC_MONETARY="pt_PT.UTF-8"
  LC_PAPER="pt_PT.UTF-8"
  LC_NAME="pt_PT.UTF-8"
  LC_ADDRESS="pt_PT.UTF-8"
  LC_TELEPHONE="pt_PT.UTF-8"
  LC_MEASUREMENT="pt_PT.UTF-8"
  LC_IDENTIFICATION="pt_PT.UTF-8"

  It doesn't work even installing and configuring locales with language-
  selector-gnome, which is not installed by default on Lubuntu 20.04.

  If I try to change the main language, I see that most of translations
  exist, either in one language or another. So the problem is with the
  fallback, determined by the LANGUAGE = section in /etc/default/locale.

  *Using Spanish as first language:*
  https://emma.cloud.tabdigital.eu/s/X2TRjAnPjJq76JH
  *Using Galician as first language:*
  https://emma.cloud.tabdigital.eu/s/StbkHwFPC27kzLo

  We are not the only ones with this problem, polyglot people or
  inhabitants of regions with languages with two different spelling
  regulations can be combined in this way.

  Thank you for your attention.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: language-selector-gnome 0.203
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: LXQt
  Date: Sun Mar 29 18:20:30 2020
  ExecutablePath: /usr/bin/gnome-language-selector
  InstallationDate: Installed on 2020-03-29 (0 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200316)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: N/A
  SourcePackage: language-selector
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1869592] [NEW] Lubuntu LXQt - Locale fallback fails

[Pablo César Galdo Regueiro]

Public bug reported:

I have always been a locale-fallback feature user. With Lubuntu 18.04
LTS I haven't any problem.

The computer users are fluent in those languages, except in English (the
default one). If there's a string untranslated in one language, it jumps
and try to show the string of the next listed language and so on.

In most of the programs the fallback works, but the LXQt menu, some
details like some dialogs, don't work well, even editing
/etc/default/locale file:

LANG="pt_BR.UTF-8"
LANGUAGE="pt_BR:pt_PT:gl_ES:es_ES:en"
LC_NUMERIC="pt_PT.UTF-8"
LC_TIME="pt_PT.UTF-8"
LC_MONETARY="pt_PT.UTF-8"
LC_PAPER="pt_PT.UTF-8"
LC_NAME="pt_PT.UTF-8"
LC_ADDRESS="pt_PT.UTF-8"
LC_TELEPHONE="pt_PT.UTF-8"
LC_MEASUREMENT="pt_PT.UTF-8"
LC_IDENTIFICATION="pt_PT.UTF-8"

It doesn't work even installing and configuring locales with language-
selector-gnome, which is not installed by default on Lubuntu 20.04.

If I try to change the main language, I see that most of translations
exist, either in one language or another. So the problem is with the
fallback, determined by the LANGUAGE = section in /etc/default/locale.

*Using Spanish as first language:*
https://emma.cloud.tabdigital.eu/s/X2TRjAnPjJq76JH
*Using Galician as first language:*
https://emma.cloud.tabdigital.eu/s/StbkHwFPC27kzLo

We are not the only ones with this problem, polyglot people or
inhabitants of regions with languages with two different spelling
regulations can be combined in this way.

Thank you for your attention.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: language-selector-gnome 0.203
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CurrentDesktop: LXQt
Date: Sun Mar 29 18:20:30 2020
ExecutablePath: /usr/bin/gnome-language-selector
InstallationDate: Installed on 2020-03-29 (0 days ago)
InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200316)
InterpreterPath: /usr/bin/python3.8
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
PythonDetails: N/A
SourcePackage: language-selector
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Lubuntu LXQt - Locale fallback fails

Status in language-selector package in Ubuntu:
  New

Bug description:
  I have always been a locale-fallback feature user. With Lubuntu 18.04
  LTS I haven't any problem.

  The computer users are fluent in those languages, except in English
  (the default one). If there's a string untranslated in one language,
  it jumps and try to show the string of the next listed language and so
  on.

  In most of the programs the fallback works, but the LXQt menu, some
  details like some dialogs, don't work well, even editing
  /etc/default/locale file:

  LANG="pt_BR.UTF-8"
  LANGUAGE="pt_BR:pt_PT:gl_ES:es_ES:en"
  LC_NUMERIC="pt_PT.UTF-8"
  LC_TIME="pt_PT.UTF-8"
  LC_MONETARY="pt_PT.UTF-8"
  LC_PAPER="pt_PT.UTF-8"
  LC_NAME="pt_PT.UTF-8"
  LC_ADDRESS="pt_PT.UTF-8"
  LC_TELEPHONE="pt_PT.UTF-8"
  LC_MEASUREMENT="pt_PT.UTF-8"
  LC_IDENTIFICATION="pt_PT.UTF-8"

  It doesn't work even installing and configuring locales with language-
  selector-gnome, which is not installed by default on Lubuntu 20.04.

  If I try to change the main language, I see that most of translations
  exist, either in one language or another. So the problem is with the
  fallback, determined by the LANGUAGE = section in /etc/default/locale.

  *Using Spanish as first language:*
  https://emma.cloud.tabdigital.eu/s/X2TRjAnPjJq76JH
  *Using Galician as first language:*
  https://emma.cloud.tabdigital.eu/s/StbkHwFPC27kzLo

  We are not the only ones with this problem, polyglot people or
  inhabitants of regions with languages with two different spelling
  regulations can be combined in this way.

  Thank you for your attention.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: language-selector-gnome 0.203
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: LXQt
  Date: Sun Mar 29 18:20:30 2020
  ExecutablePath: /usr/bin/gnome-language-selector
  InstallationDate: Installed on 2020-03-29 (0 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200316)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: N/A
  SourcePackage: language-selector
  UpgradeStatus: No upgrade log 

[Desktop-packages] [Bug 1868131] Re: [Toshiba NB250] Integrated speakers always muted

[Pablo César Galdo Regueiro]

I tried to boot Puppy Linux BionicPup64 8.0 based on Ubuntu Bionic
x86_64 64-bit and sound works out of the box.

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

Title:
  [Toshiba NB250] Integrated speakers always muted

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Speakers are muted at boot and remains muted after plug and unplug 
headphones. Only can be activated from alsamixer, unmuting the headphones while 
the headphones are unplugged. Both speakers and
  headphones muting seems to be controlled in the Headphones area using 
alsamixer.

  Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia
  base: Ubuntu 18.04 bionic.

  I've "solved" it Linux Mint 19.3 Tricia in a not very good way,
  keeping automute activated in alsamixer, modifiyng
  /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf
  and executing a bash script at boot (sonido.sh) with the command
  "amixer set -c 0 Headphone unmute 100%" in order to prevent the
  speakers being muted.

  There are some issues reported to pulseaudio manteiners. Not the same
  but related:

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu1881 F pulseaudio
  CasperVersion: 1.427
  CurrentDesktop: XFCE
  Date: Thu Mar 19 15:58:26 2020
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2010
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V1.60
  dmi.board.name: PAV10 DDR2
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ
  dmi.product.name: TOSHIBA NB250
  dmi.product.sku: 012345678912345678912345678
  dmi.product.version: PLL2XE-005003AS
  dmi.sys.vendor: TOSHIBA

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

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

[Desktop-packages] [Bug 1868131] Re: Integrated speakers always muted

[Pablo César Galdo Regueiro]

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

Increasing the headphones volume in alsamixer, speakers start to sound.
If I plug the headphones, it works. When unplug the headphones, alsamixer 
Headphones volume goes to zero and it affects speaker, because headphones 
volume in alsamixer control both speaker and headphones.

** Attachment added: "With volume un Headphone section in alsamixer thre're 
sound"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1868131/+attachment/5339031/+files/sound.png

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

Title:
  Integrated speakers always muted

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Speakers are muted at boot and remains muted after plug and unplug 
headphones. Only can be activated from alsamixer, unmuting the headphones while 
the headphones are unplugged. Both speakers and
  headphones muting seems to be controlled in the Headphones area using 
alsamixer.

  Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia
  base: Ubuntu 18.04 bionic.

  I've "solved" it Linux Mint 19.3 Tricia in a not very good way,
  keeping automute activated in alsamixer, modifiyng
  /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf
  and executing a bash script at boot (sonido.sh) with the command
  "amixer set -c 0 Headphone unmute 100%" in order to prevent the
  speakers being muted.

  There are some issues reported to pulseaudio manteiners. Not the same
  but related:

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu1881 F pulseaudio
  CasperVersion: 1.427
  CurrentDesktop: XFCE
  Date: Thu Mar 19 15:58:26 2020
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2010
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V1.60
  dmi.board.name: PAV10 DDR2
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ
  dmi.product.name: TOSHIBA NB250
  dmi.product.sku: 012345678912345678912345678
  dmi.product.version: PLL2XE-005003AS
  dmi.sys.vendor: TOSHIBA

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

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

[Desktop-packages] [Bug 1868131] Re: Integrated speakers always muted

[Pablo César Galdo Regueiro]

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

Just after boot, no sound.
It can't be activated using pavucontrol.
Only with alsamixer.

** Attachment added: "State of alsamixer and pavucontrol on boot"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1868131/+attachment/5339029/+files/boot.png

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

Title:
  Integrated speakers always muted

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Speakers are muted at boot and remains muted after plug and unplug 
headphones. Only can be activated from alsamixer, unmuting the headphones while 
the headphones are unplugged. Both speakers and
  headphones muting seems to be controlled in the Headphones area using 
alsamixer.

  Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia
  base: Ubuntu 18.04 bionic.

  I've "solved" it Linux Mint 19.3 Tricia in a not very good way,
  keeping automute activated in alsamixer, modifiyng
  /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf
  and executing a bash script at boot (sonido.sh) with the command
  "amixer set -c 0 Headphone unmute 100%" in order to prevent the
  speakers being muted.

  There are some issues reported to pulseaudio manteiners. Not the same
  but related:

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu1881 F pulseaudio
  CasperVersion: 1.427
  CurrentDesktop: XFCE
  Date: Thu Mar 19 15:58:26 2020
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2010
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V1.60
  dmi.board.name: PAV10 DDR2
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ
  dmi.product.name: TOSHIBA NB250
  dmi.product.sku: 012345678912345678912345678
  dmi.product.version: PLL2XE-005003AS
  dmi.sys.vendor: TOSHIBA

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

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

[Desktop-packages] [Bug 1868131] Re: Integrated speakers always muted

[Pablo César Galdo Regueiro]

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

It is a duplicate of bug #1310121, unsolved from 2014, but
administrators closed it.

Daniel van Vugt (vanvugt) wrote 10 hours ago:   #9

Everyone please report your own new bugs by running:

  ubuntu-bug pulseaudio

This bug is closed.

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

Title:
  Integrated speakers always muted

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Speakers are muted at boot and remains muted after plug and unplug 
headphones. Only can be activated from alsamixer, unmuting the headphones while 
the headphones are unplugged. Both speakers and
  headphones muting seems to be controlled in the Headphones area using 
alsamixer.

  Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia
  base: Ubuntu 18.04 bionic.

  I've "solved" it Linux Mint 19.3 Tricia in a not very good way,
  keeping automute activated in alsamixer, modifiyng
  /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf
  and executing a bash script at boot (sonido.sh) with the command
  "amixer set -c 0 Headphone unmute 100%" in order to prevent the
  speakers being muted.

  There are some issues reported to pulseaudio manteiners. Not the same
  but related:

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu1881 F pulseaudio
  CasperVersion: 1.427
  CurrentDesktop: XFCE
  Date: Thu Mar 19 15:58:26 2020
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2010
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V1.60
  dmi.board.name: PAV10 DDR2
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ
  dmi.product.name: TOSHIBA NB250
  dmi.product.sku: 012345678912345678912345678
  dmi.product.version: PLL2XE-005003AS
  dmi.sys.vendor: TOSHIBA

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

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

[Desktop-packages] [Bug 1868131] [NEW] Integrated speakers always muted

[Pablo César Galdo Regueiro]

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

Public bug reported:

Speakers are muted at boot and remains muted after plug and unplug headphones. 
Only can be activated from alsamixer, unmuting the headphones while the 
headphones are unplugged. Both speakers and
headphones muting seems to be controlled in the Headphones area using alsamixer.

Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia
base: Ubuntu 18.04 bionic.

I've "solved" it Linux Mint 19.3 Tricia in a not very good way, keeping
automute activated in alsamixer, modifiyng /usr/share/pulseaudio/alsa-
mixer/paths/analog-output-headphones.conf and executing a bash script at
boot (sonido.sh) with the command "amixer set -c 0 Headphone unmute
100%" in order to prevent the speakers being muted.

There are some issues reported to pulseaudio manteiners. Not the same
but related:

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: pulseaudio 1:13.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  xubuntu1881 F pulseaudio
CasperVersion: 1.427
CurrentDesktop: XFCE
Date: Thu Mar 19 15:58:26 2020
LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/30/2010
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.60
dmi.board.name: PAV10 DDR2
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.asset.tag: *
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ
dmi.product.name: TOSHIBA NB250
dmi.product.sku: 012345678912345678912345678
dmi.product.version: PLL2XE-005003AS
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-bug eoan

** Attachment added: "analog-output-headphones.conf"
   
https://bugs.launchpad.net/bugs/1868131/+attachment/5338919/+files/analog-output-headphones.conf

** This bug has been marked a duplicate of bug 1310121
   headphones working while speakers not working

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

Title:
  Integrated speakers always muted

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Speakers are muted at boot and remains muted after plug and unplug 
headphones. Only can be activated from alsamixer, unmuting the headphones while 
the headphones are unplugged. Both speakers and
  headphones muting seems to be controlled in the Headphones area using 
alsamixer.

  Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia
  base: Ubuntu 18.04 bionic.

  I've "solved" it Linux Mint 19.3 Tricia in a not very good way,
  keeping automute activated in alsamixer, modifiyng
  /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf
  and executing a bash script at boot (sonido.sh) with the command
  "amixer set -c 0 Headphone unmute 100%" in order to prevent the
  speakers being muted.

  There are some issues reported to pulseaudio manteiners. Not the same
  but related:

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu1881 F pulseaudio
  CasperVersion: 1.427
  CurrentDesktop: XFCE
  Date: Thu Mar 19 15:58:26 2020
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2010
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V1.60
  dmi.board.name: PAV10 DDR2
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ
  

[Desktop-packages] [Bug 1310121] Re: headphones working while speakers not working

[Pablo César Galdo Regueiro]

There are some issues reported to pulseaudio manteiners. Not the same
but related:

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540

** Bug watch added: PulseAudio #256
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256

** Bug watch added: PulseAudio #540
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540

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

Title:
  headphones working while speakers not working

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  to change kernel does not help, I tried 3.11 kernel, 3.8 kernel, 3.5
  kernel.

  Testing the left and right channel work for headphones output , a
  minijack is connected to the ampli.

  Removing the jack the notebook ( system76 notebook) is like mute. I have 
tried to use alsamixer , all the volume are ok.
  application seem to output their audios... but nothing to through the 
speakers.

  thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11
  ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
  Uname: Linux 3.8.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  francesca   2074 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr 20 00:23:09 2014
  InstallationDate: Installed on 2012-10-18 (548 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (0 days ago)
  dmi.bios.date: 09/27/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Gazelle Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp8
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd09/27/2012:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp8:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp8:cvnNoEnclosure:ct9:cvrN/A:
  dmi.product.name: Gazelle Professional
  dmi.product.version: gazp8
  dmi.sys.vendor: System76, Inc.

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

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

[Desktop-packages] [Bug 1310121] Re: headphones working while speakers not working

[Pablo César Galdo Regueiro]

Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia
base: Ubuntu 18.04 bionic.

Speakers are muted at boot and remains muted after plug and unplug
headphones. Only can be activated from alsamixer, unmuting the
headphones while the headphones are unplugged. Both speakers and
headphones muting seems to be controlled in the Headphones area using
alsamixer.

I've "solved" it in a not very good way, keeping automute activated in
alsamixer, modifiyng /usr/share/pulseaudio/alsa-mixer/paths/analog-
output-headphones.conf and executing a bash script at boot (sonido.sh)
with the command "amixer set -c 0 Headphone unmute 100%" in order to
prevent the speakers being muted.

Tomorrow I'm going to send more details and try to reproduce the same
bug using Xubuntu 18.04.

System:
  Host: ROI-TOSHIBA-NB250 Kernel: 5.3.0-42-generic x86_64 bits: 64 
  compiler: gcc v: 7.4.0 Desktop: Xfce 4.14.1 tk: Gtk 3.22.30 wm: xfwm4 
  dm: LightDM Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic

Machine:
  Type: Laptop System: TOSHIBA product: TOSHIBA NB250 v: PLL2XE-005003AS 
  serial:  Chassis: type: 10 serial:  
  Mobo: TOSHIBA model: PAV10 DDR2 v: 1.00 serial:  BIOS: TOSHIBA 
  v: 1.60 date: 07/30/2010 

CPU:
  Topology: Single Core model: Intel Atom N455 bits: 64 type: MT 
  arch: Bonnell rev: A L2 cache: 512 KiB 
  flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 6649 
  Speed: 997 MHz min/max: 1000/1667 MHz Core speeds (MHz): 1: 997 2: 997

Audio:
  Device-1: Intel NM10/ICH7 Family High Definition Audio 
  vendor: Toshiba America Info Systems driver: snd_hda_intel v: kernel 
  bus ID: 00:1b.0 chip ID: 8086:27d8 
  Sound Server: ALSA v: k5.3.0-42-generic 

Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: 
/etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://mirrors.evowise.com/linuxmint/packages tricia main upstream 
import backport
  2: deb http://es-mirrors.evowise.com/ubuntu bionic main restricted universe 
multiverse
  3: deb http://es-mirrors.evowise.com/ubuntu bionic-updates main restricted 
universe multiverse
  4: deb http://es-mirrors.evowise.com/ubuntu bionic-backports main restricted 
universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ bionic-security main restricted 
universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ bionic partner
Info:
  Processes: 160 Uptime: 40m Memory: 1.93 GiB used: 927.8 MiB (46.9%) 
  Init: systemd v: 237 runlevel: 5 Compilers: gcc: 7.5.0 alt: 7 Shell: bash 
  v: 4.4.20 running in: xfce4-terminal inxi: 3.0.32 

** Attachment added: "analog-output-headphones.conf"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1310121/+attachment/5338626/+files/analog-output-headphones.conf

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

Title:
  headphones working while speakers not working

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  to change kernel does not help, I tried 3.11 kernel, 3.8 kernel, 3.5
  kernel.

  Testing the left and right channel work for headphones output , a
  minijack is connected to the ampli.

  Removing the jack the notebook ( system76 notebook) is like mute. I have 
tried to use alsamixer , all the volume are ok.
  application seem to output their audios... but nothing to through the 
speakers.

  thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11
  ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
  Uname: Linux 3.8.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  francesca   2074 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr 20 00:23:09 2014
  InstallationDate: Installed on 2012-10-18 (548 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (0 days ago)
  dmi.bios.date: 09/27/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Gazelle Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp8
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd09/27/2012:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp8:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp8:cvnNoEnclosure:ct9:cvrN/A:
  dmi.product.name: Gazelle Professional
  dmi.product.version: gazp8
  dmi.sys.vendor: System76, Inc.

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

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

[Desktop-packages] [Bug 1862264] Re: Browsing smb share is painfully slow when mounted via "gio" (compared with "mount")

[Pablo Copissa]

Reported upstream as issue 2062
(https://gitlab.gnome.org/GNOME/glib/issues/2062)

** Bug watch added: gitlab.gnome.org/GNOME/glib/issues #2062
   https://gitlab.gnome.org/GNOME/glib/issues/2062

** Description changed:

+ Reported upstream as issue 2062
+ (https://gitlab.gnome.org/GNOME/glib/issues/2062)
+ 
  Ubuntu 18.04 LTS here, fully updated (as of late Jan 2020).
  TEST #1:
  To establish a baseline/expected behavior, we first mount an SMB share via 
mount.cifs and time an ls command:
  $ sudo mount -t cifs -o username=pablo //myserver.example.com/share 
~/mnt/share
  $ cd ~/mnt/share/some/dir
  $ time ls
  ... approx 320 files ...
  real  0m1,080s
  user  0m0,008s
  sys   0m0,005s
  $ sudo umount ~/mnt/share
  
  TEST #2
  Now we do the same via gio mount:
  $ gio mount smb://myserver.example.com/share
  cd 
/run/user/1000/gvfs/smb-share\:server\=myserver.example.com\,share\=share/some/dir
  $ time ls
  ... same 320 files ...
  real  0m28,999s
  user  0m0,013s
  sys   0m0,032s
  
  Enumeration of files is about 29 times slower when mounted via gio mount
  than via mount -t cifs.
  
  TEST #3
  Now for the real weird: while using the gio-mounted folder, we now time ls IN 
COMBINATION WITH SOMETHING ELSE (can be strace ls, ls|wc etc...):
  $ time ls | wc
     321 3239804
  
  real  0m0,546s
  user  0m0,006s
  sys   0m0,004s
  
  Note that this is almost TWICE AS FAST than the "fast" mount of test #1
  and about 53 times faster than "slow" test #2 !
  
  The expectation is that Tests 1 and 2 should have similar timings, not
  differing by a factor of 30 or so. More disturbing, there is no good
  reason why tests 2 and 3 differ by an even bigger factor of 53: They use
  the same underlying infrastructure which test 3 proves is adequately
  fast. And yet, we get this slow down in test 2.
  
  As a final note, these benchmarks are a distilled version of the original 
real-life motivating scenario where a Java-based program would simply take tens 
of minutes to display the same list of 320 files when mounted via gio mount and 
a second or so when mounted via mount -t cifs.
  The same timing difference is of course visible in any file manager.
  
  Hope this helps
  
  PS: several old/ancient bug reports exist for a similar issue and I
  deliberately copied the title from one of them (#259771)
  
  PS2: may or may not be relevant: The remote server is a VM running
  Windows 7 (yes, I know...) and the connection was made via VPN (Ubuntu
  stock SSTP).
  
  PS3: Another data point (server is now a Synolgy NAS, not a Win7 VM)
  
  $ gio mount smb://nas.example.com/share2
  
  $ cd /run/user/1000/gvfs/smb-
  share\:server\=nas.example.com\,share\=share2/another/path
  
  $ time ls
  
  ... 528 subdirs approximately ...
  
  real  0m45,075s
  user  0m0,013s
  sys   0m0,058s
  
  $ time ls | wc
- 5281631   10893
+ 5281631   10893
  
  real  0m0,911s
  user  0m0,003s
  sys   0m0,005s
  
  Factor is about 50.

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

Title:
  Browsing smb share is painfully slow when mounted via "gio" (compared
  with "mount")

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Reported upstream as issue 2062
  (https://gitlab.gnome.org/GNOME/glib/issues/2062)

  Ubuntu 18.04 LTS here, fully updated (as of late Jan 2020).
  TEST #1:
  To establish a baseline/expected behavior, we first mount an SMB share via 
mount.cifs and time an ls command:
  $ sudo mount -t cifs -o username=pablo //myserver.example.com/share 
~/mnt/share
  $ cd ~/mnt/share/some/dir
  $ time ls
  ... approx 320 files ...
  real  0m1,080s
  user  0m0,008s
  sys   0m0,005s
  $ sudo umount ~/mnt/share

  TEST #2
  Now we do the same via gio mount:
  $ gio mount smb://myserver.example.com/share
  cd 
/run/user/1000/gvfs/smb-share\:server\=myserver.example.com\,share\=share/some/dir
  $ time ls
  ... same 320 files ...
  real  0m28,999s
  user  0m0,013s
  sys   0m0,032s

  Enumeration of files is about 29 times slower when mounted via gio
  mount than via mount -t cifs.

  TEST #3
  Now for the real weird: while using the gio-mounted folder, we now time ls IN 
COMBINATION WITH SOMETHING ELSE (can be strace ls, ls|wc etc...):
  $ time ls | wc
     321 3239804

  real  0m0,546s
  user  0m0,006s
  sys   0m0,004s

  Note that this is almost TWICE AS FAST than the "fast" mount of test
  #1 and about 53 times faster than "slow" test #2 !

  The expectation is that Tests 1 and 2 should have similar timings, not
  differing by a factor of 30 or so. More disturbing, there is no good
  reason why tests 2 and 3 differ by an even bigger factor of 53: They
  use the same underlying infrastructure which test 3 proves is
  adequately fast. And yet, we get this slow down in test 2.

  As a final note, these benchmarks a

[Desktop-packages] [Bug 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all

[Pablo Rodríguez Guillén]

I was able to solve the control volume thing but the root problem still
there. If someone gets to this point I will show you my solution.

I realized (in alsamixer) that I was able to change the speakers volume
controlling PCM device instead of Master one. So I searched about that
and found that you can make pulseaudio to control another device. All
the information is in here: https://askubuntu.com/questions/15069/how-
do-i-change-the-way-ubuntu-adjusts-my-volume-mixer-levels

However, I think this should be fixed. Thank you for your help ^^

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

Title:
  [X555UA, Realtek ALC256, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256

  speakers work, it's just the mic not working.

  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0

  8 lines make mic working until reboot.

  thx a lot for

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Sun Jun 26 23:56:46 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 2 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UA
  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.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all

[Pablo Rodríguez Guillén]

I have the same problem on Asus Zenbook UX430UA (Realtek ALC295) in
Ubuntu 18.04 with 5.3.0-40-generic linux kernel version.

Comment #8 fix's worked for me but now I get the same volume level from
my laptop speakers with 1% volume level, than the one I get with 100%
volume level. The only thing that I can change from volume controls is
that with 0% volume level, the speakers are muted.

I have tried with "options snd-hda-intel model=auto,laptop-dmic" but I
get the expected behaviour with model=auto (speakers works great but no
audio recording from laptop microphone). With "options snd-hda-intel
model=laptop-dmic,auto" I get the same behaviour that the one I get with
"model=laptop-dmic" only (microphone working but volume control doing
nothing).

I thought this was fixed, but maybe I'm doing something wrong.

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

Title:
  [X555UA, Realtek ALC256, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256

  speakers work, it's just the mic not working.

  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0

  8 lines make mic working until reboot.

  thx a lot for

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Sun Jun 26 23:56:46 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 2 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UA
  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.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all

[Pablo Rodríguez Guillén]

I have the same problem on my Asus Zenbook UX430UA (Realtek ALC295)
although I have "5.3.0-40-generic" linux kernel version with Ubuntu
18.04. Comment #8 solved my problem but with "options snd-hda-intel
model=laptop-dmic" in my alsa conf, up and down volume don't change the
speakers volume.

I can only mute the speakers with 0 volume, but I get the same volume
level with 1% volume than the one I get with 100%

With "options snd-hda-intel model=auto" or "options snd-hda-intel
model=alc295" I get the expected behaviour from the speakers but no
record of the internal microphone. I have already tried combining
auto/alc295 with laptop-dmic but I get the behaviour of the first option
I write (like as it were alone)

I thought this was fixed, maybe I am doing something wrong.

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

Title:
  [X555UA, Realtek ALC256, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256

  speakers work, it's just the mic not working.

  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0

  8 lines make mic working until reboot.

  thx a lot for

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Sun Jun 26 23:56:46 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 2 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UA
  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.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1862264] Re: Browsing smb share is painfully slow

[Pablo Copissa]

Looks like gio is part of glib, not gvfs, so changed the package accordingly. 
Also made clear in the title that gio vs mount is part of the issue.

** Package changed: gvfs (Ubuntu) => glib2.0 (Ubuntu)

** Summary changed:

- Browsing smb share is painfully slow
+ Browsing smb share is painfully slow when mounted via "gio" (compared with 
"mount")

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

Title:
  Browsing smb share is painfully slow when mounted via "gio" (compared
  with "mount")

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 LTS here, fully updated (as of late Jan 2020).
  TEST #1:
  To establish a baseline/expected behavior, we first mount an SMB share via 
mount.cifs and time an ls command:
  $ sudo mount -t cifs -o username=pablo //myserver.example.com/share 
~/mnt/share
  $ cd ~/mnt/share/some/dir
  $ time ls
  ... approx 320 files ...
  real  0m1,080s
  user  0m0,008s
  sys   0m0,005s
  $ sudo umount ~/mnt/share

  TEST #2
  Now we do the same via gio mount:
  $ gio mount smb://myserver.example.com/share
  cd 
/run/user/1000/gvfs/smb-share\:server\=myserver.example.com\,share\=share/some/dir
  $ time ls
  ... same 320 files ...
  real  0m28,999s
  user  0m0,013s
  sys   0m0,032s

  Enumeration of files is about 29 times slower when mounted via gio
  mount than via mount -t cifs.

  TEST #3
  Now for the real weird: while using the gio-mounted folder, we now time ls IN 
COMBINATION WITH SOMETHING ELSE (can be strace ls, ls|wc etc...):
  $ time ls | wc
     321 3239804

  real  0m0,546s
  user  0m0,006s
  sys   0m0,004s

  Note that this is almost TWICE AS FAST than the "fast" mount of test
  #1 and about 53 times faster than "slow" test #2 !

  The expectation is that Tests 1 and 2 should have similar timings, not
  differing by a factor of 30 or so. More disturbing, there is no good
  reason why tests 2 and 3 differ by an even bigger factor of 53: They
  use the same underlying infrastructure which test 3 proves is
  adequately fast. And yet, we get this slow down in test 2.

  As a final note, these benchmarks are a distilled version of the original 
real-life motivating scenario where a Java-based program would simply take tens 
of minutes to display the same list of 320 files when mounted via gio mount and 
a second or so when mounted via mount -t cifs.
  The same timing difference is of course visible in any file manager.

  Hope this helps

  PS: several old/ancient bug reports exist for a similar issue and I
  deliberately copied the title from one of them (#259771)

  PS2: may or may not be relevant: The remote server is a VM running
  Windows 7 (yes, I know...) and the connection was made via VPN (Ubuntu
  stock SSTP).

  PS3: Another data point (server is now a Synolgy NAS, not a Win7 VM)

  $ gio mount smb://nas.example.com/share2

  $ cd /run/user/1000/gvfs/smb-
  share\:server\=nas.example.com\,share\=share2/another/path

  $ time ls

  ... 528 subdirs approximately ...

  real  0m45,075s
  user  0m0,013s
  sys   0m0,058s

  $ time ls | wc
  5281631   10893

  real  0m0,911s
  user  0m0,003s
  sys   0m0,005s

  Factor is about 50.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1862264/+subscriptions

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

[Desktop-packages] [Bug 1862264] Re: Browsing smb share is painfully slow

[Pablo Copissa]

** Package changed: ubuntu => gvfs (Ubuntu)

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

Title:
  Browsing smb share is painfully slow

Status in gvfs package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 LTS here, fully updated (as of late Jan 2020).
  TEST #1:
  To establish a baseline/expected behavior, we first mount an SMB share via 
mount.cifs and time an ls command:
  $ sudo mount -t cifs -o username=pablo //myserver.example.com/share 
~/mnt/share
  $ cd ~/mnt/share/some/dir
  $ time ls
  ... approx 320 files ...
  real  0m1,080s
  user  0m0,008s
  sys   0m0,005s
  $ sudo umount ~/mnt/share

  TEST #2
  Now we do the same via gio mount:
  $ gio mount smb://myserver.example.com/share
  cd 
/run/user/1000/gvfs/smb-share\:server\=myserver.example.com\,share\=share/some/dir
  $ time ls
  ... same 320 files ...
  real  0m28,999s
  user  0m0,013s
  sys   0m0,032s

  Enumeration of files is about 29 times slower when mounted via gio
  mount than via mount -t cifs.

  TEST #3
  Now for the real weird: while using the gio-mounted folder, we now time ls IN 
COMBINATION WITH SOMETHING ELSE (can be strace ls, ls|wc etc...):
  $ time ls | wc
     321 3239804

  real  0m0,546s
  user  0m0,006s
  sys   0m0,004s

  Note that this is almost TWICE AS FAST than the "fast" mount of test
  #1 and about 53 times faster than "slow" test #2 !

  The expectation is that Tests 1 and 2 should have similar timings, not
  differing by a factor of 30 or so. More disturbing, there is no good
  reason why tests 2 and 3 differ by an even bigger factor of 53: They
  use the same underlying infrastructure which test 3 proves is
  adequately fast. And yet, we get this slow down in test 2.

  As a final note, these benchmarks are a distilled version of the original 
real-life motivating scenario where a Java-based program would simply take tens 
of minutes to display the same list of 320 files when mounted via gio mount and 
a second or so when mounted via mount -t cifs.
  The same timing difference is of course visible in any file manager.

  Hope this helps

  PS: several old/ancient bug reports exist for a similar issue and I
  deliberately copied the title from one of them (#259771)

  PS2: may or may not be relevant: The remote server is a VM running
  Windows 7 (yes, I know...) and the connection was made via VPN (Ubuntu
  stock SSTP).

  PS3: Another data point (server is now a Synolgy NAS, not a Win7 VM)

  $ gio mount smb://nas.example.com/share2

  $ cd /run/user/1000/gvfs/smb-
  share\:server\=nas.example.com\,share\=share2/another/path

  $ time ls

  ... 528 subdirs approximately ...

  real  0m45,075s
  user  0m0,013s
  sys   0m0,058s

  $ time ls | wc
  5281631   10893

  real  0m0,911s
  user  0m0,003s
  sys   0m0,005s

  Factor is about 50.

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

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

[Desktop-packages] [Bug 1823793] Re: [regression] Font scaling not working on gnome startup

[Juan Pablo Aroztegi]

Version 3.32.0-1ubuntu2, released today, has fixed the issue for me.

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

Title:
  [regression] Font scaling not working on gnome startup

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  The font text scaling setting is not being loaded on gnome startup. I
  have font text scaling set to 1.25. After updating mutter to package
  version 3.32.0-1ubuntu1 the text scaling setting is not loaded any
  more when starting gnome. Steps to reproduce the issue:

  1) Set your font scaling factor to something other than the default
  '1'. This can be set, for example, either by using "Gnome tweaks" or
  with gsettings:

  settings set org.gnome.desktop.interface text-scaling-factor 1.25

  2) You'll see that the top bar text gets larger.
  3) Log out and log in. You'll see that the top bar text and text in general 
has been reset to the default '1'. The setting is still set to '1.25', but 
visually it's '1'.

  If you set the value to something else, it gets applied correctly,
  until you log out.

  
  This worked as expected on package version 3.32.0-1. I wonder if this patch 
listed in the CHANGELOG could have somehow created this side effect:
  debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: mutter 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  8 13:42:39 2019
  InstallationDate: Installed on 2019-04-08 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190408)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1823793] Re: [regression] Font scaling not working on gnome startup

[Juan Pablo Aroztegi]

They look related. Fwiw, I'm using Xorg with an Intel video card and the
modesetting driver.

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

Title:
  [regression] Font scaling not working on gnome startup

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  The font text scaling setting is not being loaded on gnome startup. I
  have font text scaling set to 1.25. After updating mutter to package
  version 3.32.0-1ubuntu1 the text scaling setting is not loaded any
  more when starting gnome. Steps to reproduce the issue:

  1) Set your font scaling factor to something other than the default
  '1'. This can be set, for example, either by using "Gnome tweaks" or
  with gsettings:

  settings set org.gnome.desktop.interface text-scaling-factor 1.25

  2) You'll see that the top bar text gets larger.
  3) Log out and log in. You'll see that the top bar text and text in general 
has been reset to the default '1'. The setting is still set to '1.25', but 
visually it's '1'.

  If you set the value to something else, it gets applied correctly,
  until you log out.

  
  This worked as expected on package version 3.32.0-1. I wonder if this patch 
listed in the CHANGELOG could have somehow created this side effect:
  debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: mutter 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  8 13:42:39 2019
  InstallationDate: Installed on 2019-04-08 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190408)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1823793] [NEW] Font scaling not working on gnome startup

[Juan Pablo Aroztegi]

Public bug reported:

The font text scaling setting is not being loaded on gnome startup. I
have font text scaling set to 1.25. After updating mutter to package
version 3.32.0-1ubuntu1 the text scaling setting is not loaded any more
when starting gnome. Steps to reproduce the issue:

1) Set your font scaling factor to something other than the default '1'.
This can be set, for example, either by using "Gnome tweaks" or with
gsettings:

settings set org.gnome.desktop.interface text-scaling-factor 1.25

2) You'll see that the top bar text gets larger.
3) Log out and log in. You'll see that the top bar text and text in general has 
been reset to the default '1'. The setting is still set to '1.25', but visually 
it's '1'.

If you set the value to something else, it gets applied correctly, until
you log out.


This worked as expected on package version 3.32.0-1. I wonder if this patch 
listed in the CHANGELOG could have somehow created this side effect:
debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- X11: Add support for fractional scaling using Randr

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: mutter 3.32.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu25
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr  8 13:42:39 2019
InstallationDate: Installed on 2019-04-08 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190408)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco

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

Title:
  Font scaling not working on gnome startup

Status in mutter package in Ubuntu:
  New

Bug description:
  The font text scaling setting is not being loaded on gnome startup. I
  have font text scaling set to 1.25. After updating mutter to package
  version 3.32.0-1ubuntu1 the text scaling setting is not loaded any
  more when starting gnome. Steps to reproduce the issue:

  1) Set your font scaling factor to something other than the default
  '1'. This can be set, for example, either by using "Gnome tweaks" or
  with gsettings:

  settings set org.gnome.desktop.interface text-scaling-factor 1.25

  2) You'll see that the top bar text gets larger.
  3) Log out and log in. You'll see that the top bar text and text in general 
has been reset to the default '1'. The setting is still set to '1.25', but 
visually it's '1'.

  If you set the value to something else, it gets applied correctly,
  until you log out.

  
  This worked as expected on package version 3.32.0-1. I wonder if this patch 
listed in the CHANGELOG could have somehow created this side effect:
  debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: mutter 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  8 13:42:39 2019
  InstallationDate: Installed on 2019-04-08 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190408)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1455857] Re: Program crashes before a window appears. Having Xlib: extension GLX missing problems

[Pablo E. Adames]

Paul,Thanks.I am on 18.04 LTS and ever since I updated from 16.04 LTS the 
laptop integrated webcam stopped working.
pablo@pablo-P170EM:~$ lsusb
Bus 002 Device 003: ID 147e:1002 Upek Biometric Touchchip/Touchstrip 
Fingerprint Sensor
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 05ac:12a8 Apple, Inc. iPhone5/5C/5S/6
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 005: ID 047d:1012 Kensington PocketMouse
Bus 003 Device 004: ID 045e:0780 Microsoft Corp. Comfort Curve Keyboard 3000
Bus 003 Device 003: ID 1058:10b8 Western Digital Technologies, Inc. Elements 
Portable (WDBU6Y, WDBUZG)
Bus 003 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


pablo@pablo-P170EM:~$ lsmod
Module  Size  Used by
btrfs    1122304  0
zstd_compress 163840  1 btrfs
xor    24576  1 btrfs
raid6_pq  114688  1 btrfs
ufs    77824  0
qnx4   16384  0
hfsplus   106496  0
hfs    57344  0
minix  32768  0
ntfs  102400  0
msdos  20480  0
jfs   188416  0
xfs  1200128  0
libcrc32c  16384  1 xfs
cpuid  16384  0
nls_iso8859_1  16384  1
pci_stub   16384  1
vboxpci    24576  0
vboxnetadp 28672  0
vboxnetflt 28672  0
vboxdrv   471040  3 vboxpci,vboxnetadp,vboxnetflt
ipheth 16384  0
binfmt_misc    20480  1
intel_rapl 20480  0
x86_pkg_temp_thermal    16384  0
intel_powerclamp   16384  0
coretemp   16384  0
kvm_intel 212992  0
kvm   598016  1 kvm_intel
irqbypass  16384  1 kvm
crct10dif_pclmul   16384  0
snd_hda_codec_hdmi 49152  1
crc32_pclmul   16384  0
ghash_clmulni_intel    16384  0
arc4   16384  2
pcbc   16384  0
ath9k 151552  0
aesni_intel   188416  0
snd_hda_codec_realtek   106496  1
snd_hda_codec_generic    73728  1 snd_hda_codec_realtek
aes_x86_64 20480  1 aesni_intel
snd_hda_intel  40960  6
snd_hda_codec 126976  4 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
snd_hda_core   81920  5 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
snd_hwdep  20480  1 snd_hda_codec
crypto_simd    16384  1 aesni_intel
snd_pcm    98304  4 
snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core
snd_seq_midi   16384  0
snd_seq_midi_event 16384  1 snd_seq_midi
snd_rawmidi    32768  1 snd_seq_midi
ath9k_common   36864  1 ath9k
ath9k_hw  471040  2 ath9k_common,ath9k
snd_seq    65536  2 snd_seq_midi,snd_seq_midi_event
snd_seq_device 16384  3 snd_seq,snd_seq_midi,snd_rawmidi
ath    28672  3 ath9k_common,ath9k,ath9k_hw
snd_timer  32768  2 snd_seq,snd_pcm
glue_helper    16384  1 aesni_intel
cryptd 24576  3 crypto_simd,ghash_clmulni_intel,aesni_intel
intel_cstate   20480  0
intel_rapl_perf    16384  0
rtsx_pci_ms    20480  0
snd    81920  23 
snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm,snd_rawmidi
mac80211  778240  1 ath9k
memstick   16384  1 rtsx_pci_ms
joydev 24576  0
input_leds 16384  0
wmi_bmof   16384  0
serio_raw  16384  0
cfg80211  622592  4 ath9k_common,ath9k,ath,mac80211
mei_me 40960  0
shpchp 36864  0
lpc_ich    24576  0
soundcore  16384  1 snd
mei    90112  1 mei_me
mac_hid    16384  0
sch_fq_codel   20480  3
parport_pc 36864  0
ppdev  20480  0
lp 20480  0
parport    49152  3 parport_pc,lp,ppdev
ip_tables  28672  0
x_tables   40960  1 ip_tables
autofs4    40960  2
hid_generic    16384  0
usbhid 49152  0
hid   118784  2 usbhid,hid_generic
mmc_block  36864  2
uas    24576  0
usb_storage    69632  2 uas
nouveau  1716224  2
i915 1617920  24
rtsx_pci_sdmmc 24576  0
ttm   106496  1 nouveau
i2c_algo_bit   16384  2 i915,nouveau
drm_kms_helper    172032  2 i915,nouveau
syscopyarea

[Desktop-packages] [Bug 950843] Re: simple scan fails to scan. "unable to start scan" change scan ner gives no options

[Pablo Menéndez del Barrio]

Hi guys, I have the same problem than John and Miles over different
Epson Wifi Scanners or combis (printer + scanner). After searching a
lot, many other Linux Distributions have the same problem in their
latest versions with the scanner drivers well installed and the
conection to the equipment working. Using the program what you want, the
scanner starts (you can see the process on the scanner screen) to do his
work and then all fails.


The most worrisome situation is that anyone of this forums don't give any 
solution and it looks like a big problem. To nornmal users and institutional or 
educational ines, this type of problems are very important to select a good OS, 
and it's crazy that in 2019 we have problems to work propperly with a modern 
scan in Linux, no to mention that many manufacturers like Epson still do not 
give direct support...


Greetings from Spain,
Pablo.

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

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

Title:
  simple scan fails to scan. "unable to start scan" change scan ner
  gives no options

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  running 10.10
  epson stylus cx3200
  usb
  reboot of pc and printer/scanner tried.  
  same problem in 'xsane' and 'scanner utility' packages.
  the software used to work before i had to reinstall it.
...
  james@james-XL58laptop:~$ sane-find-scanner

# sane-find-scanner will now attempt to detect your scanner. If the
# result is different from what you expected, first make sure your
# scanner is powered up and properly connected to your computer.

# No SCSI scanners found. If you expected something different, make sure 
that
# you have loaded a kernel SCSI driver for your SCSI adapter.

  found USB scanner (vendor=0x04b8 [EPSON], product=0x0802 [USB MFP]) at 
libusb:006:002
# Your USB scanner was (probably) detected. It may or may not be supported 
by
# SANE. Try scanimage -L and read the backend's manpage.

# Not checking for parallel port scanners.

# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.

# You may want to run this program as root to find all devices. Once you
# found the scanner devices, be sure to adjust access permissions as
# necessary.
  james@james-XL58laptop:~$ scanimage -L

  No scanners were identified. If you were expecting something different,
  check that the scanner is plugged in, turned on and detected by the
  sane-find-scanner tool (if appropriate). Please read the documentation
  which came with this software (README, FAQ, manpages).
  james@james-XL58laptop:~$ 
  

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: simple-scan 2.32.0-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.35-32.66-generic 2.6.35.14
  Uname: Linux 2.6.35-32-generic i686
  Architecture: i386
  Date: Fri Mar  9 13:25:52 2012
  DriverPackageVersions:
   libsane 1.0.21-2ubuntu2
   libsane-extras N/A
   hplip 3.10.6-1ubuntu10.2
   hpoj N/A
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release i386 (20120214.2)
  MachineType: ASUSTeK Computer Inc. X58L
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-32-generic 
root=UUID=1adaa652-ac13-4a80-9382-d57361e69748 ro quiet splash
  ProcEnviron:
   LANG=en_GB.utf8
   SHELL=/bin/bash
  SourcePackage: simple-scan
  dmi.bios.date: 09/08/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 201
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X58L
  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.:bvr201:bd09/08/2008:svnASUSTeKComputerInc.:pnX58L:pvr1.0:rvnASUSTeKComputerInc.:rnX58L:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: X58L
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

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

[Desktop-packages] [Bug 1810675] [NEW] Bug 950843 not fixed in any distro.

[Pablo Menéndez del Barrio]

Public bug reported:

Hi guys, in relationship with this closed post:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/950843, I
have the same problem than John and Miles over different Epson Wifi
Scanners or combis (printer + scanner). After searching a lot, many
other Linux Distributions have the same problem in their latest versions
with the scanner drivers well installed and the conection to the
equipment working. Using the program what you want, the scanner starts
(you can see the process on the scanner screen) to do his work and then
all fails.

The most worrisome situation is that anyone of this forums don't give
any solution and it looks like a big problem. To nornmal users and
institutional or educational ines, this type of problems are very
important to select a good OS, and it's crazy that in 2019 we have
problems to work propperly with a modern scan in Linux, no to mention
that many manufacturers like Epson still do not give direct support...

I'm using Ubuntu 18.04 LTS and usually an Epson XP-530.

Greetings from Spain,
Pablo.

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

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

Title:
  Bug 950843 not fixed in any distro.

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Hi guys, in relationship with this closed post:
  https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/950843, I
  have the same problem than John and Miles over different Epson Wifi
  Scanners or combis (printer + scanner). After searching a lot, many
  other Linux Distributions have the same problem in their latest
  versions with the scanner drivers well installed and the conection to
  the equipment working. Using the program what you want, the scanner
  starts (you can see the process on the scanner screen) to do his work
  and then all fails.

  The most worrisome situation is that anyone of this forums don't give
  any solution and it looks like a big problem. To nornmal users and
  institutional or educational ines, this type of problems are very
  important to select a good OS, and it's crazy that in 2019 we have
  problems to work propperly with a modern scan in Linux, no to mention
  that many manufacturers like Epson still do not give direct support...

  I'm using Ubuntu 18.04 LTS and usually an Epson XP-530.

  Greetings from Spain,
  Pablo.

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

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

[Desktop-packages] [Bug 1725384] Re: On touch screens, the apps icon in the dock does not open when touched

[Juan Pablo Lozano]

This bug apply to Ubuntu 18.04.1 too. Please fix it!

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

Title:
  On touch screens, the apps icon in the dock does not open when touched

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

Bug description:
  I have an Bangho AERO 1104 with touch screen, when I try to open the
  application drawer from the applications icon in the dock, it does not
  open.

  1)- Ubuntu 17.10 Artful Aardvark 64 bit
  2)- gnome-shell-extension-ubuntu-dock_0.7
  3)- What should happen is that touching the applications icon in the dock, 
opens the application drawer.
  4)- Instead, what has happened is that absolutely nothing happened

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1725384/+subscriptions

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

[Desktop-packages] [Bug 1782925] Re: No me deja usar NVIDIA 304.135

[Juan Pablo Montiel]

Si me van a ayudar por favor que sea en mi idioma (Castellano-Español).
Gracias!!!

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

Title:
  No me deja usar NVIDIA 304.135

Status in xorg package in Ubuntu:
  New

Bug description:
  Instalé NVIDIA-Linux-x86_64-304.135.run pero no me deja usarlo y estoy
  con una resolución muy mala.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Jul 21 11:26:39 2018
  DistUpgraded: 2018-07-18 03:54:52,667 DEBUG failed to SystemUnLock() (E:No 
bloqueado)
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation C61 [GeForce 6150SE nForce 430] [1849:03d0]
  InstallationDate: Installed on 2017-04-10 (467 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical 
Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=5ec15496-f7c3-4826-b449-502d83c3141c ro splash quiet
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-07-18 (3 days ago)
  dmi.bios.date: 05/04/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: ALiveNF6G-VSTA
  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.:bvrP1.50:bd05/04/2007:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvn:rnALiveNF6G-VSTA:rvr:cvnToBeFilledByO.E.M.: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: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Jul 21 10:56:17 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical MouseMOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4

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

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

[Desktop-packages] [Bug 1782925] [NEW] No me deja usar NVIDIA 304.135

[Juan Pablo Montiel]

Public bug reported:

Instalé NVIDIA-Linux-x86_64-304.135.run pero no me deja usarlo y estoy
con una resolución muy mala.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat Jul 21 11:26:39 2018
DistUpgraded: 2018-07-18 03:54:52,667 DEBUG failed to SystemUnLock() (E:No 
bloqueado)
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation C61 [GeForce 6150SE nForce 430] [1849:03d0]
InstallationDate: Installed on 2017-04-10 (467 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical 
Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=es_AR:es
 PATH=(custom, no user)
 LANG=es_AR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=5ec15496-f7c3-4826-b449-502d83c3141c ro splash quiet
Renderer: Software
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-07-18 (3 days ago)
dmi.bios.date: 05/04/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: ALiveNF6G-VSTA
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.:bvrP1.50:bd05/04/2007:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvn:rnALiveNF6G-VSTA:rvr:cvnToBeFilledByO.E.M.: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: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Sat Jul 21 10:56:17 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputUSB Optical MouseMOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4

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


** Tags: amd64 apport-bug bionic possible-manual-nvidia-install 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/1782925

Title:
  No me deja usar NVIDIA 304.135

Status in xorg package in Ubuntu:
  New

Bug description:
  Instalé NVIDIA-Linux-x86_64-304.135.run pero no me deja usarlo y estoy
  con una resolución muy mala.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Jul 21 11:26:39 2018
  DistUpgraded: 2018-07-18 03:54:52,667 DEBUG failed to SystemUnLock() (E:No 
bloqueado)
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation C61 [GeForce 6150SE nForce 430] [1849:03d0]
  InstallationDate: Installed on 2017-04-10 (467 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical 
Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   LANG=es_AR.UTF-8
   

[Desktop-packages] [Bug 1782498] [NEW] Se tilda pantalla

[Juan Pablo Montiel]

Public bug reported:

Hola amigos!
El tema es que siempre y con versiones anteriores (además de con esta) se me 
tilda la pantalla y queda el SO totalmente inmovilizado, con la pantalla en 
algunos de los colores que estaba viendo. Nunca puedo encontrar el porqué, ya 
que el equipo se bloquea y no me deja entrar a las otras terminales como tty1, 
etc.
Siempre el sistema me dice que les avisará, pero la verdad es que nunca me ha 
llegado un mensaje al respecto.

Un gran saludo a todos desde Argentina, vivo en un pueblito de 1.500
habitantes y uso Ubunto hace aproximadamente unos 10 años. Los quiero
mucho y aprecio mucho lo que hacen por nosotros como usuarios. GRACIAS

Juan Pablo Montiel
6551 - Pirovano - Bs As - Argentina

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Jul 18 23:57:18 2018
DistUpgraded: 2018-07-18 03:54:52,667 DEBUG failed to SystemUnLock() (E:No 
bloqueado)
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation C61 [GeForce 6150SE nForce 430] [1849:03d0]
InstallationDate: Installed on 2017-04-10 (464 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical 
Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=es_AR:es
 PATH=(custom, no user)
 LANG=es_AR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=5ec15496-f7c3-4826-b449-502d83c3141c ro splash quiet
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-07-18 (0 days ago)
dmi.bios.date: 05/04/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: ALiveNF6G-VSTA
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.:bvrP1.50:bd05/04/2007:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvn:rnALiveNF6G-VSTA:rvr:cvnToBeFilledByO.E.M.: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: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Wed Jul 18 23:05:59 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputUSB Optical MouseMOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4
xserver.video_driver: nouveau

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

Title:
  Se tilda pantalla

Status in xorg package in Ubuntu:
  New

Bug description:
  Hola amigos!
  El tema es que siempre y con versiones anteriores (además de con esta) se me 
tilda la pantalla y queda el SO totalmente inmovilizado, con la pantalla en 
algunos de los colores que estaba viendo. Nunca puedo encontrar el porqué, ya 
que el equipo se bloquea y no me deja entrar a las otras terminales como tty1, 
etc.
  Siempre el sistema me dice que les avisará, pero la verdad es que nunca me ha 
llegado un mensaje al respecto.

  Un gran saludo a todos desde Argentina, vivo en un pueblito de 1.500
  habitantes y uso Ubunto hace aproximadamente unos 10 años. Los quiero
  mucho y aprecio mucho lo que hacen por nosotros como usuarios. GRACIAS

  Juan Pablo Montiel
  6551 - Pirovano - Bs As - Argentina

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7

[Desktop-packages] [Bug 1779687] Re: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia kernel module failed to build [error: implicit declaration of function ‘init_timer’]

[Juan Pablo Firrincieli]

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

Confirmed, using kernel 4.15.0-22 it works but fails in 4.15.0-24

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

Title:
  nvidia-340 340.104-0ubuntu0.16.04.1: nvidia kernel module failed to
  build [error: implicit declaration of function ‘init_timer’]

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

Bug description:
  When switching kernels from 4.13.0-45-generic to 4.15.0-24-generic,
  dkms fails in buildign the  nvidia-340 module(s). My graphics
  component doesn't allow for a newer nvidia driver than the 340 one.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-340 340.104-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.104  Thu Sep 14 17:13:13 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  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
  DKMSKernelVersion: 4.15.0-24-generic
  Date: Mon Jul  2 15:44:09 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DuplicateSignature: 
dkms:nvidia-340:340.104-0ubuntu0.16.04.1:/var/lib/dkms/nvidia/340-340.104/build/nv.c:2407:5:
 error: implicit declaration of function ‘init_timer’ 
[-Werror=implicit-function-declaration]
  GraphicsCard:
   NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo GT216GLM [Quadro FX 880M] [17aa:2145]
  InstallationDate: Installed on 2015-07-08 (1089 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 4389W1B
  PackageVersion: 340.104-0ubuntu0.16.04.1
  ProcKernelCmdLine: BOOT_IMAGE=Linux ro root=LABEL=Linux_root_Ubu splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6NET74WW (1.34 )
  dmi.board.name: 4389W1B
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6NET74WW(1.34):bd10/27/2010:svnLENOVO:pn4389W1B:pvrThinkPadW510:rvnLENOVO:rn4389W1B:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W510
  dmi.product.name: 4389W1B
  dmi.product.version: ThinkPad W510
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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 Jul  2 15:11:57 2018
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1

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

-- 
Mailing list: https://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 1138166] Re: Thunderbird deletes and doesn't save email addresses

[Pablo]

Thank you for contacting me.  It is no longer a problem.
Pablo

En jueves, 5 de julio de 2018 18:25:44 GMT-5, gf 
<1138...@bugs.launchpad.net> escribió:  
 
 Hello Pablo,
Thank you for submitting this bug and reporting a problem with Thunderbird.

You made this bug report in 2013 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?
Or, if it is still a problem, 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

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

Title:
  Thunderbird deletes and doesn't save email addresses

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  After Thunderbird working well for months, suddenly email addresses
  disappear, only the name remains.  I reenter the email address and
  save it, but next time I log on, the name is still there, but the
  email address has disappeared again.  I am using a google address book
  with thunderbird.  Prior to this week, I have had no trouble, and on
  another computer i have no trouble with the Google address book.  I am
  using  Thunderbird version 17.0.3 with Ubutnu 12.10.

  Note that this doesn't happen with all addresses.  What is most
  notable is that it wipes out some or all of the content of address
  lists. and it erases the address of any contacts included in that
  list.

  I don't know if this is part of a larger problem , since I have also
  reported recent difficulties with LibreOffice Writer not inserting or
  pasting images or graphics (see 222810      LibreOffice Writer
  doesn't paste images or Calc sheet)

  thank you for your help

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

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

Title:
  Thunderbird deletes and doesn't save email addresses

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  After Thunderbird working well for months, suddenly email addresses
  disappear, only the name remains.  I reenter the email address and
  save it, but next time I log on, the name is still there, but the
  email address has disappeared again.  I am using a google address book
  with thunderbird.  Prior to this week, I have had no trouble, and on
  another computer i have no trouble with the Google address book.  I am
  using  Thunderbird version 17.0.3 with Ubutnu 12.10.

  Note that this doesn't happen with all addresses.   What is most
  notable is that it wipes out some or all of the content of address
  lists. and it erases the address of any contacts included in that
  list.

  I don't know if this is part of a larger problem , since I have also
  reported recent difficulties with LibreOffice Writer not inserting or
  pasting images or graphics (see 222810   LibreOffice Writer
  doesn't paste images or Calc sheet)

  thank you for your help

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

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

[Desktop-packages] [Bug 1138166] Re: Thunderbird deletes and doesn't save email addresses

[Pablo]

Thank you for your followup.  This is no longer a problem and the ticket can be 
closed.
Thank you

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

Title:
  Thunderbird deletes and doesn't save email addresses

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  After Thunderbird working well for months, suddenly email addresses
  disappear, only the name remains.  I reenter the email address and
  save it, but next time I log on, the name is still there, but the
  email address has disappeared again.  I am using a google address book
  with thunderbird.  Prior to this week, I have had no trouble, and on
  another computer i have no trouble with the Google address book.  I am
  using  Thunderbird version 17.0.3 with Ubutnu 12.10.

  Note that this doesn't happen with all addresses.   What is most
  notable is that it wipes out some or all of the content of address
  lists. and it erases the address of any contacts included in that
  list.

  I don't know if this is part of a larger problem , since I have also
  reported recent difficulties with LibreOffice Writer not inserting or
  pasting images or graphics (see 222810   LibreOffice Writer
  doesn't paste images or Calc sheet)

  thank you for your help

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

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

[Desktop-packages] [Bug 1262719] Re: Crash if trying to compress contents of a directory mounted in nautilus via sftp

[Pablo Hinojosa]

This bug is still happening on Ubuntu 16.04

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

Title:
  Crash if trying to compress contents of a directory mounted in
  nautilus via sftp

Status in file-roller package in Ubuntu:
  Confirmed

Bug description:
  Steps to repro:

  1. in Nautilus, do "File->Connect to Server" and enter connection details to 
a remote SFTP server 
  2. "Mount" the newly created SFTP server directory
  3. Navigate into the SFTP share, select a bunch of files
  4. Right click and select "Compress"
  5. File roller appears, the status bar flickers up to 100% and then crashes.
  --- 
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-06-17 (185 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  NonfreeKernelModules: wl
  Package: file-roller 3.10.2.1-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2
  Tags:  trusty
  Uname: Linux 3.12.0-5-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2013-11-13 (36 days ago)
  UserGroups: adm autopilot cdrom dip fuse lpadmin plugdev sambashare sbuild 
sudo

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

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

[Desktop-packages] [Bug 1435421] Re: Dell XPS 15 - audio combo jack - microphone not working

[Jose Pablo]

I am on Arch Linux, same laptop model, same bug, I notice this is a 3
year old issue and I do not know if there has been any update to it in
the meantime. Is there anything I can do to help solve this issue?

(ps I made a thread on the arch forum about my problem
https://bbs.archlinux.org/viewtopic.php?pid=1777240#p1777240 )

** Also affects: alsa-driver (Arch Linux)
   Importance: Undecided
   Status: New

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

Title:
  Dell XPS 15 - audio combo jack - microphone not working

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Arch Linux:
  New

Bug description:
  Combo jack (headphones and microphone) working only as headphone
  output. Microphone is not detected at all when plugged-in.

  My exact laptop model is: Dell XPS 15 9530.

  I'm on 14.04 LTS, but I dont think its version-related. What more
  informations shall I collect and post here?

  I have also sent a report via http://www.alsa-project.org/alsa-
  info.sh. Would it help if I include one here?

  $ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bartek 2296 F pulseaudio
   /dev/snd/controlC0:  bartek 2296 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 14.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-19 (218 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. XPS 15 9530
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic 
root=UUID=a8714bf2-f3fb-4875-bb9e-4354f36a7f66 ro quiet splash nomdmonddf 
nomdmonisw
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-36-generic N/A
   linux-backports-modules-3.13.0-36-generic  N/A
   linux-firmware 1.127.6
  Tags:  trusty
  Uname: Linux 3.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip libvirtd lpadmin plugdev sambashare sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 03/28/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: XPS 15 9530
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd03/28/2014:svnDellInc.:pnXPS159530:pvrA04:rvnDellInc.:rnXPS159530:rvrA04:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 15 9530
  dmi.product.version: A04
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1616332] Re: gnome-software using hundreds of MB of memory when not in use

[Pablo Catalina]

Seems that it is could be a duplicated of #1723362

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

Title:
  gnome-software using hundreds of MB of memory when not in use

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  It seems gnome-software is running in the background all the time. Not
  a big deal if it was lightweight, but it seems to use hundreds of MB
  (from smem output):

PID User Command Swap  USS  PSS  
RSS 
   2291 jan  /usr/bin/gnome-software --g   285436   112576   117982   
134036 

  A total of over 400MB in RAM and swap combined.

  After killing and restarting, it takes "only" a bit over 100MB.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug 24 09:45:53 2016
  InstallationDate: Installed on 2012-11-10 (1382 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to xenial on 2016-06-19 (65 days ago)

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

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

[Desktop-packages] [Bug 1721087] [NEW] package enchant 1.6.0-11build2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Pablo Guillén Marquina]

Public bug reported:

It happens from time to time without any known reason why. Sometimes the
system just crash and stop working until you reboot.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: enchant 1.6.0-11build2
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
Date: Tue Oct  3 18:40:32 2017
DuplicateSignature:
 package:enchant:1.6.0-11build2
 Setting up libnss-resolve:amd64 (234-2ubuntu10) ...
 dpkg: error processing package enchant (--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 2017-07-10 (85 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5~beta1
SourcePackage: enchant
Title: package enchant 1.6.0-11build2 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: enchant (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package enchant 1.6.0-11build2 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in enchant package in Ubuntu:
  New

Bug description:
  It happens from time to time without any known reason why. Sometimes
  the system just crash and stop working until you reboot.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: enchant 1.6.0-11build2
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  Date: Tue Oct  3 18:40:32 2017
  DuplicateSignature:
   package:enchant:1.6.0-11build2
   Setting up libnss-resolve:amd64 (234-2ubuntu10) ...
   dpkg: error processing package enchant (--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 2017-07-10 (85 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5~beta1
  SourcePackage: enchant
  Title: package enchant 1.6.0-11build2 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/enchant/+bug/1721087/+subscriptions

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

[Desktop-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot

[Pablo Sanabria]

Well, this bug also is affecting me, I used the workaround in #10 and it works, 
but I still need to put my password in order to unlock the "Login" Keyring (My 
system don't have autologin enabled btw), the weird thing is that this system 
is fresh installed (no more than a week) and It was working fine until today. 
Maybe there is some package that I installed yesterday that is affecting the 
system.
Google-chrome affected
Online accounts also is affected
I didn't test other apps, but as far I could check those apps were affected by 
this issue
Greetings

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

Title:
  gnome-keyring not unlocked on boot

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

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1696580] [NEW] dificultades con kadenlive

[José Pablo Jaramillo]

Public bug reported:

No funciona en el ambiente mate

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Jun  7 16:22:27 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard: Microsoft Corporation Hyper-V virtual VGA [1414:5353] (prog-if 00 
[VGA controller])
InstallationDate: Installed on 2017-06-07 (0 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: Microsoft Corporation Virtual Machine
ProcEnviron:
 LANGUAGE=es_CO:es
 PATH=(custom, no user)
 LANG=es_CO.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=b208d30b-42e0-40d6-b53e-f82e15d5e64c ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', 
'-f'] failed with exit code 1: Error: no composite extension
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/23/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 090006
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: 7.0
dmi.chassis.asset.tag: 1155-0718-8197-6541-2374-2356-24
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: 7.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
dmi.product.name: Virtual Machine
dmi.product.version: 7.0
dmi.sys.vendor: Microsoft Corporation
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
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: Wed Jun  7 14:25:27 2017
xserver.configfile: default
xserver.devices:
 inputMicrosoft Vmbus HID-compliant Mouse TOUCHSCREEN, id 6
 inputPower Button KEYBOARD, id 7
 inputAT Translated Set 2 keyboard KEYBOARD, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
 inputTPPS/2 IBM TrackPoint MOUSE, id 10
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1

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


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

Title:
  dificultades con kadenlive

Status in xorg package in Ubuntu:
  New

Bug description:
  No funciona en el ambiente mate

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Jun  7 16:22:27 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard: Microsoft Corporation Hyper-V virtual VGA [1414:5353] (prog-if 
00 [VGA controller])
  InstallationDate: Installed on 2017-06-07 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  ProcEnviron:
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   LANG=es_CO.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=b208d30b-42e0-40d6-b53e-f82e15d5e64c ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UnitySupportTest: Error: 

[Desktop-packages] [Bug 1693531] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Pablo Vanegas Enríquez]

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

Public bug reported:

I don`t now

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
AptOrdering:
 gconf2-common:amd64: Install
 libgconf-2-4:amd64: Install
 gconf-service-backend:amd64: Install
 gconf-service:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Thu May 25 00:48:34 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-05-25 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  I don`t now

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu May 25 00:48:34 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-25 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1672424] Re: Cannot install Debian files outside of the repositories

[Pablo Axeitos]

gconf2 was not installed (?):

gconf2:
  Instalados: (ninguno)
  Candidato:  3.2.6-3ubuntu7
  Tabla de versión:
 3.2.6-3ubuntu7 500
500 http://es.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages

After installing gconf2 it works flawlessly.

Thank you very much for your help!!

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

Title:
  Cannot install Debian files outside of the repositories

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Released

Bug description:
  Impact
  --
  It is not possible to use the default Software app to install .debs for 
packages that are not already available in Ubuntu.

  Test Case
  -
  1.
  a. Download the .deb for a simple app for your version of Ubuntu directly 
from Launchpad.
  For 16.10, try 
https://launchpad.net/ubuntu/+source/gnome-clocks/3.22.1-0ubuntu1/
  Click amd64 then download the last .deb on that page.

  b. Open the .deb with gnome-software:
  gnome-software --local-filename=gnome-clocks_3.22.1-0ubuntu1_amd64.deb

  gnome-software should open to a page with an Install button for the
  package.

  This test case should already work.

  2.
  a. Download a .deb that is not already in Ubuntu.
  It is important that the package not be available in your local apt cache.
  https://www.google.com/chrome/
  https://itch.io/app

  b. Open the .deb with gnome-software
  gnome-software --local-filename=itch_23.2.1_amd64.deb

  gnome-software should open to a page with an Install button for the
  package.

  Click Install and verify that the app is installed.

  What Happens
  
  The second test fails. On Ubuntu 17.04, I get a popup
  "Sorry this did not work The file is not supported"

  On Ubuntu 16.04 LTS or 16.10, I get "Sorry this did not work No
  file_to_app results to show"

  Regression Potential
  

  Original Bug Report
  ---
  .deb files fail to install from non repository locations i.e. The file 
manager gnome-software claims "this file type is not supported".

  Using dpkg from the command line works as expected so the files aren't
  corrupt. This happened last distribution as well when it was first
  released. Might be a regression caused by adding snap package
  capabilities to the software-center?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-software 3.22.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar 13 10:02:00 2017
  InstallationDate: Installed on 2017-02-20 (20 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to zesty on 2017-02-28 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1672424/+subscriptions

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

[Desktop-packages] [Bug 1672424] Re: Cannot install Debian files outside of the repositories

[Pablo Axeitos]

I'm actually using a fresh install of Zesty.

gnome-software:
  Instalados: 3.22.7-0ubuntu3.17.04.2
  Candidato:  3.22.7-0ubuntu3.17.04.2
  Tabla de versión:
 *** 3.22.7-0ubuntu3.17.04.2 500
500 http://es.archive.ubuntu.com/ubuntu zesty-updates/main amd64 
Packages
500 http://es.archive.ubuntu.com/ubuntu zesty-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 3.22.7-0ubuntu3 500
500 http://es.archive.ubuntu.com/ubuntu zesty/main amd64 Packages

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

Title:
  Cannot install Debian files outside of the repositories

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Released

Bug description:
  Impact
  --
  It is not possible to use the default Software app to install .debs for 
packages that are not already available in Ubuntu.

  Test Case
  -
  1.
  a. Download the .deb for a simple app for your version of Ubuntu directly 
from Launchpad.
  For 16.10, try 
https://launchpad.net/ubuntu/+source/gnome-clocks/3.22.1-0ubuntu1/
  Click amd64 then download the last .deb on that page.

  b. Open the .deb with gnome-software:
  gnome-software --local-filename=gnome-clocks_3.22.1-0ubuntu1_amd64.deb

  gnome-software should open to a page with an Install button for the
  package.

  This test case should already work.

  2.
  a. Download a .deb that is not already in Ubuntu.
  It is important that the package not be available in your local apt cache.
  https://www.google.com/chrome/
  https://itch.io/app

  b. Open the .deb with gnome-software
  gnome-software --local-filename=itch_23.2.1_amd64.deb

  gnome-software should open to a page with an Install button for the
  package.

  Click Install and verify that the app is installed.

  What Happens
  
  The second test fails. On Ubuntu 17.04, I get a popup
  "Sorry this did not work The file is not supported"

  On Ubuntu 16.04 LTS or 16.10, I get "Sorry this did not work No
  file_to_app results to show"

  Regression Potential
  

  Original Bug Report
  ---
  .deb files fail to install from non repository locations i.e. The file 
manager gnome-software claims "this file type is not supported".

  Using dpkg from the command line works as expected so the files aren't
  corrupt. This happened last distribution as well when it was first
  released. Might be a regression caused by adding snap package
  capabilities to the software-center?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-software 3.22.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar 13 10:02:00 2017
  InstallationDate: Installed on 2017-02-20 (20 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to zesty on 2017-02-28 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1672424/+subscriptions

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

[Desktop-packages] [Bug 1672424] Re: Cannot install Debian files outside of the repositories

[Pablo Axeitos]

Trying to install steam right now, opening the deb package with double-
click or with the command gnome-software --local-
filename=steam_latest.deb opens gnome software, but "install" button
does not work.

Proposed activated and software up to date.

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

Title:
  Cannot install Debian files outside of the repositories

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Released

Bug description:
  Impact
  --
  It is not possible to use the default Software app to install .debs for 
packages that are not already available in Ubuntu.

  Test Case
  -
  1.
  a. Download the .deb for a simple app for your version of Ubuntu directly 
from Launchpad.
  For 16.10, try 
https://launchpad.net/ubuntu/+source/gnome-clocks/3.22.1-0ubuntu1/
  Click amd64 then download the last .deb on that page.

  b. Open the .deb with gnome-software:
  gnome-software --local-filename=gnome-clocks_3.22.1-0ubuntu1_amd64.deb

  gnome-software should open to a page with an Install button for the
  package.

  This test case should already work.

  2.
  a. Download a .deb that is not already in Ubuntu.
  It is important that the package not be available in your local apt cache.
  https://www.google.com/chrome/
  https://itch.io/app

  b. Open the .deb with gnome-software
  gnome-software --local-filename=itch_23.2.1_amd64.deb

  gnome-software should open to a page with an Install button for the
  package.

  Click Install and verify that the app is installed.

  What Happens
  
  The second test fails. On Ubuntu 17.04, I get a popup
  "Sorry this did not work The file is not supported"

  On Ubuntu 16.04 LTS or 16.10, I get "Sorry this did not work No
  file_to_app results to show"

  Regression Potential
  

  Original Bug Report
  ---
  .deb files fail to install from non repository locations i.e. The file 
manager gnome-software claims "this file type is not supported".

  Using dpkg from the command line works as expected so the files aren't
  corrupt. This happened last distribution as well when it was first
  released. Might be a regression caused by adding snap package
  capabilities to the software-center?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-software 3.22.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar 13 10:02:00 2017
  InstallationDate: Installed on 2017-02-20 (20 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to zesty on 2017-02-28 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1672424/+subscriptions

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

[Desktop-packages] [Bug 1650395] Re: Strange large grey border around gnome-terminal when transparency is enabled

[Juan Pablo Firrincieli]

I can confirm this is happening in Ubuntu Gnome 17.04.
http://imgur.com/a/uuPbx

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

Title:
  Strange large grey border around gnome-terminal when transparency is
  enabled

Status in Ubuntu GNOME:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  I have found that after switching from Xorg to Wayland on Ubuntu GNOME
  16.10 with GNOME 3.22, that there is a large strange grey border
  around the window:

  - Fullscreen_gnome-terminal_in_AO_no_strange_border.png
  - Fullscreen_gnome-terminal_window.png
  - gnome-terminal_in_AO_strange_border.png
  - gnome-terminal_window_strange_border.png

  But this only occurs when the window is not fullscreen, and when
  transparency is enabled. Turning transparency off immediately fixes
  the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-terminal 3.22.1-1ubuntu0~yakkety1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Dec 15 21:29:17 2016
  InstallationDate: Installed on 2016-05-15 (214 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (57 days ago)

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

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

[Desktop-packages] [Bug 1673416] Re: Huge calendar icon in preferences window

[Pablo]

I chose the "Arc" theme in lxappearance

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

Title:
  Huge calendar icon in preferences window

Status in evolution package in Ubuntu:
  Incomplete

Bug description:
  The preferences window (Edit -> Preferences) shows a huge calendar icon in 
the left side section selector.
  See attached screenshot

  Running evolution 3.22.6
  On fully updated Linux arch.

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

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

[Desktop-packages] [Bug 1673416] [NEW] Huge calendar icon in preferences window

[Pablo]

Public bug reported:

The preferences window (Edit -> Preferences) shows a huge calendar icon in the 
left side section selector.
See attached screenshot

Running evolution 3.22.6
On fully updated Linux arch.

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

** Attachment added: "2017-03-16-114054_1238x743_scrot.png"
   
https://bugs.launchpad.net/bugs/1673416/+attachment/4838909/+files/2017-03-16-114054_1238x743_scrot.png

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

Title:
  Huge calendar icon in preferences window

Status in evolution package in Ubuntu:
  New

Bug description:
  The preferences window (Edit -> Preferences) shows a huge calendar icon in 
the left side section selector.
  See attached screenshot

  Running evolution 3.22.6
  On fully updated Linux arch.

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

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

[Desktop-packages] [Bug 1638012] Re: Backport for tab names being unreadable in gtk3 not working in 16.04

[Juan Pablo Aroztegi]

This is fixed in 5.2.4~rc2-0ubuntu1~xenial2.

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

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

Title:
  Backport for tab names being unreadable in gtk3 not working in 16.04

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  I'm using Libreoffice 5.2.3~rc2-0ubuntu1~xenial1 from the
  libreoffice/libreoffice-5-2 PPA under Ubuntu 16.04. I'm suffering bug
  #1527053 in which tab names are not readable in GTK3. The problem is
  that ever though the fix has been backported [1] to the xenial ppa
  package the fix is not working for me.

  I've built the latest master from GIT
  (85101d2a4da95f6c8a8e51065985409b285d2ebd) and tab names are readable
  in that version. I attach two screenshots: 1) Using the latest version
  from master, where tabs are readable. 2) Using
  5.2.3~rc2-0ubuntu1~xenial1 where tabs are not readable.

  Thank you.

  [1] As seen in the diff in
  
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-5-2/+sourcepub/7066628
  /+listing-archive-extra

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

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

[Desktop-packages] [Bug 1614593] Re: gimp freezes at end of cage-base transform

[Pablo Piaggio]

This still present in:

$lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
Codename:   xenial

$ uname -a
Linux vanhalen 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:59:10 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

$ apt-cache policy gimp
gimp:
  Installed: 2.8.16-1ubuntu1.1
  Candidate: 2.8.16-1ubuntu1.1
  Version table:
 *** 2.8.16-1ubuntu1.1 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
100 /var/lib/dpkg/status
 2.8.16-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

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

Title:
  gimp freezes at end of cage-base transform

Status in The Gimp:
  Fix Released
Status in gimp package in Ubuntu:
  Confirmed

Bug description:
  
  Hello.

  I am currently unable to apply the cage-base transform, whatever the
  image: at the end of the two first computations (creation of the cage
  and first deformation), gimp freezes (at the last pixel of the
  circle)!

  And no way to get it back...  Except closing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gimp 2.8.16-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Aug 18 17:36:44 2016
  InstallationDate: Installed on 2013-07-29 (1116 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  SourcePackage: gimp
  UpgradeStatus: Upgraded to xenial on 2016-07-30 (18 days ago)

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

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

[Desktop-packages] [Bug 1638012] Re: Backport for tab names being unreadable in gtk3 not working in 16.04

[Juan Pablo Aroztegi]

** Description changed:

  I'm using Libreoffice 5.2.3~rc2-0ubuntu1~xenial1 from the
  libreoffice/libreoffice-5-2 PPA under Ubuntu 16.04. I'm suffering bug
  #1527053 in which tab names are not readable in GTK3. The problem is
  that ever though the fix has been backported [1] to the xenial ppa
- package fix is not working for me.
+ package the fix is not working for me.
  
  I've built the latest master from GIT
  (85101d2a4da95f6c8a8e51065985409b285d2ebd) and tab names are readable in
  that version. I attach two screenshots: 1) Using the latest version from
  master, where tabs are readable. 2) Using 5.2.3~rc2-0ubuntu1~xenial1
  where tabs are not readable.
  
- 
  Thank you.
  
- 
- [1] As seen in the diff in 
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-5-2/+sourcepub/7066628/+listing-archive-extra
+ [1] As seen in the diff in
+ 
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-5-2/+sourcepub/7066628
+ /+listing-archive-extra

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

Title:
  Backport for tab names being unreadable in gtk3 not working in 16.04

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I'm using Libreoffice 5.2.3~rc2-0ubuntu1~xenial1 from the
  libreoffice/libreoffice-5-2 PPA under Ubuntu 16.04. I'm suffering bug
  #1527053 in which tab names are not readable in GTK3. The problem is
  that ever though the fix has been backported [1] to the xenial ppa
  package the fix is not working for me.

  I've built the latest master from GIT
  (85101d2a4da95f6c8a8e51065985409b285d2ebd) and tab names are readable
  in that version. I attach two screenshots: 1) Using the latest version
  from master, where tabs are readable. 2) Using
  5.2.3~rc2-0ubuntu1~xenial1 where tabs are not readable.

  Thank you.

  [1] As seen in the diff in
  
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-5-2/+sourcepub/7066628
  /+listing-archive-extra

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

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

[Desktop-packages] [Bug 1638012] Re: Backport for tab names being unreadable in gtk3 not working in 16.04

[Juan Pablo Aroztegi]

** Attachment added: "Using the latest dev build 85101d where tabs are readable"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1638012/+attachment/4770150/+files/Tab-names-readable-DevBuild-85101d.png

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

Title:
  Backport for tab names being unreadable in gtk3 not working in 16.04

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I'm using Libreoffice 5.2.3~rc2-0ubuntu1~xenial1 from the
  libreoffice/libreoffice-5-2 PPA under Ubuntu 16.04. I'm suffering bug
  #1527053 in which tab names are not readable in GTK3. The problem is
  that ever though the fix has been backported [1] to the xenial ppa
  package fix is not working for me.

  I've built the latest master from GIT
  (85101d2a4da95f6c8a8e51065985409b285d2ebd) and tab names are readable
  in that version. I attach two screenshots: 1) Using the latest version
  from master, where tabs are readable. 2) Using
  5.2.3~rc2-0ubuntu1~xenial1 where tabs are not readable.

  
  Thank you.

  
  [1] As seen in the diff in 
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-5-2/+sourcepub/7066628/+listing-archive-extra

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

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

[Desktop-packages] [Bug 1638012] [NEW] Backport for tab names being unreadable in gtk3 not working in 16.04

[Juan Pablo Aroztegi]

Public bug reported:

I'm using Libreoffice 5.2.3~rc2-0ubuntu1~xenial1 from the
libreoffice/libreoffice-5-2 PPA under Ubuntu 16.04. I'm suffering bug
#1527053 in which tab names are not readable in GTK3. The problem is
that ever though the fix has been backported [1] to the xenial ppa
package fix is not working for me.

I've built the latest master from GIT
(85101d2a4da95f6c8a8e51065985409b285d2ebd) and tab names are readable in
that version. I attach two screenshots: 1) Using the latest version from
master, where tabs are readable. 2) Using 5.2.3~rc2-0ubuntu1~xenial1
where tabs are not readable.


Thank you.


[1] As seen in the diff in 
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-5-2/+sourcepub/7066628/+listing-archive-extra

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


** Tags: ppa

** Attachment added: "Using 5.2.3~rc2-0ubuntu1~xenial1 where tabs are not 
readable"
   
https://bugs.launchpad.net/bugs/1638012/+attachment/4770149/+files/Tab-names-unreadable-5.2.3rc2.png

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

Title:
  Backport for tab names being unreadable in gtk3 not working in 16.04

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I'm using Libreoffice 5.2.3~rc2-0ubuntu1~xenial1 from the
  libreoffice/libreoffice-5-2 PPA under Ubuntu 16.04. I'm suffering bug
  #1527053 in which tab names are not readable in GTK3. The problem is
  that ever though the fix has been backported [1] to the xenial ppa
  package fix is not working for me.

  I've built the latest master from GIT
  (85101d2a4da95f6c8a8e51065985409b285d2ebd) and tab names are readable
  in that version. I attach two screenshots: 1) Using the latest version
  from master, where tabs are readable. 2) Using
  5.2.3~rc2-0ubuntu1~xenial1 where tabs are not readable.

  
  Thank you.

  
  [1] As seen in the diff in 
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-5-2/+sourcepub/7066628/+listing-archive-extra

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

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

[Desktop-packages] [Bug 1576605] Re: Activating menu items creates permanent space between title bar and tabs

[Pablo Lillia]

** Attachment added: "screen capture on video"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1576605/+attachment/4716132/+files/bug1576605.ogv

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

Title:
  Activating menu items creates permanent space between title bar and
  tabs

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  This bug applies to all Firefox versions since Unity brought global
  menus. However, only Firefox is affected, I've not observed any other
  app with a similar issue.

  What I expected:
   * Activating a menu item to simply display the relevant menu and cause no 
further interface changes

  What happened instead:
   * Activating a menu item displays the relevant menu and introduces a space 
between the titlebar and tabs

  The change is persistent as long as the window is open. Resizing or 
maximizing makes no difference. Enabling and activating menus from the title 
bar causes the exact same effect. Closing the window and reopening it from 
History's "Restore Closed Windows" removes the space. In other words, it does 
not affect newly opened windows.
  --- 
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  virtouni   1649 F pulseaudio
  BuildID: 20160425114621
  Channel: Unavailable
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-04-26 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Locales: extensions.sqlite corrupt or missing
  Package: firefox 46.0+build5-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  PrefSources: prefs.js
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  Profiles: Profile0 (Default) - LastVersion=46.0/20160425114621 (In use)
  RunningIncompatibleAddons: False
  Tags:  xenial
  Themes: extensions.sqlite corrupt or missing
  Uname: Linux 4.4.0-22-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/04/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MDU Ver. F.0D
  dmi.board.name: 30D8
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 83.0E
  dmi.chassis.asset.tag: CNU73433WV
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MDUVer.F.0D:bd11/04/2008:svnHewlett-Packard:pnHPCompaq6720s:pvrF.0D:rvnHewlett-Packard:rn30D8:rvrKBCVersion83.0E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq 6720s
  dmi.product.version: F.0D
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1576605] Re: Activating menu items creates permanent space between title bar and tabs

[Pablo Lillia]

It affects me too. Ubuntu 16.04.1 (64-bit) with Unity. Please note: it's
more visible with GTK dark themes. I'm using Arc Dark Theme. This
happens with light themes too, but it's subtle with them. But with dark
themes is very prominent.

Arc Dark Theme: https://github.com/horst3180/arc-theme
Firefox Arc Dark Theme: 
https://addons.mozilla.org/en-US/firefox/addon/arc-dark-theme/
Using NVIDIA binary driver 361.42 from nvidia-361. (GeForce GTX 960)


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

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

Title:
  Activating menu items creates permanent space between title bar and
  tabs

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  This bug applies to all Firefox versions since Unity brought global
  menus. However, only Firefox is affected, I've not observed any other
  app with a similar issue.

  What I expected:
   * Activating a menu item to simply display the relevant menu and cause no 
further interface changes

  What happened instead:
   * Activating a menu item displays the relevant menu and introduces a space 
between the titlebar and tabs

  The change is persistent as long as the window is open. Resizing or 
maximizing makes no difference. Enabling and activating menus from the title 
bar causes the exact same effect. Closing the window and reopening it from 
History's "Restore Closed Windows" removes the space. In other words, it does 
not affect newly opened windows.
  --- 
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  virtouni   1649 F pulseaudio
  BuildID: 20160425114621
  Channel: Unavailable
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-04-26 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Locales: extensions.sqlite corrupt or missing
  Package: firefox 46.0+build5-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  PrefSources: prefs.js
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  Profiles: Profile0 (Default) - LastVersion=46.0/20160425114621 (In use)
  RunningIncompatibleAddons: False
  Tags:  xenial
  Themes: extensions.sqlite corrupt or missing
  Uname: Linux 4.4.0-22-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/04/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MDU Ver. F.0D
  dmi.board.name: 30D8
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 83.0E
  dmi.chassis.asset.tag: CNU73433WV
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MDUVer.F.0D:bd11/04/2008:svnHewlett-Packard:pnHPCompaq6720s:pvrF.0D:rvnHewlett-Packard:rn30D8:rvrKBCVersion83.0E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq 6720s
  dmi.product.version: F.0D
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1592123] Re: org.freedesktop.packagekit.trigger-offline-update warning

[Pablo Cabrera]

I'm not getting the error when running from command line, but I see the
errors in my syslog.

Running 16.04 (gnome-software 3.20.1+git20160617.1.0440874.ubuntu-
xenial-0ubuntu1~16.04.1)

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

Title:
  org.freedesktop.packagekit.trigger-offline-update warning

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  When run from the command line, I see this warning:

  Gs-WARNING **: Failed to create permission org.freedesktop.packagekit
  .trigger-offline-update:
  GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action
  org.freedesktop.packagekit.trigger-offline-update is not registered


  Version: gnome-software 3.20.1+git20160608.2.6c64ff1-ubuntu-xenial-0ubuntu1
  on Ubuntu 16.10 (yakkety)
  from https://launchpad.net/~attente/+archive/ubuntu/gnome-software

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

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