date:20191004

** Changed in: nautilus
   Status: Unknown => New

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

Title:
  Selecting "Copy To..." on an object in "Starred" returns error "The
  specified location is not supported"

Status in Nautilus:
  New
Status in nautilus package in Ubuntu:
  New

Bug description:
  While in "Starred" right-clicking on a FSO¹ and selecting "Copy to.." brings 
up a new window to choose the destination, but this window shows an error 
message:
The folder contents could not be displayed
The specified location is not supported

  Steps to reproduce:
  1. Star a file system object
  2. Activate the "Starred" folder
  3. Right-click on starred FSO
  4. Select "Copy To..." from context menu
  5. A new window ("Select Copy Destination") pops up, as well as the error 
message in front of it.

  
  ¹ FSO: file system object, e.g. a file or folder

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0
  Uname: Linux 5.3.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 21:32:12 2019
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-09-27 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1846249] Re: Num lock works in reverse on Ubuntu 19.10 wayland

2019-10-04 Thread Bickhaus

Essentially, it seems like when logging in under Wayland, the system
remembers the status of the numlock LED, BUT it always starts the system
with the numlock functionality disabled.  This is why the LED is out of
sync if it's on when logging on, but not if it's off when logging in.

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

Title:
  Num lock works in reverse on Ubuntu 19.10 wayland

Status in x11-utils package in Ubuntu:
  New

Bug description:
  I updated to the Ubuntu 19.10 beta yesterday, and since updating, the
  num lock key on my keyboard (DASKeyboard Prime 13 from System76) is
  reversed.  When it is on (indicator light is lit), the numbers do not
  work, but the arrows, page up/down, home, end keys, etc. work.  When
  it is off, the numbers work and the arrows, etc. are disabled.
  Viewing the image of my keyboard layout (English US) in the Regions
  and Language section of GNOME settings shows Num Lock lit up when it
  is not lit on the keyboard and vice versa.

  I use the Wayland session, and this issue was not present prior to
  upgrading (I originally installed 18.10 and then upgraded to 19.04.).
  It is not present if I use another keyboard (I booted with a LITE-ON
  SK-9020 which uses USB like the DASKeyboard.).  It is not present
  while using the DASKeyboard, if I log into an X session, rather than
  Wayland.  I also tried changing the keyboard language, deleting the
  English (US) language and then switching back (so I am now back on the
  English (US) layout).  That did not work.

  I ran the commands specified on the Ubuntu Wiki's
  debuggingKeyboardDetection page.  The output of lsusb -v is attached
  as an attachment.  I do not have gconftool-2 installed, so I did not
  run that.  The output of xprop -root | grep XKB > ~/xk is:

  _XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us", "", ""

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: x11-utils 7.7+4build1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 11:17:31 2019
  DistUpgraded: 2019-09-30 20:21:51,653 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.0.12, 5.3.0-13-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev ef) (prog-if 00 [VGA 
controller])
 Subsystem: Tul Corporation / PowerColor Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [148c:2379]
  InstallationDate: Installed on 2019-03-19 (195 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: x11-utils
  UpgradeStatus: Upgraded to eoan on 2019-10-01 (0 days ago)
  dmi.bios.date: 09/12/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1820
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1820:bd09/12/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  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.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 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/x11-utils/+bug/1846249/+subscriptions

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

[Desktop-packages] [Bug 1846853] [NEW] Mouse scroll should control VOLUME NOT TIME

2019-10-04 Thread Anonymous

Public bug reported:

I want the mouse scroll to scroll the volume up and down, not the time
forward and back. This is a non-standard behavior that I consider to be
a BUG within Totem, and I preferentially use VNC because of this BUG.

Fix it so mouse scroll controls volume instead of time please.

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

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

Title:
  Mouse scroll should control VOLUME NOT TIME

Status in totem package in Ubuntu:
  New

Bug description:
  I want the mouse scroll to scroll the volume up and down, not the time
  forward and back. This is a non-standard behavior that I consider to
  be a BUG within Totem, and I preferentially use VNC because of this
  BUG.

  Fix it so mouse scroll controls volume instead of time please.

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

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

[Desktop-packages] [Bug 1845709] Re: Selecting "Copy To..." on an object in "Starred" returns error "The specified location is not supported"

2019-10-04 Thread Tom Reynolds

I just reported it upstream at
https://gitlab.gnome.org/GNOME/nautilus/issues/1243

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1243
   https://gitlab.gnome.org/GNOME/nautilus/issues/1243

** Also affects: nautilus via
   https://gitlab.gnome.org/GNOME/nautilus/issues/1243
   Importance: Unknown
   Status: Unknown

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

Title:
  Selecting "Copy To..." on an object in "Starred" returns error "The
  specified location is not supported"

Status in Nautilus:
  Unknown
Status in nautilus package in Ubuntu:
  New

Bug description:
  While in "Starred" right-clicking on a FSO¹ and selecting "Copy to.." brings 
up a new window to choose the destination, but this window shows an error 
message:
The folder contents could not be displayed
The specified location is not supported

  Steps to reproduce:
  1. Star a file system object
  2. Activate the "Starred" folder
  3. Right-click on starred FSO
  4. Select "Copy To..." from context menu
  5. A new window ("Select Copy Destination") pops up, as well as the error 
message in front of it.

  
  ¹ FSO: file system object, e.g. a file or folder

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0
  Uname: Linux 5.3.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 21:32:12 2019
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-09-27 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1846848] [NEW] Upgrade Mono package from 5.18.0 to 6.4.0

2019-10-04 Thread Reelix

Public bug reported:

Ubuntu 19.04

The latest version of Mono in Ubuntu is currently 5.18.0
Please upgrade it to the stable 6.4.0 release

Current download link (Ubuntu 18.04 - Should support Ubuntu 19.04)
- https://www.mono-project.com/download/stable/#download-lin

Thanks :)

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


** Tags: upgrade-software-version

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

Title:
  Upgrade Mono package from 5.18.0 to 6.4.0

Status in mono package in Ubuntu:
  New

Bug description:
  Ubuntu 19.04

  The latest version of Mono in Ubuntu is currently 5.18.0
  Please upgrade it to the stable 6.4.0 release

  Current download link (Ubuntu 18.04 - Should support Ubuntu 19.04)
  - https://www.mono-project.com/download/stable/#download-lin

  Thanks :)

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

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

[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2019-10-04 Thread midopa

I get this problem several times a day and it's become very frustrating.

Ubuntu 18.04.3
GNOME 3.28.2

Please let me know if any additional information can help triage the
bug.

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

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

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, but it seems to happen
  upon opening a new window, changing windows, closing windows, or
  opening the activities pane (whether a change of window is thus
  instigated or not)

  ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
  and to log in again, but that is also less than ideal

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1819207] Re: [FFe] Add Modaliases to open-vm-tools-desktop to allow automatic installation by ubuntu-drivers

2019-10-04 Thread Steve Langasek

Hello Jean-Baptiste, or anyone else affected,

Accepted ubuntu-drivers-common into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-drivers-common/1:0.5.2.4 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

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

** Changed in: ubuntu-drivers-common (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags removed: verification-done verification-done-bionic
** Tags added: verification-needed verification-needed-bionic

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

Title:
  [FFe] Add Modaliases to open-vm-tools-desktop to allow automatic
  installation by ubuntu-drivers

Status in open-vm-tools package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in open-vm-tools source package in Bionic:
  Fix Released
Status in ubiquity source package in Bionic:
  Won't Fix
Status in ubuntu-drivers-common source package in Bionic:
  Fix Committed
Status in open-vm-tools source package in Cosmic:
  Fix Released
Status in ubiquity source package in Cosmic:
  Won't Fix
Status in ubuntu-drivers-common source package in Cosmic:
  Won't Fix
Status in open-vm-tools source package in Disco:
  Fix Released
Status in ubiquity source package in Disco:
  Fix Released
Status in ubuntu-drivers-common source package in Disco:
  Fix Released

Bug description:
  [Rationale]
  On Ubuntu Desktop, we want to install automatically at installation time 
open-vm-tools-desktop and its dependencies to provide an improved user 
experience on first boot after installation of the guest. This method also 
provides an easy way to install the drivers after installation if they have not 
been installed at installation time.

  It is achieved adding an XB-Modaliases field to the control file for
  the record 'open-vm-tools-desktop' so ubuntu-drivers can detect the
  packages to install when running in a VMware guest and adding open-vm-
  tools to the list of whitelisted packages in ubuntu-drivers

  [Impact]
  The change adds an additional field to the control file used by 
ubuntu-drivers to detect the drivers to install automatically. In the worst 
case scenario either the field is not added or the detection by ubuntu-drivers 
fails. In both cases the package o-v-t-desktop is not installed and can still 
be installed manually.

  Note: open-vm-tools-desktop is in universe and for the final feature
  (>=Disco) it must be in main (already promoted). But for the SRU
  context (as this was accepted by Debian in 10.3.5-8) in our regular
  MRE we only cover the open-vm-tools change to "provide" the modalias.
  We do not change the ubuntu-drivers or ubiquity to depend on it - so
  no need to promote it on the SRU.

  [Test Case]
  With the patched versions of ubuntu-drivers and open-vm-tools
  1. Boot a daily ISO of Ubuntu Desktop to the live session in a VMware Guest 
(with VMWare Workstation for example)
  2. Open a terminal, make sure the package cache is up to date with the 
version of o-v-t containing the Modaliases field
  3. Run the command:
     $ ubuntu-drivers list
     and verify that o-v-t-desktop is in the output
  4. Run the command:
     $ ubuntu-drivers devices
     And verify that the output shows the details of the sys entry for this 
device
  5. Run the command:
     $ sudo ubuntu-drivers install
     and verify that the package o-v-t-desktop is installed

  [Regression Potential]
  Very Low. Package may fail to build if for some reason dh-gencontrol fails. 
Otherwise, given that the package is not already installed automatically, if 
automated installation doesn't work then we're still in the same situation than 
today.
  On ubuntu-drivers side, the change just adds o-v-t-desktop to the whitelist 
using an existing mechanism so other than a typo there is no risk of

[Desktop-packages] [Bug 1843796] Re: ubuntu-drivers install --gpgpu should use a DKMS fallback when no linux-modules-nvidia package is available

2019-10-04 Thread Steve Langasek

Hello Alberto, or anyone else affected,

Accepted ubuntu-drivers-common into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-drivers-common/1:0.5.2.4 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

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

** Changed in: ubuntu-drivers-common (Ubuntu Bionic)
   Status: Incomplete => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  ubuntu-drivers install --gpgpu should use a DKMS fallback when no
  linux-modules-nvidia package is available

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]

   * Calling "ubuntu-drivers install" does not install the kernel
  modules when passed the "--gpgpu" argument.

  While matching linux-modules-nvidia packages for the running kernel
  should be the default choice, we should fall back to the DKMS package
  when they are not available.

  The cha

  
  [Test Case]

   * Remove any currently installed nvidia drivers:
 sudo apt-get --purge remove '*nvidia*'

   * Call the ubuntu drivers tool:
 sudo ubuntu-drivers install --gpgpu

   * Restart your computer, and run the nvidia-smi package:
 sudo nvidia-smi

   * Check that the output shows the NVIDIA GPU (this is a sign that the
  kernel module was loaded, and is running properly).

  [Regression Potential]

   * Low. Currently, users relying on the --gpgpu parameter have no NVIDIA 
kernel modules, which prevents them from actually using the NVIDIA GPU.
  
  ubuntu-drivers install --gpgpu should use a DKMS fallback when no 
linux-modules-nvidia package is available.

  Currently, we do not deal with this kind of failure i.e. when no
  linux-modules-nvidia package is available for the kernel in use. If no
  such package can be found, we need to at least attempt installing the
  relevant DKMS package, so that users get the required kernel modules.

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

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

[Desktop-packages] [Bug 1846837] Re: totem-video-thumbnailer in Ubuntu 19.10 is currently broken on aarch64

2019-10-04 Thread RussianNeuroMancer

I added gcc-9 and ffmpeg to related packages because if search
"libgomp.so.1: cannot allocate memory in static TLS block" in Google you
will find this issue starting to appear in different program this years
(such as Anaconda installer, OpenCV, PHP ImageMagick module) so I don't
think this issue is isolated to Totem. However, Totem is only program
where I can reliable reproduce this issue right now.

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

Title:
  totem-video-thumbnailer in Ubuntu 19.10 is currently broken on aarch64

Status in ffmpeg package in Ubuntu:
  New
Status in gcc-9 package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New

