[Desktop-packages] [Bug 1918308] Re: Upgrading liblibreoffice-java pulls openjdk/jre on ISOs

2021-03-13 Thread Launchpad Bug Tracker
This bug was fixed in the package libreoffice - 1:7.1.2~rc1-0ubuntu1

---
libreoffice (1:7.1.2~rc1-0ubuntu1) hirsute; urgency=medium

  * New upstream release candidate

  * Disable JunitTest_dbaccess_complex on armhf for junit autopkgtests
  * Demote liblibreoffice-java from Recommends to Suggests of ure
(LP: #1918308)

libreoffice (1:7.1.2~rc1-1) experimental; urgency=medium

  * New upstream release candidate

  * debian/tests/control.in: make uicheck-sw depend on -draw, the AutoRedact
dialog test apparently needs it (hangs otherwise)
  * debian/rules:
- build with -Wno-psabi on armel/armhf to suppress long obsolete
  warnings

 -- Rico Tzschichholz   Fri, 12 Mar 2021 10:31:16
+0100

** Changed in: libreoffice (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Upgrading liblibreoffice-java pulls openjdk/jre on ISOs

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Upgrading liblibreoffice-java (7.0.4 -> 7.1.1) in hirsute drags in the
  ure-jave/jdk/jre.

  Build log:
  
https://launchpadlibrarian.net/527002812/buildlog_ubuntu_hirsute_amd64_ubuntu_BUILDING.txt.gz

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

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


[Desktop-packages] [Bug 1909496] Re: [i915] Blinking unlock screen

2021-03-13 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [i915] Blinking unlock screen

Status in linux package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired

Bug description:
  Hello,
  I am facing this issue since the upgrade of Ubuntu to Ubuntu 20.04.1 LTS. The 
issue still persists even after re-installing Ubuntu 20.04.1 LTS.

  Due to inactivity the system goes to the Suspend mode. On restoring from the 
suspend mode the login screen appears but it starts to blink continuously 
making it impossible to use the system.
  The only option is to force restart the system.

  Please let me know if this is an already known issue/bug and if there
  is a solution available for the same.

  Thank You

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 28 19:21:12 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0793]
  InstallationDate: Installed on 2020-12-27 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Vostro 15-3568
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=44a1973f-ce3f-46bb-ab72-156c1d047556 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.08.00
  dmi.board.name: 05HRPP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 15-3568
  dmi.product.sku: 0793
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-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/linux/+bug/1909496/+subscriptions

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


[Desktop-packages] [Bug 1909496] Re: [i915] Blinking unlock screen

2021-03-13 Thread Launchpad Bug Tracker
[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [i915] Blinking unlock screen

Status in linux package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired

Bug description:
  Hello,
  I am facing this issue since the upgrade of Ubuntu to Ubuntu 20.04.1 LTS. The 
issue still persists even after re-installing Ubuntu 20.04.1 LTS.

  Due to inactivity the system goes to the Suspend mode. On restoring from the 
suspend mode the login screen appears but it starts to blink continuously 
making it impossible to use the system.
  The only option is to force restart the system.

  Please let me know if this is an already known issue/bug and if there
  is a solution available for the same.

  Thank You

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 28 19:21:12 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0793]
  InstallationDate: Installed on 2020-12-27 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Vostro 15-3568
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=44a1973f-ce3f-46bb-ab72-156c1d047556 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.08.00
  dmi.board.name: 05HRPP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 15-3568
  dmi.product.sku: 0793
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-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/linux/+bug/1909496/+subscriptions

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


[Desktop-packages] [Bug 1919048] Re: the Geometry doesn't correct in brother MFC-T4500DW

2021-03-13 Thread ezequiel merecias
** Tags added: scan

** Tags removed: scan
** Tags added: brother

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

Title:
  the Geometry doesn't correct in brother MFC-T4500DW

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Installing brscan4 the options for Scan Brother MFC-T4500DW
  using scanimage -h I have only the next options

  Geometry:
  -l 0..293mm (in steps of 0.008) [0]
  Top-left x position of scan area.
  -t 0..420mm (in steps of 0.008) [0]
  Top-left y position of scan area.
  -x 0..293mm (in steps of 0.008) [292.973]
  Width of scan-area.
  -y 0..420mm (in steps of 0.008) [415.962]
  Height of scan-area.

  But the ADF and the Plane should to have maximum paper 293mmx430mm

  Where is the problem and how to solve it?

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

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


[Desktop-packages] [Bug 1696250] Re: Please hide Start Center and Math

2021-03-13 Thread Gunnar Hjalmarsson
The decision to hide the LO startcenter launcher was recently questioned
in a thread at the ubuntu-devel-discuss mailing list:

https://lists.ubuntu.com/archives/ubuntu-devel-
discuss/2021-March/018966.html

I too would like that launcher become visible again. It's not only about
the visual impression in the "Start Applications" view, but the
technique for hiding the LO startcenter launcher prevents you from
having it among the "Favorites" in the Dock. Myself was in the habit of
replacing the Writer/Impress/Calc icons in the Dock with the startcenter
one.

Also, as pointed out in comment #12 above, there are use cases where the
LO startcenter plays a role on its own merits.

Debian didn't hide it, btw. While they hid Math, they chose to keep
startcenter visible.

Please consider to drop hide-startcenter-desktop-file.patch.

** Changed in: libreoffice (Ubuntu)
   Status: Fix Released => Triaged

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

Title:
  Please hide Start Center and Math

Status in libreoffice package in Ubuntu:
  Triaged
Status in libreoffice package in Debian:
  Won't Fix

Bug description:
  From GNOME Shell, open the Applications Overview and click the Show
  Applications button to see the list of apps. Currently, LibreOffice
  takes up a whole row on my computer (6 icons) which seems excessive
  with GNOME Shell's current design.

  I suggest that we do like Fedora and hide the LibreOffice Start Center
  and LibreOffice Math.

  Instead of opening a Start Center, it makes more sense for a user to
  just open the app they want directly.

  I don't think users want to create a mathematical formula just to
  create one, but to insert into a document so it makes more sense to
  start Math from within the other app.

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

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


[Desktop-packages] [Bug 1919008] Re: 'Extract here' for .zip files not working as intended.

2021-03-13 Thread Paul White
Excellent. I'n un-subscribing now. Someone else will take a look and
help you further.

** Changed in: file-roller (Ubuntu)
   Status: Incomplete => New

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

Title:
  'Extract here' for .zip files not working as intended.

Status in file-roller package in Ubuntu:
  New

Bug description:
  Repro steps:

  1. Download a .zip file.
  2. Right-click on it and select 'Extract here'.

  Note that my .zip file had one sub-folder and that sub-folder had many
  other sub-folders and files. Size ~ 240 MB

  Expected behavior: A sub-folder should be extracted with size ~240 MB.

  Actual behavior: A sub-folder was extracted, but its size was zero. No
  sub-folders or files in it.

  This has happened multiple times with me over the past few weeks.
  Opening the .zip file and dragging and dropping the files works for
  the time being.

  If it helps, the zip file I am mentioning here was downloaded from Google 
Drive.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-10 (123 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  Package: file-roller 3.36.3-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-11-11 (122 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1919048] [NEW] the Geometry doesn't correct in brother MFC-T4500DW

2021-03-13 Thread ezequiel merecias
Public bug reported:

Installing brscan4 the options for Scan Brother MFC-T4500DW
using scanimage -h I have only the next options

Geometry:
-l 0..293mm (in steps of 0.008) [0]
Top-left x position of scan area.
-t 0..420mm (in steps of 0.008) [0]
Top-left y position of scan area.
-x 0..293mm (in steps of 0.008) [292.973]
Width of scan-area.
-y 0..420mm (in steps of 0.008) [415.962]
Height of scan-area.

But the ADF and the Plane should to have maximum paper 293mmx430mm

Where is the problem and how to solve it?

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  the Geometry doesn't correct in brother MFC-T4500DW

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Installing brscan4 the options for Scan Brother MFC-T4500DW
  using scanimage -h I have only the next options

  Geometry:
  -l 0..293mm (in steps of 0.008) [0]
  Top-left x position of scan area.
  -t 0..420mm (in steps of 0.008) [0]
  Top-left y position of scan area.
  -x 0..293mm (in steps of 0.008) [292.973]
  Width of scan-area.
  -y 0..420mm (in steps of 0.008) [415.962]
  Height of scan-area.

  But the ADF and the Plane should to have maximum paper 293mmx430mm

  Where is the problem and how to solve it?

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

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


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

2021-03-13 Thread Jalansh Munshi
apport information

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

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

Title:
  'Extract here' for .zip files not working as intended.

Status in file-roller package in Ubuntu:
  Incomplete

Bug description:
  Repro steps:

  1. Download a .zip file.
  2. Right-click on it and select 'Extract here'.

  Note that my .zip file had one sub-folder and that sub-folder had many
  other sub-folders and files. Size ~ 240 MB

  Expected behavior: A sub-folder should be extracted with size ~240 MB.

  Actual behavior: A sub-folder was extracted, but its size was zero. No
  sub-folders or files in it.

  This has happened multiple times with me over the past few weeks.
  Opening the .zip file and dragging and dropping the files works for
  the time being.

  If it helps, the zip file I am mentioning here was downloaded from Google 
Drive.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-10 (123 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  Package: file-roller 3.36.3-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-11-11 (122 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1919008] Re: 'Extract here' for .zip files not working as intended.

2021-03-13 Thread Jalansh Munshi
Done! Please let me know if there's anything else I need to do.

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

Title:
  'Extract here' for .zip files not working as intended.

Status in file-roller package in Ubuntu:
  Incomplete

Bug description:
  Repro steps:

  1. Download a .zip file.
  2. Right-click on it and select 'Extract here'.

  Note that my .zip file had one sub-folder and that sub-folder had many
  other sub-folders and files. Size ~ 240 MB

  Expected behavior: A sub-folder should be extracted with size ~240 MB.

  Actual behavior: A sub-folder was extracted, but its size was zero. No
  sub-folders or files in it.

  This has happened multiple times with me over the past few weeks.
  Opening the .zip file and dragging and dropping the files works for
  the time being.

  If it helps, the zip file I am mentioning here was downloaded from Google 
Drive.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-10 (123 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  Package: file-roller 3.36.3-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-11-11 (122 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1919008] Re: 'Extract here' for .zip files not working as intended.

2021-03-13 Thread Jalansh Munshi
apport information

** Tags added: apport-collected

** Description changed:

  Repro steps:
  
  1. Download a .zip file.
  2. Right-click on it and select 'Extract here'.
  
  Note that my .zip file had one sub-folder and that sub-folder had many
  other sub-folders and files. Size ~ 240 MB
  
  Expected behavior: A sub-folder should be extracted with size ~240 MB.
  
  Actual behavior: A sub-folder was extracted, but its size was zero. No
  sub-folders or files in it.
  
  This has happened multiple times with me over the past few weeks.
  Opening the .zip file and dragging and dropping the files works for the
  time being.
  
- If it helps, the zip file I am mentioning here was downloaded from
- Google Drive.
+ If it helps, the zip file I am mentioning here was downloaded from Google 
Drive.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.16
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-11-10 (123 days ago)
+ InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
+ Package: file-roller 3.36.3-0ubuntu1
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
+ Tags:  focal
+ Uname: Linux 5.4.0-66-generic x86_64
+ UpgradeStatus: Upgraded to focal on 2020-11-11 (122 days ago)
+ UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1919008/+attachment/5476328/+files/Dependencies.txt

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

Title:
  'Extract here' for .zip files not working as intended.

Status in file-roller package in Ubuntu:
  Incomplete

Bug description:
  Repro steps:

  1. Download a .zip file.
  2. Right-click on it and select 'Extract here'.

  Note that my .zip file had one sub-folder and that sub-folder had many
  other sub-folders and files. Size ~ 240 MB

  Expected behavior: A sub-folder should be extracted with size ~240 MB.

  Actual behavior: A sub-folder was extracted, but its size was zero. No
  sub-folders or files in it.

  This has happened multiple times with me over the past few weeks.
  Opening the .zip file and dragging and dropping the files works for
  the time being.

  If it helps, the zip file I am mentioning here was downloaded from Google 
Drive.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-11-10 (123 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  Package: file-roller 3.36.3-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-11-11 (122 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1891079] Re: Issues Encountered installing lirc on new 20.04 device

2021-03-13 Thread Bug Watch Updater
** Changed in: lirc (Debian)
   Status: New => Fix Released

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

Title:
  Issues Encountered installing lirc on new 20.04 device

Status in lirc package in Ubuntu:
  New
Status in lirc package in Debian:
  Fix Released

Bug description:
  ** The first issue: Missing module and Deprecated syntax

  While installing lirc:

  If I run at the command line: sudo apt install lirc, it installs
  lirc version 0.10.1-6.1ubuntu1.1 successfully.

  However, when I run "sudo lirc-setup", I get the following dump;

  -
  
/usr/lib/x86_64-linux-gnu/python3.8/site-packages/lirc-setup/mvc_control.py:13: 
PyGIWarning: Gtk was imported without specifying a v
  ersion first. Use gi.require_version('Gtk', '3.0') before import to ensure 
that the right version gets loaded.
from gi.repository import Gtk # pylint: disable=no-name-in-module
  /usr/lib/x86_64-linux-gnu/python3.8/site-packages/lirc-setup/mvc_view.py:14: 
PyGIWarning: Vte was imported without specifying a vers
  ion first. Use gi.require_version('Vte', '2.91') before import to ensure that 
the right version gets loaded.
from gi.repository import Vte # pylint: disable=no-name-in-module
  /usr/lib/python3/dist-packages/lirc/database.py:135: YAMLLoadWarning: calling 
yaml.load() without Loader=... is deprecated, as the d
  efault Loader is unsafe. Please read https://msg.pyyaml.org/load for full 
details.
cf = yaml.load(f.read())
  /usr/lib/python3/dist-packages/lirc/database.py:69: YAMLLoadWarning: calling 
yaml.load() without Loader=... is deprecated, as the de
  fault Loader is unsafe. Please read https://msg.pyyaml.org/load for full 
details.
cf = yaml.load(f.read())
  /usr/lib/python3/dist-packages/lirc/database.py:142: YAMLLoadWarning: calling 
yaml.load() without Loader=... is deprecated, as the d
  efault Loader is unsafe. Please read https://msg.pyyaml.org/load for full 
details.
cf = yaml.load(f.read())
  /usr/lib/python3/dist-packages/lirc/database.py:161: YAMLLoadWarning: calling 
yaml.load() without Loader=... is deprecated, as the d
  efault Loader is unsafe. Please read https://msg.pyyaml.org/load for full 
details.
cf = yaml.load(f.read())
  jwb@richese:~$ sudo lirc-setup
  [sudo] password for jwb:
  
/usr/lib/x86_64-linux-gnu/python3.8/site-packages/lirc-setup/mvc_control.py:13: 
PyGIWarning: Gtk was imported without specifying a v
  ersion first. Use gi.require_version('Gtk', '3.0') before import to ensure 
that the right version gets loaded.
from gi.repository import Gtk # pylint: disable=no-name-in-module
  Traceback (most recent call last):
File "/usr/bin/lirc-setup", line 16, in 
  import mvc_control
File 
"/usr/lib/x86_64-linux-gnu/python3.8/site-packages/lirc-setup/mvc_control.py", 
line 16, in 
  import choosers
File 
"/usr/lib/x86_64-linux-gnu/python3.8/site-packages/lirc-setup/choosers.py", 
line 11, in 
  import mvc_model
File 
"/usr/lib/x86_64-linux-gnu/python3.8/site-packages/lirc-setup/mvc_model.py", 
line 14, in 
  from lirc.database import Database
File "/usr/lib/python3/dist-packages/lirc/__init__.py", line 7, in 
  from .client import get_default_lircrc_path
File "/usr/lib/python3/dist-packages/lirc/client.py", line 38, in 
  import _client
  ModuleNotFoundError: No module named '_client'
  -

  The last line "ModuleNotFoundError: No module named '_client'" is
  apparently the same as was found in 18.04 and previously reported.

  Note: I only installed from the binary package and did not install any
  related source package.

  The "deprecated calls" also will need addressing, but this is not
  required immediately.

  ** Mis-located Document
 :PROPERTIES:
 :ID:   a39c9ba0-7bfe-4ea9-8354-a67519473250
 :END:

  See the attached screenshot of the message from lirc-setup when trying
  to verify some of the online documentation. The installed document is
  not in the location the source code expects, so only the warning message is 
displayed.

  I have completed the install and configuration of lirc manually, but I
  feel these issues should be resolved to simplify use of lirc by
  others.

  John

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

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


[Desktop-packages] [Bug 1813441] Re: Can no longer drag and drop files between desktop and applications

2021-03-13 Thread Jonathan Kamens
I want to thank you from the bottom of my heart for taking time out of
what I'm sure is a very busy schedule to educate poor little me, who is
so ignorant that I've only been working on open source and commercial
software for over 30 years and using Linux since the early days of
Slackware and at one point had submitted more Linux bug reports to Red
Hat than literally any other account in bugzilla, about what a "show-
stopper" bug is. Truly, I am enlightened.

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

Title:
  Can no longer drag and drop files between desktop and applications

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

Bug description:
  In releases before 19.04, you could drag and drop files from the
  desktop into applications.

  This no longer works.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-desktop-icons 19.01-1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 26 21:47:14 2019
  InstallationDate: Installed on 2019-01-02 (24 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago)

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

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


[Desktop-packages] [Bug 1919008] Re: 'Extract here' for .zip files not working as intended.

2021-03-13 Thread Paul White
Assuming that it's Ubuntu you're using and not a flavour I've assigned
the bug to file-roller.

Try running
  
  apport-collect 1919008

in a terminal and see what data gets added to the bug report. I

** Tags added: focal

** Package changed: ubuntu => file-roller (Ubuntu)

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

Title:
  'Extract here' for .zip files not working as intended.

Status in file-roller package in Ubuntu:
  Incomplete

Bug description:
  Repro steps:

  1. Download a .zip file.
  2. Right-click on it and select 'Extract here'.

  Note that my .zip file had one sub-folder and that sub-folder had many
  other sub-folders and files. Size ~ 240 MB

  Expected behavior: A sub-folder should be extracted with size ~240 MB.

  Actual behavior: A sub-folder was extracted, but its size was zero. No
  sub-folders or files in it.

  This has happened multiple times with me over the past few weeks.
  Opening the .zip file and dragging and dropping the files works for
  the time being.

  If it helps, the zip file I am mentioning here was downloaded from
  Google Drive.

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

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


[Desktop-packages] [Bug 1919008] [NEW] 'Extract here' for .zip files not working as intended.

2021-03-13 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Repro steps:

1. Download a .zip file.
2. Right-click on it and select 'Extract here'.

Note that my .zip file had one sub-folder and that sub-folder had many
other sub-folders and files. Size ~ 240 MB

Expected behavior: A sub-folder should be extracted with size ~240 MB.

Actual behavior: A sub-folder was extracted, but its size was zero. No
sub-folders or files in it.

This has happened multiple times with me over the past few weeks.
Opening the .zip file and dragging and dropping the files works for the
time being.

If it helps, the zip file I am mentioning here was downloaded from
Google Drive.

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


** Tags: focal
-- 
'Extract here' for .zip files not working as intended.
https://bugs.launchpad.net/bugs/1919008
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to file-roller 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 1813441] Re: Can no longer drag and drop files between desktop and applications

2021-03-13 Thread Vladislav K. Valtchev
@dundir Maybe you're right, I don't know.
I just tried to do what I believed is best for Ubuntu, the distro I've been 
using since 2008 or so: to speak out giving my feedback, hoping it will be 
heard by the right people. If things won't change I'll look elsewhere, clearly.

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

Title:
  Can no longer drag and drop files between desktop and applications

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

Bug description:
  In releases before 19.04, you could drag and drop files from the
  desktop into applications.

  This no longer works.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-desktop-icons 19.01-1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 26 21:47:14 2019
  InstallationDate: Installed on 2019-01-02 (24 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago)

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

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


[Desktop-packages] [Bug 1919043] Re: gnome-software-dev misses dependencies required for development

2021-03-13 Thread Olivier Tilloy
Which version of Ubuntu? If it's 20.04, that would be bug #1914868
(which you reported yourself).

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

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

Title:
  gnome-software-dev misses dependencies required for development

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  Installing package gnome-software-dev doesn't satisfy all of
  dependencies needed for development.

  After installing it there are still missing libraries needed for
  compilation of basic examples provided by gnome
  (https://developer.gnome.org/gnome-software/stable/plugins.html - the
  first example from here)

  ```
  ~/plugin$ gcc -shared -o libgs_plugin_example.so gs-plugin-example.c -fPIC  
`pkg-config --libs --cflags gnome-software`  
-DI_KNOW_THE_GNOME_SOFTWARE_API_IS_SUBJECT_TO_CHANGE &&  sudo cp 
libgs_plugin_example.so `pkg-config gnome-software --variable=plugindir`
  Package json-glib-1.0 was not found in the pkg-config search path.
  Perhaps you should add the directory containing `json-glib-1.0.pc'
  to the PKG_CONFIG_PATH environment variable
  Package 'json-glib-1.0', required by 'gnome-software', not found
  gs-plugin-example.c:5:10: fatal error: gnome-software.h: No such file or 
directory
  5 | #include 
|  ^~
  compilation terminated.
  ```

  As a reference list of packages required by Fedora version of this
  package could is worth checking: https://fedora.pkgs.org/33/fedora-
  updates-x86_64/gnome-software-devel-3.38.1-1.fc33.x86_64.rpm.html

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

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


[Desktop-packages] [Bug 1919043] [NEW] gnome-software-dev misses dependencies required for development

2021-03-13 Thread Paweł
Public bug reported:

Installing package gnome-software-dev doesn't satisfy all of
dependencies needed for development.

After installing it there are still missing libraries needed for
compilation of basic examples provided by gnome
(https://developer.gnome.org/gnome-software/stable/plugins.html - the
first example from here)

```
~/plugin$ gcc -shared -o libgs_plugin_example.so gs-plugin-example.c -fPIC  
`pkg-config --libs --cflags gnome-software`  
-DI_KNOW_THE_GNOME_SOFTWARE_API_IS_SUBJECT_TO_CHANGE &&  sudo cp 
libgs_plugin_example.so `pkg-config gnome-software --variable=plugindir`
Package json-glib-1.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `json-glib-1.0.pc'
to the PKG_CONFIG_PATH environment variable
Package 'json-glib-1.0', required by 'gnome-software', not found
gs-plugin-example.c:5:10: fatal error: gnome-software.h: No such file or 
directory
5 | #include 
  |  ^~
compilation terminated.
```

As a reference list of packages required by Fedora version of this
package could is worth checking: https://fedora.pkgs.org/33/fedora-
updates-x86_64/gnome-software-devel-3.38.1-1.fc33.x86_64.rpm.html

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

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

Title:
  gnome-software-dev misses dependencies required for development

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Installing package gnome-software-dev doesn't satisfy all of
  dependencies needed for development.

  After installing it there are still missing libraries needed for
  compilation of basic examples provided by gnome
  (https://developer.gnome.org/gnome-software/stable/plugins.html - the
  first example from here)

  ```
  ~/plugin$ gcc -shared -o libgs_plugin_example.so gs-plugin-example.c -fPIC  
`pkg-config --libs --cflags gnome-software`  
-DI_KNOW_THE_GNOME_SOFTWARE_API_IS_SUBJECT_TO_CHANGE &&  sudo cp 
libgs_plugin_example.so `pkg-config gnome-software --variable=plugindir`
  Package json-glib-1.0 was not found in the pkg-config search path.
  Perhaps you should add the directory containing `json-glib-1.0.pc'
  to the PKG_CONFIG_PATH environment variable
  Package 'json-glib-1.0', required by 'gnome-software', not found
  gs-plugin-example.c:5:10: fatal error: gnome-software.h: No such file or 
directory
  5 | #include 
|  ^~
  compilation terminated.
  ```

  As a reference list of packages required by Fedora version of this
  package could is worth checking: https://fedora.pkgs.org/33/fedora-
  updates-x86_64/gnome-software-devel-3.38.1-1.fc33.x86_64.rpm.html

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

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


[Desktop-packages] [Bug 1816674] Re: Update-mime-database is getting very slow during apps installation

2021-03-13 Thread yurx cherio
This has been a disk muncher for over a year now. The way I know the
update is running through mime database is I hear my disks going into
grinding mode.

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

Title:
  Update-mime-database is getting very slow during apps installation

Status in shared-mime-info package in Ubuntu:
  Confirmed

Bug description:
  The installation of some apps has become very slow due to the update-
  mime-database command that takes up a lot of time.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: shared-mime-info 1.10-1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 19 22:37:53 2019
  InstallationDate: Installed on 2019-01-16 (34 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: shared-mime-info
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1816674/+subscriptions

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


[Desktop-packages] [Bug 1846334] Re: cupsd assert failure: free(): invalid pointer

2021-03-13 Thread rew
I'm also seeing this on a samsung printer

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

Title:
  cupsd assert failure: free(): invalid pointer

Status in cups package in Ubuntu:
  Fix Committed

Bug description:
  Just running in the background, no user action (printing)

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: cups-daemon 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-16.17-generic 5.3.1
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AssertionMessage: free(): invalid pointer
  Date: Tue Oct  1 19:41:35 2019
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2019-02-09 (234 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  Lpstat:
   device for HP_LaserJet_CM1415fn_44A808_: 
implicitclass://HP_LaserJet_CM1415fn_44A808_/
   device for Samsung_C48x_Series_SEC84251900EE44_: 
implicitclass://Samsung_C48x_Series_SEC84251900EE44_/
  MachineType: Dell Inc. Latitude E6530
  Papersize: letter
  PpdFiles:
   HP_LaserJet_CM1415fn_44A808_: LaserJet CM1415fn - IPP Everywhere
   Samsung_C48x_Series_SEC84251900EE44_: C48x Series - IPP Everywhere
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic 
root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic 
root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f923ecb83a5 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7f923ecb652a "free(): invalid pointer") at 
malloc.c:5332
   _int_free (av=, p=, have_lock=0) at 
malloc.c:4173
   ?? () from /lib/x86_64-linux-gnu/libcups.so.2
   ippDelete () from /lib/x86_64-linux-gnu/libcups.so.2
  Title: cupsd assert failure: free(): invalid pointer
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A22
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.sku: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  separator:

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

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


[Desktop-packages] [Bug 1915181] Re: cups crashes with SIGABRT every other printing attempt

2021-03-13 Thread rew
I'm also seeing this on a samsung printer

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

Title:
  cups crashes with SIGABRT every other printing attempt

Status in cups package in Ubuntu:
  New

Bug description:
  Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480
  printer (was automatically detected and set up on installation of the
  system).

  Every other attempt to print fails with a varying message depending on
  the printing app (eg. on libreoffice write, "Cannot start printer").
  Waiting a few minutes and retrying prints successfully.

  Looking at cups.service journal messages while attempting to print, it
  looks like the second printing attempt crashes cupsd

  cupsd[]: free(): invalid pointer
  systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: cups.service: Failed with result core-dump

  The service then proceeds to restart after a few seconds, and trying
  to print again succeeds. Trying to print once more thereafter triggers
  the issue again.

  Cuspd's error_log shows nothing happening around the crash (it does
  show some "org.freedesktop.ColorManager.AlreadyExists" error messages
  on restart, but I figured this would be normal, I can see the same
  message on other machines that have no printing issues).

  This is a pretty standard (and recent) ubuntu install, with not much
  customized; in particular no apport custom config was made, and
  nothing was configured on cups side or ubuntu print settings,
  everything is set up as it was autodetected on install.

  The same printer works flawlessly on a different computer using Arch
  and cups 2.3.3 as well (albeit without any ubuntu patches, obviously).

  ---

  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2021-01-28 (12 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  KernLog:
  Lpstat:
   device for Samsung_C48x_Series_SEC842519933D78_: 
implicitclass://Samsung_C48x_Series_SEC842519933D78_/
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA
  Package: cups 2.3.3-3ubuntu1
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd'] failed with exit code 
2: grep: /etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd: Permission 
denied
  ProcCmdline: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash resume=/dev/mapper/vgubuntu-root 
resume_offset=6731776
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash resume=/dev/mapper/vgubuntu-root 
resume_offset=6731776
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RebootRequiredPkgs: linux-image-5.8.0-43-generic linux-base
  Tags: groovy
  Uname: Linux 5.8.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: 
True

  dmi.bios.date: 09/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX434DA_UM433DA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX434DA
  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.:bvrUX434DA_UM433DA.302:bd09/05/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnZenBookUX434DA_UM433DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX434DA_UM433DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

-- 
Mailing list: https://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 1813441] Re: Can no longer drag and drop files between desktop and applications

2021-03-13 Thread dundir
Vlad, honestly, I don't see this getting fixed anytime soon, this has 
been an issue since a late revision of 18.10/19.04 (~2018).

Pinning is a time-tested solution for regressions but it does come with 
overhead, especially when the issue is actually a dependency of a core 
system component (nautilus).

It would have been better if Canonical could have gotten in front of the 
issue when it was first fresh (before the broken expectations). Its 
always better to under-promise expectations than to over-promise. At 
this point, not meeting expectations, and the failure to act has people 
looking for alternatives (myself included).

At this point I don't think the feedback canonical is getting regarding 
changes is working in a way that can let them do better.

N.


On 3/13/21 9:34 AM, Jonathan Kamens wrote:

> Claiming that Ubuntu could simply have stuck with the previous version
> of GNOME when shipping the LTS release is failing to see the forest for
> the trees. Many factors go into the decision of what version of a
> critical package like GNOME to put in a release. Ubuntu looked at all of
> those factors and made the decision they did. Unless you were involved
> in that discussion or have done an analysis similar to theirs, you are
> in no position to second-guess their decision; you simply are not
> considering even a small fraction of the information they considered
> when making it.
>
> Desktop Icons NG was around when 20.04 shipped, though it probably
> wasn't complete, tested, or stable enough to ship with an LTS release.
> There have been significant changes since 20.04 shipped.
>

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

Title:
  Can no longer drag and drop files between desktop and applications

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

Bug description:
  In releases before 19.04, you could drag and drop files from the
  desktop into applications.

  This no longer works.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-desktop-icons 19.01-1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 26 21:47:14 2019
  InstallationDate: Installed on 2019-01-02 (24 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago)

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

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


[Desktop-packages] [Bug 1813441] Re: Can no longer drag and drop files between desktop and applications

2021-03-13 Thread Vladislav K. Valtchev
You're failing to understand the concept of "show-stopper" bug, also known as 
"ship-stopper".
The severity of such a bug is so big, that the whole release a product must be 
postponed, until the bug is fixed. Bugs of this kind are ones that 
substantially compromise the usability of a product. For example, a bug in a 
browser's rendering engine that doesn't allow a single major website (social 
networks, search engines etc.) to render correctly. Millions of people won't 
use that browser because of that. Another example? A GCC bug that doesn't allow 
the Linux kernel to compile or, even worse, compiles but generates incorrect 
instructions and the kernel doesn't boot. Even if that C compiler had a TON of 
new and cool features and it was 200% faster than its predecessor, would you 
allow it to be released knowing the you cannot compile Linux? I wouldn't, never.

Most of the time, we make trade-offs, both in software development and in 
release management as well. For example? We've fixed 100 bugs at the price of 
introducing 5 new ones. That's fine, generally. BUT, some bugs are critical and 
cannot even be put in the equation. I don't need the whole "decision tree" for 
that. Such bugs, have priority above everything else combined. The 10,000 new 
features of KDE 4 were worthless, compared to the fact that it was not stable 
and crashed the whole time. I wanted so much to use it at the time, because it 
was so cool and visually pleasing. But, at the end I gave up because of its 
instability and switched to GNOME.
A car is *worthless* if its breaking system doesn't work. A compromise can be 
made when the breaking system is relatively worse than the one in the previous 
model, but it's still working, it's still doing an acceptable job.

So, how to decide which bugs are show-stoppers? Well, there are user
experience people, product managers, VPs etc, but ultimately, such a
decision is SUBJECTIVE. I have no "mathematical proof" that this was a
show-stopper bug, neither do you that this wasn't. I expressed my
opinion, trying to make the Ubuntu leadership to reconsider such
decision making. Maybe I failed, maybe I didn't. But if nobody makes
criticism, it's almost impossible for the leadership to get a feedback
and improve its decision-making. At the end, given users' feedback, I
hope Ubuntu leaders will ask themselves: "was that the right call to
make?". Maybe, just maybe, the next time they'll be more conservative
when releasing an LTS.

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

Title:
  Can no longer drag and drop files between desktop and applications

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

Bug description:
  In releases before 19.04, you could drag and drop files from the
  desktop into applications.

  This no longer works.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-desktop-icons 19.01-1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 26 21:47:14 2019
  InstallationDate: Installed on 2019-01-02 (24 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago)

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

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


[Desktop-packages] [Bug 1813441] Re: Can no longer drag and drop files between desktop and applications

2021-03-13 Thread Jonathan Kamens
Claiming that Ubuntu could simply have stuck with the previous version
of GNOME when shipping the LTS release is failing to see the forest for
the trees. Many factors go into the decision of what version of a
critical package like GNOME to put in a release. Ubuntu looked at all of
those factors and made the decision they did. Unless you were involved
in that discussion or have done an analysis similar to theirs, you are
in no position to second-guess their decision; you simply are not
considering even a small fraction of the information they considered
when making it.

Desktop Icons NG was around when 20.04 shipped, though it probably
wasn't complete, tested, or stable enough to ship with an LTS release.
There have been significant changes since 20.04 shipped.

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

Title:
  Can no longer drag and drop files between desktop and applications

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

Bug description:
  In releases before 19.04, you could drag and drop files from the
  desktop into applications.

  This no longer works.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-desktop-icons 19.01-1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 26 21:47:14 2019
  InstallationDate: Installed on 2019-01-02 (24 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago)

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

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


[Desktop-packages] [Bug 1813441] Re: Can no longer drag and drop files between desktop and applications

2021-03-13 Thread Vladislav K. Valtchev
Hi Jonathan,

I'm happy to start a dialogue about this issue.

1. It's great to hear that the problem will be fixed in 21.04. Maybe a
backport to the 20.04 LTS should be considered as well?

2. I know, I don't have problems with fixing things by myself, per se.
I'm irritated that this was not a "corner case" that a few will people
will even notice. It's a "show stopper" bug. I'm criticizing the
*decision making* here.

3. Yes, I realize that's GNOME's fault. So, the solution was to simply
stick to the older version of GNOME, wasn't it? It's a BAD idea to
upgrade to the latest version of XYZ, when it's broken, in particular
when we're talking about an LTS release, that's supposed to be super-
stable. That's simply *bad judgement*. Of course Canonical cannot fix
every GNOME bug, I totally agree. I'm a very practical person. Just,
don't upgrade the package; it's simple as that. A Linux distribution
maintainers' main job is choose carefully which version each software
package to include in the distro. The typical questions are: "is the
package XYZ stable enough for our release?", "shall we use libxyz 1.23
instead of libxyz 1.22 to fix the problem PR123, but risking to break
something else?".

Also, did "desktop-icons-ng-ding" exist in 2020 before the release of
the LTS? Not a rhetorical question, I honestly don't know. If it did,
than the LTS should have included it. Otherwise, the LTS should have
just used the older version of GNOME. No matter how you put it, no
technical reason justifies breaking this way the user interface. Again,
if it were something affecting < 1% of the users, I would have
understood. But not in this case. It's not a glitch hidden somewhere,
it's one of the first things people notice after installing Ubuntu. I
noticed it in a matter of minutes. It's *NOT* a problem of resources,
it's a decision-making problem.

Vlad

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

Title:
  Can no longer drag and drop files between desktop and applications

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

Bug description:
  In releases before 19.04, you could drag and drop files from the
  desktop into applications.

  This no longer works.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-desktop-icons 19.01-1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 26 21:47:14 2019
  InstallationDate: Installed on 2019-01-02 (24 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago)

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

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


[Desktop-packages] [Bug 1813441] Re: Can no longer drag and drop files between desktop and applications

2021-03-13 Thread Jonathan Kamens
Three notes:

1. Ubuntu has addressed this in 21.04 by shipping gnome-shell-extension-
desktop-icons-ng by default.

2. Note that you can fix this yourself in any earlier version of Ubuntu
by installing that extension directly from extensions.gnome.org (
https://extensions.gnome.org/extension/2087/desktop-icons-ng-ding/ ) and
disabling the older version shipped with Ubuntu.

3. This is GNOME's fault, not Ubuntu's fault, so bitching at Ubuntu
about it is not helpful or useful. It's not practical for Ubuntu to keep
using obsolete versions of GNOME when the GNOME developers introduce
regressions like this, and it's not feasible for Ubuntu to fix all of
the regressions that the GNOME developers introduce.

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

Title:
  Can no longer drag and drop files between desktop and applications

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

Bug description:
  In releases before 19.04, you could drag and drop files from the
  desktop into applications.

  This no longer works.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-desktop-icons 19.01-1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 26 21:47:14 2019
  InstallationDate: Installed on 2019-01-02 (24 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago)

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

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


[Desktop-packages] [Bug 1918725] Re: Ubuntu 21.04 QA Test - Nautilus Crashed during live session

2021-03-13 Thread Bernard Stafford
** Description changed:

- During live OS testing Nautilus crashed during the opening of the live 
desktop.
- Apport started and info could not be sent. 
+ During live OS testing Nautilus crashed during the opening of the live 
desktop.Daily Build 2021-03-11
+ Apport started and info could not be sent.
  Had a warning: Nautilus is old and out of date.
  I restarted Apport for this bug report.
+ Daily Build 2021-03-13 Nautilus crashed apport gathered information and is 
identical on this bug report. Except no warning as above.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: nautilus 1:3.38.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.460
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 11 19:06:23 2021
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true'
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210311)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
-  evince3.39.2-1
-  file-roller   3.38.0-1
-  nautilus-extension-gnome-terminal 3.38.1-1ubuntu1
-  nautilus-share0.7.3-2ubuntu3
+  evince3.39.2-1
+  file-roller   3.38.0-1
+  nautilus-extension-gnome-terminal 3.38.1-1ubuntu1
+  nautilus-share0.7.3-2ubuntu3

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

Title:
  Ubuntu 21.04 QA Test - Nautilus Crashed during live session

Status in nautilus package in Ubuntu:
  New

Bug description:
  During live OS testing Nautilus crashed during the opening of the live 
desktop.Daily Build 2021-03-11
  Apport started and info could not be sent.
  Had a warning: Nautilus is old and out of date.
  I restarted Apport for this bug report.
  Daily Build 2021-03-13 Nautilus crashed apport gathered information and is 
identical on this bug report. Except no warning as above.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: nautilus 1:3.38.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.460
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 11 19:06:23 2021
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true'
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210311)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   evince3.39.2-1
   file-roller   3.38.0-1
   nautilus-extension-gnome-terminal 3.38.1-1ubuntu1
   nautilus-share0.7.3-2ubuntu3

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

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


[Desktop-packages] [Bug 1919031] [NEW] It is a bug It seems to happens when gnome-shell-extension-appindicator is updated from 33-1 to 33.1-0ubuntu0.20.04.1. Please file a bug report from the Ubuntu t

2021-03-13 Thread volkert Ros
Public bug reported:


It is a bug

It seems to happens when gnome-shell-extension-appindicator is updated
from 33-1 to 33.1-0ubuntu0.20.04.1.

Please file a bug report from the Ubuntu terminal:

ubuntu-bug gnome-shell-extension-appindicator

or add yourself as "This bug affects you" to an existing bug report.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell-extension-appindicator 33.1-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 13 16:36:57 2021
InstallationDate: Installed on 2020-11-09 (123 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-appindicator
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
   It is a bug  It seems to happens when gnome-shell-extension-
  appindicator is updated from 33-1 to 33.1-0ubuntu0.20.04.1.  Please
  file a bug report from the Ubuntu terminal:  ubuntu-bug gnome-shell-
  extension-appindicator  or add yourself as "This bug affects you" to
  an existing bug report.

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

Bug description:
  
  It is a bug

  It seems to happens when gnome-shell-extension-appindicator is updated
  from 33-1 to 33.1-0ubuntu0.20.04.1.

  Please file a bug report from the Ubuntu terminal:

  ubuntu-bug gnome-shell-extension-appindicator

  or add yourself as "This bug affects you" to an existing bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-appindicator 33.1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 13 16:36:57 2021
  InstallationDate: Installed on 2020-11-09 (123 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-appindicator
  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-appindicator/+bug/1919031/+subscriptions

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


[Desktop-packages] [Bug 1918055] Re: blurry resolution after resume on second screen

2021-03-13 Thread Maximilian Hausmann
** Attachment added: "xrandafter.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918055/+attachment/5476260/+files/xrandafter.txt

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

Title:
  blurry resolution after resume on second screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have connected a second screen to my laptop. After resume, sometimes
  the resolution on this screen is blurry and the open windows don't fit
  to the screen in fullscreen mode (they are bigger). Maybe a wrong
  resolution.

  1)
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  3)
  I expected to happen that the resolution is correct.

  4)
  The resolution isn't correct and blurry.

  Reconnection of the external display solves the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-06-12 (635 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1918055] Re: blurry resolution after resume on second screen

2021-03-13 Thread Maximilian Hausmann
** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918055/+attachment/5476262/+files/lspci.txt

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

Title:
  blurry resolution after resume on second screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have connected a second screen to my laptop. After resume, sometimes
  the resolution on this screen is blurry and the open windows don't fit
  to the screen in fullscreen mode (they are bigger). Maybe a wrong
  resolution.

  1)
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  3)
  I expected to happen that the resolution is correct.

  4)
  The resolution isn't correct and blurry.

  Reconnection of the external display solves the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-06-12 (635 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1918055] Re: blurry resolution after resume on second screen

2021-03-13 Thread Maximilian Hausmann
** Attachment added: "journalafter.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918055/+attachment/5476261/+files/journalafter.txt

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

Title:
  blurry resolution after resume on second screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have connected a second screen to my laptop. After resume, sometimes
  the resolution on this screen is blurry and the open windows don't fit
  to the screen in fullscreen mode (they are bigger). Maybe a wrong
  resolution.

  1)
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  3)
  I expected to happen that the resolution is correct.

  4)
  The resolution isn't correct and blurry.

  Reconnection of the external display solves the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-06-12 (635 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1918055] Re: blurry resolution after resume on second screen

2021-03-13 Thread Maximilian Hausmann
** Attachment added: "xrandrbefore.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918055/+attachment/5476258/+files/xrandrbefore.txt

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

Title:
  blurry resolution after resume on second screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have connected a second screen to my laptop. After resume, sometimes
  the resolution on this screen is blurry and the open windows don't fit
  to the screen in fullscreen mode (they are bigger). Maybe a wrong
  resolution.

  1)
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  3)
  I expected to happen that the resolution is correct.

  4)
  The resolution isn't correct and blurry.

  Reconnection of the external display solves the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-06-12 (635 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1918055] Re: blurry resolution after resume on second screen

2021-03-13 Thread Maximilian Hausmann
** Attachment added: "journalbefore.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918055/+attachment/5476259/+files/journalbefore.txt

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

Title:
  blurry resolution after resume on second screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have connected a second screen to my laptop. After resume, sometimes
  the resolution on this screen is blurry and the open windows don't fit
  to the screen in fullscreen mode (they are bigger). Maybe a wrong
  resolution.

  1)
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  3)
  I expected to happen that the resolution is correct.

  4)
  The resolution isn't correct and blurry.

  Reconnection of the external display solves the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-06-12 (635 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1918055] Re: blurry resolution after resume on second screen

2021-03-13 Thread Maximilian Hausmann
It happened again. But unfortunately I forgot before suspending to run
the commands. So I did it vice-versa. *after.txt-Files were created
during the blurry resolution and *before.txt-Files before going to
suspend with correct resolution.

I also attached a screenshot with the resolution settings, because I think that 
the system
does not set the settings correctly. Instead of 1920x1080@60 it sets 
1920x1080i@30 (see screenshot). I think thats the reason for the blurry image.

Maybe it helps. If not, I will try to set some trigger to run the commands 
automatically
before and after suspend.


** Attachment added: "Screenshot with wrong resolution"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918055/+attachment/5476257/+files/Screenshot%20from%202021-03-13%2011-44-02.png

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

Title:
  blurry resolution after resume on second screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have connected a second screen to my laptop. After resume, sometimes
  the resolution on this screen is blurry and the open windows don't fit
  to the screen in fullscreen mode (they are bigger). Maybe a wrong
  resolution.

  1)
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  3)
  I expected to happen that the resolution is correct.

  4)
  The resolution isn't correct and blurry.

  Reconnection of the external display solves the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-06-12 (635 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1906267] Re: IntelHD audio not detected after upgrading to Ubuntu 20.10

2021-03-13 Thread Mark Fraser
If that workaround has fixed the problem (I'm waiting a while to make
sure) do I mark it as a duplicate of that bug?

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

Title:
  IntelHD audio not detected after upgrading to Ubuntu 20.10

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Kubuntu 20.10, from 20.04 occasionally when I turn
  my computer on the sound card doesn't work. If I load Pulse Audio
  Volume Control and disable and then re-enable the audio controller
  (Family 17h (Models 00h-0fh) HD Audio Controller it will work again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Nov 30 15:19:50 2020
  InstallationDate: Installed on 2020-03-21 (254 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago)
  dmi.bios.date: 12/09/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.90
  dmi.board.name: B450M Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=e53f97b3-d450-45b0-be09-5c7f0e17b18d
  InstallationDate: Installed on 2020-03-21 (254 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic 
root=UUID=d29e468f-8ce0-494e-9de4-c9cb9211b09e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-29-generic N/A
   linux-backports-modules-5.8.0-29-generic  N/A
   linux-firmware1.190.1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  groovy
  Uname: Linux 5.8.0-29-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/09/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.90
  dmi.board.name: B450M Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=e53f97b3-d450-45b0-be09-5c7f0e17b18d
  InstallationDate: Installed on 2020-03-21 (254 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic 
root=UUID=d29e468f-8ce0-494e-9de4-c9cb9211b09e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 

Re: [Desktop-packages] [Bug 1916877] Re: Bluetooth sound card not detected

2021-03-13 Thread zaf
*** This bug is a duplicate of bug 1875259 ***
https://bugs.launchpad.net/bugs/1875259

Good morning,
Sound works when I connect bluetooth speaker but no sound on headphones and
speaker of computer. Still dummy output.
If you have any suggestion, please let me know.

Daniel van Vugt <1916...@bugs.launchpad.net>, 8 Mar 2021 Pzt, 03:35
tarihinde şunu yazdı:

> This sounds like bug 1897965, which might now be affecting 20.04.2.
> Please try the suggestions in bug 1897965.
>
> ** Changed in: alsa-driver (Ubuntu)
>Status: New => Incomplete
>
> ** Package changed: alsa-driver (Ubuntu) => pulseaudio (Ubuntu)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1916877
>
> Title:
>   Bluetooth sound card not detected
>
> Status in pulseaudio package in Ubuntu:
>   Incomplete
>
> Bug description:
>   "Dummy output" is on audio volume setting and there is no sound
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: alsa-base 1.0.25+dfsg-0ubuntu5
>   ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
>   Uname: Linux 5.8.0-44-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.16
>   Architecture: amd64
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
> '/dev/snd/controlC0', '/dev/snd/hwC0D1', '/dev/snd/seq', '/dev/snd/timer']
> failed with exit code 1:
>   CasperMD5CheckResult: skip
>   CurrentDesktop: KDE
>   Date: Thu Feb 25 06:06:58 2021
>   InstallationDate: Installed on 2021-02-24 (0 days ago)
>   InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
> (20210209.1)
>   PackageArchitecture: all
>   SourcePackage: alsa-driver
>   Symptom: audio
>   Title: Bluetooth sound card not detected
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 07/11/2007
>   dmi.bios.release: 5.2
>   dmi.bios.vendor: Phoenix Technologies LTD
>   dmi.bios.version: R0052N7
>   dmi.board.asset.tag: N/A
>   dmi.board.name: VAIO
>   dmi.board.vendor: Sony Corporation
>   dmi.board.version: N/A
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Sony Corporation
>   dmi.chassis.version: N/A
>   dmi.ec.firmware.release: 5.2
>   dmi.modalias:
> dmi:bvnPhoenixTechnologiesLTD:bvrR0052N7:bd07/11/2007:br5.2:efr5.2:svnSonyCorporation:pnVGN-TZ150N:pvrJ002NHLG:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
>   dmi.product.family: N/A
>   dmi.product.name: VGN-TZ150N
>   dmi.product.sku: N/A
>   dmi.product.version: J002NHLG
>   dmi.sys.vendor: Sony Corporation
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1916877/+subscriptions
>

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

Title:
  [Sony VGN-TZ150N] Bluetooth sound card not detected

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  "Dummy output" is on audio volume setting and there is no sound

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D1', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Thu Feb 25 06:06:58 2021
  InstallationDate: Installed on 2021-02-24 (0 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2007
  dmi.bios.release: 5.2
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R0052N7
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 5.2
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR0052N7:bd07/11/2007:br5.2:efr5.2:svnSonyCorporation:pnVGN-TZ150N:pvrJ002NHLG:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: N/A
  dmi.product.name: VGN-TZ150N
  dmi.product.sku: N/A
  dmi.product.version: J002NHLG
  dmi.sys.vendor: Sony Corporation

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

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


[Desktop-packages] [Bug 1910694] Re: When saving a text file with Ctrl + S, gedit enables "Highlight current line" on its own

2021-03-13 Thread Lyubomir
** Changed in: gedit (Ubuntu)
   Status: Expired => New

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

Title:
  When saving a text file with Ctrl + S, gedit enables "Highlight
  current line" on its own

Status in gedit package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have some text file opened in gedit
  2. Disable "Highlight current line"
  3. Press Ctrl + S to save changes
  4. Notice the "Highlight current line" is now enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gedit 3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-59.65-lowlatency 5.4.78
  Uname: Linux 5.4.0-59-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Jan  8 11:27:13 2021
  InstallationDate: Installed on 2020-12-27 (11 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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