Bug description:
  Hello!

  I found that totem-video-thumbnailer is broken on aarch64. It fail
  with following error:

  (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.740:
  Failed to load plugin '/usr/lib/aarch64-linux-
  gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-
  gnu/libgomp.so.1: cannot allocate memory in static TLS block

  (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.764:
  Failed to load plugin '/usr/lib/aarch64-linux-
  gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-
  gnu/libgomp.so.1: cannot allocate memory in static TLS block

  (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.788:
  Failed to load plugin '/usr/lib/aarch64-linux-
  gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-
  gnu/libgomp.so.1: cannot allocate memory in static TLS block

  I tried to rollback all related packages I could think of (totem,
  gcc-9, ffmpeg) to previous releases, but for some reason this doesn't
  help. I remember video thumbnail generation on aarch64 worked fine few
  weeks ago.

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

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

[Desktop-packages] [Bug 1846837] [NEW] totem-video-thumbnailer in Ubuntu 19.10 is currently broken on aarch64

2019-10-04 Thread RussianNeuroMancer

Public bug reported:

Hello!

I found that totem-video-thumbnailer is broken on aarch64. It fail with
following error:

(totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.740:
Failed to load plugin '/usr/lib/aarch64-linux-
gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-gnu/libgomp.so.1:
cannot allocate memory in static TLS block

(totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.764:
Failed to load plugin '/usr/lib/aarch64-linux-
gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-gnu/libgomp.so.1:
cannot allocate memory in static TLS block

(totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.788:
Failed to load plugin '/usr/lib/aarch64-linux-
gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-gnu/libgomp.so.1:
cannot allocate memory in static TLS block

I tried to rollback all related packages I could think of (totem, gcc-9,
ffmpeg) to previous releases, but for some reason this doesn't help. I
remember video thumbnail generation on aarch64 worked fine few weeks
ago.

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

** Affects: gcc-9 (Ubuntu)
 Importance: Undecided
 Status: New

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

** Also affects: gcc-9 (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  totem-video-thumbnailer in Ubuntu 19.10 is currently broken on aarch64

Status in ffmpeg package in Ubuntu:
  New
Status in gcc-9 package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New

Bug description:
  Hello!

  I found that totem-video-thumbnailer is broken on aarch64. It fail
  with following error:

  (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.740:
  Failed to load plugin '/usr/lib/aarch64-linux-
  gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-
  gnu/libgomp.so.1: cannot allocate memory in static TLS block

  (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.764:
  Failed to load plugin '/usr/lib/aarch64-linux-
  gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-
  gnu/libgomp.so.1: cannot allocate memory in static TLS block

  (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.788:
  Failed to load plugin '/usr/lib/aarch64-linux-
  gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-
  gnu/libgomp.so.1: cannot allocate memory in static TLS block

  I tried to rollback all related packages I could think of (totem,
  gcc-9, ffmpeg) to previous releases, but for some reason this doesn't
  help. I remember video thumbnail generation on aarch64 worked fine few
  weeks ago.

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

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

[Desktop-packages] [Bug 1846258] Re: Chromium Policy - Force Browser Signin - broken with 77.0.3865.90-0

2019-10-04 Thread Jonathan Langdon

Thanks, Olivier. That would explain it. It worked a few weeks ago just
fine, but apparently Google is no longer supporting it.

Thanks for helping figure out what happened!

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

Title:
  Chromium Policy - Force Browser Signin - broken with 77.0.3865.90-0

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Our school depends on the policy that forces students to sign into the
  browser with their Google accounts before being able to access the
  internet.  With the latest update, it no longer works and students can
  access the internet without being forced to login.

  Our current build on our student computers:
  77.0.3865.90-0ubuntu0.18.04.1

  If you need to read up on this policy, type in chrome://policy
  Policy: BrowserSignin currently set to 2

  It worked fine before updating the computers to the current version of
  Chromium-browser.

  Thanks for looking at this for our school!

  More details:
  Release: Bionic 18.04

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

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

[Desktop-packages] [Bug 1846807] [NEW] Xorg crash

2019-10-04 Thread kokoye2007 

Public bug reported:

When upgrade (include firmware update)

can't see login screen 
when i use startx 
looping login screen

Upgrade to 19.10 and install lightdm 
still again

when i use wayland is ok.
other gnome, gnome-classic, ubuntu is looping

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
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct  5 00:50:39 2019
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo UHD Graphics 620 [17aa:225c]
InstallationDate: Installed on 2019-01-22 (254 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190122)
MachineType: LENOVO 20KH007UVA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/02/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N23ET66W (1.41 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20KH007UVA
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET66W(1.41):bd09/02/2019:svnLENOVO:pn20KH007UVA:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KH007UVA:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 6th
dmi.product.name: 20KH007UVA
dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
dmi.product.version: ThinkPad X1 Carbon 6th
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99+git1909241510.0c4275~oibaf~d
version.libgl1-mesa-dri: libgl1-mesa-dri 19.3~git1909260954.031752~oibaf~d
version.libgl1-mesa-glx: libgl1-mesa-glx 19.3~git1909260954.031752~oibaf~d
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

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


** Tags: amd64 apport-bug crash eoan third-party-packages 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/1846807

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  When upgrade (include firmware update)

  can't see login screen 
  when i use startx 
  looping login screen

  Upgrade to 19.10 and install lightdm 
  still again

  when i use wayland is ok.
  other gnome, gnome-classic, ubuntu is looping

  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
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct  5 00:50:39 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:225c]
  InstallationDate: Installed on 2019-01-22 (254 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190122)
  MachineType: LENOVO 20KH007UVA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET66W (1.41 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KH007UVA
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET66W(1.41):bd09/02/2019:svnLENOVO:pn20KH007UVA:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KH007UVA:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KH007UVA

[Desktop-packages] [Bug 1846776] Re: Renaming a desktop item causes the shell to hang

2019-10-04 Thread Sergio Costas

I did several tries yesterday, but none of them worked. First I tried to
remove the "emit" calls and the "addSignalMethods" in desktopGrid, just
in case the problem was an incompatibility with the new class system in
Gnome Shell 3.34. Also removed all the grabHelper calls, but also didn't
work. The problem seems to be the text entry, that is not editable.

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

Title:
  Renaming a desktop item causes the shell to hang

Status in gnome-shell-extension-desktop-icons:
  New
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  In Progress

Bug description:
  Right click on a desktop icon and rename it:
   - The shell will hang and there's no way to recover it

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

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

[Desktop-packages] [Bug 1846759] Re: Ubuntu's evolution-data-server package incompatible with gnome-calendar package

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

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

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

Title:
  Ubuntu's evolution-data-server package incompatible with gnome-
  calendar package

Status in gnome-calendar package in Ubuntu:
  Confirmed

Bug description:
  On reporting an issue in gnome-calendar, I was told "GNOME Calendar
  3.34 requires EDS 3.34 running in the host system.".  Ubuntu has 3.32.

  See:

  https://gitlab.gnome.org/GNOME/gnome-calendar/issues/464#note_617797

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-calendar 3.32.2-1~ubuntu19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  4 08:00:32 2019
  InstallationDate: Installed on 2019-07-31 (64 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2019-09-22T11:01:00.065291

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

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

[Desktop-packages] [Bug 1699360] Re: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2019-10-04 Thread Gioele Barabucci

** Changed in: gnome-software (Ubuntu)
   Status: Incomplete => Opinion

** Changed in: gnome-software (Ubuntu)
   Status: Opinion => Confirmed

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

Title:
  package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in debconf package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  this all

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libpam-systemd:amd64 232-21ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Wed Jun 21 00:45:00 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-19 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: systemd
  Title: package libpam-systemd:amd64 232-21ubuntu4 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/debconf/+bug/1699360/+subscriptions

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

[Desktop-packages] [Bug 1822179] Re: Resuming from sleep breaks desktop and lock screen background in GNOME

2019-10-04 Thread Sean Ferguson

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

I have the same issue,

Ubuntu 19.04 disco
Nvidia GeForce GTX 1050
Pentium G4600


nvidia-smi
Fri Oct  4 17:24:16 2019   
+-+
| NVIDIA-SMI 418.56   Driver Version: 418.56   CUDA Version: 10.1 |
|---+--+--+
| GPU  NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap| Memory-Usage | GPU-Util  Compute M. |
|===+==+==|
|   0  GeForce GTX 1050Off  | :01:00.0  On |  N/A |
| 35%   34CP0N/A /  75W |430MiB /  1991MiB |  0%  Default |
+---+--+--+
   
+-+
| Processes:   GPU Memory |
|  GPU   PID   Type   Process name Usage  |
|=|
|0  1266  G   /usr/lib/xorg/Xorg26MiB |
|0  1300  G   /usr/bin/gnome-shell  47MiB |
|0  1520  G   /usr/lib/xorg/Xorg   111MiB |
|0  1659  G   /usr/bin/gnome-shell 241MiB |
+-+


lshw -C video
  *-display 
   description: VGA compatible controller
   product: GP107 [GeForce GTX 1050]
   vendor: NVIDIA Corporation
   physical id: 0
   bus info: pci@:01:00.0
   version: a1
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
   configuration: driver=nvidia latency=0
   resources: irq:125 memory:de00-deff memory:c000-cfff 
memory:d000-d1ff ioport:e000(size=128) memory:c-d

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

Title:
  Resuming from sleep breaks desktop and lock screen background in GNOME

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  CPU: AMD Ryzen 5 1600
  MOBO: MSI B350M MORTAR
  GPU: NVIDIA GTX 1060

  Ubuntu version: 19.04
  Nvidia driver version: 418.56

  
  The system is updated with the latest updates as today, 28 March 2019

  As the title says, in Ubuntu 19.04 the GNOME lockscreen gets
  corrupted, and the GNOME desktop has blank background after resuming
  from standby/sleep

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

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

[Desktop-packages] [Bug 1846790] [NEW] Saving files with a '#' in the name silently(!) fails on GVFS smb:// paths (Samba share)

2019-10-04 Thread Christian Pernegger

Public bug reported:

[Reported via ubuntu-bug, I'm assuming it has gathered all relevant
system info. More, especially on the Samba server, if required, is
available on request.]

What I'm trying to do:
Save a file whose name contains a '#' character to a Samba share accessed via a 
GVFS smb:// path.
Ex. 1: Open a blank Writer (ODT) document, save that under the name "Test 
#1.odt" on a Samba share mounted via Nautilus.
Ex. 2: Open a pre-existing file "Test #2.odt", either via Nautilus or 
File-Open, make some changes, save it & quit. 

What I'm expecting to happen:
The file shows up under the assigned name on both the client and the Samba 
server (in case of a new file); or the existing file now contains the changes 
made (in case of an existing file being modified).
Ex. 1: I'd expect to see "Test #1.odt" in the relevant directory.
Ex. 2: I'd expect "Test #2.odt" to contain my changes. 

What happens instead:
Ex. 1: LibreOffice actually saves the data in a file named "TFNZPF~F" as seen 
from the client, "Test " [note the space at the end] on the server.
Ex. 2: The original file remains untouched, but a new file "TFNZPF~F" (client), 
or "Test " (server) is created with the saved data.
Effectively, the save operation does not succeed -- without any error message.

Analysis:
This is based on experiments with more complex filenames. Somehow, when 
LibreOffice saves a file in this constellation, the filename gets truncated at 
the first '#', inclusive, first, suffix and all. (This in turn leaves a 
filename ending in a space, which isn't legal under Windows, so Samba's name 
mangling kicks in.)

The problem does not occur with local files or on a sshfs-mount. Gedit has no 
problem even on smb://.
It's unclear whether '#' is the only character affected.

Some kind of URL handling/escaping bug in LibreOffice's GIO support?

In any case, this cost me a day of work. (By the time I realised my
changes hadn't actually been lost but landed in a new, cryptically-named
file, I'd already recreated it to meet the deadline.)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libreoffice-gnome 1:6.0.7-0ubuntu0.18.04.10
ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct  4 17:12:21 2019
InstallationDate: Installed on 2019-09-23 (10 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Saving files with a '#' in the name silently(!) fails on GVFS smb://
  paths (Samba share)

Status in libreoffice package in Ubuntu:
  New

Bug description:
  [Reported via ubuntu-bug, I'm assuming it has gathered all relevant
  system info. More, especially on the Samba server, if required, is
  available on request.]

  What I'm trying to do:
  Save a file whose name contains a '#' character to a Samba share accessed via 
a GVFS smb:// path.
  Ex. 1: Open a blank Writer (ODT) document, save that under the name "Test 
#1.odt" on a Samba share mounted via Nautilus.
  Ex. 2: Open a pre-existing file "Test #2.odt", either via Nautilus or 
File-Open, make some changes, save it & quit. 

  What I'm expecting to happen:
  The file shows up under the assigned name on both the client and the Samba 
server (in case of a new file); or the existing file now contains the changes 
made (in case of an existing file being modified).
  Ex. 1: I'd expect to see "Test #1.odt" in the relevant directory.
  Ex. 2: I'd expect "Test #2.odt" to contain my changes. 

  What happens instead:
  Ex. 1: LibreOffice actually saves the data in a file named "TFNZPF~F" as seen 
from the client, "Test " [note the space at the end] on the server.
  Ex. 2: The original file remains untouched, but a new file "TFNZPF~F" 
(client), or "Test " (server) is created with the saved data.
  Effectively, the save operation does not succeed -- without any error message.

  Analysis:
  This is based on experiments with more complex filenames. Somehow, when 
LibreOffice saves a file in this constellation, the filename gets truncated at 
the first '#', inclusive, first, suffix and all. (This in turn leaves a 
filename ending in a space, which isn't legal under Windows, so Samba's name 
mangling kicks in.)

  The problem does not occur with local files or on a sshfs-mount. Gedit has no 
problem even on smb://.
  It's unclear whether '#' is the only character affected.

  Some kind of URL handling/escaping bug in LibreOffice's GIO support?

  In any case, this cost me a day of work. (By the time I realised

[Desktop-packages] [Bug 1846776] Re: Renaming a desktop item causes the shell to hang

** Changed in: gnome-shell-extension-desktop-icons
   Status: Unknown => New

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

Title:
  Renaming a desktop item causes the shell to hang

Status in gnome-shell-extension-desktop-icons:
  New
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  In Progress

Bug description:
  Right click on a desktop icon and rename it:
   - The shell will hang and there's no way to recover it

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

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

[Desktop-packages] [Bug 1838132] Re: file browser hangs system for several seconds on save/load/exit

2019-10-04 Thread Christopher Barrington-Leigh

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

@seb128, I added the log when you asked. This bug affects all file saves
/ loads on all applications on Ubuntu, so it is very debilitating. Can't
imagine why there are no other complainants.

** This bug has been marked a duplicate of bug 1833114
   print page dialog latency when trying to cancel or to save

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

Title:
  file browser hangs system for several seconds on save/load/exit

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  For the last month, saving a file or printing a file from my browser
  or any other application, or even trying to quit the file browser
  without doing anything, causes the file dialog and the entire system
  to hang (become unresponsive) for several seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.32.1-0ubuntu0.19.04.0
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 05:53:20 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-01-24 (183 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-05-29 (58 days ago)
  usr_lib_nautilus: dropbox 2018.11.28

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

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

[Desktop-packages] [Bug 1846785] [NEW] Crashes instantly on launch with Pentium J5005 Processor

2019-10-04 Thread milvi

Public bug reported:

[PROBLEM] Djvulibre version 3.5.27.1-8/bionic crashes immediately on intel Atom 
based processors. (I got a J5005 pentium ).
Doesn't crash on a  Intel® Core™ i7-7567U.

Due to this bug https://sourceforge.net/p/djvu/bugs/293/ ,

and fixed in commit 8407dd, on the 7th of October 2018.

>From git tags, it is included in 3.5.27.1-11 (probably version xxx -10,
though I cannot see this tag in git history)

I notice that no dependency change affects any of the versions to the
build process up to Disco (3.5.27.1-10)

For intel J5005 (or N5000 on other popular machines ) this bug renders
the package useless.

Indeed, it crashes immediately at application startup. Note that this
affects rdependencies such as evince, djview4.

I suggest upgrading the version available for Bionic LTS as part of the
development hardware stack long term support to 3.5.27.1-11.

Yours sincerly,

Milvi

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

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

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

** Description changed:

- [PROBLEM] Djvulibre on bionic is 3.5.27.1-8 crashes immediately on intel Atom 
based processors. (I got a J5005 pentium ).
+ [PROBLEM] Djvulibre version 3.5.27.1-8/bionic crashes immediately on intel 
Atom based processors. (I got a J5005 pentium ).
  Doesn't crash on a  Intel® Core™ i7-7567U.
  
  Due to this bug https://sourceforge.net/p/djvu/bugs/293/ ,
  
  and fixed in commit 8407dd, on the 7th of October 2018.
  
  From git tags, it is included in 3.5.27.1-11 (probably version xxx -10,
  though I cannot see this tag in git history)
  
  I notice that no dependency change affects any of the versions to the
  build process up to Disco (3.5.27.1-10)
  
  For intel J5005 (or N5000 on other popular machines ) this bug renders
  the package useless.
  
  Indeed, it crashes immediately at application startup. Note that this
  affects rdependencies such as evince, djview4.
  
  I suggest upgrading the version available to Bionic LTS as part of the
  development hardware stack long term support. Patch released under
  3.5.27.1-11 solves it. (Check reproducibility)
  
  Yours sincerly,
  
  Milvi

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

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

** Description changed:

  [PROBLEM] Djvulibre version 3.5.27.1-8/bionic crashes immediately on intel 
Atom based processors. (I got a J5005 pentium ).
  Doesn't crash on a  Intel® Core™ i7-7567U.
  
  Due to this bug https://sourceforge.net/p/djvu/bugs/293/ ,
  
  and fixed in commit 8407dd, on the 7th of October 2018.
  
  From git tags, it is included in 3.5.27.1-11 (probably version xxx -10,
  though I cannot see this tag in git history)
  
  I notice that no dependency change affects any of the versions to the
  build process up to Disco (3.5.27.1-10)
  
  For intel J5005 (or N5000 on other popular machines ) this bug renders
  the package useless.
  
  Indeed, it crashes immediately at application startup. Note that this
  affects rdependencies such as evince, djview4.
  
- I suggest upgrading the version available to Bionic LTS as part of the
- development hardware stack long term support. Patch released under
- 3.5.27.1-11 solves it. (Check reproducibility)
+ I suggest upgrading the version available for Bionic LTS as part of the
+ development hardware stack long term support to 3.5.27.1-11.
  
  Yours sincerly,
  
  Milvi

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

Title:
  Crashes instantly on launch with Pentium J5005 Processor

Status in djview4 package in Ubuntu:
  New
Status in djvulibre package in Ubuntu:
  New
Status in evince package in Ubuntu:
  New

Bug description:
  [PROBLEM] Djvulibre version 3.5.27.1-8/bionic crashes immediately on intel 
Atom based processors. (I got a J5005 pentium ).
  Doesn't crash on a  Intel® Core™ i7-7567U.

  Due to this bug https://sourceforge.net/p/djvu/bugs/293/ ,

  and fixed in commit 8407dd, on the 7th of October 2018.

  From git tags, it is included in 3.5.27.1-11 (probably version xxx
  -10, though I cannot see this tag in git history)

  I notice that no dependency change affects any of the versions to the
  build process up to Disco (3.5.27.1-10)

  For intel J5005 (or N5000 on other popular machines ) this bug renders
  the package useless.

  Indeed, it crashes immediately at application startup. Note that this
  affects rdependencies such as evince, djview4.

  I suggest upgrading the version available for Bionic LTS as part of
  the development hardware stack long term support to 3.5.27.1-11.

  Yours sincerly,

  Milvi

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1845772] Re: package nvidia-dkms-430 430.50-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-430 package post-installation script subprocess returned error exit status

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

** Changed in: nvidia-graphics-drivers-430 (Ubuntu)
   Status: New => Confirmed

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

Title:
  package nvidia-dkms-430 430.50-0ubuntu1 failed to install/upgrade:
  installed nvidia-dkms-430 package post-installation script subprocess
  returned error exit status 10

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

Bug description:
  This error pops-up every time I start the computer. Since the update
  to eoan, this pop-up appears, however, I didn't trust that it worked
  on disco either, as I have a hardware light indicating wether I'm
  using or not my GPU, and even though I had the option "Nvidia on
  demand", my GPU was still being used every time, so I think there's
  something wrong with the driver itself, ad it's not controlling the
  use of the GPU.

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: nvidia-dkms-430 430.50-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Fri Sep 27 17:27:03 2019
  ErrorMessage: installed nvidia-dkms-430 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2019-09-07 (20 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Python3Details: /usr/bin/python3.7, Python 3.7.4+, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: nvidia-graphics-drivers-430
  Title: package nvidia-dkms-430 430.50-0ubuntu1 failed to install/upgrade: 
installed nvidia-dkms-430 package post-installation script subprocess returned 
error exit status 10
  UpgradeStatus: Upgraded to eoan on 2019-09-27 (0 days ago)

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

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

[Desktop-packages] [Bug 1846779] [NEW] gsd-housekeeping is regularly opening /etc/fstab and the atime update is causing meta data write fluesh

Public bug reported:

gsd-housekeeping is opening /etc/fstab every 60 seconds and because it
is being opened without the O_NOATIME flag the access time updates are
causing regular meta data flushes. On an idle laptop this can cause the
HDD to spin up, flush write and spin down every 60 seconds. This
consumes power unnecessarily.

I've traced this using health-check for 15 minutes of activity:

sudo heath-check -p gsd-housekeeping -d 900 -f -r -v > gnome-gsd-
househeeping-15.min

See attached log.

Running strace on the process will show that the open of /etc/fstab does
not use O_NOATIME, hence atime is being updated on the file each time it
is accessed, causing dirtying of metadata for this file and hence the
dirty metadata has to be flushed back periodically.

Can this be fixed to save some power. I've estimated it can save ~0.1
Watts on my Lenovo x220.

** Affects: gnome-settings-daemon (Ubuntu)
Importance: High
Status: New

** Attachment added: "capture of gsd-housekeeping activity using heath-check
tool"

https://bugs.launchpad.net/bugs/1846779/+attachment/5294354/+files/gnome-gsd-housekeeping-15min.log

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

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

Title:
gsd-housekeeping is regularly opening /etc/fstab and the atime update
is causing meta data write fluesh

Status in gnome-settings-daemon package in Ubuntu:
New

Bug description:
gsd-housekeeping is opening /etc/fstab every 60 seconds and because it
is being opened without the O_NOATIME flag the access time updates are
causing regular meta data flushes. On an idle laptop this can cause
the HDD to spin up, flush write and spin down every 60 seconds. This
consumes power unnecessarily.

I've traced this using health-check for 15 minutes of activity:

sudo heath-check -p gsd-housekeeping -d 900 -f -r -v > gnome-gsd-
househeeping-15.min

See attached log.

Running strace on the process will show that the open of /etc/fstab
does not use O_NOATIME, hence atime is being updated on the file each
time it is accessed, causing dirtying of metadata for this file and
hence the dirty metadata has to be flushed back periodically.

Can this be fixed to save some power. I've estimated it can save ~0.1
Watts on my Lenovo x220.

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

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

[Desktop-packages] [Bug 1846776] Re: Renaming a desktop item causes the shell to hang

2019-10-04 Thread Treviño

Upstream issue https://gitlab.gnome.org/World/ShellExtensions/desktop-
icons/issues/153


** Bug watch added: gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues 
#153
   https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/153

** Also affects: gnome-shell-extension-desktop-icons via
   https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/153
   Importance: Unknown
   Status: Unknown

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

Title:
  Renaming a desktop item causes the shell to hang

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  In Progress

Bug description:
  Right click on a desktop icon and rename it:
   - The shell will hang and there's no way to recover it

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

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

[Desktop-packages] [Bug 1846776] [NEW] Renaming a desktop item causes the shell to hang

2019-10-04 Thread Treviño

Public bug reported:

Right click on a desktop icon and rename it:
 - The shell will hang and there's no way to recover it

** Affects: gnome-shell-extension-desktop-icons
 Importance: Unknown
 Status: Unknown

** Affects: gnome-shell-extension-desktop-icons (Ubuntu)
 Importance: High
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: In Progress


** Tags: rls-ee-incoming

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

Title:
  Renaming a desktop item causes the shell to hang

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  In Progress

Bug description:
  Right click on a desktop icon and rename it:
   - The shell will hang and there's no way to recover it

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

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

[Desktop-packages] [Bug 1846771] [NEW] gnome-settings-daemon opens /usr/share/zoneinfo/* every 30 seconds or so

Public bug reported:

I've been trying to figure out why my HDD keeps on flushing metadata out
every minute on an idle laptop and discovered that gsd-color opens
/usr/share/zoneinfo/Europe/London on my machine at regular intervals.
This causes the access time (atime) to be updated causing a metadata
flush afterwards. On an idle laptop this makes the HDD spin up, write
data and then spin down again. This consumes power.

Can this periodic open/closing be fixed or at least try to use O_NOATIME
on the opening to reduce the metadata atime updates?

I diagnosed this by running:

sudo fnotifystat -v -x/sys,/proc,/home

one can see that the gsd-color is opening and closing the file.

Looking deeper, I used health-check on gsd-color to gather the attached
activity log of 5 minutes of activity of gsd-color on the idle machine.

To capture the activity I used:

sudo health-check -p gsd-color -d 300 -f -r -v > gnome-gsd-color-
5min.log

I'm pretty sure that opening the zoneinfo file with O_NOATIME will avoid
the metadata atime flushes and because the data has not changed on disk
it should avoid the HDD spinup/spindown cycling. Alternatively, can the
regular zoneinfo reads be avoided to save power?

This seems like an identical bug as: https://launchpad.net/bugs/1846768

** Affects: gnome-settings-daemon (Ubuntu)
 Importance: High
 Status: New

** Attachment added: "capture of gnome-gsd-color activity using heath-check 
tool"
   
https://bugs.launchpad.net/bugs/1846771/+attachment/5294348/+files/gnome-gsd-color-5min.log

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

** Description changed:

  I've been trying to figure out why my HDD keeps on flushing metadata out
- every minute on an idle laptop and discovered that gnome-gsd-color opens
+ every minute on an idle laptop and discovered that gsd-color opens
  /usr/share/zoneinfo/Europe/London on my machine at regular intervals.
  This causes the access time (atime) to be updated causing a metadata
  flush afterwards. On an idle laptop this makes the HDD spin up, write
  data and then spin down again. This consumes power.
  
  Can this periodic open/closing be fixed or at least try to use O_NOATIME
  on the opening to reduce the metadata atime updates?
  
  I diagnosed this by running:
  
  sudo fnotifystat -v -x/sys,/proc,/home
  
- one can see that the gnome-settings-daemon is opening and closing the
- file.
+ one can see that the gsd-color is opening and closing the file.
  
- Looking deeper, I used health-check on gnome-gsd-color to gather the
- attached activity log of 5 minutes of activity of gnome-gsd-color on the
- idle machine.
+ Looking deeper, I used health-check on gsd-color to gather the attached
+ activity log of 5 minutes of activity of gsd-color on the idle machine.
  
  To capture the activity I used:
  
- sudo health-check -p gnome-gsd-color -d 300 -f -r -v > gnome-gsd-color-
+ sudo health-check -p gsd-color -d 300 -f -r -v > gnome-gsd-color-
  5min.log
  
  I'm pretty sure that opening the zoneinfo file with O_NOATIME will avoid
  the metadata atime flushes and because the data has not changed on disk
  it should avoid the HDD spinup/spindown cycling. Alternatively, can the
  regular zoneinfo reads be avoided to save power?
  
  This seems like an identical bug as: https://launchpad.net/bugs/1846768

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

Title:
  gnome-settings-daemon opens /usr/share/zoneinfo/* every 30 seconds or
  so

Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  I've been trying to figure out why my HDD keeps on flushing metadata
  out every minute on an idle laptop and discovered that gsd-color opens
  /usr/share/zoneinfo/Europe/London on my machine at regular intervals.
  This causes the access time (atime) to be updated causing a metadata
  flush afterwards. On an idle laptop this makes the HDD spin up, write
  data and then spin down again. This consumes power.

  Can this periodic open/closing be fixed or at least try to use
  O_NOATIME on the opening to reduce the metadata atime updates?

  I diagnosed this by running:

  sudo fnotifystat -v -x/sys,/proc,/home

  one can see that the gsd-color is opening and closing the file.

  Looking deeper, I used health-check on gsd-color to gather the
  attached activity log of 5 minutes of activity of gsd-color on the
  idle machine.

  To capture the activity I used:

  sudo health-check -p gsd-color -d 300 -f -r -v > gnome-gsd-color-
  5min.log

  I'm pretty sure that opening the zoneinfo file with O_NOATIME will
  avoid the metadata atime flushes and because the data has not changed
  on disk it should avoid the HDD spinup/spindown cycling.
  Alternatively, can the regular zoneinfo reads be avoided to save
  power?

  This seems like an identical bug as:

Re: [Desktop-packages] [Bug 1721424] Re: 17.10 Sound Indicator Applet doesn't "boop" to let me know how loud it is.

2019-10-04 Thread tom

It's inconsistent, so very hard to reproduce, but I've experienced it
intermittently at least up to 19.04. Maybe close it if it's not
reproducible, I'm not sure what is best.

On Fri, Oct 4, 2019, 07:01 Paul White <1721...@bugs.launchpad.net>
wrote:

> We are sorry that we do not always have the capacity to review all
> reported bugs in a timely manner.
>
> Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
> I'm not sure if I'm moving this to the right package but 
>
> Is this still an issue? Unable to reproduce here with Ubuntu 18.04.
>
> Paul White
> [Ubuntu Bug Squad]
>
>
> ** Package changed: ubuntu => gnome-settings-daemon (Ubuntu)
>
> ** Tags added: artful
>
> ** Changed in: gnome-settings-daemon (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1721424
>
> Title:
>   17.10 Sound Indicator Applet doesn't "boop" to let me know how loud it
>   is.
>
> Status in gnome-settings-daemon package in Ubuntu:
>   Incomplete
>
> Bug description:
>   4.13.0-12-generic
>   17.10
>   XPS 9560
>
>   Sound works fine, headphones or speakers. I initially thought it
>   didn't, based on a bug I had experienced days ago in 17.04. I tried
>   closing the lid and re-opening, but it did nothing. Then I watched a
>   YouTube video about how to fix sound, and HEARD SOUND.
>
>   So I realized the little sound indicator square that pops up when u
>   press volume up or volume down just isn't "booping" any sound to give
>   that feedback of the sound level.
>
>   Expected behavior: boops when i press volume up or volume down
>   Happened: no sound upon volume up or down, volume otherwise appears to
> work fine.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1721424/+subscriptions
>

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

Title:
  17.10 Sound Indicator Applet doesn't "boop" to let me know how loud it
  is.

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  4.13.0-12-generic
  17.10
  XPS 9560

  Sound works fine, headphones or speakers. I initially thought it
  didn't, based on a bug I had experienced days ago in 17.04. I tried
  closing the lid and re-opening, but it did nothing. Then I watched a
  YouTube video about how to fix sound, and HEARD SOUND.

  So I realized the little sound indicator square that pops up when u
  press volume up or volume down just isn't "booping" any sound to give
  that feedback of the sound level.

  Expected behavior: boops when i press volume up or volume down
  Happened: no sound upon volume up or down, volume otherwise appears to work 
fine.

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

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

[Desktop-packages] [Bug 1846768] Re: gnome-calendar opens /usr/share/zoneinfo/* every 60 seconds

Oh, actually, it was doing 10 accesses in 300 seconds, so it's polling
every 30 seconds, higher than I first thought.

** Summary changed:

- gnome-calendar opens /usr/share/zoneinfo/* every 60 seconds
+ gnome-calendar opens /usr/share/zoneinfo/* every 30 seconds

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

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

Title:
  gnome-calendar opens /usr/share/zoneinfo/* every 30 seconds

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  I've been trying to figure out why my HDD keeps on flushing metadata
  out every minute on an idle laptop and discovered that gnome-calendar
  opens /usr/share/zoneinfo/Europe/London on my machine every minute.
  This causes the access time (atime) to be updated causing a metadata
  flush afterwards. On an idle laptop this makes the HDD spin up, write
  data and then spin down again.  This consumes power.

  Can this periodic open/closing be fixed or at least try to use
  O_NOATIME on the opening to reduce the metadata atime updates?

  I diagnosed this by running:

  sudo fnotifystat -v -x/sys,/proc,/home

  one can see that the gnome-calendar is opening and closing the file.

  Looking deeper, I used health-check on gnome-calendar to gather the
  attached activity log of 5 minutes of activity of gnome-calendar on
  the idle machine. One can see it sleeps for ~60 seconds on a poll()
  system call and every 60 seconds opens and closes the zoneinfo file.

  To capture the activity I used:

  sudo health-check -p gnome-calendar -d 300 -f -r -v > gnome-calendar-
  5min.log

  I'm pretty sure that opening the zoneinfo file with O_NOATIME will
  avoid the metadata atime flushes and because the data has not changed
  on disk it should avoid the HDD spinup/spindown cycling.
  Alternatively, can the zoneinfo reads be avoided totally every 60
  seconds to save power?

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

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

[Desktop-packages] [Bug 1846768] [NEW] gnome-calendar opens /usr/share/zoneinfo/* every 30 seconds

Public bug reported:

I've been trying to figure out why my HDD keeps on flushing metadata out
every minute on an idle laptop and discovered that gnome-calendar opens
/usr/share/zoneinfo/Europe/London on my machine every minute. This
causes the access time (atime) to be updated causing a metadata flush
afterwards. On an idle laptop this makes the HDD spin up, write data and
then spin down again.  This consumes power.

Can this periodic open/closing be fixed or at least try to use O_NOATIME
on the opening to reduce the metadata atime updates?

I diagnosed this by running:

sudo fnotifystat -v -x/sys,/proc,/home

one can see that the gnome-calendar is opening and closing the file.

Looking deeper, I used health-check on gnome-calendar to gather the
attached activity log of 5 minutes of activity of gnome-calendar on the
idle machine. One can see it sleeps for ~60 seconds on a poll() system
call and every 60 seconds opens and closes the zoneinfo file.

To capture the activity I used:

sudo health-check -p gnome-calendar -d 300 -f -r -v > gnome-calendar-
5min.log

I'm pretty sure that opening the zoneinfo file with O_NOATIME will avoid
the metadata atime flushes and because the data has not changed on disk
it should avoid the HDD spinup/spindown cycling. Alternatively, can the
zoneinfo reads be avoided totally every 60 seconds to save power?

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

** Attachment added: "capture of gnome-calendar activity using heath-check tool"
   
https://bugs.launchpad.net/bugs/1846768/+attachment/5294333/+files/gnome-calendar-5min.log

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

Title:
  gnome-calendar opens /usr/share/zoneinfo/* every 30 seconds

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  I've been trying to figure out why my HDD keeps on flushing metadata
  out every minute on an idle laptop and discovered that gnome-calendar
  opens /usr/share/zoneinfo/Europe/London on my machine every minute.
  This causes the access time (atime) to be updated causing a metadata
  flush afterwards. On an idle laptop this makes the HDD spin up, write
  data and then spin down again.  This consumes power.

  Can this periodic open/closing be fixed or at least try to use
  O_NOATIME on the opening to reduce the metadata atime updates?

  I diagnosed this by running:

  sudo fnotifystat -v -x/sys,/proc,/home

  one can see that the gnome-calendar is opening and closing the file.

  Looking deeper, I used health-check on gnome-calendar to gather the
  attached activity log of 5 minutes of activity of gnome-calendar on
  the idle machine. One can see it sleeps for ~60 seconds on a poll()
  system call and every 60 seconds opens and closes the zoneinfo file.

  To capture the activity I used:

  sudo health-check -p gnome-calendar -d 300 -f -r -v > gnome-calendar-
  5min.log

  I'm pretty sure that opening the zoneinfo file with O_NOATIME will
  avoid the metadata atime flushes and because the data has not changed
  on disk it should avoid the HDD spinup/spindown cycling.
  Alternatively, can the zoneinfo reads be avoided totally every 60
  seconds to save power?

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

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

[Desktop-packages] [Bug 1822351] Re: Nautilus does not open after updating to 19.04

2019-10-04 Thread Doru Costea

Same experience as julo. Also, I have a storage volume I use to mount
manually after boot. If I mount it quickly I have no problems. Sometimes
I get into this bug. And sometimes all starred locations on that volume
disapper. It appears to be a race between me and the tracker.

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

Title:
  Nautilus does not open after updating to 19.04

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  After updating to Ubuntu 19.04 dev branch, nautilus does not open at
  all. Moreover, trying to open nautilus from the terminal does not give
  any error, nor any output at all, and no window opens.

  I don't really know how to report this bug without any terminal
  output.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.32.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 29 13:58:12 2019
  InstallationDate: Installed on 2018-02-23 (398 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1747314] Re: gnome-terminal-server --help does not include option --app-id

** Changed in: ubuntu
   Status: New => Invalid

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

Title:
  gnome-terminal-server --help does not include option --app-id

Status in Ubuntu:
  Invalid
Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Below is the current full usage info, and the option --app-id is
  missing.

  Also, while in that section of the code, please consider adding
  --version option.

  I had to learn of this option via other means.  The reason is when
  gnome-terminal-server crashes it takes down all gnome-terminals that I
  have created in "Startup Applications".

  [The crash appears to be caused by mouse clicking on the minimize icon
  of my ssh session, but I have not enough info to file a bug report on
  that.  Ubuntu 16.04 LTS - GNOME Terminal 3.18.3-1ubuntu1 ]

  [I am filing another bug within minutes, about the app-id option not
  accepting digits after a period.  That bug report will include the
  script I am using.]

  
  STDOUT:

  /usr/lib/gnome-terminal/gnome-terminal-server --help-all
  Usage:
gnome-terminal-server [OPTION...]

  Help Options:
-h, --help   Show help options
--help-all   Show all help options
--help-gtk   Show GTK+ Options

  GTK+ Options
--class=CLASSProgram class as used by the window manager
--name=NAME  Program name as used by the window manager
--gdk-debug=FLAGSGDK debugging flags to set
--gdk-no-debug=FLAGS GDK debugging flags to unset
--gtk-module=MODULES Load additional GTK+ modules
--g-fatal-warnings   Make all warnings fatal
--gtk-debug=FLAGSGTK+ debugging flags to set
--gtk-no-debug=FLAGS GTK+ debugging flags to unset

  Application Options:
--display=DISPLAYX display to 

  
  gnome-terminal --version
  GNOME Terminal 3.18.3
  pete@U16t54:~/bin$ /usr/lib/gnome-terminal-server --version
  bash: /usr/lib/gnome-terminal-server: No such file or directory

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

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

[Desktop-packages] [Bug 1846759] [NEW] Ubuntu's evolution-data-server package incompatible with gnome-calendar package

2019-10-04 Thread Chris Graham

Public bug reported:

On reporting an issue in gnome-calendar, I was told "GNOME Calendar 3.34
requires EDS 3.34 running in the host system.".  Ubuntu has 3.32.

See:

https://gitlab.gnome.org/GNOME/gnome-calendar/issues/464#note_617797

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-calendar 3.32.2-1~ubuntu19.04.1
ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
Uname: Linux 5.0.0-29-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct  4 08:00:32 2019
InstallationDate: Installed on 2019-07-31 (64 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-calendar
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2019-09-22T11:01:00.065291

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


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

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

Title:
  Ubuntu's evolution-data-server package incompatible with gnome-
  calendar package

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  On reporting an issue in gnome-calendar, I was told "GNOME Calendar
  3.34 requires EDS 3.34 running in the host system.".  Ubuntu has 3.32.

  See:

  https://gitlab.gnome.org/GNOME/gnome-calendar/issues/464#note_617797

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-calendar 3.32.2-1~ubuntu19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  4 08:00:32 2019
  InstallationDate: Installed on 2019-07-31 (64 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2019-09-22T11:01:00.065291

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

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

[Desktop-packages] [Bug 1721424] Re: 17.10 Sound Indicator Applet doesn't "boop" to let me know how loud it is.

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner.

Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
I'm not sure if I'm moving this to the right package but 

Is this still an issue? Unable to reproduce here with Ubuntu 18.04.

Paul White
[Ubuntu Bug Squad]


** Package changed: ubuntu => gnome-settings-daemon (Ubuntu)

** Tags added: artful

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

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

Title:
  17.10 Sound Indicator Applet doesn't "boop" to let me know how loud it
  is.

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  4.13.0-12-generic
  17.10
  XPS 9560

  Sound works fine, headphones or speakers. I initially thought it
  didn't, based on a bug I had experienced days ago in 17.04. I tried
  closing the lid and re-opening, but it did nothing. Then I watched a
  YouTube video about how to fix sound, and HEARD SOUND.

  So I realized the little sound indicator square that pops up when u
  press volume up or volume down just isn't "booping" any sound to give
  that feedback of the sound level.

  Expected behavior: boops when i press volume up or volume down
  Happened: no sound upon volume up or down, volume otherwise appears to work 
fine.

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

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

[Desktop-packages] [Bug 1721424] [NEW] 17.10 Sound Indicator Applet doesn't "boop" to let me know how loud it is.

You have been subscribed to a public bug:

4.13.0-12-generic
17.10
XPS 9560

Sound works fine, headphones or speakers. I initially thought it didn't,
based on a bug I had experienced days ago in 17.04. I tried closing the
lid and re-opening, but it did nothing. Then I watched a YouTube video
about how to fix sound, and HEARD SOUND.

So I realized the little sound indicator square that pops up when u
press volume up or volume down just isn't "booping" any sound to give
that feedback of the sound level.

Expected behavior: boops when i press volume up or volume down
Happened: no sound upon volume up or down, volume otherwise appears to work 
fine.

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


** Tags: bot-comment
-- 
17.10 Sound Indicator Applet doesn't "boop" to let me know how loud it is.
https://bugs.launchpad.net/bugs/1721424
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.

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

[Desktop-packages] [Bug 1846742] [NEW] Dock location moves dock to wrong screen

2019-10-04 Thread Jack Micklethwaite

Public bug reported:

When my laptop is on its dock there is an option to select which monitor
has the application dock. Selecting my external monitor moves the dock
to my laptop's built in display and selecting built-in display moves the
dock to my external monitor.


Description:Ubuntu Eoan Ermine (development branch)
Release:19.10

gnome-control-center:
  Installed: 1:3.34.0.1-1ubuntu2

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-control-center 1:3.34.0.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct  4 13:04:00 2019
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2019-10-04 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
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 eoan

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

Title:
  Dock location moves dock to wrong screen

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

Bug description:
  When my laptop is on its dock there is an option to select which
  monitor has the application dock. Selecting my external monitor moves
  the dock to my laptop's built in display and selecting built-in
  display moves the dock to my external monitor.


  Description:  Ubuntu Eoan Ermine (development branch)
  Release:  19.10

  gnome-control-center:
Installed: 1:3.34.0.1-1ubuntu2

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.0.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  4 13:04:00 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-10-04 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
  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/1846742/+subscriptions

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

[Desktop-packages] [Bug 1072199] Re: Alt+Print Screen only takes picture of the HUD

MestreLion, as this issue was fixed over 5 years ago you should open a
new bug report so that *your* log files and those pertaining to Ubuntu
18.04 are attached to the report. By all means refer to this report in
your new report.

Unsubscribing from this one...

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

Title:
  Alt+Print Screen only takes picture of the HUD

Status in One Hundred Papercuts:
  Fix Released
Status in Ubuntu Kylin:
  Fix Released
Status in Unity:
  Fix Released
Status in gnome-screenshot package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  According to Ubuntu Desktop Guide (see attached screenshot of the
  Ubuntu Desktop Guide) pressing "Alt+Print Screen" should take a
  screenshot of a window.

  However when I press "Alt+Print Screen" it always takes the screenshot
  of the launcher and not of the active window.

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

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

[Desktop-packages] [Bug 1846702] Re: wifi

wifi has nothing to do with xorg

** Package changed: xorg (Ubuntu) => 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/1846702

Title:
  wifi

Status in Ubuntu:
  Incomplete

Bug description:
  Bonjour, je ne parvient pas à installer la wifi sur mon ordinateur

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Oct  4 11:44:45 2019
  DistUpgraded: 2019-03-02 13:28:53,256 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:124d]
  InstallationDate: Installed on 2019-01-25 (251 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: ASUSTeK COMPUTER INC. X550CA
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=d60ac68b-590e-48c4-b2a0-9ec3efa253d7 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-03-02 (215 days ago)
  dmi.bios.date: 03/24/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550CA.300:bd03/24/2014:svnASUSTeKCOMPUTERINC.:pnX550CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X550CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  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 Mar  2 11:26:17 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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

[Desktop-packages] [Bug 1846718] [NEW] Pressing and holding the Super key should display numbers [1-9] on the dock icons before pressing any number key

2019-10-04 Thread Amr Ibrahim

Public bug reported:

Currently, this feature is incomplete, pressing and holding the Super
key should display numbers [1-9] on the dock icons before actually
pressing any number key.

Steps to reproduce the bug:
1. Press and hold the Super key
2. Notice that no numbers appear on the dock icons
3. Press 0 (zero) key while still holding the Super key
4. Numbers appear on the dock icons for 2 seconds then disappear
5. Press any number key [1-9] that corresponds to an icon
6. Numbers appear on the dock icons for 2 seconds then disappear and the app 
launches

What should happen:
Numbers should appear on the dock icons while holding the Super key before 
pressing any number key in order to choose which number key to press to launch 
the corresponding app. I believe that's how this feature is supposed to work. 
And that's how it is working in Unity7 in Ubuntu 16.04 LTS.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3
ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: communitheme:ubuntu:GNOME
Date: Fri Oct  4 13:21:32 2019
InstallationDate: Installed on 2018-11-29 (308 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Pressing and holding the Super key should display numbers [1-9] on the
  dock icons before pressing any number key

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

Bug description:
  Currently, this feature is incomplete, pressing and holding the Super
  key should display numbers [1-9] on the dock icons before actually
  pressing any number key.

  Steps to reproduce the bug:
  1. Press and hold the Super key
  2. Notice that no numbers appear on the dock icons
  3. Press 0 (zero) key while still holding the Super key
  4. Numbers appear on the dock icons for 2 seconds then disappear
  5. Press any number key [1-9] that corresponds to an icon
  6. Numbers appear on the dock icons for 2 seconds then disappear and the app 
launches

  What should happen:
  Numbers should appear on the dock icons while holding the Super key before 
pressing any number key in order to choose which number key to press to launch 
the corresponding app. I believe that's how this feature is supposed to work. 
And that's how it is working in Unity7 in Ubuntu 16.04 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Fri Oct  4 13:21:32 2019
  InstallationDate: Installed on 2018-11-29 (308 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1845578] Re: Power indicator doesn't show when charging

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

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

Title:
  Power indicator doesn't show when charging

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This problem is intermittent, I have not found a pattern.

  Sometimes, when I plug my laptop into AC, the battery icon in the top
  right of the screen doesn't show the charging (lightning) symbol.
  Sometimes it stays this way until I restart, sometimes it shows the
  lightning bolt when it increases a % point.

  Description:  Ubuntu 19.04
  Release:  19.04

  apt-cache policy pkgname
  N: Unable to locate package pkgname

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

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

[Desktop-packages] [Bug 1845578] [NEW] Power indicator doesn't show when charging

You have been subscribed to a public bug:

This problem is intermittent, I have not found a pattern.

Sometimes, when I plug my laptop into AC, the battery icon in the top
right of the screen doesn't show the charging (lightning) symbol.
Sometimes it stays this way until I restart, sometimes it shows the
lightning bolt when it increases a % point.

Description:Ubuntu 19.04
Release:19.04

apt-cache policy pkgname
N: Unable to locate package pkgname

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


** Tags: bot-comment disco
-- 
Power indicator doesn't show when charging
https://bugs.launchpad.net/bugs/1845578
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

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

[Desktop-packages] [Bug 1772451]

2019-10-04 Thread Qa-admin-q

Dear vaaydayaasra,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time, it's possible that the bug has
been fixed, or the details of the problem have changed. We'd really
appreciate your help in getting confirmation that the bug is still
present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of
LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not
appropriate in this case)

If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

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

Title:
Diacritical marks become visible only after changing view in Writer

Status in LibreOffice:
Confirmed
Status in libreoffice package in Ubuntu:
Triaged

Bug description:
Arabic is sometimes written with diacritical vowel marks, which are
placed either above or below each letter of the word. Many
multipurpose fonts, which are not designed specifically for Arabic,
place some of these marks in the empty space between lines, outside of
the space reserved for line height. Writing Arabic in LibreOffice
Writer, these marks don't become visible while typing but only after
the page view has changed once.

See the attached series of screenshots, where the first screenshot has
been taken while typing. The first letter of the first word (reading
from right to left) should have two diacritical marks: ء and a
diagonal line above the letter: أَ. Only the lower half of the ء mark
is visible and the diagonal line not at all. The second letter of the
same word has a circle on top of it but only the lower half of it is
visible. Equally so for the third word of the sentence بِبَرْنَامِجِ,
where the last letter of the word has a diagonal line below, but it is
not visible at all. The second screenshot has been taken after I
scrolled the page down by a couple of screens and then scrolled back.
Now all the diacritics are shown as they should. In the third
screenshot I have deleted all of the text I typed but as you can see,
some parts of the diacritics are still visible above the line. If I
scroll down and back, they would disappear. If you want to test it
yourself, the sentence I wrote reads "أَكْتُبُ هُنَا بِبَرْنَامِجِ
لِيبَرْ أُفِيسْ".

As a user, I would expect the diacritics to be visible as soon as I
type them, and for them to be removed from the screen immediately when
I delete the word.

Description: Ubuntu 17.10
Release: 17.10

libreoffice-writer:
Installed: 1:5.4.6-0ubuntu0.17.10.1
Candidate: 1:5.4.6-0ubuntu0.17.10.1
Version table:
*** 1:5.4.6-0ubuntu0.17.10.1 500
500 http://mr.archive.ubuntu.com/ubuntu artful-updates/main amd64
Packages
100 /var/lib/dpkg/status
1:5.4.5-0ubuntu0.17.10.5 500
500 http://security.ubuntu.com/ubuntu artful-security/main amd64
Packages
1:5.4.1-0ubuntu1 500
500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libreoffice-writer 1:5.4.6-0ubuntu0.17.10.1
ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
Uname: Linux 4.13.0-41-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon May 21 16:17:03 2018
InstallationDate: Installed on 2017-02-13 (462 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcEnviron:

[Desktop-packages] [Bug 1845302] Re: cannot click on others opened applications while the "application not responding" dialog is opened

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

** Tags added: bionic

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

Title:
  cannot click on others opened applications while the "application not
  responding" dialog is opened

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I cannot click on others opened applications while the "application
  not responding" dialog is opened in other application.

  To reproduce it:

  1) upload a file of about 80 MB on a web server.
  2) Open it with sublimetext3 through the sublime's SFTP plugin.
  3) Save the file: the application will "freeze" until it finished to upload 
the modified file and the "application not responding" dialog will appear.
  While this dialog is opened, you cannot click on the others applications.

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

  It's a fresh install.

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

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

[Desktop-packages] [Bug 1845163] Re: The cancel button of the paring dialog does not work during pairing a bluetooth keyboard

2019-10-04 Thread Rex Tsai

** Changed in: oem-priority
   Importance: Undecided => High

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

Title:
  The cancel button of the paring dialog does not work during pairing a
  bluetooth keyboard

Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  The cancel button of the paring dialog does not work during pairing a 
bluetooth keyboard.
  The dialog can be cancel via press the "ESC" on the keyboard.
  But, sometimes after around 1 minute, the gnome-control-center is crashed.

  Reproduce steps:
  1. On bluetooth tab in Settings, click a unpaired bluetooth keyboard
  2. When the pairing XXX dialog show up
  3. click the Cancel button (on the top left of the dialog).

  Expected: the Cancel button is work. And, the pairing is canceled normally.
  Actually: the Cancel button does not work. The pairing action can not be 
canceled via the button.

  Ubuntu: 18.04
  gnome-control-center: 1:3.28.2-0ubuntu0.18.04.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1845163/+subscriptions

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

[Desktop-packages] [Bug 1843887] Re: egfault at ... error 6 in libglib-2.0.so

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

** Tags added: disco

** Summary changed:

- egfault at ... error 6 in libglib-2.0.so
+ segfault at ... error 6 in libglib-2.0.so

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

Title:
  segfault at ... error 6 in libglib-2.0.so

Status in glib2.0 package in Ubuntu:
  New

Bug description:

  Ubuntu 19.04

  after waking up I get the following errors. Sometimes the laptop does
  not wake up.  (I expect it to wake up)

  --- BIOS contains WGDS but no WRDS
  --- [ 4695.737914] geoclue[1309]: segfault at 20

  
  this is the dmesg output (only after suspend).

  [ 4690.382631] PM: suspend entry (deep)
  [ 4690.382632] PM: Syncing filesystems ... done.
  [ 4690.641807] rfkill: input handler enabled
  [ 4690.666176] Freezing user space processes ... (elapsed 0.001 seconds) done.
  [ 4690.667819] OOM killer disabled.
  [ 4690.667819] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [ 4690.669009] printk: Suspending console(s) (use no_console_suspend to debug)
  [ 4690.884850] wlp5s0: deauthenticating from 0e:8d:cb:6e:3e:4e by local 
choice (Reason: 3=DEAUTH_LEAVING)
  [ 4691.015894] sd 0:0:0:0: [sda] Synchronizing SCSI cache
  [ 4691.017317] sd 0:0:0:0: [sda] Stopping disk
  [ 4691.420328] ACPI: EC: interrupt blocked
  [ 4691.541129] ACPI: Preparing to enter system sleep state S3
  [ 4691.544137] ACPI: EC: event blocked
  [ 4691.544138] ACPI: EC: EC stopped
  [ 4691.544139] PM: Saving platform NVS memory
  [ 4691.544188] Disabling non-boot CPUs ...
  [ 4691.544807] IRQ 157: no longer affine to CPU1
  [ 4691.545841] smpboot: CPU 1 is now offline
  [ 4691.550093] smpboot: CPU 2 is now offline
  [ 4691.554206] smpboot: CPU 3 is now offline
  [ 4691.558467] smpboot: CPU 4 is now offline
  [ 4691.562523] smpboot: CPU 5 is now offline
  [ 4691.566191] IRQ 128: no longer affine to CPU6
  [ 4691.567207] smpboot: CPU 6 is now offline
  [ 4691.571194] IRQ 125: no longer affine to CPU7
  [ 4691.572245] smpboot: CPU 7 is now offline
  [ 4691.575342] IRQ 124: no longer affine to CPU8
  [ 4691.576453] smpboot: CPU 8 is now offline
  [ 4691.579601] IRQ 23: no longer affine to CPU9
  [ 4691.579606] IRQ 122: no longer affine to CPU9
  [ 4691.580654] smpboot: CPU 9 is now offline
  [ 4691.584036] IRQ 127: no longer affine to CPU10
  [ 4691.584045] IRQ 132: no longer affine to CPU10
  [ 4691.584052] IRQ 152: no longer affine to CPU10
  [ 4691.585080] smpboot: CPU 10 is now offline
  [ 4691.588113] IRQ 123: no longer affine to CPU11
  [ 4691.589175] smpboot: CPU 11 is now offline
  [ 4691.598456] ACPI: Low-level resume complete
  [ 4691.598615] ACPI: EC: EC started
  [ 4691.598616] PM: Restoring platform NVS memory
  [ 4691.604642] Enabling non-boot CPUs ...
  [ 4691.604739] x86: Booting SMP configuration:
  [ 4691.604741] smpboot: Booting Node 0 Processor 1 APIC 0x2
  [ 4691.610214] unchecked MSR access error: WRMSR to 0x10f (tried to write 
0x) at rIP: 0xb9873fc8 (native_write_msr+0x8/0x30)
  [ 4691.610217] Call Trace:
  [ 4691.610228]  intel_pmu_cpu_starting+0x87/0x260
  [ 4691.610235]  ? x86_pmu_dead_cpu+0x30/0x30
  [ 4691.610241]  x86_pmu_starting_cpu+0x1a/0x30
  [ 4691.610247]  cpuhp_invoke_callback+0x99/0x540
  [ 4691.610254]  notify_cpu_starting+0x58/0x70
  [ 4691.610260]  start_secondary+0xed/0x200
  [ 4691.610265]  secondary_startup_64+0xa4/0xb0
  [ 4691.610515]  cache: parent cpu1 should not be sleeping
  [ 4691.610633] intel_pstate: Disabling energy efficiency optimization
  [ 4691.610770] microcode: sig=0x906ea, pf=0x20, revision=0x84
  [ 4691.615411] microcode: updated to revision 0xb4, date = 2019-04-01
  [ 4691.615654] CPU1 is up
  [ 4691.615708] smpboot: Booting Node 0 Processor 2 APIC 0x4
  [ 4691.617138]  cache: parent cpu2 should not be sleeping
  [ 4691.622352] CPU2 is up
  [ 4691.622403] smpboot: Booting Node 0 Processor 3 APIC 0x6
  [ 4691.623838]  cache: parent cpu3 should not be sleeping
  [ 4691.629075] CPU3 is up
  [ 4691.629122] smpboot: Booting Node 0 Processor 4 APIC 0x8
  [ 4691.630557]  cache: parent cpu4 should not be sleeping
  [ 4691.635753] CPU4 is up
  [ 4691.635805] smpboot: Booting Node 0 Processor 5 APIC 0xa
  [ 4691.637241]  cache: parent cpu5 should not be sleeping
  [ 4691.642570] CPU5 is up
  [ 4691.642646] smpboot: Booting Node 0 Processor 6 APIC 0x1
  [ 4691.644329]  cache: parent cpu6 should not be sleeping
  [ 4691.644569] microcode: sig=0x906ea, pf=0x20, revision=0xb4
  [ 4691.645446] CPU6 is up
  [ 4691.645504] smpboot: Booting Node 0 Processor 7 APIC 0x3
  [ 4691.646935]  cache: parent cpu7 should not be sleeping
  [ 4691.647519] CPU7 is up
  [ 4691.647565] smpboot: Booting Node 0 Processor 8 APIC 0x5
  [ 4691.648981]  cache: parent cpu8 should not be sleeping
  [ 4691.649601] CPU8 is up
  [ 4691.649646] smpboot: Booting Node 0 Processor 9 APIC 0x7
  [ 4691.651097]

[Desktop-packages] [Bug 1846692] Re: PCI/internal sound card not detected

2019-10-04 Thread Rex Tsai

** Changed in: alsa-driver (Ubuntu)
 Assignee: (unassigned) => Rex Tsai (chihchun)

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  As discussed with Rex Tsai

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  4 09:43:52 2019
  InstallationDate: Installed on 2019-09-23 (10 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET37W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET37W(1.20):bd09/11/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1846177] Re: 1910 Tap the sensor in the login window

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

** Tags removed: login pad touch
** Tags added: eoan

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

Title:
  1910 Tap the sensor in the login window

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Eoan Ermine (development branch)
  Release:  19.10
  Dell Inspiron 3180 Laptop

  Touch on the sensor does not work in the login window. Pressing works
  only with the buttons on the sensor. It works in the system itself.

  This issue always occurs when the computer starts or when you log out
  of the account.

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

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

[Desktop-packages] [Bug 1841793] Re: Don't update to 2.631

2019-10-04 Thread Jeremy Bicha

Alejandro, this bug is simply a note about early development releases
like 2.61.1 and 2.63.1. The bug is to help the Ubuntu Desktop Team track
out-of-date packages more effectively.

This bug does not have anything to do with updating stable versions of
glibmm which are found in even numbers like 2.58, 2.60, etc.

Ubuntu 19.10 will be released in 2 weeks with glibmm 2.60 available.

** Summary changed:

- Don't update to 2.61.1
+ Don't update to 2.631

** Description changed:

  The .news entry starts with
  
- '2.61.1: (unstable):
+ '2.63.1: (unstable):
  Distro packagers should probably not package this yet.'
  
  Let's follow upstream's advice there

** Tags removed: version-skip-2.61.1
** Tags added: version-skip-2.63.1

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

Title:
  Don't update to 2.631

Status in glibmm2.4 package in Ubuntu:
  Triaged

Bug description:
  The .news entry starts with

  '2.63.1: (unstable):
  Distro packagers should probably not package this yet.'

  Let's follow upstream's advice there

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1841793/+subscriptions

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

[Desktop-packages] [Bug 1843887] [NEW] egfault at ... error 6 in libglib-2.0.so

You have been subscribed to a public bug:


Ubuntu 19.04

after waking up I get the following errors. Sometimes the laptop does
not wake up.  (I expect it to wake up)

--- BIOS contains WGDS but no WRDS
--- [ 4695.737914] geoclue[1309]: segfault at 20


this is the dmesg output (only after suspend).

[ 4690.382631] PM: suspend entry (deep)
[ 4690.382632] PM: Syncing filesystems ... done.
[ 4690.641807] rfkill: input handler enabled
[ 4690.666176] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 4690.667819] OOM killer disabled.
[ 4690.667819] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
[ 4690.669009] printk: Suspending console(s) (use no_console_suspend to debug)
[ 4690.884850] wlp5s0: deauthenticating from 0e:8d:cb:6e:3e:4e by local choice 
(Reason: 3=DEAUTH_LEAVING)
[ 4691.015894] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 4691.017317] sd 0:0:0:0: [sda] Stopping disk
[ 4691.420328] ACPI: EC: interrupt blocked
[ 4691.541129] ACPI: Preparing to enter system sleep state S3
[ 4691.544137] ACPI: EC: event blocked
[ 4691.544138] ACPI: EC: EC stopped
[ 4691.544139] PM: Saving platform NVS memory
[ 4691.544188] Disabling non-boot CPUs ...
[ 4691.544807] IRQ 157: no longer affine to CPU1
[ 4691.545841] smpboot: CPU 1 is now offline
[ 4691.550093] smpboot: CPU 2 is now offline
[ 4691.554206] smpboot: CPU 3 is now offline
[ 4691.558467] smpboot: CPU 4 is now offline
[ 4691.562523] smpboot: CPU 5 is now offline
[ 4691.566191] IRQ 128: no longer affine to CPU6
[ 4691.567207] smpboot: CPU 6 is now offline
[ 4691.571194] IRQ 125: no longer affine to CPU7
[ 4691.572245] smpboot: CPU 7 is now offline
[ 4691.575342] IRQ 124: no longer affine to CPU8
[ 4691.576453] smpboot: CPU 8 is now offline
[ 4691.579601] IRQ 23: no longer affine to CPU9
[ 4691.579606] IRQ 122: no longer affine to CPU9
[ 4691.580654] smpboot: CPU 9 is now offline
[ 4691.584036] IRQ 127: no longer affine to CPU10
[ 4691.584045] IRQ 132: no longer affine to CPU10
[ 4691.584052] IRQ 152: no longer affine to CPU10
[ 4691.585080] smpboot: CPU 10 is now offline
[ 4691.588113] IRQ 123: no longer affine to CPU11
[ 4691.589175] smpboot: CPU 11 is now offline
[ 4691.598456] ACPI: Low-level resume complete
[ 4691.598615] ACPI: EC: EC started
[ 4691.598616] PM: Restoring platform NVS memory
[ 4691.604642] Enabling non-boot CPUs ...
[ 4691.604739] x86: Booting SMP configuration:
[ 4691.604741] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 4691.610214] unchecked MSR access error: WRMSR to 0x10f (tried to write 
0x) at rIP: 0xb9873fc8 (native_write_msr+0x8/0x30)
[ 4691.610217] Call Trace:
[ 4691.610228]  intel_pmu_cpu_starting+0x87/0x260
[ 4691.610235]  ? x86_pmu_dead_cpu+0x30/0x30
[ 4691.610241]  x86_pmu_starting_cpu+0x1a/0x30
[ 4691.610247]  cpuhp_invoke_callback+0x99/0x540
[ 4691.610254]  notify_cpu_starting+0x58/0x70
[ 4691.610260]  start_secondary+0xed/0x200
[ 4691.610265]  secondary_startup_64+0xa4/0xb0
[ 4691.610515]  cache: parent cpu1 should not be sleeping
[ 4691.610633] intel_pstate: Disabling energy efficiency optimization
[ 4691.610770] microcode: sig=0x906ea, pf=0x20, revision=0x84
[ 4691.615411] microcode: updated to revision 0xb4, date = 2019-04-01
[ 4691.615654] CPU1 is up
[ 4691.615708] smpboot: Booting Node 0 Processor 2 APIC 0x4
[ 4691.617138]  cache: parent cpu2 should not be sleeping
[ 4691.622352] CPU2 is up
[ 4691.622403] smpboot: Booting Node 0 Processor 3 APIC 0x6
[ 4691.623838]  cache: parent cpu3 should not be sleeping
[ 4691.629075] CPU3 is up
[ 4691.629122] smpboot: Booting Node 0 Processor 4 APIC 0x8
[ 4691.630557]  cache: parent cpu4 should not be sleeping
[ 4691.635753] CPU4 is up
[ 4691.635805] smpboot: Booting Node 0 Processor 5 APIC 0xa
[ 4691.637241]  cache: parent cpu5 should not be sleeping
[ 4691.642570] CPU5 is up
[ 4691.642646] smpboot: Booting Node 0 Processor 6 APIC 0x1
[ 4691.644329]  cache: parent cpu6 should not be sleeping
[ 4691.644569] microcode: sig=0x906ea, pf=0x20, revision=0xb4
[ 4691.645446] CPU6 is up
[ 4691.645504] smpboot: Booting Node 0 Processor 7 APIC 0x3
[ 4691.646935]  cache: parent cpu7 should not be sleeping
[ 4691.647519] CPU7 is up
[ 4691.647565] smpboot: Booting Node 0 Processor 8 APIC 0x5
[ 4691.648981]  cache: parent cpu8 should not be sleeping
[ 4691.649601] CPU8 is up
[ 4691.649646] smpboot: Booting Node 0 Processor 9 APIC 0x7
[ 4691.651097]  cache: parent cpu9 should not be sleeping
[ 4691.651760] CPU9 is up
[ 4691.651803] smpboot: Booting Node 0 Processor 10 APIC 0x9
[ 4691.653237]  cache: parent cpu10 should not be sleeping
[ 4691.653932] CPU10 is up
[ 4691.653977] smpboot: Booting Node 0 Processor 11 APIC 0xb
[ 4691.655415]  cache: parent cpu11 should not be sleeping
[ 4691.656156] CPU11 is up
[ 4691.690038] ACPI: Waking up from system sleep state S3
[ 4691.697408] ACPI: button: The lid device is not compliant to SW_LID.
[ 4691.701755] ACPI: EC: interrupt unblocked
[ 4691.754868] ACPI: EC: event unblocked
[ 4691.756283] sd

[Desktop-packages] [Bug 1845302] [NEW] cannot click on others opened applications while the "application not responding" dialog is opened

You have been subscribed to a public bug:

I cannot click on others opened applications while the "application not
responding" dialog is opened in other application.

To reproduce it:

1) upload a file of about 80 MB on a web server.
2) Open it with sublimetext3 through the sublime's SFTP plugin.
3) Save the file: the application will "freeze" until it finished to upload the 
modified file and the "application not responding" dialog will appear.
While this dialog is opened, you cannot click on the others applications.

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

It's a fresh install.

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

-- 
cannot click on others opened applications while the "application not 
responding" dialog is opened
https://bugs.launchpad.net/bugs/1845302
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

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

[Desktop-packages] [Bug 1846177] [NEW] 1910 Tap the sensor in the login window

You have been subscribed to a public bug:

Description:Ubuntu Eoan Ermine (development branch)
Release:19.10
Dell Inspiron 3180 Laptop

Touch on the sensor does not work in the login window. Pressing works
only with the buttons on the sensor. It works in the system itself.

This issue always occurs when the computer starts or when you log out of
the account.

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


** Tags: bot-comment login pad touch
-- 
1910 Tap the sensor in the login window
https://bugs.launchpad.net/bugs/1846177
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

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

[Desktop-packages] [Bug 1846371] Re: firefox 70.0 beta 11 isn't fully translated

Launchpad has imported 4 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1586216.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2019-10-04T08:58:26+00:00 Olivier Tilloy wrote:

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0)
Gecko/20100101 Firefox/70.0

Steps to reproduce:

1. Download firefox 70.0 beta 11 (default English locale)
2. Remove ~/.mozilla/firefox folder
3. Unpack and run firefox, observe that the UI is in English as expected
4. Go to about:preferences, "Language" section, search for more languages and 
install the French langpack and make French the default language
5. Restart firefox


Actual results:

Most of the UI elements are localized in French, as expected, but some
are not. The elements that are *not* localized include the
about:preferences page, the "What's New" popover and the "About Firefox"
dialog.


Expected results:

All UI elements should be localized in French, with no exception.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1846371/comments/8


On 2019-10-04T09:01:05+00:00 Olivier Tilloy wrote:

Note that this is a regression in Firefox 70. Firefox 69.0.2 works as
expected in that regard.

Also note that after disabling and enabling again the French language
pack in about:addons, then refreshing the tab with about:preferences, it
is correctly localized in French, and so is the "What's New" popover.
The "About Firefox" dialog remains in English though.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1846371/comments/9


On 2019-10-04T09:02:23+00:00 Olivier Tilloy wrote:

This bug was initially reported against the Firefox Ubuntu beta packages
(https://launchpad.net/bugs/1846371), but it turns out it's not
distribution-specific.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1846371/comments/10


On 2019-10-04T09:17:38+00:00 Release-mgmt-account-bot wrote:

[Bugbug](https://github.com/mozilla/bugbug/) thinks this bug should
belong to this component, but please revert this change in case of
error.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1846371/comments/12


** Changed in: firefox
   Status: Unknown => New

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

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

Title:
  firefox 70.0 beta 11 isn't fully translated

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  (this was initially spotted by ricotz)

  I'm running firefox 70.0~b11+build1-0ubuntu0.19.10.1 from
  ppa:mozillateam/firefox-next with a French locale, and the UI is not
  fully translated to French. The chrome (menu items and address bar
  help text) as well as other parts of the UI (new tab page) are
  correctly translated, but other parts aren't, such as the
  about:preferences settings page. Other about: pages (such as
  about:mozilla or about:robots) are correctly translated. about:addons
  is partially translated.

  Fully translated:
   - menu items
   - address bar
   - about:mozilla
   - about:robots
   - about:compat
   - about:welcome
   - about:newtab
   - about:webrtc

  Partially translated:
   - about:addons

  Not translated:
   - about:preferences
   - about:cache
   - "new extensions won't work in private mode" popover
   - "what's new" popover
   - about firefox dialog

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 70.0~b11+build1-0ubuntu0.19.10.1 [origin: 
LP-PPA-mozillateam-firefox-next]
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BuildID: 20190930191143
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  2 18:27:45 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
  DefaultProfilePrefSources:
   /usr/lib/firefox/defaults/pref/vendor-gre.js
   /usr/lib/firefox/defaults/pref/channel-prefs.js
  DefaultProfilePrefs: network.manage-offline-status: true 
(/usr/lib/firefox/defaults/pref/vendor-gre.js)
  DefaultProfileThemes: extensions.sqlite corrupt or

[Desktop-packages] [Bug 1774242] Re: Wacom touchscreens should use libinput, not wacom driver

paoletto: nothing changed in 18.04, it never got this update

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

Title:
  Wacom touchscreens should use libinput, not wacom driver

Status in xf86-input-wacom package in Ubuntu:
  Fix Released

Bug description:
  /usr/share/X11/xorg.conf.d/70-wacom.conf as shipped, has this:

  Section "InputClass"
  Identifier "Wacom touchscreen class"
  MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
  MatchDevicePath "/dev/input/event*"
  MatchIsTouchscreen "true"
  Driver "wacom"
  EndSection

  The result is that on my Yoga 920, in a plain X11 session (running
  openbox in my case), the touchscreen acts like a broken mouse: there
  is no multi-touch capability in Qt Quick applications, and clicking
  isn't quite right either.  I also verified it with Peter Hutterer's
  old cairo-based mt-touch test program.

  I suspect we will get some users mistakenly writing up Qt bugs about
  this if you don't ship a fix.  (Seems to me that already happened at
  least once, actually.)

  Yes, the touchscreen is made by Wacom, but wacom_drv.so has
  historically been only for Wacom tablets and in-screen stylus
  digitizers, and IMO that continues to be the case.  libinput is a much
  better choice of driver for this hardware (so is evdev for that
  matter), so I changed it to Driver "libinput" and got it working.
  (Wayland uses libinput, so in a wayland session, touch already works
  fine in Qt apps on this hardware.)

  I'm one of the Qt Quick maintainers, most concerned with touch
  handling, and I've also written some of the Qt xcb code for dealing
  with XInput touch and tablet devices.  So if you think that there's
  something wrong with Qt, such that it should still work anyway to use
  a wacom driver for a Wacom touchscreen, let me know.  These AES
  devices are still new to me (that's why I got a Yoga, to try it out).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-input-wacom 1:0.36.1-0ubuntu1 [modified: 
usr/share/X11/xorg.conf.d/70-wacom.conf]
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 30 19:40:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  MachineType: LENOVO 80Y7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=ZFS=rpool/ROOT/ubuntu ro
  SourcePackage: xf86-input-wacom
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5NCN38WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 920-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB:
  dmi.product.family: YOGA 920-13IKB
  dmi.product.name: 80Y7
  dmi.product.version: Lenovo YOGA 920-13IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1774242/+subscriptions

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

[Desktop-packages] [Bug 1774242] Re: Wacom touchscreens should use libinput, not wacom driver

Jason: that's a good suggestion, I'll fix the package to use that
instead

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

Title:
  Wacom touchscreens should use libinput, not wacom driver

Status in xf86-input-wacom package in Ubuntu:
  Fix Released

Bug description:
  /usr/share/X11/xorg.conf.d/70-wacom.conf as shipped, has this:

  Section "InputClass"
  Identifier "Wacom touchscreen class"
  MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
  MatchDevicePath "/dev/input/event*"
  MatchIsTouchscreen "true"
  Driver "wacom"
  EndSection

  The result is that on my Yoga 920, in a plain X11 session (running
  openbox in my case), the touchscreen acts like a broken mouse: there
  is no multi-touch capability in Qt Quick applications, and clicking
  isn't quite right either.  I also verified it with Peter Hutterer's
  old cairo-based mt-touch test program.

  I suspect we will get some users mistakenly writing up Qt bugs about
  this if you don't ship a fix.  (Seems to me that already happened at
  least once, actually.)

  Yes, the touchscreen is made by Wacom, but wacom_drv.so has
  historically been only for Wacom tablets and in-screen stylus
  digitizers, and IMO that continues to be the case.  libinput is a much
  better choice of driver for this hardware (so is evdev for that
  matter), so I changed it to Driver "libinput" and got it working.
  (Wayland uses libinput, so in a wayland session, touch already works
  fine in Qt apps on this hardware.)

  I'm one of the Qt Quick maintainers, most concerned with touch
  handling, and I've also written some of the Qt xcb code for dealing
  with XInput touch and tablet devices.  So if you think that there's
  something wrong with Qt, such that it should still work anyway to use
  a wacom driver for a Wacom touchscreen, let me know.  These AES
  devices are still new to me (that's why I got a Yoga, to try it out).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-input-wacom 1:0.36.1-0ubuntu1 [modified: 
usr/share/X11/xorg.conf.d/70-wacom.conf]
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 30 19:40:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  MachineType: LENOVO 80Y7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=ZFS=rpool/ROOT/ubuntu ro
  SourcePackage: xf86-input-wacom
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5NCN38WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 920-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB:
  dmi.product.family: YOGA 920-13IKB
  dmi.product.name: 80Y7
  dmi.product.version: Lenovo YOGA 920-13IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1774242/+subscriptions

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

[Desktop-packages] [Bug 1774242] Re: Wacom touchscreens should use libinput, not wacom driver

actually, could someone test that before it's pushed to the distro?
Modify 70-wacom.conf, uncomment the touchscreen class(es) and add the
option there.

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

Title:
  Wacom touchscreens should use libinput, not wacom driver

Status in xf86-input-wacom package in Ubuntu:
  Fix Released

Bug description:
  /usr/share/X11/xorg.conf.d/70-wacom.conf as shipped, has this:

  Section "InputClass"
  Identifier "Wacom touchscreen class"
  MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
  MatchDevicePath "/dev/input/event*"
  MatchIsTouchscreen "true"
  Driver "wacom"
  EndSection

  The result is that on my Yoga 920, in a plain X11 session (running
  openbox in my case), the touchscreen acts like a broken mouse: there
  is no multi-touch capability in Qt Quick applications, and clicking
  isn't quite right either.  I also verified it with Peter Hutterer's
  old cairo-based mt-touch test program.

  I suspect we will get some users mistakenly writing up Qt bugs about
  this if you don't ship a fix.  (Seems to me that already happened at
  least once, actually.)

  Yes, the touchscreen is made by Wacom, but wacom_drv.so has
  historically been only for Wacom tablets and in-screen stylus
  digitizers, and IMO that continues to be the case.  libinput is a much
  better choice of driver for this hardware (so is evdev for that
  matter), so I changed it to Driver "libinput" and got it working.
  (Wayland uses libinput, so in a wayland session, touch already works
  fine in Qt apps on this hardware.)

  I'm one of the Qt Quick maintainers, most concerned with touch
  handling, and I've also written some of the Qt xcb code for dealing
  with XInput touch and tablet devices.  So if you think that there's
  something wrong with Qt, such that it should still work anyway to use
  a wacom driver for a Wacom touchscreen, let me know.  These AES
  devices are still new to me (that's why I got a Yoga, to try it out).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-input-wacom 1:0.36.1-0ubuntu1 [modified: 
usr/share/X11/xorg.conf.d/70-wacom.conf]
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 30 19:40:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  MachineType: LENOVO 80Y7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=ZFS=rpool/ROOT/ubuntu ro
  SourcePackage: xf86-input-wacom
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5NCN38WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 920-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB:
  dmi.product.family: YOGA 920-13IKB
  dmi.product.name: 80Y7
  dmi.product.version: Lenovo YOGA 920-13IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1774242/+subscriptions

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

[Desktop-packages] [Bug 293832]

2019-10-04 Thread Johnruth652

Thanks for sharing such a informative blog. It is really helpful for us.
Keep sharing such informative blogs again.

Office Com Setup - https://www.office-com-setup.com/

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

Title:
  printer prints page at wrong position, page cut

Status in Poppler:
  Unknown
Status in brother-cups-wrapper-extra package in Ubuntu:
  Invalid
Status in brother-lpr-drivers-extra package in Ubuntu:
  Invalid
Status in cups package in Ubuntu:
  Invalid
Status in poppler package in Ubuntu:
  Fix Released
Status in brother-cups-wrapper-extra source package in Karmic:
  Invalid
Status in brother-lpr-drivers-extra source package in Karmic:
  Invalid
Status in cups source package in Karmic:
  Invalid
Status in poppler source package in Karmic:
  Won't Fix

Bug description:
  After updating to intrepid, my Brother DCP-7025 printed every page
  about 2 cm above the usual position. This leads to pages cut as if
  printing with wrong paper configuration though A4 paper is set
  everywhere (Cups settings, program settings). For example when
  printing a test page with the printer configuration tool I cannot see
  the upper part of the Ubuntu logo.

  I have used both a hardy and an intrepid live cd to test and found out
  that the problem only occurs using intrepid, so I think it's a problem
  with the intrepid driver packages.

  However I found out, that in the printer configuration tool a wrong
  driver "DCP-7025 BR-Script" is loaded. The correct (and working!)
  driver is "DCP-7025 for CUPS". So to manually solve the problem simply
  choose the correct driver in the tool.

  I think that during the installation process of the package "brother-
  cups-wrapper-laser" the correct driver is not set to be used as
  default driver and the system continues to use the wrong driver
  instead.

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

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

[Desktop-packages] [Bug 1729433] Re: LibreOffice doesn't remember window size when running under Wayland

2019-10-04 Thread J-Paul BERARD

The bug is no more present in this version.
BUT, the behavior is not really the good one : when you unmaximize the window, 
it doesn't come back to the previous size but to a nearly maximum size.

Version: 6.3.2.2
Build ID: 1:6.3.2-0ubuntu1
Ubuntu GNOME WAYLAND 19.10

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

Title:
  LibreOffice doesn't remember window size when running under Wayland

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice package in Fedora:
  Confirmed

Bug description:
  1. Open any LibreOffice document, e.g., a Writer or Calc document.
  2. Make the window a reasonable, non-maximized size.
  3. Maximize the window.
  4. Close LibreOffice.
  5. Open the document again; it will open maximized.
  6. Un-maximize the window.
  7. Observe how the window has a ridiculously small size, not its previously 
unmaximized size.

  LibreOffice or gnome-shell bug? Not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  1 16:21:29 2017
  InstallationDate: Installed on 2017-05-19 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-10-20 (12 days ago)

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

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

[Desktop-packages] [Bug 1843733] Re: fftw3 ftbfs in eoan (armhf only)

2019-10-04 Thread Daniel van Vugt

So far I can't reproduce any crash in the tests on armhf (or aarch64).
But I haven't tried everything yet...

In the meantime, can anyone reproduce the failure and produce a fresh
log? If so, can you verify for me which binary is crashing?

** Changed in: fftw3 (Ubuntu Eoan)
   Status: In Progress => Incomplete

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

Title:
  fftw3 ftbfs in eoan (armhf only)

Status in fftw3 package in Ubuntu:
  Incomplete
Status in fftw3 source package in Eoan:
  Incomplete

Bug description:
  fftw3 ftbfs in eoan (armhf only).

  https://launchpadlibrarian.net/441265031/buildlog_ubuntu-eoan-
  armhf.fftw3_3.3.8-2_BUILDING.txt.gz

  ( cd tests ; /usr/bin/make smallcheck )
  make[1]: Entering directory '/<>/tests'
  perl -w ./check.pl -r -c=1 -v `pwd`/bench
  Executing "/<>/tests/bench --verbose=1   --verify 
'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify 
'//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' 
--verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' 
--verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 
'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304'"
  ok7e10x12bv29 1.71318e-07 1.44516e-06 2.00887e-07
  ik7e10x12bv29 1.66737e-07 1.44901e-06 1.76717e-07
  Segmentation fault (core dumped)
  FAILED /<>/tests/bench:  --verify 'ok7e10x12bv29' --verify 
'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' 
--verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' 
--verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify 
'//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 
'ofc2304' --verify 'ifc2304'
  make[1]: *** [Makefile:723: smallcheck] Error 1
  make[1]: Leaving directory '/<>/tests'

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

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

[Desktop-packages] [Bug 1846461] Re: Disconcerting Folder/Selection flashing when deleting files/folders

** Changed in: nautilus
   Status: Unknown => New

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

Title:
  Disconcerting Folder/Selection flashing when deleting files/folders

Status in Nautilus:
  New
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  When entering a folder in nautilus and deleting a file permanently
  "shift+del" the selection jumps and sometimes even the previous folder
  level is being displayed.

  This is super confusing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct  3 11:06:08 2019
  InstallationDate: Installed on 2018-05-02 (518 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to eoan on 2019-09-29 (3 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1846702] Re: wifi

2019-10-04 Thread Chris Guiver

Thank you for taking the time to report this issue and helping to make
Ubuntu better.

This bug report can be converted to a question (which is aimed at
support). You can also find help with your problem in the support forum
of your local Ubuntu community http://loco.ubuntu.com/ or asking at
https://askubuntu.com or https://ubuntuforums.org, or for more support
options please look at https://discourse.ubuntu.com/t/community-
support/709

The first place I'd for wifi problems is
https://help.ubuntu.com/community/WifiDocs/WirelessTroubleShootingGuide
and if you need help in French/Francais you could try
https://wiki.ubuntu.com/IRC/ChannelList

I've marked this bug incomplete as normal support steps don't appear to
have been tried, or evidence of them hasn't been provided. If you
believe I'm in error, or can provide additional detail of steps done,
please change status back to "New" and leave comment, or additional
information as to what was attempted.

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

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

Title:
  wifi

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Bonjour, je ne parvient pas à installer la wifi sur mon ordinateur

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Oct  4 11:44:45 2019
  DistUpgraded: 2019-03-02 13:28:53,256 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:124d]
  InstallationDate: Installed on 2019-01-25 (251 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: ASUSTeK COMPUTER INC. X550CA
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=d60ac68b-590e-48c4-b2a0-9ec3efa253d7 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-03-02 (215 days ago)
  dmi.bios.date: 03/24/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550CA.300:bd03/24/2014:svnASUSTeKCOMPUTERINC.:pnX550CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X550CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  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 Mar  2 11:26:17 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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

[Desktop-packages] [Bug 1846709] [NEW] pcscd crashed with SIGSEGV in usb_claim_interface()

2019-10-04 Thread Pavel Selivanov

Public bug reported:

iBank token and driver was used

** Affects: pcsc-lite (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  pcscd crashed with SIGSEGV in usb_claim_interface()

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  iBank token and driver was used

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

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

[Desktop-packages] [Bug 1846702] [NEW] wifi

2019-10-04 Thread lacroix

Public bug reported:

Bonjour, je ne parvient pas à installer la wifi sur mon ordinateur

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompositorRunning: None
Date: Fri Oct  4 11:44:45 2019
DistUpgraded: 2019-03-02 13:28:53,256 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
DpkgLog:
 
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller 
[1043:124d]
InstallationDate: Installed on 2019-01-25 (251 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
MachineType: ASUSTeK COMPUTER INC. X550CA
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=d60ac68b-590e-48c4-b2a0-9ec3efa253d7 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2019-03-02 (215 days ago)
dmi.bios.date: 03/24/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X550CA.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X550CA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550CA.300:bd03/24/2014:svnASUSTeKCOMPUTERINC.:pnX550CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X550CA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
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 Mar  2 11:26:17 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   17900 
 vendor AUO
xserver.version: 2:1.18.4-0ubuntu0.8

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  wifi

Status in xorg package in Ubuntu:
  New

Bug description:
  Bonjour, je ne parvient pas à installer la wifi sur mon ordinateur

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Oct  4 11:44:45 2019
  DistUpgraded: 2019-03-02 13:28:53,256 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:124d]
  InstallationDate: Installed on 2019-01-25 (251 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: ASUSTeK COMPUTER INC. X550CA
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=d60ac68b-590e-48c4-b2a0-9ec3efa253d7 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-03-02 (215 days ago)
  dmi.bios.date: 03/24/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550CA.300:bd03/24/2014:svnASUSTeKCOMPUTERINC.:pnX550CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X550CA
  dmi.product.version: 1.0

[Desktop-packages] [Bug 1846699] [NEW] Missing mechanism in Glibmm that prevents the support of some themes (CSS) in Gtkmm

2019-10-04 Thread Alejandro Claro

Public bug reported:

In  GTK+ 3.20 the theming mechanics was heavily changed.

https://developer.gnome.org/gtk3/stable/ch32s10.html

One of the major changes was the use of element names much more than
style classes. For this the function gtk_widget_class_set_css_name() was
added to t he API and used to assign the element names. However, this
was not added in GTKmm, making impossible to assign element names in
custom widget, and no automatically assignment was developed in GTKmm's
Widget class in order to be able to identify widget classes in the
theming system (CSS).

The problem was discussed and tracked up to Glibmm in GNOME bug tracking
system:

https://gitlab.gnome.org/GNOME/gtkmm/issues/17
https://gitlab.gnome.org/GNOME/glibmm/issues/33

The issues are due to the lack of the mechanism to call
gtk_widget_class_set_css_name() function in the instance init function.

This was solved in Glibmm2.4 2.60, however Ubuntu is still behind this
version and it's affecting some of our products.

We have applied a patch to the current version (2.56) of Glibmm2.4 in
Ubuntu 18.04 successfully, but I would like to ask you to consider
upgrading the version of Glibmm in the official repository or apply the
patch.

** Affects: glibmm2.4 (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  In  GTK+ 3.20 the theming mechanics was heavily changed.
  
  https://developer.gnome.org/gtk3/stable/ch32s10.html
  
  One of the major changes was the use of element names much more than
  style classes. For this the function gtk_widget_class_set_css_name() was
  added to t he API and used to assign the element names. However, this
  was not added in GTKmm, making impossible to assign element names in
  custom widget, and no automatically assignment was developed in GTKmm's
  Widget class in order to be able to identify widget classes in the
  theming system (CSS).
  
  The problem was discussed and tracked up to Glibmm in GNOME bug tracking
  system:
  
  https://gitlab.gnome.org/GNOME/gtkmm/issues/17
  https://gitlab.gnome.org/GNOME/glibmm/issues/33
  
  The issues are due to the lack of the mechanism to call
  gtk_widget_class_set_css_name() function in the instance init function.
  
  This was solved in Glibmm2.4 2.60, however Ubuntu is still behind this
  version and it's affecting some of our products.
  
  We have applied a patch to the current version (2.56) of Glibmm2.4 in
- Ubuntu 18.04 successfully, but I would like to ask considered upgrading
- the version of Glibmm in the official repository or apply the patch.
+ Ubuntu 18.04 successfully, but I would like to ask you to consider
+ upgrading the version of Glibmm in the official repository or apply the
+ patch.

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

Title:
  Missing mechanism in Glibmm that prevents the support of some themes
  (CSS) in Gtkmm

Status in glibmm2.4 package in Ubuntu:
  New

Bug description:
  In  GTK+ 3.20 the theming mechanics was heavily changed.

  https://developer.gnome.org/gtk3/stable/ch32s10.html

  One of the major changes was the use of element names much more than
  style classes. For this the function gtk_widget_class_set_css_name()
  was added to t he API and used to assign the element names. However,
  this was not added in GTKmm, making impossible to assign element names
  in custom widget, and no automatically assignment was developed in
  GTKmm's Widget class in order to be able to identify widget classes in
  the theming system (CSS).

  The problem was discussed and tracked up to Glibmm in GNOME bug
  tracking system:

  https://gitlab.gnome.org/GNOME/gtkmm/issues/17
  https://gitlab.gnome.org/GNOME/glibmm/issues/33

  The issues are due to the lack of the mechanism to call
  gtk_widget_class_set_css_name() function in the instance init
  function.

  This was solved in Glibmm2.4 2.60, however Ubuntu is still behind this
  version and it's affecting some of our products.

  We have applied a patch to the current version (2.56) of Glibmm2.4 in
  Ubuntu 18.04 successfully, but I would like to ask you to consider
  upgrading the version of Glibmm in the official repository or apply
  the patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1846699/+subscriptions

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

[Desktop-packages] [Bug 1846371] Re: firefox 70.0 beta 11 isn't fully translated

2019-10-04 Thread Olivier Tilloy

It turns out the problem also affects upstream builds:
https://bugzilla.mozilla.org/show_bug.cgi?id=1586216.

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

** Also affects: firefox via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1586216
   Importance: Unknown
   Status: Unknown

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

Title:
  firefox 70.0 beta 11 isn't fully translated

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  (this was initially spotted by ricotz)

  I'm running firefox 70.0~b11+build1-0ubuntu0.19.10.1 from
  ppa:mozillateam/firefox-next with a French locale, and the UI is not
  fully translated to French. The chrome (menu items and address bar
  help text) as well as other parts of the UI (new tab page) are
  correctly translated, but other parts aren't, such as the
  about:preferences settings page. Other about: pages (such as
  about:mozilla or about:robots) are correctly translated. about:addons
  is partially translated.

  Fully translated:
   - menu items
   - address bar
   - about:mozilla
   - about:robots
   - about:compat
   - about:welcome
   - about:newtab
   - about:webrtc

  Partially translated:
   - about:addons

  Not translated:
   - about:preferences
   - about:cache
   - "new extensions won't work in private mode" popover
   - "what's new" popover
   - about firefox dialog

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 70.0~b11+build1-0ubuntu0.19.10.1 [origin: 
LP-PPA-mozillateam-firefox-next]
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BuildID: 20190930191143
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  2 18:27:45 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
  DefaultProfilePrefSources:
   /usr/lib/firefox/defaults/pref/vendor-gre.js
   /usr/lib/firefox/defaults/pref/channel-prefs.js
  DefaultProfilePrefs: network.manage-offline-status: true 
(/usr/lib/firefox/defaults/pref/vendor-gre.js)
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2018-08-21 (407 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821)
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=70.0/20190930191143 (In use)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to eoan on 2019-06-05 (119 days ago)

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

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

[Desktop-packages] [Bug 1841793] Re: Don't update to 2.61.1

2019-10-04 Thread Alejandro Claro

Good morning Sebastien,

can you please describe why is it a problem to upgrade Glibmm?

We are affected by an issue in the current version (2.58). After some
changes in GTK+ theme mechanisms in order to be able to configure the
CSS class names properly it is important to be able to call
gtk_widget_class_set_css_name() in the object instance init function.

However, this was not possible until Glibmm team add the support to this
in version 2.60. Without these change there is no way to solve the
problem. The discussion about this can be found in GNOME issue tracking:

https://gitlab.gnome.org/GNOME/glibmm/issues/33
https://gitlab.gnome.org/GNOME/gtkmm/issues/17


** Bug watch added: gitlab.gnome.org/GNOME/glibmm/issues #33
   https://gitlab.gnome.org/GNOME/glibmm/issues/33

** Bug watch added: gitlab.gnome.org/GNOME/gtkmm/issues #17
   https://gitlab.gnome.org/GNOME/gtkmm/issues/17

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

Title:
  Don't update to 2.61.1

Status in glibmm2.4 package in Ubuntu:
  Triaged

Bug description:
  The .news entry starts with

  '2.61.1: (unstable):
  Distro packagers should probably not package this yet.'

  Let's follow upstream's advice there

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1841793/+subscriptions

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

[Desktop-packages] [Bug 1846692] [NEW] PCI/internal sound card not detected

2019-10-04 Thread Lech Sandecki

Public bug reported:

As discussed with Rex Tsai

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
Uname: Linux 5.0.0-29-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct  4 09:43:52 2019
InstallationDate: Installed on 2019-09-23 (10 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/11/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET37W (1.20 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET37W(1.20):bd09/11/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDCTO1WW
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  As discussed with Rex Tsai

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  4 09:43:52 2019
  InstallationDate: Installed on 2019-09-23 (10 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET37W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET37W(1.20):bd09/11/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1846371] Re: firefox 70.0 beta 11 isn't fully translated

2019-10-04 Thread Olivier Tilloy

The contents of the langpack xpi are not to blame. I replaced the one
installed by firefox-locale-fr by the upstream one downloaded from
https://addons.mozilla.org/firefox/downloads/file/3417333/francais_language_pack-70.0buildid20191002212950-fx.xpi,
and the issue persists.

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

Title:
  firefox 70.0 beta 11 isn't fully translated

Status in firefox package in Ubuntu:
  Triaged

Bug description:
  (this was initially spotted by ricotz)

  I'm running firefox 70.0~b11+build1-0ubuntu0.19.10.1 from
  ppa:mozillateam/firefox-next with a French locale, and the UI is not
  fully translated to French. The chrome (menu items and address bar
  help text) as well as other parts of the UI (new tab page) are
  correctly translated, but other parts aren't, such as the
  about:preferences settings page. Other about: pages (such as
  about:mozilla or about:robots) are correctly translated. about:addons
  is partially translated.

  Fully translated:
   - menu items
   - address bar
   - about:mozilla
   - about:robots
   - about:compat
   - about:welcome
   - about:newtab
   - about:webrtc

  Partially translated:
   - about:addons

  Not translated:
   - about:preferences
   - about:cache
   - "new extensions won't work in private mode" popover
   - "what's new" popover
   - about firefox dialog

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 70.0~b11+build1-0ubuntu0.19.10.1 [origin: 
LP-PPA-mozillateam-firefox-next]
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BuildID: 20190930191143
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  2 18:27:45 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
  DefaultProfilePrefSources:
   /usr/lib/firefox/defaults/pref/vendor-gre.js
   /usr/lib/firefox/defaults/pref/channel-prefs.js
  DefaultProfilePrefs: network.manage-offline-status: true 
(/usr/lib/firefox/defaults/pref/vendor-gre.js)
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2018-08-21 (407 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821)
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=70.0/20190930191143 (In use)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to eoan on 2019-06-05 (119 days ago)

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

-- 
Mailing list: https://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 1514474] Re: package tex-common 6.04... Safe legit patch?

2019-10-04 Thread Domren2

Hi,

The answer :

"You received this bug notification because you are subscribed to a
duplicate bug report (1703980).
https://bugs.launchpad.net/bugs/1514474;

Unsubscribe ?

Good day ...

Le 02/10/2019 à 11:40, ian a écrit :
> Strangers to me too.
> Snow
-- 
Dominique Renaudin
http://domren.free.fr

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  Fix Released

Bug description:
  dist-upgrade from wily to xenial

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu4
  Architecture: amd64
  Date: Mon Nov  9 09:56:09 2015
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2011-07-12 (1580 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.3ubuntu1
   apt  1.0.10.2ubuntu1
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2011-12-23 (1416 days ago)

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

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

[Desktop-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation

2019-10-04 Thread Daniel van Vugt

Curious. I was looking at preparing a fix for Ubuntu 18.04 but in my
initial setup for backporting have found that I can't reproduce the bug
with Gnome 3.28. Though this is now with Nvidia driver 430.50 too.

Is anyone seeing this bug in Ubuntu 18.04? If so then please tell me
what Nvidia driver you are using.

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

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

Title:
  [nvidia] Corrupted wallpaper after resuming from suspend or
  hibernation

Status in GNOME Shell:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Incomplete
Status in mutter source package in Disco:
  In Progress
Status in mutter source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  The Nvidia (Xorg) driver corrupts the desktop wallpaper (by design
  (1)) upon resuming from suspend. This creates a poor user experience
  and gives the impression of severe memory corruption.

  (1)
  
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt

  [Test Case]

  0. Set up an Nvidia-only system using the proprietary Nvidia Xorg driver.
  1. Suspend and resume the machine.
  Expect: The wallpaper still looks like it did before suspending.

  [Regression Potential]

  Low. The exact same patch is in Gnome 3.34 (Ubuntu 19.10) already and
  has been used for a couple of months without issue.

  [Original Report]

  https://trello.com/c/i5hENxSO

  Every other wake from sleep presents a corrupted screen with no unlock
  app.  There's a dock and system menu on a black background with pixel
  garbage.  Some personal information in the dock's large window
  thumbnails.  Bitmap garbage flashes on the screen when interacting
  with anything.  Only workaround is doing another sleep-wake cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:4b:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 20 22:19:29 2018
  DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-11-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-12-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162]
  InstallationDate: Installed on 2018-10-28 (54 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic 
root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F24
  dmi.board.asset.tag: Default string
  dmi.board.name: X99P-SLI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz

[Desktop-packages] [Bug 1828491] Re: gnome-calendar not listed as a calendar app in default app settings

** Changed in: gnome-calendar
   Status: New => Fix Released

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

Title:
  gnome-calendar not listed as a calendar app in default app settings

Status in GNOME Calendar:
  Fix Released
Status in gnome-calendar package in Ubuntu:
  Triaged

Bug description:
  Gnome-Calendar doesn't appear in the list of default apps for calendar
  in gnome settings. This is probably due to the fact that, in the
  .desktop file, the "text/calendar" mime type is not registered?

  Anyway, a workaround exists: just type "gio mime text/calendar
  org.gnome.Calendar.desktop".

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

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

[Desktop-packages] [Bug 1827328] Re: ModemManager does not honor blacklisted ttys (ID_MM_DEVICE_IGNORE)