[Desktop-packages] [Bug 1899262] Re: Broken dbus GetAll message to wpa supplicant interface properties

2020-12-01 Thread Michael Nazzareno Trimarchi
@Sebastien I will test it today. Sorry for the delay

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

Title:
  Broken dbus GetAll message to wpa supplicant interface properties

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Bionic:
  Fix Committed

Bug description:
  * Impact
  One of the distro patch is incorrect and create issues when trying to query 
dbus properties

  * Test Case

  $ sudo dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1
  /fi/w1/wpa_supplicant1/Interfaces/1
  org.freedesktop.DBus.Properties.GetAll
  string:fi.w1.wpa_supplicant1.Interface

  shouldn't error out

  (the /1 reflect the interface number and could be a different value,
  check with d-feet if needed)

  * Regression potential

  The fixes is in the dbus interface, check that communication with
  desktop clients (indicator, applet, settings) still works correctly,
  returning expected informations on the signal, etc

  -

  dbus-send is able to read the properties of interface using GetAll. Those 
information include interface name, status, encryption method, etc.
  The regression was introduced when someone try to have the Station attribute 
supported

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

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


[Desktop-packages] [Bug 1900777] Re: [amdgpu] Screen freeze with AMD/ATI Renoir

2020-12-01 Thread Daniel van Vugt
Those are both different issues to this. To make the debugging process
clear please open new bugs for each of those.

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

Title:
  [amdgpu] Screen freeze with AMD/ATI Renoir

Status in linux package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid

Bug description:
  I upgraded to a Ryzen 7, 24-RAM ASUS computer because I thought that
  my 2-year-old Dell laptop was the problem. However, I froze during
  Zoom yesterday and during coding today after fresh-installing Ubuntu
  20.04 on Sunday. I also froze mid-attempt to submit a bug report after
  the coding freeze. Any help is appreciated. Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 20 17:38:31 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   amdgpu, 5.6.0.15-1098277, 5.4.0-51-generic, x86_64: installed
   amdgpu, 5.6.0.15-1098277, 5.4.0-52-generic, x86_64: installed
   rtl8821ce, 5.5.2.1, 5.4.0-51-generic, x86_64: installed
   rtl8821ce, 5.5.2.1, 5.4.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Within the last few days
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Renoir [1043:1352]
  InstallationDate: Installed on 2020-10-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513IA_M513IA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=df36462b-f672-4f1c-a8b2-060922542daf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X513IA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X513IA
  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.:bvrX513IA.300:bd06/05/2020:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513IA_M513IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X513IA_M513IA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER 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 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  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/1900777/+subscriptions

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


[Desktop-packages] [Bug 1905775] Re: Uninstalling python3-apporrt should not uninstall xorg packages

2020-12-01 Thread flux242
*** This bug is a duplicate of bug 1899971 ***
https://bugs.launchpad.net/bugs/1899971

well, based on the reply from Timo Aaltonen it seems like there's canonical 
politics involved 
so, i purged python3-apport and reinstalled only 2 packages:
sudo apt install xserver-xorg-core xserver-xorg-input-libinput

x11-apps x11-session-utils xinput xinit x11-apps could be installed
extra

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

Title:
  Uninstalling python3-apporrt should not uninstall xorg packages

Status in xorg package in Ubuntu:
  New

Bug description:
  ```
  sudo apt purge python3-apport 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
libglu1-mesa libxfont2 python3-certifi python3-chardet python3-idna 
python3-problem-report python3-requests
python3-requests-unixsocket python3-urllib3 x11-apps x11-session-utils 
xinit xinput xserver-common
xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput
  Use 'sudo apt autoremove' to remove them.
  The following packages will be REMOVED:
python3-apport* xorg* xserver-xorg*
  0 upgraded, 0 newly installed, 3 to remove and 61 not upgraded.
  After this operation, 1,070 kB disk space will be freed.
  Do you want to continue? [Y/n] ^C
  ```

  so, apparently dependencies aren't correctly set, because I don't want
  to send no problem reports but still want to use xorg subsystem

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

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


[Desktop-packages] [Bug 1906449] Re: Xorg randomly freezes

2020-12-01 Thread Daniel van Vugt
Please either go to step 2 in comment #2, or update the system and wait
until a new crash file is produced.

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

Title:
  Xorg randomly freezes

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Initially, I thought it only happened during file transfers (because
  that's when it happens most often), but I later found that it can
  happen at any time, because I just turned my computer on, went to go
  make a coffee, have a cigarette, and when I came back, the entire
  screen, desktop, system, etc had frozen again. I always need to hold
  the power button down to do an emergency restart, because I can't even
  use Alt+F# to get into the TTY.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.95.01  Thu May 28 
07:03:08 UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Dec  1 12:28:44 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.95.01, 5.4.0-56-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1e21]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21]
  InstallationDate: Installed on 2020-12-01 (0 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=UUID=11577769-570c-4297-a9b2-35fb3a30f6bf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA506IV.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FA506IV
  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.:bvrFA506IV.309:bd07/02/2020:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF Gaming FA506IV
  dmi.product.name: TUF Gaming FA506IV_TUF506IV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  nvidia-settings:
   ERROR: Unable to load info from any available system
   
   
   ERROR: Unable to load info from any available system
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/xorg-server/+bug/1906449/+subscriptions

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


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

2020-12-01 Thread Jonah Libster
Cannot use Microphone at all because when I switch to HSP/HSF mode the
Microphone has no input and the speakers stop working. I tried
installing Ofono which resulted in the Microphone working as a "speaker"
(got sound levels) and the speakers not working at all when attempting
to use HSP/HSF mode.Here are the hardware/Os basic details.

Ubuntu 20.0.4.1 LTS
Lenovo 20QU-S4RC00
Plantronics BackBeat Pro 2

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

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

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

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

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

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

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

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


[Desktop-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

2020-12-01 Thread Jonah Libster
*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794

Identical issues with:

Ubuntu 20.0.4.1 LTS
Lenovo 20QU-S4RC00
Plantronics BackBeat Pro 2

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

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

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

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

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


[Desktop-packages] [Bug 1896098] Re: Lenovo P1G3 - unable to select system speakers when headset plugged into audio jack

2020-12-01 Thread Chi-Wei Chen
Hi @Hui,
Our PA team confirmed this issue was verified PASS using BIOS 24W.
It seems to be BIOS related issue.
Please let me know if this BIOS 24W or later version not work on your side.

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

Title:
  Lenovo P1G3 - unable to select system speakers when headset plugged
  into audio jack

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I suspect this is a pulseaudio or alsa bug.

  Our test team reported this:
  1. Prepare Padme-3 machine and Install Ubuntu_20.04 OS .
  2. Boot system.
  3. Play audio or video file.
  4. Open Settings > Sound.
  5. Hot attach headset.
  6. Notice that headset is selected as output device in sound settings and 
sound can be heard from headset => EXPECTED
  7. While playback, select Internal Speaker as output device => KEYPOINT
  9. Notice:SUT havo no sound from Internal Speakers => PROBLEM

  I was able to confirm this - it seems with the headphones connected
  that I can't select the system speakers. If I don't have headphones
  connected I can switch between dock audio and system speakers
  correctly - so it's just related to the audio jack

  Thanks
  Mark

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

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


[Desktop-packages] [Bug 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition

2020-12-01 Thread Alexey Tsitsin
This problem still persist and SPNEGO won't work even with new policies:

https://cloud.google.com/docs/chrome-enterprise/policies/?policy=AuthServerAllowlist
https://cloud.google.com/docs/chrome-enterprise/policies/?policy=AuthNegotiateDelegateAllowlist

The policies are loaded successfully but  kerboros negotiation won't
work

** Information type changed from Public to Public Security

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

Title:
  [snap] kerberos GSSAPI no longer works after deb->snap transition

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  I configure AuthServerWhitelist as documented:

  https://www.chromium.org/developers/design-documents/http-
  authentication

  and can see my whitelisted domains in chrome://policy/

  but websites that used to work with SPNEGO/GSSAPI/kerberos no longer
  work. I'm guessing the snap needs some sort of permission to use the
  kerberos ticket cache (or the plumbing to do so doesn't exist...).

  I can confirm that Chrome has the desired behavior.

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

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


[Desktop-packages] [Bug 1866732] Re: [snap] Unable to add policies

2020-12-01 Thread Alexey Tsitsin
The bug is solved

We need to create folder mkdir -p /etc/chromium-browser/policies/managed 
manually and then browsre check the policies successfully

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

Title:
  [snap] Unable to add policies

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  When using the Chromium snap, the policies located in the directory
  /etc/chromium-browser/policies/managed/ are no longer being read. The
  consequence is that the policies are not applied.

  This is particularly problematic on, for example, public computers,
  where browsing history and passwords may be saved, or on school
  computers, where the dinosaur game will be easily available.

  Is there another way I'm unaware of to add system-wide policies when
  using the Chromium snap? If not, would it be possible to make the snap
  read the settings in the /etc/chromium-browser/policies/managed/
  directory? This would make the transition from deb to snap easier on
  systems which are already configured with system-wide policies.

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

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


[Desktop-packages] [Bug 1414753] Re: Chromium browser 39.0.2171.65 does not load policies

2020-12-01 Thread Alexey Tsitsin
Hello!
This bug still persist in Chromium 87.0.4280.66 (Official Build) snap (64-bit)
Ubuntu 20.10

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

Title:
  Chromium browser 39.0.2171.65 does not load policies

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Following the information I gathered from

  http://www.chromium.org/administrators/linux-quick-start
  http://www.chromium.org/administrators/linux-quick-start
  https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1373802

  I tried to set a simple policy for the browser.
  All I did is create a file "policy.json" in /etc/chromium-
  browser/policies/managed with the following content:

  {
"HomepageLocation": "www.chromium.org"
  }

  However when starting chromium there is no sign of the policy: "about:policy" 
  does not show any policy being set. Running 'strings /usr/lib/chromium-
  browser/chromium-browser|grep policies' gives me:

  /etc/chromium/policies
  /etc/chromium-browser/policies

  so everything should be fine. To be sure I also tried setting the policy in 
  /etc/chromium/policies. I also tried to set the policy in "recommended"  in 
  both paths. I also tested running chromium under a new user account, but it 
  did not change anything. The policy is simply not set. Either I am doing 
  something wrong or this is not working.
  To be on the safe side I also tried a different content:

  {
"RestoreOnStartup": 4,
"RestoreOnStartupURLs": ["http://www.chromium.org;
  }

  Did not work either.

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

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


[Desktop-packages] [Bug 1900777] Re: [amdgpu] Screen freeze with AMD/ATI Renoir

2020-12-01 Thread Blaise Mariner
I would also like to add that the night light function and HDMI external
monitors seem to work in windows if I select to boot into that OS.
Thanks.

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

Title:
  [amdgpu] Screen freeze with AMD/ATI Renoir

Status in linux package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid

Bug description:
  I upgraded to a Ryzen 7, 24-RAM ASUS computer because I thought that
  my 2-year-old Dell laptop was the problem. However, I froze during
  Zoom yesterday and during coding today after fresh-installing Ubuntu
  20.04 on Sunday. I also froze mid-attempt to submit a bug report after
  the coding freeze. Any help is appreciated. Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 20 17:38:31 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   amdgpu, 5.6.0.15-1098277, 5.4.0-51-generic, x86_64: installed
   amdgpu, 5.6.0.15-1098277, 5.4.0-52-generic, x86_64: installed
   rtl8821ce, 5.5.2.1, 5.4.0-51-generic, x86_64: installed
   rtl8821ce, 5.5.2.1, 5.4.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Within the last few days
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Renoir [1043:1352]
  InstallationDate: Installed on 2020-10-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513IA_M513IA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=df36462b-f672-4f1c-a8b2-060922542daf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X513IA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X513IA
  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.:bvrX513IA.300:bd06/05/2020:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513IA_M513IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X513IA_M513IA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER 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 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  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/1900777/+subscriptions

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


[Desktop-packages] [Bug 1900777] Re: [amdgpu] Screen freeze with AMD/ATI Renoir

2020-12-01 Thread Blaise Mariner
Hi Daniel, the driver that I have with ubuntu's support (the one that is
downloaded automatically) is giving me some problems. No freezes yet
(it's been around 6 hours).

The first problem is that the display does not seem to be claimed.

blaise@blaise-VivoBook2:~$ sudo lshw -c video
[sudo] password for blaise: 
  *-display UNCLAIMED   
   description: VGA compatible controller
   product: Renoir
   vendor: Advanced Micro Devices, Inc. [AMD/ATI]
   physical id: 0
   bus info: pci@:03:00.0
   version: c2
   width: 64 bits
   clock: 33MHz
   capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
   configuration: latency=0
   resources: memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe70-fe77
 

This I believe leads to the following problems in which the night light
does not work. (when I had the driver installed from the amd website it
did work). And similarly, I cannot attach an HDMI external monitor to my
computer anymore, where previously with the other driver I could.

Please let me know what steps I can take to resolve these issues. I have
gone through the internet and many suggestions just tell me to install
the driver from the amd site. but I do not want something that Ubuntu
does not support or freezes on me. Thanks. Blaise

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

Title:
  [amdgpu] Screen freeze with AMD/ATI Renoir

Status in linux package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid

Bug description:
  I upgraded to a Ryzen 7, 24-RAM ASUS computer because I thought that
  my 2-year-old Dell laptop was the problem. However, I froze during
  Zoom yesterday and during coding today after fresh-installing Ubuntu
  20.04 on Sunday. I also froze mid-attempt to submit a bug report after
  the coding freeze. Any help is appreciated. Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 20 17:38:31 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   amdgpu, 5.6.0.15-1098277, 5.4.0-51-generic, x86_64: installed
   amdgpu, 5.6.0.15-1098277, 5.4.0-52-generic, x86_64: installed
   rtl8821ce, 5.5.2.1, 5.4.0-51-generic, x86_64: installed
   rtl8821ce, 5.5.2.1, 5.4.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Within the last few days
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Renoir [1043:1352]
  InstallationDate: Installed on 2020-10-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513IA_M513IA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=df36462b-f672-4f1c-a8b2-060922542daf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X513IA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X513IA
  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.:bvrX513IA.300:bd06/05/2020:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513IA_M513IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X513IA_M513IA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER 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 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  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
  

[Desktop-packages] [Bug 1906449] Re: Xorg randomly freezes

2020-12-01 Thread Kuroš Taheri-Golværzi
When I tried Step 1, I got an error messaged saying that Ubuntu 20.04
has experienced and error and asking if I'd like to report it to the
developers, and when I clicked Yes, it gave another error message saying
that "the problem happened with /usr/lib/xorg/Xorg which changed since
the crash occurred". I copied the *.crash file to a USB so that I can
send it on my older computer (which I'm typing this report on now).
Would you like me to paste it here?

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

Title:
  Xorg randomly freezes

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Initially, I thought it only happened during file transfers (because
  that's when it happens most often), but I later found that it can
  happen at any time, because I just turned my computer on, went to go
  make a coffee, have a cigarette, and when I came back, the entire
  screen, desktop, system, etc had frozen again. I always need to hold
  the power button down to do an emergency restart, because I can't even
  use Alt+F# to get into the TTY.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.95.01  Thu May 28 
07:03:08 UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Dec  1 12:28:44 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.95.01, 5.4.0-56-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1e21]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21]
  InstallationDate: Installed on 2020-12-01 (0 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=UUID=11577769-570c-4297-a9b2-35fb3a30f6bf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA506IV.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FA506IV
  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.:bvrFA506IV.309:bd07/02/2020:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF Gaming FA506IV
  dmi.product.name: TUF Gaming FA506IV_TUF506IV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  nvidia-settings:
   ERROR: Unable to load info from any available system
   
   
   ERROR: Unable to load info from any available system
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/xorg-server/+bug/1906449/+subscriptions

-- 
Mailing list: 

[Desktop-packages] [Bug 1906086] Re: DIsplay is limited to top half of the screen

2020-12-01 Thread Daniel van Vugt
On the login screen, select your account but before entering a password
click the icon that appears in the bottom right corner of the screen.
There you can select 'Ubuntu on Wayland'.

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

Title:
  DIsplay is limited to top half of the screen

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Display is limited to the top half of the screen.
  I have tried changing the resolution, without success.

  I am attempting to trial Ubuntu 20.10 from a USB stick.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.445.1
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 28 04:09:34 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8058]
  LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: HP HP EliteOne 800 G2 23-in Touch AiO
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2019
  dmi.bios.vendor: HP
  dmi.bios.version: N11 Ver. 02.45
  dmi.board.name: 8058
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 05.39
  dmi.chassis.asset.tag: AUD6100LCF
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN11Ver.02.45:bd12/24/2019:svnHP:pnHPEliteOne800G223-inTouchAiO:pvr:rvnHP:rn8058:rvrKBCVersion05.39:cvnHP:ct13:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteOne 800 G2 23-in Touch AiO
  dmi.product.sku: T6T88PA#ABG
  dmi.sys.vendor: HP
  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.2
  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/mutter/+bug/1906086/+subscriptions

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


[Desktop-packages] [Bug 1715435] Re: Can't lock screen when using lightdm with gnome-shell

2020-12-01 Thread Daniel van Vugt
** Summary changed:

- Can't lock screen with keyboard shortcuts when using lightdm
+ Can't lock screen when using lightdm with gnome-shell

** Tags removed: eoan
** Tags added: focal

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

Title:
  Can't lock screen when using lightdm with gnome-shell

Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen.
  Additionally, if I wait a very long time the screen does not lock
  either.

  Switching from LightDM to GDM3 fixes the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep  6 09:17:35 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2016-01-22 (592 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1905982] Re: Screen not Blanking after upgrade to 20.04

2020-12-01 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1715435 ***
https://bugs.launchpad.net/bugs/1715435

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1715435, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Tags added: focal

** This bug has been marked a duplicate of bug 1715435
   Can't lock screen with keyboard shortcuts when using lightdm

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

Title:
  Screen not Blanking after upgrade to 20.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After a do-release-upgrade from 18.04 to 20.04 screen blanking stopped 
working.
  I had my desktop set to blank but no lock the screen.
  After the upgrtade it does not ever blank. 

   preferences are set in Settings-> Power -> Blank Screen 10 minutes
   Automatic Suspend is OFF

   gnome-screensaver is running

   gnome-screensaver command -a doesn't do anything.

   video driver is Nvidia-455

   Display Manager is lightdm switching to gdm3 causes the video to not
  work properly.

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

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


[Desktop-packages] [Bug 1880785] Re: Lockscreen doesn't work when using lightdm

2020-12-01 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1715435 ***
https://bugs.launchpad.net/bugs/1715435

** This bug has been marked a duplicate of bug 1715435
   Can't lock screen with keyboard shortcuts when using lightdm

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

Title:
  Lockscreen doesn't work when using lightdm

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I am trying to make my laptop lock the screen upon unsuspending. I
  have made sure that the setting is enabled in 'Settings > Privacy >
  Screen lock > Lock screen on suspend', but my laptop opens without a
  lock screen when I open it or press a key. This only started since
  upgrading to Ubuntu 20.04. Previously, I would have a locked screen
  and be prompted for a password upon unsuspending.

  $ gsettings get org.gnome.desktop.screensaver ubuntu-lock-on-suspend
  true

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.36.2-1ubuntu1~20.04.1
Candidate: 3.36.2-1ubuntu1~20.04.1
Version table:
   *** 3.36.2-1ubuntu1~20.04.1 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   3.36.1-5ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 26 21:28:39 2020
  DisplayManager: lightdm
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2018-07-16 (680 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-23 (33 days ago)

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

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


[Desktop-packages] [Bug 1906394] Re: Displays blinking after Ubuntu 20.10 upgrade

2020-12-01 Thread Daniel van Vugt
I can't see anything relevant in the attached files. Can you provide a
video of the problem?

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

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

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

Title:
  Displays blinking after Ubuntu 20.10 upgrade

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi!

  MY Displays are blinking after Ubuntu 20.10 upgrade. Please see the
  log.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Dec  1 14:02:04 2020
  DistUpgraded: 2020-11-26 14:18:08,201 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-osp1-20171027-1
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0818]
  InstallationDate: Installed on 2019-01-24 (677 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20171027-10:57
  MachineType: Dell Inc. Latitude 5491
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic 
root=UUID=33b5750d-e24c-406f-924e-050b03935415 ro alx.enable_wol=1 
mem_sleep_default=deep quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to groovy on 2020-11-26 (4 days ago)
  dmi.bios.date: 02/25/2020
  dmi.bios.release: 1.12
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.0
  dmi.board.name: 0R8P2H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd02/25/2020:br1.12:svnDellInc.:pnLatitude5491:pvr:rvnDellInc.:rn0R8P2H:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5491
  dmi.product.sku: 0818
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Tue Jul 28 12:22:12 2020
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.8-2ubuntu2.2

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

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


[Desktop-packages] [Bug 1906316] Re: [nvidia] Xorg crash

2020-12-01 Thread Daniel van Vugt
Thanks. None of those .crash files look relevant so please go to step 2
of comment #3.

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

Title:
  [nvidia] Xorg crash

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Just crached all of a sudden. I was in a terminal using dialog...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  455.38  Thu Oct 22 06:06:59 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 30 22:50:10 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 455.38, 5.4.0-42-generic, x86_64: installed
   virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed
   virtualbox, 6.1.10, 5.4.0-45-generic, x86_64: installed
   virtualbox, 6.1.10, 5.4.0-47-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] TU116 [GeForce GTX 
1660 Ti] [1462:3750]
  InstallationDate: Installed on 2020-08-04 (118 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-B08911
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/20/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V8.1
  dmi.board.name: MS-78511
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: 3.1
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV8.1:bd07/20/2015:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-B08911:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-78511:rvr3.1:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-B08911
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  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 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  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/xorg-server/+bug/1906316/+subscriptions

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


[Desktop-packages] [Bug 1906449] Re: Xorg randomly freezes

2020-12-01 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

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

Title:
  Xorg randomly freezes

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Initially, I thought it only happened during file transfers (because
  that's when it happens most often), but I later found that it can
  happen at any time, because I just turned my computer on, went to go
  make a coffee, have a cigarette, and when I came back, the entire
  screen, desktop, system, etc had frozen again. I always need to hold
  the power button down to do an emergency restart, because I can't even
  use Alt+F# to get into the TTY.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.95.01  Thu May 28 
07:03:08 UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Dec  1 12:28:44 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.95.01, 5.4.0-56-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1e21]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21]
  InstallationDate: Installed on 2020-12-01 (0 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=UUID=11577769-570c-4297-a9b2-35fb3a30f6bf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA506IV.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FA506IV
  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.:bvrFA506IV.309:bd07/02/2020:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF Gaming FA506IV
  dmi.product.name: TUF Gaming FA506IV_TUF506IV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  nvidia-settings:
   ERROR: Unable to load info from any available system
   
   
   ERROR: Unable to load info from any available system
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  

[Desktop-packages] [Bug 1905637] Re: Games don't go full screen correctly with newer version of libmutter

2020-12-01 Thread Daniel van Vugt
Thanks. It looks like the "gamemode" extension is causing a lot of
errors in your log. Please try uninstalling that and any other non-
default extensions you have:

  gnome-shell-extension-gamemode
  gnome-shell-extension-system-monitor

and

  cd ~/.local/share/gnome-shell/
  rm -rf extensions

Then log out and in again, and tell us if the problem still happens.

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

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

Title:
  Games don't go full screen correctly with newer version of libmutter

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Some games (I tried using Portal and Tomb Raider 2013, both native
  games) don't go full screen correctly (even configured for it). I
  tracked down the problem to a regression on package libmutter-7-0. The
  problem occurs with latest version, 3.38.1-2ubuntu1, but when I
  downgrade the package (and also the package gir1.2-mutter-7) to
  3.38.1-1ubuntu1 the gomes went full screen normally.

  I'm using Ubuntu 20.10.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-23 (33 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: libmutter-7-0 3.38.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
  Tags: groovy third-party-packages
  Uname: Linux 5.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1905637] Re: Games don't go full screen correctly with newer version of libmutter

2020-12-01 Thread Daniel van Vugt
** Tags added: hybrid nvidia

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

Title:
  Games don't go full screen correctly with newer version of libmutter

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Some games (I tried using Portal and Tomb Raider 2013, both native
  games) don't go full screen correctly (even configured for it). I
  tracked down the problem to a regression on package libmutter-7-0. The
  problem occurs with latest version, 3.38.1-2ubuntu1, but when I
  downgrade the package (and also the package gir1.2-mutter-7) to
  3.38.1-1ubuntu1 the gomes went full screen normally.

  I'm using Ubuntu 20.10.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-23 (33 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: libmutter-7-0 3.38.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
  Tags: groovy third-party-packages
  Uname: Linux 5.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1905775] Re: Uninstalling python3-apporrt should not uninstall xorg packages

2020-12-01 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1899971 ***
https://bugs.launchpad.net/bugs/1899971

Sounds like the same issue as bug 1899971.

** This bug has been marked a duplicate of bug 1899971
   Problematic dependency on python3-apport causes all Python invocations to 
install apport hook

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

Title:
  Uninstalling python3-apporrt should not uninstall xorg packages

Status in xorg package in Ubuntu:
  New

Bug description:
  ```
  sudo apt purge python3-apport 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
libglu1-mesa libxfont2 python3-certifi python3-chardet python3-idna 
python3-problem-report python3-requests
python3-requests-unixsocket python3-urllib3 x11-apps x11-session-utils 
xinit xinput xserver-common
xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput
  Use 'sudo apt autoremove' to remove them.
  The following packages will be REMOVED:
python3-apport* xorg* xserver-xorg*
  0 upgraded, 0 newly installed, 3 to remove and 61 not upgraded.
  After this operation, 1,070 kB disk space will be freed.
  Do you want to continue? [Y/n] ^C
  ```

  so, apparently dependencies aren't correctly set, because I don't want
  to send no problem reports but still want to use xorg subsystem

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

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


[Desktop-packages] [Bug 1906087] Re: Half of the date-time text is hidden in the calendar popover

2020-12-01 Thread Daniel van Vugt
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3445
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3445

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3445
   Importance: Unknown
   Status: Unknown

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gnome-shell (Ubuntu)
   Status: New => Triaged

** Summary changed:

- Half of the date-time text is hidden in the calendar popover
+ Half of the date-time text is hidden in the calendar popover when using Tamil 
(India) as the language

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

Title:
  Half of the date-time text is hidden in the calendar popover when
  using Tamil (India) as the language

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  I am using Tamil(india) as the date-time language from Ubuntu 19. But
  after upgrading to Ubuntu 20, the date-time is half-hidden (see
  attachments).

  before upgrade it was working fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 28 10:47:42 2020
  DistUpgraded: 2020-06-06 18:27:37,926 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:0792]
  InstallationDate: Installed on 2018-11-04 (755 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Vostro 14-3468
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=UUID=6272611c-ab7e-4b80-86ed-8e7dbe8d5396 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-06-06 (174 days ago)
  acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
  dmi.bios.date: 05/15/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.0
  dmi.board.name: 0T1X3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.0:bd05/15/2018:svnDellInc.:pnVostro14-3468:pvr:rvnDellInc.:rn0T1X3V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 14-3468
  dmi.product.sku: 0792
  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 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  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/gnome-shell/+bug/1906087/+subscriptions

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


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

2020-12-01 Thread Daniel van Vugt
Unfortunately the developers could not agree and closed:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/227

That doesn't mean desktop Linux will never have it. Just not any time
soon :(


** Changed in: pulseaudio (Ubuntu)
   Status: In Progress => Triaged

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

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

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Triaged
Status in Arch Linux:
  New

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

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

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

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

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

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

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

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

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

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

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


[Desktop-packages] [Bug 1906420] Re: Please replace default Gnome extension "Desktop Icons" with "Desktop Icons NG (DING)" (by the same author)

2020-12-01 Thread Daniel van Vugt
** Package changed: gnome-shell-extension-desktop-icons (Ubuntu) =>
ubuntu-meta (Ubuntu)

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

Title:
  Please replace default Gnome extension "Desktop Icons" with "Desktop
  Icons NG (DING)" (by the same author)

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  By default, Ubuntu installs the Gnome extension "Desktop Icons" [1]
  (by rastersoft).

  Unfortunately, this extension is now unmaintained, is problematic, and
  leads to several bugs, including but not limited to Bug #1901150 and
  Bug #1813441.

  The same author has created, and continues to maintain, the far
  superior "Desktop Icons NG (DING)" [2]. It solves a number of problems
  including the two aforementioned bugs.

  It's possible to disable, but not uninstall, "Desktop Icons", and then
  to install "Desktop Icons NG (DING)". I did this a while ago with
  great results.

  If Canonical replaces the former with the latter, not only will Ubuntu
  be using a better desktop manager, but also it will be able clear all
  related bugs at a stroke.

  This is a simple, cheap, quick and effective solution that will let
  the devs concentrate on more important tasks.

  Please give this serious consideration.

  
  More information:

  Ubuntu 20.04.1 LTS
  64-bit
  Gnome version 3.36.3

  
  [1] https://extensions.gnome.org/extension/1465/desktop-icons/

  [2] https://extensions.gnome.org/extension/2087/desktop-icons-ng-ding/

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

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


[Desktop-packages] [Bug 1828434] Re: Unable to print after libgs 9.26 installed

2020-12-01 Thread rtimai
*** This bug is a duplicate of bug 1828401 ***
https://bugs.launchpad.net/bugs/1828401

Forgot to mention, Debian 10 Buster currently installs
cups-filters 1.21.6-5 with ghostscript 9.27~dfsg-2+deb10u4

I tried and failed to revert the ghostscript version.

~$  lsb_release -ds ; uname -srm ; gnome-shell --version ; echo 
$XDG_SESSION_TYPE
Debian GNU/Linux 10 (buster)
Linux 4.19.0-13-amd64 x86_64
GNOME Shell 3.30.2
x11
~$

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

Title:
  Unable to print after libgs 9.26 installed

Status in ghostscript package in Ubuntu:
  Confirmed

Bug description:
  I'm receiving the following error in the cups error_log after libgs
  was updated to 9.26:

  D [09/May/2019:11:19:22 -0400] [Job 6927] Filetype: PDF
  D [09/May/2019:11:19:22 -0400] [Job 6927] Storing temporary files in /tmp
  D [09/May/2019:11:19:22 -0400] [Job 6927] PID 28996 
(/usr/lib/cups/filter/pdftopdf) exited with no errors.
  D [09/May/2019:11:19:22 -0400] [Job 6927] GPL Ghostscript 9.26: Unrecoverable 
error, exit code 1
  D [09/May/2019:11:19:22 -0400] [Job 6927] Process is dying with \"Unable to 
determine number of pages, page count: -1
  D [09/May/2019:11:19:22 -0400] [Job 6927] \", exit stat 3
  D [09/May/2019:11:19:22 -0400] [Job 6927] Cleaning up...
  D [09/May/2019:11:19:22 -0400] [Job 6927] PID 28997 
(/usr/lib/cups/filter/foomatic-rip) stopped with status 3.
  D [09/May/2019:11:19:22 -0400] [Job 6927] prnt/backend/hp.c 919: ERROR: null 
print job total=0
  D [09/May/2019:11:19:22 -0400] [Job 6927] PID 28998 
(/usr/lib/cups/backend/hp) exited with no errors

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

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


[Desktop-packages] [Bug 1902044] Re: SRU the current 42.6 stable update

2020-12-01 Thread Robie Basak
> It's not under the GNOME MRE no, just a micro release update worth
SRUing for the fixes it includes.

In that case the third paragraph of my comment 1 above still needs
addressing please.

** Changed in: deja-dup (Ubuntu Groovy)
   Status: In Progress => Incomplete

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

Title:
  SRU the current 42.6 stable update

Status in deja-dup package in Ubuntu:
  Fix Released
Status in deja-dup source package in Groovy:
  Incomplete

Bug description:
  * Impact
  That's the current stable update, including some fixes and translation updates
  https://gitlab.gnome.org/World/deja-dup/-/releases/42.5

  The update should help with bug #1901340 and backup on removable
  drives

  * Test case

  Check that local and remote backups and restore are working.

  * Regression potential

  The update has some fixes for backup on removable and encrypted media
  so that's probably something to give some testing to

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

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


[Desktop-packages] [Bug 1828434] Re: Unable to print after libgs 9.26 installed

2020-12-01 Thread rtimai
*** This bug is a duplicate of bug 1828401 ***
https://bugs.launchpad.net/bugs/1828401

While the last post was in 05/2019, this Ubuntu page on launchpad is
still relevant for Debian users, as conservative Debian is several
versions behind most distros. I am encountering this compatibility issue
between cups-filters 1.21.6-5 amd64 and ghostscript 9.27~dfsg-2+deb10u4
amd64 since 11/2020, i.e., since GS was upgraded (possibly a regression
error, since 1.21 was supposed to have fixed a previous 'filters failed'
error.)

Debian does not appear to support specifying downgraded package
versions.

~$  sudo apt-get install ghostscript=9.26a~dfsg-0+deb9u1 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
E: Version '9.26a~dfsg-0+deb9u1' for 'ghostscript' was not found
~$ 

This issue appears to cross multiple printer series -- I am using an HP-
Deskjet-1112, and am unable to apply selective page printing for double-
sided results on a single-function printer (e.g., printing ODD pages,
flip-reloading and then printing EVEN pages.) This is for work schedule
charts, so it's not trivial to me.

If anyone can provide a workaround, I'd greatly appreciate it if you can
provide specific instructions. Thanks all, for reading.

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

Title:
  Unable to print after libgs 9.26 installed

Status in ghostscript package in Ubuntu:
  Confirmed

Bug description:
  I'm receiving the following error in the cups error_log after libgs
  was updated to 9.26:

  D [09/May/2019:11:19:22 -0400] [Job 6927] Filetype: PDF
  D [09/May/2019:11:19:22 -0400] [Job 6927] Storing temporary files in /tmp
  D [09/May/2019:11:19:22 -0400] [Job 6927] PID 28996 
(/usr/lib/cups/filter/pdftopdf) exited with no errors.
  D [09/May/2019:11:19:22 -0400] [Job 6927] GPL Ghostscript 9.26: Unrecoverable 
error, exit code 1
  D [09/May/2019:11:19:22 -0400] [Job 6927] Process is dying with \"Unable to 
determine number of pages, page count: -1
  D [09/May/2019:11:19:22 -0400] [Job 6927] \", exit stat 3
  D [09/May/2019:11:19:22 -0400] [Job 6927] Cleaning up...
  D [09/May/2019:11:19:22 -0400] [Job 6927] PID 28997 
(/usr/lib/cups/filter/foomatic-rip) stopped with status 3.
  D [09/May/2019:11:19:22 -0400] [Job 6927] prnt/backend/hp.c 919: ERROR: null 
print job total=0
  D [09/May/2019:11:19:22 -0400] [Job 6927] PID 28998 
(/usr/lib/cups/backend/hp) exited with no errors

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

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


[Desktop-packages] [Bug 1897369] Re: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)

2020-12-01 Thread Seth Arnold
It may also be an option to set the desired scheduling parameters via
systemd.exec(5) parameters instead of asking the daemon to do the
changes itself.

Thanks

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

Title:
  apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 20.04.1 with *cups-browsed* 1.27.4-1, apparmor prevents
  `/usr/sbin/cups-browsed` to change its nice value.

  $ sudo dmesg | grep apparmor
  [541870.509461] audit: type=1400 audit(1600898428.089:60): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=62030 comm="cups-browsed" capability=23  capname="sys_nice"
  [628298.779668] audit: type=1400 audit(1600984854.115:61): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=66850 comm="cups-browsed" capability=23  capname="sys_nice"
  [714667.424963] audit: type=1400 audit(1601071220.527:62): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=76828 comm="cups-browsed" capability=23  capname="sys_nice"

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

-- 
Mailing list: https://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 1906086] Re: DIsplay is limited to top half of the screen

2020-12-01 Thread Glenn Stewart
Hi Daniel.

Here is the screenshot of the start up options.  There is no 'Ubuntu on
Wayland' option available to me at start up.
I have tried each option, without success at this point.
Windows is still affected.  Hard to show as the bottom half "haze" is very
light today.

[image: image.png]

Regards,
Glenn Stewart


On Tue, Dec 1, 2020 at 9:21 PM Daniel van Vugt <1906...@bugs.launchpad.net>
wrote:

> Thanks, that sounds like a hardware problem.
>
> Please also try selecting 'Ubuntu on Wayland' before you enter your
> password.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1906086
>
> Title:
>   DIsplay is limited to top half of the screen
>
> Status in mutter package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Display is limited to the top half of the screen.
>   I have tried changing the resolution, without success.
>
>   I am attempting to trial Ubuntu 20.10 from a USB stick.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: xorg 1:7.7+19ubuntu14
>   ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
>   Uname: Linux 5.4.0-42-generic x86_64
>   NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
>   ApportVersion: 2.20.11-0ubuntu27.4
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperMD5CheckResult: pass
>   CasperVersion: 1.445.1
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Nov 28 04:09:34 2020
>   DistUpgraded: Fresh install
>   DistroCodename: focal
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, if not too technical
>   GraphicsCard:
>Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA
> controller])
>  Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8058]
>   LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64
> (20200731)
>   MachineType: HP HP EliteOne 800 G2 23-in Touch AiO
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
> file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 12/24/2019
>   dmi.bios.vendor: HP
>   dmi.bios.version: N11 Ver. 02.45
>   dmi.board.name: 8058
>   dmi.board.vendor: HP
>   dmi.board.version: KBC Version 05.39
>   dmi.chassis.asset.tag: AUD6100LCF
>   dmi.chassis.type: 13
>   dmi.chassis.vendor: HP
>   dmi.modalias:
> dmi:bvnHP:bvrN11Ver.02.45:bd12/24/2019:svnHP:pnHPEliteOne800G223-inTouchAiO:pvr:rvnHP:rn8058:rvrKBCVersion05.39:cvnHP:ct13:cvr:
>   dmi.product.family: 103C_53307F G=D
>   dmi.product.name: HP EliteOne 800 G2 23-in Touch AiO
>   dmi.product.sku: T6T88PA#ABG
>   dmi.sys.vendor: HP
>   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.2
>   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/mutter/+bug/1906086/+subscriptions
>


** Attachment added: "image.png"
   https://bugs.launchpad.net/bugs/1906086/+attachment/5440155/+files/image.png

** Attachment added: "Ubuntu_Start_Screenshot.jpg"
   
https://bugs.launchpad.net/bugs/1906086/+attachment/5440156/+files/Ubuntu_Start_Screenshot.jpg

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

Title:
  DIsplay is limited to top half of the screen

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Display is limited to the top half of the screen.
  I have tried changing the resolution, without success.

  I am attempting to trial Ubuntu 20.10 from a USB stick.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.445.1
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 28 04:09:34 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD 

[Desktop-packages] [Bug 1906454] [NEW] Firefox does not NV12 for webcams

2020-12-01 Thread Benjamin Drung
Public bug reported:

I use a Sony Alhpa camera attached to Elgato Cam Link 4K as webcam. The
only color format that is working with Cam Link 4K is NV12. Sadly
Firefox does not support NV12 (despite the source code containing
several third party libraries that refer to NV12). Looking at the kernel
log for the uvcvideo kernel module, I can see that Firefox tries to use
these formats:

* MJPG (0x47504a4d)
* YU12 (0x32315559)
* YUYV (0x56595559)
* UYVY (0x59565955)

Please add support for NV12 (0x3231564e) so that the Elgato Cam Link 4K
can be used directly as webcam input.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: firefox 83.0+build2-0ubuntu0.20.10.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
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu50.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  skipper4512 F pulseaudio
 /dev/snd/controlC0:  skipper4512 F pulseaudio
 /dev/snd/pcmC0D1p:   skipper4512 F...m pulseaudio
 /dev/snd/controlC1:  skipper4512 F pulseaudio
BuildID: 20201112153044
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: Unity:Unity7:ubuntu
Date: Tue Dec  1 23:24:23 2020
ForcedLayersAccel: False
IncompatibleExtensions:
 Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
 English (GB) Language Pack - langpack-en...@firefox.mozilla.org
 English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
 Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
IpRoute:
 default via 192.168.3.1 dev eth0 proto dhcp metric 100 
 169.254.0.0/16 dev eth0 scope link metric 1000 
 192.168.3.0/24 dev eth0 proto kernel scope link src 192.168.3.20 metric 100 
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:354
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=83.0/20201112153044 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to groovy on 2020-11-29 (2 days ago)
dmi.bios.date: 04/27/2013
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3904
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H67-M PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3904:bd04/27/2013:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug groovy

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

Title:
  Firefox does not NV12 for webcams

Status in firefox package in Ubuntu:
  New

Bug description:
  I use a Sony Alhpa camera attached to Elgato Cam Link 4K as webcam.
  The only color format that is working with Cam Link 4K is NV12. Sadly
  Firefox does not support NV12 (despite the source code containing
  several third party libraries that refer to NV12). Looking at the
  kernel log for the uvcvideo kernel module, I can see that Firefox
  tries to use these formats:

  * MJPG (0x47504a4d)
  * YU12 (0x32315559)
  * YUYV (0x56595559)
  * UYVY (0x59565955)

  Please add support for NV12 (0x3231564e) so that the Elgato Cam Link
  4K can be used directly as webcam input.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: firefox 83.0+build2-0ubuntu0.20.10.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
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  skipper4512 F pulseaudio
   /dev/snd/controlC0:  skipper4512 F pulseaudio
   /dev/snd/pcmC0D1p:   skipper4512 F...m pulseaudio
   /dev/snd/controlC1:  skipper4512 F pulseaudio
  BuildID: 20201112153044
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Dec  1 23:24:23 2020
  ForcedLayersAccel: False
  IncompatibleExtensions:
   Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Default - 

[Desktop-packages] [Bug 106737]

2020-12-01 Thread Realgrouchy
I've noticed a problematic behaviour as a consequence of this bug, which
I've described in Bug 104525, but since this thread is related and more
active, I thought I should mention it here too:

In TB 38.2.0 on OSX 10.10.5, when I try to rename a folder in a POP
account, I do *not* get the error until I dismiss the rename dialog.

As a result, if I click "Rename" X times in the rename dialog (with no
response from TB), it is only *after* I dismiss the rename dialog that I
get a succession of X error messages.

For the purposes of changing the case, this problem will be redundant
when this bug (Bug 92165) and/or Bug 104525 are resolved, but I've filed
it as a separate Bug 1207212 since this error also happens in non-bug
situations.

- RG>

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

Title:
  Renaming folder to same name but different case not allowed

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

Bug description:
  Binary package hint: mozilla-thunderbird

  In 1.5.0.10, renaming the folder "foo" to "foO", "fOo" or "Foo" isn't
  allowed; the OK button isn't clickable upon typing the new name.
  However, this can be worked around by renaming the folder "foo" to
  "bar" first, and then renaming "bar" to "foO".

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

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


[Desktop-packages] [Bug 106737]

2020-12-01 Thread Jorgk-bmo
I did a bit of debugging. folderPane.js:2605, folder.rename(aName, msgWindow);, 
calls nsImapMailFolder::Rename() which calls nsImapService::RenameLeaf() and 
that opens this URL via GetImapConnectionAndLoadUrl():
  
"imap://u...@mail.com@server:143/rename>.INBOX.TestMessages>.INBOX.testMessages"
Later we came into nsImapIncomingServer::OnlineFolderRename() and 
nsImapMailFolder::RenameClient() which does indeed call 
nsMsgDBFolder::PropagateDelete() as a comment in the patch suggests.

So that's all very well, but there appears to be some code missing to
remove the no longer existing folder from the UI.

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

Title:
  Renaming folder to same name but different case not allowed

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

Bug description:
  Binary package hint: mozilla-thunderbird

  In 1.5.0.10, renaming the folder "foo" to "foO", "fOo" or "Foo" isn't
  allowed; the OK button isn't clickable upon typing the new name.
  However, this can be worked around by renaming the folder "foo" to
  "bar" first, and then renaming "bar" to "foO".

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

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


[Desktop-packages] [Bug 106737]

2020-12-01 Thread Benc-q
Here are my notes - mostly a braindump for my own reference:


Local Folders

nsMsgLocalMailFolder::Rename() performs these steps:

1) calls nsIMsgPluggableStore::RenameFolder() to rename the raw filesystem 
artifacts:
 * mbox/maildir
 * any .sbd dir
 * .msf file (actually, I'm not sure this should be done by the msgStore)
2) updates the new folder's pretty name
3) checks up on any filters which might be referencing the folder
4) calls RenameSubFolders() which recursively creates new child folders, 
checking for filter usage as it goes.
5) detaches the old folder from the parent (and calls progagateDelete() on it) 
and adds the new one.
6) tells the nsIMsgFolderNotificationService that the folder has been renamed.


IMAP folders

nsImapMailFolder::Rename() just tells the server to rename the folder.
Later on, they'll be a nsImapIncomingServer::OnlineFolderRename() coming in, 
where the local imap folder renaming is handled.
I haven't picked all the way through this yet, but quick observations are:
1) if it's a virtual folder, it just calls nsMsgDBFolder::Rename() and leaves 
it at that.
2) the pluggable message store isn't used.
3) it calls both nsImapMailFolder::RenameClient() and 
nsImapMailFolder::RenameLocal(). RenameLocal() seems to be primarily concerned 
with renaming the local filesystem artifacts, while RenameClient() handles the 
folder hierarchy and assort imap-specific stuff.


Quick thoughts:

- The IMAP path should use the pluggable mail store to handle the filesystem 
artifacts.
- there _should_ be a whole heap of common functionality that can be shared 
between local and imap (including the nsMsgDBFolder::Rename() that imap virtual 
folders use).
- There's a whole load of folder deleting and rebuilding going on, which seems 
unnecessary and overly-complicated.
It seems like it _should_ be possible to just rename folders in place, rather 
than just ditching them completely and rebuilding them... (ie filesystem 
rename, then patch up affected URIs etc)
- that said, I'm sure this bug can be addressed with a quick-n-nasty patch for 
now.

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

Title:
  Renaming folder to same name but different case not allowed

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

Bug description:
  Binary package hint: mozilla-thunderbird

  In 1.5.0.10, renaming the folder "foo" to "foO", "fOo" or "Foo" isn't
  allowed; the OK button isn't clickable upon typing the new name.
  However, this can be worked around by renaming the folder "foo" to
  "bar" first, and then renaming "bar" to "foO".

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

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


[Desktop-packages] [Bug 106737]

2020-12-01 Thread Jorgk-bmo
(In reply to Ben Campbell from comment #140)
> It does fit in quite nicely with what I've been looking at with the
> EmptyTrash() implementation, so I'm happy to look at it ...
Thanks. I was in to minds and almost about to cancel the NI since this is going 
((too) far) into IMAP. But then on the other hand, we need to increase our 
backend knowledge of IMAP.

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

Title:
  Renaming folder to same name but different case not allowed

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

Bug description:
  Binary package hint: mozilla-thunderbird

  In 1.5.0.10, renaming the folder "foo" to "foO", "fOo" or "Foo" isn't
  allowed; the OK button isn't clickable upon typing the new name.
  However, this can be worked around by renaming the folder "foo" to
  "bar" first, and then renaming "bar" to "foO".

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

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


[Desktop-packages] [Bug 106737]

2020-12-01 Thread Benc-q
It does fit in quite nicely with what I've been looking at with the
EmptyTrash() implementation, so I'm happy to look at it (and in fact, I
just spent a couple of hours poking through the code from where Jorg
left off - I'll write up my thoughts).

I can run a profile off a vfat filesystem (usb stick or loopback
trickery) for case-insensitive filenames, I should be able to hit the
same issues as on Windows.

There is an issue even on Linux: if I rename an imap folder "aaa" ->
"Aaa", it looks fine in the GUI, but the old "aaa" directory will still
be on the filesystem. So something isn't quite right there.

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

Title:
  Renaming folder to same name but different case not allowed

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

Bug description:
  Binary package hint: mozilla-thunderbird

  In 1.5.0.10, renaming the folder "foo" to "foO", "fOo" or "Foo" isn't
  allowed; the OK button isn't clickable upon typing the new name.
  However, this can be worked around by renaming the folder "foo" to
  "bar" first, and then renaming "bar" to "foO".

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

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


[Desktop-packages] [Bug 106737]

2020-12-01 Thread UlfZibis
(In reply to Thomas D. (currently busy elsewhere; needinfo?me) from comment 
#131)
> The only scenario where this might fail are extra long nested folder names
> at the limit, where we might fail to create the tmp target folder if the tmp
> path gets too long or such.
To avoid this, you could just try to rename to fo1, fo2, ... foa, fob, ... 
until success. tmp may be already in use.

> because even some servers don't accept changing capitalization only, so we'd 
> elegantly trick those.
+1

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

Title:
  Renaming folder to same name but different case not allowed

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

Bug description:
  Binary package hint: mozilla-thunderbird

  In 1.5.0.10, renaming the folder "foo" to "foO", "fOo" or "Foo" isn't
  allowed; the OK button isn't clickable upon typing the new name.
  However, this can be worked around by renaming the folder "foo" to
  "bar" first, and then renaming "bar" to "foO".

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

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


[Desktop-packages] [Bug 106737]

2020-12-01 Thread Sherman-m
Postbox would be willing to sponsor the development of this fix if
anyone would like to work on this.

Requirements:

* Cannot be structured as an add-on (as those are no longer supported in 
Postbox)
* Cannot rely on changes or APIs made after 52.8 (as Postbox is currently based 
on this version)
* Must work on Windows 7, 8, and 10 and macOS 10.11 and higher.

If interested, let me know and we'll work out the details.

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

Title:
  Renaming folder to same name but different case not allowed

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

Bug description:
  Binary package hint: mozilla-thunderbird

  In 1.5.0.10, renaming the folder "foo" to "foO", "fOo" or "Foo" isn't
  allowed; the OK button isn't clickable upon typing the new name.
  However, this can be worked around by renaming the folder "foo" to
  "bar" first, and then renaming "bar" to "foO".

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

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


[Desktop-packages] [Bug 106737]

2020-12-01 Thread Acelists
I'd think that is would even be the final solution, not a workaround. We
can never know what filesystem we are really on (even if we knew, we do
not know all the limit or all exotic systems).

We must just try it. On any system, if we detect the new name only
changes in case, do the renaming dance comment 131 and comment 7
proposed. On on the high level TB does not allow 2 folders to exist if
they only differ in case (in CheckIfFolderExists). So this dance can be
already done in nsLocalMailFolder.cpp, I don't think we need to code it
in all the backends (mbox/maildir).

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

Title:
  Renaming folder to same name but different case not allowed

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

Bug description:
  Binary package hint: mozilla-thunderbird

  In 1.5.0.10, renaming the folder "foo" to "foO", "fOo" or "Foo" isn't
  allowed; the OK button isn't clickable upon typing the new name.
  However, this can be worked around by renaming the folder "foo" to
  "bar" first, and then renaming "bar" to "foO".

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

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


[Desktop-packages] [Bug 106737]

2020-12-01 Thread Jorgk-bmo
Created attachment 9013294
92165-v2.patch - rebased again

Carrying forward Kent's r-.

This actually works fine for a local folder, but it doesn't work for
IMAP. If you rename folder "Tests" to "tests" you end up with two
versions in the UI. In the subscribe dialogue you only get "tests" and
there's also only one "tests.msf" file. After a restart, the "Tests"
folder is gone. So the solution can't be far off. Of course it's missing
the maildir part which shouldn't be hard to add.

Since this is one of the TB "papercuts"
(https://wiki.mozilla.org/Thunderbird/Papercuts), maybe we can look at
this bug one day soon now.

Since Ben is already working a bit on fixing some maildir issues and
touching the relevant files, maybe he'd be a good candidate. Or maybe
not since this would need Windows to test? Just take it as a suggestions
since I can't allocate resources.

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

Title:
  Renaming folder to same name but different case not allowed

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

Bug description:
  Binary package hint: mozilla-thunderbird

  In 1.5.0.10, renaming the folder "foo" to "foO", "fOo" or "Foo" isn't
  allowed; the OK button isn't clickable upon typing the new name.
  However, this can be worked around by renaming the folder "foo" to
  "bar" first, and then renaming "bar" to "foO".

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

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


[Desktop-packages] [Bug 106737]

2020-12-01 Thread Vseerror
*** Bug 1485853 has been marked as a duplicate of this bug. ***

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

Title:
  Renaming folder to same name but different case not allowed

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

Bug description:
  Binary package hint: mozilla-thunderbird

  In 1.5.0.10, renaming the folder "foo" to "foO", "fOo" or "Foo" isn't
  allowed; the OK button isn't clickable upon typing the new name.
  However, this can be worked around by renaming the folder "foo" to
  "bar" first, and then renaming "bar" to "foO".

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

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


[Desktop-packages] [Bug 106737]

2020-12-01 Thread Alta88-t
*** Bug 1287718 has been marked as a duplicate of this bug. ***

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

Title:
  Renaming folder to same name but different case not allowed

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

Bug description:
  Binary package hint: mozilla-thunderbird

  In 1.5.0.10, renaming the folder "foo" to "foO", "fOo" or "Foo" isn't
  allowed; the OK button isn't clickable upon typing the new name.
  However, this can be worked around by renaming the folder "foo" to
  "bar" first, and then renaming "bar" to "foO".

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

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


[Desktop-packages] [Bug 106737]

2020-12-01 Thread Bugzilla2007
Aceman, given the high popularity of this bug, can't we use the workaround as 
an interim fix when
renaming foo to Foo:

sourcefolder=foo
targetfolder=Foo
if (lcase(sourcefolder) == lcase(targetfolder)) {
- first rename foo to foo.tmp_random
- then rename foo.tmp_random to Foo }

Renaming folders doesn't happen every day, so taking a split second longer 
doesn't matter.
That way, it'll work for all types of folders/OSs/POP/Imap no matter what 
(except for those where the server doesn't allow renaming).
Then, we can spend the next decades looking for the real fix. Or maybe this is 
the real fix, because even some servers don't accept changing capitalization 
only, so we'd elegantly trick those.
The only scenario where this might fail are extra long nested folder names at 
the limit, where we might fail to create the tmp target folder if the tmp path 
gets too long or such.

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

Title:
  Renaming folder to same name but different case not allowed

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

Bug description:
  Binary package hint: mozilla-thunderbird

  In 1.5.0.10, renaming the folder "foo" to "foO", "fOo" or "Foo" isn't
  allowed; the OK button isn't clickable upon typing the new name.
  However, this can be worked around by renaming the folder "foo" to
  "bar" first, and then renaming "bar" to "foO".

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

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


[Desktop-packages] [Bug 1905740] Re: SRU the current 3.36.5 stable update

2020-12-01 Thread Brian Murray
Hello Sebastien, or anyone else affected,

Accepted gnome-control-center into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-control-center/1:3.36.5-0ubuntu1 in a few hours, and then in the
-proposed repository.

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

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

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

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

** Changed in: gnome-control-center (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  SRU the current 3.36.5 stable update

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Focal:
  Fix Committed

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that the GNOME settings still work correctly

  * Regression potential

  Review the fixes in the update the things to try should include
  - replacing a keybinding
  - checking that connectivy changes are correctly reflected in settings and 
that informations are correctly displayed in the details screen
  - opening the printer panel to verify that ink levels are still correctly 
displayed
  - using the privacy screen to enable or disable screen sharing
  - going to the sound panel and change devices configurations

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

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


[Desktop-packages] [Bug 1905756] Re: SRU the current 3.36.8 stable update

2020-12-01 Thread Brian Murray
Hello Sebastien, or anyone else affected,

Accepted gnome-desktop3 into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
desktop3/3.36.8-0ubuntu1 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: gnome-desktop3 (Ubuntu Focal)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  SRU the current 3.36.8 stable update

Status in gnome-desktop3 package in Ubuntu:
  Fix Released
Status in gnome-desktop3 source package in Focal:
  Fix Committed

Bug description:
  * Impact
  That's the current GNOME stable update, including some translation updates
  https://gitlab.gnome.org/GNOME/gnome-desktop/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that a GNOME session still works correctly, including changing
  the background image, locale and screen settings. The GNOME version in
  setting should also be 3.36.8

  * Regression potential

  The update has some test and translations fixes and a change the
  version, check that translations and version display in settings are
  correct.

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

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


[Desktop-packages] [Bug 1898656] Re: Firefox not playing YouTube videos in Virtualbox on Xubuntu

2020-12-01 Thread Olivier Tilloy
That sounds like a possible upstream issue, so it would be useful to
report it there.

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

Title:
  Firefox not playing YouTube videos in Virtualbox on Xubuntu

Status in firefox package in Ubuntu:
  New

Bug description:
  In Xubuntu Firefox does not play videos of e.g. YouTube or the Dutch
  TV Viewer. It works in all other Virtualbox VMs with e.g. Ubuntu
  20.04, Ubuntu 16.04 or Windows 10 Pro. The problem is related to the
  buffering (stats for nerds). It build up the buffer and when the
  buffer reaches its value, it plays the content of the buffer in a few
  milli seconds. Afterwards it starts again with the same process.

  I have reinstalled firefox, but the problems remains (apt --reinstall
  install firefox)

  The problem is independent on the selection of the hw acceleration in
  the firefox preferences.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 81.0+build2-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bertadmin   1398 F pulseaudio
   /dev/snd/pcmC0D0p:   bertadmin   1398 F...m pulseaudio
   /dev/snd/timer:  bertadmin   1398 f pulseaudio
  BuildID: 20200917005511
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Mon Oct  5 23:12:41 2020
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-03-11 (940 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  IpRoute:
   default via 192.168.1.1 dev enp0s3 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s3 scope link metric 1000 
   192.168.1.0/24 dev enp0s3 proto kernel scope link src 192.168.1.111 metric 
100
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=81.0/20200917005511 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to focal on 2020-03-04 (215 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Desktop-packages] [Bug 1903329] Please test proposed package

2020-12-01 Thread Brian Murray
Hello Salim, or anyone else affected,

Accepted librsvg into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/librsvg/2.48.9-1ubuntu0.20.04.1 in
a few hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  SRU the current 2.48.9 stable update

Status in librsvg package in Ubuntu:
  Fix Released
Status in librsvg source package in Focal:
  Fix Committed

Bug description:
  * Impact

  That's the current GNOME stable update, which fixes a number of
  issues, including a regression[1] since librsvg 2.40.x which was
  shipped in Ubuntu 16.04. The NEWS file[2] summarizes the relevant
  changes between Ubuntu 20.04's current librsvg 2.48.7 (that version
  was also introduced by an SRU back in July[3]) and the current version
  2.48.9. The complete list of changes is available on GNOME GitLab[4].

  * Test case

  The update is part of GNOME stable updates[5].

  Smoke testing by opening SVG images with eog or importing them with
  gimp can be performed to ensure there are no regressions.

  * Regression potential

  This is a bugfix-only stable micro-release, however librsvg is a core
  component with a number of reverse dependencies. A combination of
  autopkgtests and manual smoke testing to try and detect SVG rendering
  issues should be performed.

  * Notes about this report

  This is my first SRU request (and at the same time my first launchpad
  bug report). I'm not really familiar with the whole SRU process which
  is why I first asked about it on Ubuntu's official discourse forum[6].
  Canonical's Sebastien Bacher encouraged me to open this ticket. I've
  copied over some parts of the last librsvg SRU ticket[3]. I hope this
  is fine.

  Thanks for considering this SRU.

  [1]: https://gitlab.gnome.org/GNOME/librsvg/-/issues/642

  [2]: https://gitlab.gnome.org/GNOME/librsvg/-/blob/librsvg-2.48/NEWS

  [3]: https://bugs.launchpad.net/bugs/1884326

  [4]: https://gitlab.gnome.org/GNOME/librsvg/-/compare/2.48.7...2.48.9

  [5]: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [6]: https://discourse.ubuntu.com/t/most-straight-forward-way-to-get-
  librsvg2-microrelease-update-into-focal-updates/19238

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

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


[Desktop-packages] [Bug 1903329] Re: SRU the current 2.48.9 stable update

2020-12-01 Thread Brian Murray
Should groovy also get the fix for upstream issue 642?

** Changed in: librsvg (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  SRU the current 2.48.9 stable update

Status in librsvg package in Ubuntu:
  Fix Released
Status in librsvg source package in Focal:
  Fix Committed

Bug description:
  * Impact

  That's the current GNOME stable update, which fixes a number of
  issues, including a regression[1] since librsvg 2.40.x which was
  shipped in Ubuntu 16.04. The NEWS file[2] summarizes the relevant
  changes between Ubuntu 20.04's current librsvg 2.48.7 (that version
  was also introduced by an SRU back in July[3]) and the current version
  2.48.9. The complete list of changes is available on GNOME GitLab[4].

  * Test case

  The update is part of GNOME stable updates[5].

  Smoke testing by opening SVG images with eog or importing them with
  gimp can be performed to ensure there are no regressions.

  * Regression potential

  This is a bugfix-only stable micro-release, however librsvg is a core
  component with a number of reverse dependencies. A combination of
  autopkgtests and manual smoke testing to try and detect SVG rendering
  issues should be performed.

  * Notes about this report

  This is my first SRU request (and at the same time my first launchpad
  bug report). I'm not really familiar with the whole SRU process which
  is why I first asked about it on Ubuntu's official discourse forum[6].
  Canonical's Sebastien Bacher encouraged me to open this ticket. I've
  copied over some parts of the last librsvg SRU ticket[3]. I hope this
  is fine.

  Thanks for considering this SRU.

  [1]: https://gitlab.gnome.org/GNOME/librsvg/-/issues/642

  [2]: https://gitlab.gnome.org/GNOME/librsvg/-/blob/librsvg-2.48/NEWS

  [3]: https://bugs.launchpad.net/bugs/1884326

  [4]: https://gitlab.gnome.org/GNOME/librsvg/-/compare/2.48.7...2.48.9

  [5]: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [6]: https://discourse.ubuntu.com/t/most-straight-forward-way-to-get-
  librsvg2-microrelease-update-into-focal-updates/19238

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

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


[Desktop-packages] [Bug 1895422] Re: Sound card not detected on Dell Latitude 9510 (Realtek ALC711)

2020-12-01 Thread Neil Burcham
Has anyone put together a step-by-step tutorial (written or video), to
give a little detailed direction to these steps?

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

Title:
  Sound card not detected on Dell Latitude 9510 (Realtek ALC711)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I am running Ubuntu 20.04.01 LTS, kernel version 5.6.0-1027-oem
  (checked via uname -r).

  
  I believe my sound card is not being detected by Ubuntu.  I checked the 
serial number and via BIOS (which I've upgraded to the latest version) 
according to the specs 
(https://topics-cdn.dell.com/pdf/latitude-15-9510-2-in-1-laptop_owners-manual5_en-us.pdf)
 the sound controller/speaker should be Realtek ALC711-CG / Realtek ALC1309D.

  However, when I run lspci only the following device appears:
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device 
[8086:02c8]

  In alsamixer, only the HDMI port appears.

  alsa-info output: http://alsa-
  project.org/db/?f=f2b70f6eb1a237378bf563cacb6f192ce0a677c3

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

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


[Desktop-packages] [Bug 1904079] Re: acute+C on US international with dead keys layout should produce cedilla sign (ç)

2020-12-01 Thread Olivier Tilloy
With that layout, I can get "ç" by using the AltGr+, (AltGr and comma key).
That is what the keyboard layout cheat sheet advertises for ç, by the way, so 
I'm not sure why acute+C would/should work.
Can you confirm that AltGr+, gets you a "ç" ?

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

Title:
  acute+C on US international with dead keys layout should produce
  cedilla sign (ç)

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I've been facing a really strange bug in Ubuntu 20.04. My laptop has
  Brazilian Portuguese layout (ABNT-2) but my external keyboard has a US
  layout. So, in order to get a cedilla sign <ç> on those keyboards, I
  have to change layout to US International with Dead Keys and use an
  acute accent plus C <'+c>.

  Everything works fine unless inside the Chromium (installed from
  snap). In this case I get an accented c <ć>. So, I don't have a way to
  get a ç inside chrome, which is used in Portuguese. I'm using chromium
  from stable channel.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  Uname: Linux 5.4.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 12 22:24:50 2020
  InstallationDate: Installed on 2020-11-07 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Snap: chromium 86.0.4240.198 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1906450] Re: [snap] snap & deb duplicate entries in snap-store

2020-12-01 Thread Olivier Tilloy
** Also affects: snap-store-desktop
   Importance: Undecided
   Status: New

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

Title:
  [snap] snap & deb duplicate entries in snap-store

Status in snap-store-desktop:
  New
Status in thunderbird package in Ubuntu:
  New

Bug description:
  Hi,

  Thunderbird snap & deb are displayed separately in Snap Store.

  This does not help beginners to find out which version has to be
  installed. Additionally we should briefly explain, in Snap Store
  description, the differences between these two packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-store-desktop/+bug/1906450/+subscriptions

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


[Desktop-packages] [Bug 1905122] Re: firefox xubuntu.20.04.1 don`t work localization

2020-12-01 Thread Alex_ander
Yes, it's okay now. But may break on next firefox update.
I will write about it.

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

Title:
  firefox xubuntu.20.04.1 don`t work localization

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  When I install Xubuntu-20-04-1.iso with russian language for OS jn
  Virtualbox Computer, Firefox don`t have russian locale. I install all
  localization files and set in Firefox russian language manually. But
  anytime when I install firefox updates language settings automatically
  sets to english.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 83.0+build2-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  olex782 F pulseaudio
  BuildID: 20201112153044
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Sat Nov 21 12:33:07 2020
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:354
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-11-21 (0 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  IpRoute:
   default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 
   10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 
   169.254.0.0/16 dev enp0s3 scope link metric 1000
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:354
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=83.0/20201112153044
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Desktop-packages] [Bug 462564]

2020-12-01 Thread Mikekaganski
*** Bug 138602 has been marked as a duplicate of this bug. ***

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

Title:
  [Upstream] Deleting a column in Writer deletes whole table

Status in LibreOffice:
  Confirmed
Status in OpenOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Triaged
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  1)  lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
    Installed: 1:3.3.3-1ubuntu2
    Candidate: 1:3.3.3-1ubuntu2
    Version table:
   *** 1:3.3.3-1ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.3.2-1ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  3) What is expected to happen in LibreOffice Writer via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/462564/+attachment/894856/+files/test.odt
  && lowriter -nologo test.odt

  is when one highlights the second column of the table -> secondary
  clicks -> Column -> Delete is only that column is deleted. Please see
  movie for more details:
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/462564/+attachment/894864/+files/out.ogv

  4) What happens instead is the whole table is deleted.

  Reproducible in:
  lsb_release -rd
  Description:  Ubuntu precise (development branch)
  Release:  12.04

  apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:3.5.2-2ubuntu1
Candidate: 1:3.5.2-2ubuntu1
Version table:
   *** 1:3.5.2-2ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
  100 /var/lib/dpkg/status

  WORKAROUND: Split the table then delete the column.

  WORKAROUND: Use Word via WINE.

  Microsoft Office Word 2003 (11.5604.6505)

  apt-cache policy wine1.3
  wine1.3:
    Installed: 1.3.28-0ubuntu1~ppa1~natty1
    Candidate: 1.3.28-0ubuntu1~ppa1~natty1
    Version table:
   *** 1.3.28-0ubuntu1~ppa1~natty1 0
  500 http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu/ natty/main i386 
Packages
  100 /var/lib/dpkg/status
   1.3.15-0ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages

  ProblemType: Bug
  Architecture: amd64
  Date: Wed Oct 28 09:43:20 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: fglrx
  Package: openoffice.org-core 1:3.1.1-5ubuntu1
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: openoffice.org
  Uname: Linux 2.6.31-14-generic x86_64

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

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


[Desktop-packages] [Bug 1906450] [NEW] [snap] snap & deb duplicate entries in snap-store

2020-12-01 Thread Francois Thirioux
Public bug reported:

Hi,

Thunderbird snap & deb are displayed separately in Snap Store.

This does not help beginners to find out which version has to be
installed. Additionally we should briefly explain, in Snap Store
description, the differences between these two packages.

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

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

Title:
  [snap] snap & deb duplicate entries in snap-store

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Hi,

  Thunderbird snap & deb are displayed separately in Snap Store.

  This does not help beginners to find out which version has to be
  installed. Additionally we should briefly explain, in Snap Store
  description, the differences between these two packages.

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

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


[Desktop-packages] [Bug 1897369] Re: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)

2020-12-01 Thread Sebastien Bacher
** Changed in: cups (Ubuntu)
   Importance: Undecided => Low

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

Title:
  apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 20.04.1 with *cups-browsed* 1.27.4-1, apparmor prevents
  `/usr/sbin/cups-browsed` to change its nice value.

  $ sudo dmesg | grep apparmor
  [541870.509461] audit: type=1400 audit(1600898428.089:60): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=62030 comm="cups-browsed" capability=23  capname="sys_nice"
  [628298.779668] audit: type=1400 audit(1600984854.115:61): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=66850 comm="cups-browsed" capability=23  capname="sys_nice"
  [714667.424963] audit: type=1400 audit(1601071220.527:62): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=76828 comm="cups-browsed" capability=23  capname="sys_nice"

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

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


[Desktop-packages] [Bug 1905344] Re: [snap] thunderbird seccomp profile missing a few syscalls

2020-12-01 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  [snap] thunderbird seccomp profile missing a few syscalls

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Launching thunderbird's snap result in the following logs:

  Nov 23 20:07:37 simon-lemur kernel: audit: type=1326 
audit(1606180057.636:655): auid=1000 uid=1000 gid=1000 ses=2 pid=8588 
comm="thunderbird-bin" exe="/snap/thunderbird/95/thunderbird-bin" sig=0 
arch=c03e syscall=203 compat=0 ip=0x7f198a2d5b9f code=0x5
  Nov 23 20:07:37 simon-lemur kernel: audit: type=1326 
audit(1606180057.640:656): auid=1000 uid=1000 gid=1000 ses=2 pid=8588 
comm="thunderbird-bin" exe="/snap/thunderbird/95/thunderbird-bin" sig=0 
arch=c03e syscall=203 compat=0 ip=0x7f198a2d5b9f code=0x5
  Nov 23 20:07:37 simon-lemur kernel: audit: type=1326 
audit(1606180057.640:657): auid=1000 uid=1000 gid=1000 ses=2 pid=8588 
comm="thunderbird-bin" exe="/snap/thunderbird/95/thunderbird-bin" sig=0 
arch=c03e syscall=203 compat=0 ip=0x7f198a2d5b9f code=0x5
  Nov 23 20:07:37 simon-lemur kernel: audit: type=1326 
audit(1606180057.640:658): auid=1000 uid=1000 gid=1000 ses=2 pid=8588 
comm="thunderbird-bin" exe="/snap/thunderbird/95/thunderbird-bin" sig=0 
arch=c03e syscall=203 compat=0 ip=0x7f198a2d5b9f code=0x5
  Nov 23 20:07:38 simon-lemur kernel: audit: type=1326 
audit(1606180058.356:659): auid=1000 uid=1000 gid=1000 ses=2 pid=8512 
comm=64636F6E6620776F726B6572 exe="/snap/thunderbird/95/thunderbird-bin" sig=0 
arch=c03e syscall=314 compat=0 ip=0x7f19894aa959 code=0x5

  $ aa-decode 64636F6E6620776F726B6572
  Decoded: dconf worker

  So syscall 203 (sys_sched_setaffinity?) and 314 (sys_sched_setattr?)
  are not permitted.

  
  Additional information:

  $ lsb_release -rd
  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04

  $ uname -a
  Linux simon-lemur 5.4.0-53-generic #59~18.04.1-Ubuntu SMP Wed Oct 21 12:14:56 
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

  $ snap info thunderbird
  name:  thunderbird
  summary:   Mozilla Thunderbird email application
  publisher: Canonical✓
  store-url: https://snapcraft.io/thunderbird
  contact:   https://launchpad.net/distros/ubuntu/+source/thunderbird
  license:   unset
  description: |
Thunderbird is a free and open source email, newsfeed, chat, and 
calendaring client, that’s easy
to set up and customize. One of the core principles of Thunderbird is the 
use and promotion of
open standards - this focus is a rejection of our world of closed platforms 
and services that
can’t communicate with each other. We want our users to have freedom and 
choice in how they
communicate.
  commands:
- thunderbird
  snap-id:  k1Ml1O9GzSO2QftV0ZlWSbUfQ78nN460
  tracking: latest/stable
  refresh-date: today at 20:00 EST
  channels:
latest/stable:78.5.0 2020-11-18 (95) 69MB -
latest/candidate: ↑   
latest/beta:  ↑   
latest/edge:  78.5.0 2020-11-18 (95) 69MB -
  installed:  78.5.0(95) 69MB -

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

-- 
Mailing list: https://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 1906316] Re: Xorg crash

2020-12-01 Thread Vonschutter
Daniel,
these are the files in the location you suggested:

_opt_brave.com_brave_brave.1000.crash
_usr_bin_blueman-applet.1000.crash
 _usr_bin_ksysguard.1000.crash
 _usr_bin_tilix.1000.crash
_opt_brave.com_brave_brave.1000.upload
_usr_bin_blueman-applet.1000.upload
_usr_bin_ksysguard.1000.upload
_usr_bin_tilix.1000.upload
_opt_brave.com_brave_brave.1000.uploaded
_usr_bin_blueman-applet.1000.uploaded
_usr_bin_ksysguard.1000.uploaded
_usr_bin_tilix.1000.uploaded
_usr_bin_baloo_file.1000.crash
 _usr_bin_kglobalaccel5.1000.crash
_usr_bin_nautilus.1000.crash
_usr_lib_x86_64-linux-gnu_libexec_DiscoverNotifier.1000.crash
_usr_bin_baloo_file.1000.upload
_usr_bin_kglobalaccel5.1000.upload
_usr_bin_nautilus.1000.upload
_usr_lib_x86_64-linux-gnu_libexec_DiscoverNotifier.1000.upload
_usr_bin_baloo_file.1000.uploaded
_usr_bin_kglobalaccel5.1000.uploaded
_usr_bin_nautilus.1000.uploaded
_usr_lib_x86_64-linux-gnu_libexec_DiscoverNotifier.1000.uploaded

which ones are you interested in?

In this case it seemed like gdm3 just restarted all of a sudden while I was
in the application Tilix messing with the app dialog.

Please note that sometimes my screen will freeze. However, when I unplug
the HDMI and plug it back in again it will often release and I can work
again. The problem seems to be less frequent now that i have switched to
using the Video only (DP 1.4a).

HW:
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM
Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core
Processor PCI Express x16 Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
Family USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series
Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
Family USB EHCI #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High
Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family
PCI Express Root Port #1 (rev d5)
00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family
PCI Express Root Port #4 (rev d5)
00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family
PCI Express Root Port #5 (rev d5)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
Family USB EHCI #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation B85 Express LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset
Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus
Controller (rev 05)
01:00.0 VGA compatible controller: NVIDIA Corporation TU116 [GeForce GTX
1660 Ti] (rev a1)
01:00.1 Audio device: NVIDIA Corporation TU116 High Definition Audio
Controller (rev a1)
01:00.2 USB controller: NVIDIA Corporation TU116 USB 3.1 Host Controller
(rev a1)
01:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU116 [GeForce GTX
1650 SUPER] (rev a1)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
04:00.0 Network controller: Intel Corporation Wireless 3160 (rev 83)


Kind regards
___
)
¸.·´¸.·*´¨)
(¸.·´ (¸. Stephan


Stephan Schutter

Cell: +46 70 641 3983
Profile: http://www.linkedin.com/in/stephanschutter
Email:  stephan.schut...@gmail.com


This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you have
received it in error, please notify the sender immediately and delete the
original. Any other use of the email by you is prohibited.


On Tue, Dec 1, 2020 at 4:00 AM Daniel van Vugt <1906...@bugs.launchpad.net>
wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. It sounds like some part of the system has crashed. To
> help us find the cause of the crash please follow these steps:
>
> 1. Look in /var/crash for crash files and if found run:
> ubuntu-bug YOURFILE.crash
> Then tell us the ID of the newly-created bug.
>
> 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
> ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
> Do you find any links to recent problems on that page? If so then please
> send the links to us.
>
> 3. If step 2 also failed then apply the workaround from bug 994921,
> reboot, reproduce the crash, and retry step 1.
>
> Please take care to avoid attaching .crash files to bugs as we are
> unable to process them as file attachments. It would also be a security
> risk for yourself.
>
> ** Tags added: nvidia
>
> ** Summary changed:
>
> - Xorg crash
> + [nvidia] Xorg crash
>
> ** Changed in: xorg-server (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 

[Desktop-packages] [Bug 1906449] [NEW] Xorg randomly freezes

2020-12-01 Thread Kuroš Taheri-Golværzi
Public bug reported:

Initially, I thought it only happened during file transfers (because
that's when it happens most often), but I later found that it can happen
at any time, because I just turned my computer on, went to go make a
coffee, have a cigarette, and when I came back, the entire screen,
desktop, system, etc had frozen again. I always need to hold the power
button down to do an emergency restart, because I can't even use Alt+F#
to get into the TTY.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
Uname: Linux 5.4.0-56-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.95.01  Thu May 28 07:03:08 
UTC 2020
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Tue Dec  1 12:28:44 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 440.95.01, 5.4.0-56-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Continuously
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:1e21]
 Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21]
InstallationDate: Installed on 2020-12-01 (0 days ago)
InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=UUID=11577769-570c-4297-a9b2-35fb3a30f6bf ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/02/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FA506IV.309
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: FA506IV
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.:bvrFA506IV.309:bd07/02/2020:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: TUF Gaming FA506IV
dmi.product.name: TUF Gaming FA506IV_TUF506IV
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
nvidia-settings:
 ERROR: Unable to load info from any available system
 
 
 ERROR: Unable to load info from any available system
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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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

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


** Tags: amd64 apport-bug focal freeze ubuntu

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

Title:
  Xorg randomly freezes

Status in xorg package in Ubuntu:
  New

Bug description:
  Initially, I thought it only happened during file transfers (because
  that's when it happens most often), but I later found that it can
  happen at any time, because I just turned my computer on, went to go
  make a coffee, have a cigarette, and when I came back, the entire
  screen, desktop, system, etc had frozen again. I always need to hold
  the power button down to do an emergency restart, because I can't even
  use Alt+F# to get into the TTY.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  NonfreeKernelModules: 

[Desktop-packages] [Bug 1897369] Re: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)

2020-12-01 Thread Till Kamppeter
I have searched the code of cups-browsed and libcupsfilters and did not
find any call of the mentioned functions which require CAP_SYS_NICE.
Most probably some of the library functions cups-browsed is using
contains such calls.

As cups-browsed works correctly I suggest to add the "deny capability
sys_nice," to silence the log messages.

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

Title:
  apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 20.04.1 with *cups-browsed* 1.27.4-1, apparmor prevents
  `/usr/sbin/cups-browsed` to change its nice value.

  $ sudo dmesg | grep apparmor
  [541870.509461] audit: type=1400 audit(1600898428.089:60): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=62030 comm="cups-browsed" capability=23  capname="sys_nice"
  [628298.779668] audit: type=1400 audit(1600984854.115:61): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=66850 comm="cups-browsed" capability=23  capname="sys_nice"
  [714667.424963] audit: type=1400 audit(1601071220.527:62): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=76828 comm="cups-browsed" capability=23  capname="sys_nice"

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

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


[Desktop-packages] [Bug 1905322] Re: LibreOffice crashes under load.

2020-12-01 Thread Leó Kolbeinsson
@hellsworth Heather Ellsworth

In order to reproduce the crash this is the proceedure you need to use -

1. Open in this order - calc,draw,impress (do not select a template at this 
time,proceed and select math and then writer from the menu. 
2. Now select the vivid template (which should be on the desktop - 
3. the crash occurs

I have not been able to reproduce thi unless apps opened in this order.

Also I tested as per your instructions in #18 - this crash did not
occur.

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

Title:
  LibreOffice crashes under load.

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  apt-cache policy libreoffice
  libreoffice:
Installed: (none)
Candidate: 1:7.0.3-0ubuntu1
Version table:
   1:7.0.3-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages

  I expect to be able to open all of LibreOffice's apps at once and use
  them.

  If you open all the LibreOffice applications and then select a
  template for LibreOffice Writer, they all close immediately, reopen,
  and offer to recover any lost data.

  Error reports may have been sent. I am not sure as this is Hirsute and
  I'm testing it.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu51
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: LXQt
  Date: Mon Nov 23 20:06:19 2020
  LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201123)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1906146] Re: Firefox does not auto-play Twitter videos in 20.10 Ubuntu

2020-12-01 Thread Olivier Tilloy
Can you try installing libavcodec58 ?

sudo apt install libavcodec58

Does it fix the problem?

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

Title:
  Firefox does not auto-play Twitter videos in 20.10 Ubuntu

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Hello!
  Been facing this problem since many Ubuntu editions ...

  Firefox is the default browser but does not play auto-play videos in
  Twitter. How to fix this - it becomes cumbersome to copy URL to Chrome
  and see it ...

  Any solution?

  Thanks.
  Akash
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  akash  1152 F pulseaudio
  BuildID: 20201012085804
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 20.10
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-11-27 (2 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  IpRoute:
   default via 192.168.225.1 dev wlp1s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp1s0 scope link metric 1000 
   192.168.225.0/24 dev wlp1s0 proto kernel scope link src 192.168.225.79 
metric 600
  Package: firefox 81.0.2+build1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=81.0.2/20201012085804
  RunningIncompatibleAddons: False
  Tags:  groovy
  Uname: Linux 5.8.0-25-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: 01/05/2018
  dmi.bios.release: 5.12
  dmi.bios.version: HQ-BI-11.6-Y116AR130-AA34O-011
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: WEIBU
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.version: To be filled by O.E.M.
  dmi.ec.firmware.release: 11.5
  dmi.modalias: 
dmi:bvn:bvrHQ-BI-11.6-Y116AR130-AA34O-011:bd01/05/2018:br5.12:efr11.5:svniBall:pnMeritG9:pvrTobefilledbyO.E.M.:rvnWEIBU:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvn:ct10:cvrTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MeritG9
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: iBall
  mtime.conffile..etc.apport.crashdb.conf: 2020-11-29T18:35:36.913752

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

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


[Desktop-packages] [Bug 1897249] Re: Scrolling in Chromium stops working when moving mouse when running in virtual machine

2020-12-01 Thread Lars Rustand
I'm not using the virtual machine anymore so I can't check it right now,
but it shouldn't be hard to reproduce if anyone wants to follow up.

Like I mentioned in the linked Chromium bug, this happens in both
Virtualbox and VMWare, so this is not specific to either one of them. I
can't remember if I ever tried uninstalling guest additions (although I
think so).

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

Title:
  Scrolling in Chromium stops working when moving mouse when running in
  virtual machine

Status in chromium-browser package in Ubuntu:
  Incomplete
Status in falkon package in Ubuntu:
  New
Status in qutebrowser package in Ubuntu:
  New
Status in chromium package in Arch Linux:
  New
Status in chromium package in openSUSE:
  New

Bug description:
  When Ubuntu is running in a virtual machine scrolling in Chromium
  stops working when moving the mouse even the slightest. Also the first
  scroll step is always ignored after moving the mouse. This results in
  a very uneven scrolling which is very difficult to use. Scrolling
  works perfectly in other applications like for example Firefox.

  This bug seems to have appeared in Ubuntu 16.04.0, as all Ubuntu
  releases before 16.04 works correctly, while all releases after 16.04
  are affected by this bug. Ubuntu is not the only distro that has this
  bug, but there are also several distros that are not affected by it.

  My current testing have shown the following distros to be affected:
  - Arch Linux
  - Linux Mint 20 Cinnamon
  - Manjaro XFCE 20.1
  - OpenSUSE Tumbleweed
  - Ubuntu 16.04, 18.04, 20.04

  And the following distros and operating systems are NOT affected:
  - Centos 8
  - Debian 10 (Buster)
  - DragonFly BSD 5.8.1
  - Fedora 32
  - GhostBSD 20.08.04
  - Ubuntu 12.04 to 15.10
  - Windows 10

  The fact that there are current updated distros that are unaffected
  indicates to me that this is probably not a bug in Chromium upstream,
  but I've not been able to pinpoint whether the problem is caused by
  something in the Chromium packaged by Ubuntu or some other difference
  in the system like the kernel or system libraries.

  I have already reported the bug to Chromium, link to the bug report
  here: https://bugs.chromium.org/p/chromium/issues/detail?id=1128405.

  There is also another bug report here:
  https://bugs.chromium.org/p/chromium/issues/detail?id=1100179

  
  I've already spent well over a week trying to troubleshoot this issue. I'm 
willing to do most of the work myself, but I really need some guidance as to 
what are the best next steps in troubleshooting this. Any help would be greatly 
appreciated!

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

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


[Desktop-packages] [Bug 1873713] Re: appstreamcli: symbol lookup error: appstreamcli: undefined symbol: AS_APPSTREAM_METADATA_PATHS

2020-12-01 Thread Olivier Tilloy
Wileam, this appears to be an entirely different problem than the one
originally discussed here. Please file a separate bug by running
`ubuntu-bug chromium-browser`. Thanks.

** No longer affects: chromium-browser (Ubuntu)

** No longer affects: chromium-browser

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

Title:
  appstreamcli: symbol lookup error: appstreamcli: undefined symbol:
  AS_APPSTREAM_METADATA_PATHS

Status in Ubuntu:
  Fix Released

Bug description:
  After upgrading from Kubuntu 18.04 to 20.04 I started getting this
  error:

  ```
  ~ $ sudo apt update 
  Hit:1 http://us.archive.ubuntu.com/ubuntu focal InRelease
  Hit:2 http://security.ubuntu.com/ubuntu focal-security InRelease
  Hit:3 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease
  Hit:4 https://packages.cloud.google.com/apt cloud-sdk InRelease
  Hit:5 http://us.archive.ubuntu.com/ubuntu focal-backports InRelease
  appstreamcli: symbol lookup error: appstreamcli: undefined symbol: 
AS_APPSTREAM_METADATA_PATHS
  Reading package lists... Done
  E: Problem executing scripts APT::Update::Post-Invoke-Success 'if 
/usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then 
appstreamcli refresh-cache > /dev/null; fi'
  E: Sub-process returned an error code
  ```

  Other required information:
  ```
  ~ $ lsb_release -rd
  Description:Ubuntu 20.04 LTS
  Release:20.04
  ```

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

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


[Desktop-packages] [Bug 1899041] Re: Gnome-Network-Displays crashes with Intel Wireless AC due to wpasupplicant

2020-12-01 Thread Launchpad Bug Tracker
This bug was fixed in the package wpa - 2:2.9-1ubuntu9

---
wpa (2:2.9-1ubuntu9) hirsute; urgency=medium

  * debian/patches/git_name_limit.patch:
- backport a fix for a segfault which is impacting the GNOME display
  sharing option (lp: #1899041)

 -- Sebastien Bacher   Tue, 01 Dec 2020 13:53:43
+0100

** Changed in: wpa (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Gnome-Network-Displays crashes with Intel Wireless AC due to
  wpasupplicant

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa package in Debian:
  Unknown

Bug description:
  When using Gnome-Network-Displays on a laptop with an Intel Wireless
  AC 9462/9560 card, wpasupplicant crashes. This reproducible bug can be
  fixed with this patch:

  
https://patchwork.ozlabs.org/project/hostap/patch/20200825062902.124600-1-benja...@sipsolutions.net/

  A further description can be found here:

  https://gitlab.gnome.org/GNOME/gnome-network-displays/-/issues/157

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

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


[Desktop-packages] [Bug 1901609] Re: signond causes qprocess crash

2020-12-01 Thread Launchpad Bug Tracker
This bug was fixed in the package signon - 8.59+17.10.20170606-0ubuntu3

---
signon (8.59+17.10.20170606-0ubuntu3) hirsute; urgency=medium

  * Add ubuntu_01_rtti.diff to remove the no rtti flags as they'd
break compatibility with QProcess (LP: #1901609)
  * Build depend on quilt and integrate into debian/rules. Since this
this source uses the legacy v1 format we need to manually wire up
patching instead of having dpkg-source handle it

 -- Harald Sitter   Mon, 23 Nov 2020 13:24:59 +0100

** Changed in: signon (Ubuntu Hirsute)
   Status: Fix Committed => Fix Released

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

Title:
  signond causes qprocess crash

Status in signon package in Ubuntu:
  Fix Released
Status in signon source package in Focal:
  Confirmed
Status in signon source package in Groovy:
  Confirmed
Status in signon source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Without the patch users are unable to add google accounts because signond 
crashes.
  This prevents users from using KDE's online accounts feature for google.
  The fix for this is to drop the no-rtti compile flag as qprocess relies on 
type info. This has no real downside for the user as it simply brings in type 
info.

  [Test Case]

  - in a plasma session
  - install kio-gdrive
  - run `systemsettings5 kcm_kaccounts`
  - add a new account
  - click on google
  - wait for login window to appear
  - signond shouldn't be crashing

  [Where problems could occur]

  Cannot think of any. It simply adds type info to the objects. Also
  upstream has rtti disabled for months and I'm not aware of any
  problems.

  [Other Info]

  This is a fairly grave issue as far as user experience is concerned.

  
  

  
  I'm reporting this bug upstream from where I found it, since I've learned 
that the signond package in KDE Neon is sourced from Ubuntu focal.

  This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64)
  from Focal Fossa

  Steps to reproduce:

  1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon)
  2. Install the kaccounts integration and kio-gdrive packages.
  3. Open System settings and navigate to "Online Accounts"
  4. Press "+ Add New Account"
  5. Select "Google"

  Observed behaviour:

  - Window that would ask for authentication fails to load, and Online Accounts 
goes back to overview
  - system logs show a segfault in libqt5core.so which can be traced to a 
failure in qporcess, casued by signond (see links for further details)

  Expected behaviour:
  - New window opens with a webview where Google authentication credentials can 
be posted.
  - When qprocess runs it does not crash.

  Further reference information at the following links:

  1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034

  3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts-
  sso/signond/-/merge_requests/27

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

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


[Desktop-packages] [Bug 1905122] Re: firefox xubuntu.20.04.1 don`t work localization

2020-12-01 Thread Olivier Tilloy
Ok, so what happens if you delete the second file (langpack-
r...@firefox.mozilla.org.xpi) and restart firefox? Is the interface
correctly localized in Russian?

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

Title:
  firefox xubuntu.20.04.1 don`t work localization

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  When I install Xubuntu-20-04-1.iso with russian language for OS jn
  Virtualbox Computer, Firefox don`t have russian locale. I install all
  localization files and set in Firefox russian language manually. But
  anytime when I install firefox updates language settings automatically
  sets to english.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 83.0+build2-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  olex782 F pulseaudio
  BuildID: 20201112153044
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Sat Nov 21 12:33:07 2020
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:354
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-11-21 (0 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  IpRoute:
   default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 
   10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 
   169.254.0.0/16 dev enp0s3 scope link metric 1000
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:354
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=83.0/20201112153044
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Desktop-packages] [Bug 1897249] Re: Scrolling in Chromium stops working when moving mouse when running in virtual machine

2020-12-01 Thread Olivier Tilloy
You linked to a virtualbox forum thread, but I realize you didn't
specify which virtualization technology you're using. Is this virtualbox
too? If so, does uninstalling the guest additions make a difference?

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

Title:
  Scrolling in Chromium stops working when moving mouse when running in
  virtual machine

Status in chromium-browser package in Ubuntu:
  Incomplete
Status in falkon package in Ubuntu:
  New
Status in qutebrowser package in Ubuntu:
  New
Status in chromium package in Arch Linux:
  New
Status in chromium package in openSUSE:
  New

Bug description:
  When Ubuntu is running in a virtual machine scrolling in Chromium
  stops working when moving the mouse even the slightest. Also the first
  scroll step is always ignored after moving the mouse. This results in
  a very uneven scrolling which is very difficult to use. Scrolling
  works perfectly in other applications like for example Firefox.

  This bug seems to have appeared in Ubuntu 16.04.0, as all Ubuntu
  releases before 16.04 works correctly, while all releases after 16.04
  are affected by this bug. Ubuntu is not the only distro that has this
  bug, but there are also several distros that are not affected by it.

  My current testing have shown the following distros to be affected:
  - Arch Linux
  - Linux Mint 20 Cinnamon
  - Manjaro XFCE 20.1
  - OpenSUSE Tumbleweed
  - Ubuntu 16.04, 18.04, 20.04

  And the following distros and operating systems are NOT affected:
  - Centos 8
  - Debian 10 (Buster)
  - DragonFly BSD 5.8.1
  - Fedora 32
  - GhostBSD 20.08.04
  - Ubuntu 12.04 to 15.10
  - Windows 10

  The fact that there are current updated distros that are unaffected
  indicates to me that this is probably not a bug in Chromium upstream,
  but I've not been able to pinpoint whether the problem is caused by
  something in the Chromium packaged by Ubuntu or some other difference
  in the system like the kernel or system libraries.

  I have already reported the bug to Chromium, link to the bug report
  here: https://bugs.chromium.org/p/chromium/issues/detail?id=1128405.

  There is also another bug report here:
  https://bugs.chromium.org/p/chromium/issues/detail?id=1100179

  
  I've already spent well over a week trying to troubleshoot this issue. I'm 
willing to do most of the work myself, but I really need some guidance as to 
what are the best next steps in troubleshooting this. Any help would be greatly 
appreciated!

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

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


[Desktop-packages] [Bug 1905791] Re: Resizing in awesome WM makes chromium stop redrawing its window

2020-12-01 Thread Olivier Tilloy
Would you mind commenting there to revive the bug and hopefully get
upstream's attention on it?

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

Title:
  Resizing in awesome WM makes chromium stop redrawing its window

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Start chromium in awesome.
  Start a new terminal.
  Try clicking on chromium. It is working, it is just not redrawn making it 
mostly useless.

  The last version that worked for sure was the 1328 snap version, but
  it is not available anymore.

  Reproducible on Ubuntu 20.04 and 21.04. Maybe on other releases as
  well.

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

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


[Desktop-packages] [Bug 1905791] Re: Resizing in awesome WM makes chromium stop redrawing its window

2020-12-01 Thread Olivier Tilloy
It looks like this upstream issue might be related:
https://bugs.chromium.org/p/chromium/issues/detail?id=1018712

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

Title:
  Resizing in awesome WM makes chromium stop redrawing its window

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Start chromium in awesome.
  Start a new terminal.
  Try clicking on chromium. It is working, it is just not redrawn making it 
mostly useless.

  The last version that worked for sure was the 1328 snap version, but
  it is not available anymore.

  Reproducible on Ubuntu 20.04 and 21.04. Maybe on other releases as
  well.

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

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


[Desktop-packages] [Bug 1905114] Re: Lenovo System Firmware update will not download or install and Impress 7.0 crashes

2020-12-01 Thread Heather Ellsworth
I opened the odp presentation but Impress never crashes so it's not the
presentation that is the problem and we need more information about the
environment.

Lillian, please open a new bug about the impress issue by typing this in
a terminal on your system:

ubuntu-bug libreoffice

In the description please mention:
1. The output of "cat /etc/os-release"
2. Capture the logs in a terminal while you generate the crash:
  - Open a terminal and do "journalctl -f"
  - Then open your presentation in impress and see it crash after ~2 min
  - go back to your terminal and copy/paste the logs generated into the 
description (and be sure to say in the bug description that this is what you 
did)

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

Title:
  Lenovo System Firmware update will not download or install and Impress
  7.0 crashes

Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  I am trying to update a security patch for  my computer. However, it will not 
update.
  The patch is called Lenovo System Firmware 0.1.69 - 0.1.70. Whenever there a 
update or patch for my lenovo it either does not download and or won't install 
the software. 

  
  Libreoffice impress 7.0 keeps crashing every couple of minutes 

  I had this problem before I upgraded to ubuntu gorilla. I just
  upgraded my system and the problem is still there. I have an important
  presentation to complete for school. It does not save the presentation
  at 365 PowerPoint. When it is opened in 365 the slide text,
  transitions and sound does not display correctly.


  I am using a 
  Lenovo thinkpad T590
  Memory 15.4 gib
  Processor Intel core i7

  OS Name Ubuntu 20.10
  OS Type 64-bit
  Gnome Version 3.38.1
  Windowing System X11

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

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


[Desktop-packages] [Bug 1905729] Re: power button configuration broken

2020-12-01 Thread Timo Aaltonen
** Summary changed:

- power button conifiguration broken
+ power button configuration broken

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

Title:
  power button configuration broken

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

Bug description:
  I'm not able to suspend the machine anymore by pressing the power
  button, instead a popup saying the machine will be shut down in 60s
  appears. The settings for configuring the behaviour is no longer
  visible in control center. And selecting suspend from the menu now
  asks for my password.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-settings-daemon 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14
  Uname: Linux 5.8.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 24 16:35:55 2020
  InstallationDate: Installed on 2019-10-14 (406 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/zsh
  RebootRequiredPkgs:
   gnome-shell
   linux-image-5.8.0-29-generic
   linux-base
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to groovy on 2020-09-29 (56 days ago)

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

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


[Desktop-packages] [Bug 1906420] Re: Please replace default Gnome extension "Desktop Icons" with "Desktop Icons NG (DING)" (by the same author)

2020-12-01 Thread Paddy Landau
@seb128 — Hmm, maybe I'm wrong about it being maintained. It's just that
it shows a lower level of compatibility in its Extensions listing. Sorry
if I was wrong.

I don't recall where specifically I have came across the recommendation
for NG, but I found it referenced in several places when I was trying to
solve another problem with Desktop Icons (it shows a permanent error
that cannot be fixed).

In any case, even if Desktop Icons is maintained, it lacks the features
that NG has, so it would be much easier to just use the latter than to
try to fix the former. I would hate to return to Desktop Icons, having
used Desktop Icons NG (DING) for some time.

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

Title:
  Please replace default Gnome extension "Desktop Icons" with "Desktop
  Icons NG (DING)" (by the same author)

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Confirmed

Bug description:
  By default, Ubuntu installs the Gnome extension "Desktop Icons" [1]
  (by rastersoft).

  Unfortunately, this extension is now unmaintained, is problematic, and
  leads to several bugs, including but not limited to Bug #1901150 and
  Bug #1813441.

  The same author has created, and continues to maintain, the far
  superior "Desktop Icons NG (DING)" [2]. It solves a number of problems
  including the two aforementioned bugs.

  It's possible to disable, but not uninstall, "Desktop Icons", and then
  to install "Desktop Icons NG (DING)". I did this a while ago with
  great results.

  If Canonical replaces the former with the latter, not only will Ubuntu
  be using a better desktop manager, but also it will be able clear all
  related bugs at a stroke.

  This is a simple, cheap, quick and effective solution that will let
  the devs concentrate on more important tasks.

  Please give this serious consideration.

  
  More information:

  Ubuntu 20.04.1 LTS
  64-bit
  Gnome version 3.36.3

  
  [1] https://extensions.gnome.org/extension/1465/desktop-icons/

  [2] https://extensions.gnome.org/extension/2087/desktop-icons-ng-ding/

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

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


[Desktop-packages] [Bug 1905775] Re: Uninstalling python3-apporrt should not uninstall xorg packages

2020-12-01 Thread flux242
i've just checked debian xorg package dependencies and no it doesn't
depend on that problem reporting.

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

Title:
  Uninstalling python3-apporrt should not uninstall xorg packages

Status in xorg package in Ubuntu:
  New

Bug description:
  ```
  sudo apt purge python3-apport 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
libglu1-mesa libxfont2 python3-certifi python3-chardet python3-idna 
python3-problem-report python3-requests
python3-requests-unixsocket python3-urllib3 x11-apps x11-session-utils 
xinit xinput xserver-common
xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput
  Use 'sudo apt autoremove' to remove them.
  The following packages will be REMOVED:
python3-apport* xorg* xserver-xorg*
  0 upgraded, 0 newly installed, 3 to remove and 61 not upgraded.
  After this operation, 1,070 kB disk space will be freed.
  Do you want to continue? [Y/n] ^C
  ```

  so, apparently dependencies aren't correctly set, because I don't want
  to send no problem reports but still want to use xorg subsystem

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

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


[Desktop-packages] [Bug 1905322] Re: LibreOffice crashes under load.

2020-12-01 Thread Heather Ellsworth
Following the video, I created a daily hirsute lubuntu vm. Then I opened
calc, writer, math. Once all three of those blank documents were up, I
opened Impress and chose the vivid template. I see the template load and
nothing crashes. Other templates load fine too.

Can you please do the following:
1. Open calc, writer, math
2. Open a terminal and run impress with:
$ strace libreoffice --impress

This should open up impress, go ahead and select the vivid theme. I
assume you'll see the crash and your terminal command will exit.. Could
you please capture the output and provide it here?

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

Title:
  LibreOffice crashes under load.

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  apt-cache policy libreoffice
  libreoffice:
Installed: (none)
Candidate: 1:7.0.3-0ubuntu1
Version table:
   1:7.0.3-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages

  I expect to be able to open all of LibreOffice's apps at once and use
  them.

  If you open all the LibreOffice applications and then select a
  template for LibreOffice Writer, they all close immediately, reopen,
  and offer to recover any lost data.

  Error reports may have been sent. I am not sure as this is Hirsute and
  I'm testing it.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu51
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: LXQt
  Date: Mon Nov 23 20:06:19 2020
  LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201123)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1903966] Re: Loading keymaps via udev is not reliable, please use upstream rule

2020-12-01 Thread Launchpad Bug Tracker
This bug was fixed in the package v4l-utils - 1.20.0-2

---
v4l-utils (1.20.0-2) unstable; urgency=medium

  * Use upstream version of ir-keytable udev rule
(Closes: #966166) (LP: #1903966)
  * Bump standards to version 4.5.1 (no changes needed)

 -- Gregor Jasny   Fri, 20 Nov 2020 14:50:43
+0100

** Changed in: v4l-utils (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Loading keymaps via udev is not reliable, please use upstream rule

Status in v4l-utils package in Ubuntu:
  Fix Released
Status in v4l-utils package in Debian:
  Unknown

Bug description:
  Dear Maintainer,

  the udev rule installed from debian/ir-keytable.udev is not guaranteed to be 
run at the
  appropriate moment during bootup which can cause the remote not to be
  configured according to the settings in /etc/rc_maps.cfg. This seems to occur 
more often with newer kernel versions.

  Please use the upstream version
  (https://git.linuxtv.org/v4l-utils.git/tree/utils/keytable/70-infrared.rules) 
instead.
  This commit message explains the need for this change:
  
https://git.linuxtv.org/v4l-utils.git/commit/utils/keytable/70-infrared.rules?id=e440918467868a5f3e7f73f54ef2cbd85d68f3f1

  Description:Ubuntu 20.04.1 LTS
  Release:20.04

  ir-keytable version: 1.18.0-2build1 and later

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

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


[Desktop-packages] [Bug 1905775] Re: Uninstalling python3-apporrt should not uninstall xorg packages

2020-12-01 Thread flux242
no, it is an issue because packages are marked for automatic removal:
x11-apps x11-session-utils xinit xinput xserver-common xserver-xorg-core
xserver-xorg-input-all xserver-xorg-input-libinput

So you suggest to install all those packages extra afterwards instead of
simply getting dependencies sorted out in the first place?

so, I still think that xorg should not depend on apport - it simply
doesn't belong.

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

Title:
  Uninstalling python3-apporrt should not uninstall xorg packages

Status in xorg package in Ubuntu:
  New

Bug description:
  ```
  sudo apt purge python3-apport 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
libglu1-mesa libxfont2 python3-certifi python3-chardet python3-idna 
python3-problem-report python3-requests
python3-requests-unixsocket python3-urllib3 x11-apps x11-session-utils 
xinit xinput xserver-common
xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput
  Use 'sudo apt autoremove' to remove them.
  The following packages will be REMOVED:
python3-apport* xorg* xserver-xorg*
  0 upgraded, 0 newly installed, 3 to remove and 61 not upgraded.
  After this operation, 1,070 kB disk space will be freed.
  Do you want to continue? [Y/n] ^C
  ```

  so, apparently dependencies aren't correctly set, because I don't want
  to send no problem reports but still want to use xorg subsystem

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

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


[Desktop-packages] [Bug 1905114] Re: Lenovo System Firmware update will not download or install and Impress 7.0 crashes

2020-12-01 Thread Lillian R Davis
I have attached a the file that shows the issue with Impress for your
review.

** Attachment added: "Html 101 lesson 1.odp"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1905114/+attachment/5440070/+files/Html%20101%20lesson%201.odp

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

Title:
  Lenovo System Firmware update will not download or install and Impress
  7.0 crashes

Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  I am trying to update a security patch for  my computer. However, it will not 
update.
  The patch is called Lenovo System Firmware 0.1.69 - 0.1.70. Whenever there a 
update or patch for my lenovo it either does not download and or won't install 
the software. 

  
  Libreoffice impress 7.0 keeps crashing every couple of minutes 

  I had this problem before I upgraded to ubuntu gorilla. I just
  upgraded my system and the problem is still there. I have an important
  presentation to complete for school. It does not save the presentation
  at 365 PowerPoint. When it is opened in 365 the slide text,
  transitions and sound does not display correctly.


  I am using a 
  Lenovo thinkpad T590
  Memory 15.4 gib
  Processor Intel core i7

  OS Name Ubuntu 20.10
  OS Type 64-bit
  Gnome Version 3.38.1
  Windowing System X11

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

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


[Desktop-packages] [Bug 1906420] Re: Please replace default Gnome extension "Desktop Icons" with "Desktop Icons NG (DING)" (by the same author)

2020-12-01 Thread Sebastien Bacher
Thank you for your bug report, did upstream recommend somewhere
(reference?) to use NG? What makes you state that the current one is
unmaintained, https://gitlab.gnome.org/World/ShellExtensions/desktop-
icons/ shows recent commits

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Please replace default Gnome extension "Desktop Icons" with "Desktop
  Icons NG (DING)" (by the same author)

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Confirmed

Bug description:
  By default, Ubuntu installs the Gnome extension "Desktop Icons" [1]
  (by rastersoft).

  Unfortunately, this extension is now unmaintained, is problematic, and
  leads to several bugs, including but not limited to Bug #1901150 and
  Bug #1813441.

  The same author has created, and continues to maintain, the far
  superior "Desktop Icons NG (DING)" [2]. It solves a number of problems
  including the two aforementioned bugs.

  It's possible to disable, but not uninstall, "Desktop Icons", and then
  to install "Desktop Icons NG (DING)". I did this a while ago with
  great results.

  If Canonical replaces the former with the latter, not only will Ubuntu
  be using a better desktop manager, but also it will be able clear all
  related bugs at a stroke.

  This is a simple, cheap, quick and effective solution that will let
  the devs concentrate on more important tasks.

  Please give this serious consideration.

  
  More information:

  Ubuntu 20.04.1 LTS
  64-bit
  Gnome version 3.36.3

  
  [1] https://extensions.gnome.org/extension/1465/desktop-icons/

  [2] https://extensions.gnome.org/extension/2087/desktop-icons-ng-ding/

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

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


[Desktop-packages] [Bug 1905775] Re: Uninstalling python3-apporrt should not uninstall xorg packages

2020-12-01 Thread Sebastien Bacher
The packages getting remove don't have useful content but are just empty
binaries meant to pull a complete set to the default installation, if
you want to remove apport and get those removed it shouldn't be an issue

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Uninstalling python3-apporrt should not uninstall xorg packages

Status in xorg package in Ubuntu:
  New

Bug description:
  ```
  sudo apt purge python3-apport 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
libglu1-mesa libxfont2 python3-certifi python3-chardet python3-idna 
python3-problem-report python3-requests
python3-requests-unixsocket python3-urllib3 x11-apps x11-session-utils 
xinit xinput xserver-common
xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput
  Use 'sudo apt autoremove' to remove them.
  The following packages will be REMOVED:
python3-apport* xorg* xserver-xorg*
  0 upgraded, 0 newly installed, 3 to remove and 61 not upgraded.
  After this operation, 1,070 kB disk space will be freed.
  Do you want to continue? [Y/n] ^C
  ```

  so, apparently dependencies aren't correctly set, because I don't want
  to send no problem reports but still want to use xorg subsystem

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

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


[Desktop-packages] [Bug 1905775] Re: Uninstalling python3-apporrt should not uninstall xorg packages

2020-12-01 Thread flux242
ah, it's the other way around with dependencies. So, apparently xorg
should not depend on problem reporting. I think the only reason they put
this dependency there is because otherwise they would have to add it to
every -desktop task.

And no, I want to purge all packages related to apport, not only disable
it.

Thanks, Brian

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

Title:
  Uninstalling python3-apporrt should not uninstall xorg packages

Status in xorg package in Ubuntu:
  New

Bug description:
  ```
  sudo apt purge python3-apport 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
libglu1-mesa libxfont2 python3-certifi python3-chardet python3-idna 
python3-problem-report python3-requests
python3-requests-unixsocket python3-urllib3 x11-apps x11-session-utils 
xinit xinput xserver-common
xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput
  Use 'sudo apt autoremove' to remove them.
  The following packages will be REMOVED:
python3-apport* xorg* xserver-xorg*
  0 upgraded, 0 newly installed, 3 to remove and 61 not upgraded.
  After this operation, 1,070 kB disk space will be freed.
  Do you want to continue? [Y/n] ^C
  ```

  so, apparently dependencies aren't correctly set, because I don't want
  to send no problem reports but still want to use xorg subsystem

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

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


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

2020-12-01 Thread smurf
I had to reinstall Ubuntu 20.04 with kernel 5.4.0-56 because on 20.10
with kernel 5.8.0-28 the wifi was very unstable.

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

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

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

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

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

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

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

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


[Desktop-packages] [Bug 1906087] Re: Half of the date-time text is hidden in the calendar popover

2020-12-01 Thread Pravinkumar
Hi Team,  I have raised a new issue at GNome; issue id #3445.

Thank you!

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

Title:
  Half of the date-time text is hidden in the calendar popover

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I am using Tamil(india) as the date-time language from Ubuntu 19. But
  after upgrading to Ubuntu 20, the date-time is half-hidden (see
  attachments).

  before upgrade it was working fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 28 10:47:42 2020
  DistUpgraded: 2020-06-06 18:27:37,926 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:0792]
  InstallationDate: Installed on 2018-11-04 (755 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Vostro 14-3468
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=UUID=6272611c-ab7e-4b80-86ed-8e7dbe8d5396 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-06-06 (174 days ago)
  acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
  dmi.bios.date: 05/15/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.0
  dmi.board.name: 0T1X3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.0:bd05/15/2018:svnDellInc.:pnVostro14-3468:pvr:rvnDellInc.:rn0T1X3V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 14-3468
  dmi.product.sku: 0792
  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 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  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/gnome-shell/+bug/1906087/+subscriptions

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


[Desktop-packages] [Bug 1906420] Re: Please replace default Gnome extension "Desktop Icons" with "Desktop Icons NG (DING)" (by the same author)

2020-12-01 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
   Status: New => Confirmed

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

Title:
  Please replace default Gnome extension "Desktop Icons" with "Desktop
  Icons NG (DING)" (by the same author)

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Confirmed

Bug description:
  By default, Ubuntu installs the Gnome extension "Desktop Icons" [1]
  (by rastersoft).

  Unfortunately, this extension is now unmaintained, is problematic, and
  leads to several bugs, including but not limited to Bug #1901150 and
  Bug #1813441.

  The same author has created, and continues to maintain, the far
  superior "Desktop Icons NG (DING)" [2]. It solves a number of problems
  including the two aforementioned bugs.

  It's possible to disable, but not uninstall, "Desktop Icons", and then
  to install "Desktop Icons NG (DING)". I did this a while ago with
  great results.

  If Canonical replaces the former with the latter, not only will Ubuntu
  be using a better desktop manager, but also it will be able clear all
  related bugs at a stroke.

  This is a simple, cheap, quick and effective solution that will let
  the devs concentrate on more important tasks.

  Please give this serious consideration.

  
  More information:

  Ubuntu 20.04.1 LTS
  64-bit
  Gnome version 3.36.3

  
  [1] https://extensions.gnome.org/extension/1465/desktop-icons/

  [2] https://extensions.gnome.org/extension/2087/desktop-icons-ng-ding/

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

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


[Desktop-packages] [Bug 1897530] Re: [modeset][nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0"

2020-12-01 Thread Launchpad Bug Tracker
This bug was fixed in the package xorg-server - 2:1.20.8-2ubuntu2.6

---
xorg-server (2:1.20.8-2ubuntu2.6) focal-security; urgency=medium

  * SECURITY UPDATE: out of bounds memory accesses on too short request
- debian/patches/CVE-2020-14360.patch: check SetMap request length
  carefully in xkb/xkb.c.
- CVE-2020-14360
  * SECURITY UPDATE: multiple heap overflows
- debian/patches/CVE-2020-25712.patch: add bounds checks in xkb/xkb.c.
- CVE-2020-25712

 -- Marc Deslauriers   Mon, 30 Nov 2020
12:56:33 -0500

** Changed in: xorg-server (Ubuntu Focal)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-14360

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-25712

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

Title:
  [modeset][nvidia] X Server session crash with "No space left on
  device" and then "EnterVT failed for gpu screen 0"

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Bionic:
  Won't Fix
Status in xorg-server-hwe-18.04 source package in Bionic:
  Confirmed
Status in xorg-server source package in Focal:
  Fix Released
Status in xorg-server source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  On a hybrid machine where NVIDIA is rendering the screen, if a display
  attached to a dock is removed while on suspend mode, on resume X
  crashes.

  [Test case]

  Test hot-unplug during suspend and resume, X shouldn't crash.

  [Regression potential]

  This replaces a patch we had with two commits that got merged upstream
  after a fairly extensive review process:

  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/443/

  And we ship it in groovy. If there were issues caused by it, they
  would be around hot-unplugging a dock while on suspend and such.

  --

  Expectation: on removal of external display during S3, after resume eDP 
rendering should still continue by Nvidia.
  Symptom description: Plug out DP cable when suspension, when resume, X will 
crash.

  1. Before S3 entry, eDP and external panel(via dock) were driven by Intel but 
NV was rendering for eDP.
  2. After S3 entry dock was removed.
  3. On resume, Linux kernel tried to find dock but couldn’t find it, so fails 
resume of TB3 devices and logs confirm that.
  4. X fails to enter VT due to Null meta mode.

  To address the explanation, X is not failing to enter the VT due to
  NVIDIA’s NULL MetaMode. It’s the Intel (modesetting) driver that is
  failing to enter the VT. It’s expected that NVIDIA would have a NULL
  MetaMode, since there are no displays connected to it. Our driver is
  pretty robust to head state changes – even if we have to fall back to
  a NULL MetaMode, we will still enter the VT successfully.

  The logs clearly show that the failure is originating from the Intel
  (modesetting) driver, not the NVIDIA driver. The relevant path in X is
  driver.c:EnterVT() => drmmode_display.c:drmmode_set_desired_modes().
  In this function, the Intel driver tries to set a mode on each of the
  previously connected/enabled displays, and it tries to find the
  closest possible mode using xf86OutputFindClosestMode(). This is
  similar to our driver’s functionality, but unlike us, they don’t
  support a NULL fallback. If there are no modes supported on one of the
  displays, it simply fails, which causes X to terminate:

  DisplayModePtr mode = xf86OutputFindClosestMode(output,
  pScrn->currentMode);

  if (!mode)
  return FALSE;

  Since we removed one of the displays via the dock, it fails. It
  doesn’t matter if the internal panel is still available, Intel will
  fail if it can’t re-enable ANY of the previously connected displays.

  Technically the modesetting driver isn’t specifically an Intel driver,
  it’s a generic driver that can be used by any DRM device – it’s just
  that Intel has chosen to use the modesetting driver as their standard
  Linux X driver going forward.

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

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


[Desktop-packages] [Bug 1901150] Re: No "Are you sure?" question when deleting something from Desktop

2020-12-01 Thread Paddy Landau
I have created Bug #1906420 which, if implemented, will solve this and
other bugs.

Please visit and "star" it (the green writing at the top) if you agree
with it.

https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-
icons/+bug/1906420

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

Title:
  No "Are you sure?" question when deleting something from Desktop

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Won't Fix

Bug description:
  There isn't any "Are you sure?" question when deleting (del OR
  shift+del) something from Desktop.

  Was happening in 20.04 and now in 20.10 too.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell-extension-desktop-icons 20.04.0+git20200908-1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 23 10:08:44 2020
  InstallationDate: Installed on 2019-12-19 (308 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago)

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

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

2020-12-01 Thread Paddy Landau
I have created Bug #1906420 which, if implemented, will solve this and
other bugs.

Please visit and "star" it (the green writing at the top) if you agree
with it.

https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-
icons/+bug/1906420

-- 
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 1906420] [NEW] Please replace default Gnome extension "Desktop Icons" with "Desktop Icons NG (DING)" (by the same author)

2020-12-01 Thread Paddy Landau
Public bug reported:

By default, Ubuntu installs the Gnome extension "Desktop Icons" [1] (by
rastersoft).

Unfortunately, this extension is now unmaintained, is problematic, and
leads to several bugs, including but not limited to Bug #1901150 and Bug
#1813441.

The same author has created, and continues to maintain, the far superior
"Desktop Icons NG (DING)" [2]. It solves a number of problems including
the two aforementioned bugs.

It's possible to disable, but not uninstall, "Desktop Icons", and then
to install "Desktop Icons NG (DING)". I did this a while ago with great
results.

If Canonical replaces the former with the latter, not only will Ubuntu
be using a better desktop manager, but also it will be able clear all
related bugs at a stroke.

This is a simple, cheap, quick and effective solution that will let the
devs concentrate on more important tasks.

Please give this serious consideration.


More information:

Ubuntu 20.04.1 LTS
64-bit
Gnome version 3.36.3


[1] https://extensions.gnome.org/extension/1465/desktop-icons/

[2] https://extensions.gnome.org/extension/2087/desktop-icons-ng-ding/

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


** Tags: desktop-file

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

Title:
  Please replace default Gnome extension "Desktop Icons" with "Desktop
  Icons NG (DING)" (by the same author)

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

Bug description:
  By default, Ubuntu installs the Gnome extension "Desktop Icons" [1]
  (by rastersoft).

  Unfortunately, this extension is now unmaintained, is problematic, and
  leads to several bugs, including but not limited to Bug #1901150 and
  Bug #1813441.

  The same author has created, and continues to maintain, the far
  superior "Desktop Icons NG (DING)" [2]. It solves a number of problems
  including the two aforementioned bugs.

  It's possible to disable, but not uninstall, "Desktop Icons", and then
  to install "Desktop Icons NG (DING)". I did this a while ago with
  great results.

  If Canonical replaces the former with the latter, not only will Ubuntu
  be using a better desktop manager, but also it will be able clear all
  related bugs at a stroke.

  This is a simple, cheap, quick and effective solution that will let
  the devs concentrate on more important tasks.

  Please give this serious consideration.

  
  More information:

  Ubuntu 20.04.1 LTS
  64-bit
  Gnome version 3.36.3

  
  [1] https://extensions.gnome.org/extension/1465/desktop-icons/

  [2] https://extensions.gnome.org/extension/2087/desktop-icons-ng-ding/

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

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


[Desktop-packages] [Bug 1905775] Re: Uninstalling python3-apporrt should not uninstall xorg packages

2020-12-01 Thread Brian Murray
This does not have to do with apport's dependencies, rather it is an
xorg package which depends on apport and the removal of python3-apport
causing the xorg package to have missing dependencies.

bdmurray@clean-focal-amd64:~$ apt-cache show xserver-xorg
Package: xserver-xorg
Architecture: amd64
Version: 1:7.7+19ubuntu14
Priority: optional
Section: x11
Source: xorg
Origin: Ubuntu
Maintainer: Ubuntu X-SWAT 
Original-Maintainer: Debian X Strike Force 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 411
Provides: xserver
Depends: xserver-xorg-core (>= 2:1.17.2-2), xserver-xorg-input-all | 
xorg-driver-input, xkb-data (>= 1.4), x11-xkb-utils, python3-apport
Recommends: libgl1-mesa-dri, mesa-vulkan-drivers, xserver-xorg-legacy, 
xserver-xorg-video-all
Breaks: xdiagnose (<< 3.8.8)
Replaces: xdiagnose (<< 3.8.8)
Filename: pool/main/x/xorg/xserver-xorg_7.7+19ubuntu14_amd64.deb
Size: 65176
MD5sum: 3ed74cae9268cf378a6fc2e8a77f53ed
SHA1: 6cffe8eb38acffed33937ae7fc37d3e04973e33d
SHA256: 7b2380dbdc991497443b57dba4fe4335234e53a125d0b18f1b9b5ef3c492eab5
Homepage: http://www.x.org/
Description-en: X.Org X server
 This package depends on the full suite of the server and drivers for the
 X.Org X server.  It does not provide the actual server itself.
Description-md5: 3d8c1d268e8af6b69f54d86fbd5a3939
Task: ubuntu-desktop-minimal, ubuntu-desktop, kubuntu-desktop, xubuntu-core, 
xubuntu-desktop, lubuntu-desktop, ubuntustudio-desktop-core, 
ubuntustudio-desktop, ubuntukylin-desktop, ubuntu-mate-core, 
ubuntu-mate-desktop, ubuntu-budgie-deskt
op

If you are looking to disable apport you should adjust the following
file:

bdmurray@clean-focal-amd64:~$ cat /etc/default/apport 
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=1

** Project changed: apport => xorg (Ubuntu)

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

Title:
  Uninstalling python3-apporrt should not uninstall xorg packages

Status in xorg package in Ubuntu:
  New

Bug description:
  ```
  sudo apt purge python3-apport 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
libglu1-mesa libxfont2 python3-certifi python3-chardet python3-idna 
python3-problem-report python3-requests
python3-requests-unixsocket python3-urllib3 x11-apps x11-session-utils 
xinit xinput xserver-common
xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput
  Use 'sudo apt autoremove' to remove them.
  The following packages will be REMOVED:
python3-apport* xorg* xserver-xorg*
  0 upgraded, 0 newly installed, 3 to remove and 61 not upgraded.
  After this operation, 1,070 kB disk space will be freed.
  Do you want to continue? [Y/n] ^C
  ```

  so, apparently dependencies aren't correctly set, because I don't want
  to send no problem reports but still want to use xorg subsystem

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

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


[Desktop-packages] [Bug 1905946] Re: Mouse stop moving after few seconds. restart at click

2020-12-01 Thread AO
Issue has been fixed after the latest updates.

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

Title:
  Mouse stop moving after few seconds. restart at click

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Mouse stop moving after few seconds if i don't continue moving it, restart 
moving if i click but after few seconds sstops again.
  Problem occurs with both X11 and Wayland session. 
  corrado@corrado-x2-hh-1104:~$ inxi -Fx
  System:Host: corrado-x2-hh-1104 Kernel: 5.8.0-25-generic x86_64 bits: 64 
compiler: gcc v: 10.2.0 
 Desktop: GNOME 3.38.1 Distro: Ubuntu 21.04 (Hirsute Hippo) 
  Machine:   Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: 
 
 UEFI: American Megatrends v: P1.10 date: 05/11/2017 
  CPU:   Info: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP 
arch: Kaby Lake rev: 9 
 L2 cache: 3072 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 31199 
 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 
800 3: 800 4: 800 
  Graphics:  Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: 
kernel bus ID: 00:02.0 
 Device-2: ARC USB 2.0 Camera type: USB driver: uvcvideo bus ID: 
1-1:2 
 Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: 
fbdev,vesa 
 resolution: 1920x1080~60Hz 
 OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 
20.2.2 
 direct render: Yes 
  Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: 
ASRock 
 driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
 Device-2: Logitech QuickCam Pro 9000 type: USB driver: 
snd-usb-audio,uvcvideo 
 bus ID: 1-8:5 
 Sound Server: ALSA v: k5.8.0-25-generic 
  Network:   Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 
3.2.6-k port: f040 
 bus ID: 00:1f.6 
 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 
70:85:c2:44:7b:86 
  Drives:Local Storage: total: 2.05 TiB used: 15.92 GiB (0.8%) 
 ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 
232.89 GiB 
 ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
 ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 
GiB 
  Partition: ID-1: / size: 31.25 GiB used: 15.91 GiB (50.9%) fs: ext4 dev: 
/dev/nvme0n1p2 
  Swap:  ID-1: swap-1 type: partition size: 8.00 GiB used: 0 KiB (0.0%) 
dev: /dev/sda2 
  Sensors:   System Temperatures: cpu: 45.5 C mobo: N/A 
 Fan Speeds (RPM): N/A 
  Info:  Processes: 213 Uptime: 1h 31m Memory: 7.48 GiB used: 1.75 GiB 
(23.4%) Init: systemd 
 runlevel: 5 Compilers: gcc: N/A Packages: 1937 Shell: Bash v: 
5.1.0-rc2 inxi: 3.1.09 
  corrado@corrado-x2-hh-1104:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu53
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 27 11:12:40 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-11-04 (22 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201104)
  RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1905775] [NEW] Uninstalling python3-apporrt should not uninstall xorg packages

2020-12-01 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

```
sudo apt purge python3-apport 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libglu1-mesa libxfont2 python3-certifi python3-chardet python3-idna 
python3-problem-report python3-requests
  python3-requests-unixsocket python3-urllib3 x11-apps x11-session-utils xinit 
xinput xserver-common
  xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  python3-apport* xorg* xserver-xorg*
0 upgraded, 0 newly installed, 3 to remove and 61 not upgraded.
After this operation, 1,070 kB disk space will be freed.
Do you want to continue? [Y/n] ^C
```

so, apparently dependencies aren't correctly set, because I don't want
to send no problem reports but still want to use xorg subsystem

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

-- 
Uninstalling python3-apporrt should not uninstall xorg packages
https://bugs.launchpad.net/bugs/1905775
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg 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 1901609] Re: signond causes qprocess crash

2020-12-01 Thread Rik Mills
I have tested with the patch applied in this upload to hirsute:

https://launchpad.net/ubuntu/+source/signon/8.59+17.10.20170606-0ubuntu3

That fixes the crash for me.

** Changed in: signon (Ubuntu Hirsute)
   Status: Confirmed => Fix Committed

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

Title:
  signond causes qprocess crash

Status in signon package in Ubuntu:
  Fix Committed
Status in signon source package in Focal:
  Confirmed
Status in signon source package in Groovy:
  Confirmed
Status in signon source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

  Without the patch users are unable to add google accounts because signond 
crashes.
  This prevents users from using KDE's online accounts feature for google.
  The fix for this is to drop the no-rtti compile flag as qprocess relies on 
type info. This has no real downside for the user as it simply brings in type 
info.

  [Test Case]

  - in a plasma session
  - install kio-gdrive
  - run `systemsettings5 kcm_kaccounts`
  - add a new account
  - click on google
  - wait for login window to appear
  - signond shouldn't be crashing

  [Where problems could occur]

  Cannot think of any. It simply adds type info to the objects. Also
  upstream has rtti disabled for months and I'm not aware of any
  problems.

  [Other Info]

  This is a fairly grave issue as far as user experience is concerned.

  
  

  
  I'm reporting this bug upstream from where I found it, since I've learned 
that the signond package in KDE Neon is sourced from Ubuntu focal.

  This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64)
  from Focal Fossa

  Steps to reproduce:

  1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon)
  2. Install the kaccounts integration and kio-gdrive packages.
  3. Open System settings and navigate to "Online Accounts"
  4. Press "+ Add New Account"
  5. Select "Google"

  Observed behaviour:

  - Window that would ask for authentication fails to load, and Online Accounts 
goes back to overview
  - system logs show a segfault in libqt5core.so which can be traced to a 
failure in qporcess, casued by signond (see links for further details)

  Expected behaviour:
  - New window opens with a webview where Google authentication credentials can 
be posted.
  - When qprocess runs it does not crash.

  Further reference information at the following links:

  1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034

  3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts-
  sso/signond/-/merge_requests/27

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

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

2020-12-01 Thread Luna Jernberg
Hangs on Hirsute too :( 
@seb128 
did try now

-- 
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 1886322] Re: Unable to move all selected files on desktop

2020-12-01 Thread Luna Jernberg
Hangs on Hirsute too :(
@seb128
did try now

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

Title:
  Unable to move all selected files on desktop

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

Bug description:
  Hi,

  This bug started to happen like 1-2 months ago, and as I remember I
  didn't do any customizations like installing any external plugins and
  etc, but I have some stuff already like custom icons, shell, theme...
  but it worked normaly before.

  What is happening is that when I select more than 1 file on desktop,
  no matter which file it is (folder, .txt, image.. anything), and when
  I try to move around desktop from one place to another, it will move
  only 1 file and not the rest. So, unable to move selected files on
  desktop (drag and drop using cursor's rectangle). Its simple issue, no
  need for video or screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  5 14:18:03 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 
/ R9 270 1024SP] [1002:6819] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 7850 2GB 
GDDR5 DVI-I/DVI-D/HDMI/DP [174b:e221]
  InstallationDate: Installed on 2020-03-24 (103 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: MSI MS-7693
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=20c309bc-2b22-43b0-938e-0761aa26cd13 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/31/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-G46 (MS-7693)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.11:bd10/31/2012:svnMSI:pnMS-7693:pvr2.0:rvnMSI:rn970A-G46(MS-7693):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7693
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  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 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/gnome-shell-extension-desktop-icons/+bug/1886322/+subscriptions

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


[Desktop-packages] [Bug 1905982] Re: Screen not Blanking after upgrade to 20.04

2020-12-01 Thread rsteinmetz70112
I think I've solved it. I removed gdm3 and lightdm

apt purge gdm3
apt purge lightdm

then reinstalled gdm3 and ubuntu desktop.

apt install gdm3 ubuntu-desktop

It now seems to be working as expected.

It appears to me screen blanking may not work with lightdm, but I'm not sure 
perhaps it was something else held over form 18.04.
Just switching from lightdm to gdm3 caused a "Low Graphics Mode" error, 
removing and reinstalling gdme3 solved that.

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

Title:
  Screen not Blanking after upgrade to 20.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After a do-release-upgrade from 18.04 to 20.04 screen blanking stopped 
working.
  I had my desktop set to blank but no lock the screen.
  After the upgrtade it does not ever blank. 

   preferences are set in Settings-> Power -> Blank Screen 10 minutes
   Automatic Suspend is OFF

   gnome-screensaver is running

   gnome-screensaver command -a doesn't do anything.

   video driver is Nvidia-455

   Display Manager is lightdm switching to gdm3 causes the video to not
  work properly.

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

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


[Desktop-packages] [Bug 1897369] Re: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)

2020-12-01 Thread Jamie Strandboge
Till, it allows quite a few things (from man capabilities):

CAP_SYS_NICE
   * Raise  process nice value (nice(2), setpriority(2)) and change the
 nice value for arbitrary processes;
   * set real-time scheduling policies for  calling  process,  and  set
 scheduling   policies   and  priorities  for  arbitrary  processes
 (sched_setscheduler(2), sched_setparam(2), sched_setattr(2));
   * set CPU affinity for arbitrary processes (sched_setaffinity(2));
   * set I/O scheduling class and priority for arbitrary processes (io‐
 prio_set(2));
   * apply  migrate_pages(2) to arbitrary processes and allow processes
 to be migrated to arbitrary nodes;
   * apply move_pages(2) to arbitrary processes;
   * use the MPOL_MF_MOVE_ALL flag with mbind(2) and move_pages(2).

cups-browsed is probably just trying to renice itself, which isn't
terrible for it to try, but it probably fails gracefully with this just
being noise. If it does fail gracefully, you could consider an explicit
deny rule to silence the log. Eg:

  deny capability sys_nice,

That said, we've normally allowed system policy (ie, those shipped in
debs) to use sys_nice if they have a legitimate use case for it.

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

Title:
  apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 20.04.1 with *cups-browsed* 1.27.4-1, apparmor prevents
  `/usr/sbin/cups-browsed` to change its nice value.

  $ sudo dmesg | grep apparmor
  [541870.509461] audit: type=1400 audit(1600898428.089:60): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=62030 comm="cups-browsed" capability=23  capname="sys_nice"
  [628298.779668] audit: type=1400 audit(1600984854.115:61): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=66850 comm="cups-browsed" capability=23  capname="sys_nice"
  [714667.424963] audit: type=1400 audit(1601071220.527:62): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" 
pid=76828 comm="cups-browsed" capability=23  capname="sys_nice"

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

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


[Desktop-packages] [Bug 1905422] Re: CoinMP Solver not Available, option requires coinmp to be promoted

2020-12-01 Thread Olivier Tilloy
I think it'd be worth testing whether libreoffice-calc can be built with
coinmp support (build dependencies don't have to be in main) and still
function without the dependency installed (i.e. runtime detection).

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

Title:
  CoinMP Solver not Available, option requires coinmp to be promoted

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Hi! LibreOffice Calc supports the CoinMP Linear Solver, which is an
  excellent solver to be used in spreadsheets and makes LO Calc superior
  to other office suites in that regard.

  However, the build provided by this PPA does not come with CoinMP
  Solver enabled (see Tools > Solver > Options). I posted a question at
  Ask LibreOffice and I was informed that CoinMP is enabled by default
  during build and maybe the PPA maintainers chose to disable it.

  https://ask.libreoffice.org/en/question/240836/coinmp-solver-on-
  libreoffice-calc/

  In fact, I built LibreOffice from source and CoinMP was there.
  However, building from source is not convenient and I'd like to use
  the PPA.

  Is it possible that CoinMP Solver be included in future builds of
  LibreOffice provided by this PPA?

  I am currently using LibreOffice 7.0.3.1 on Ubuntu 20.04.

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

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


[Desktop-packages] [Bug 1906326] Re: package xcursor-themes 1.0.6-0ubuntu1 failed to install/upgrade: installed xcursor-themes package post-installation script subprocess returned error exit status 2

2020-12-01 Thread rsteinmetz70112
No I didn't remove of edit anything.

When I run an upgrade I get an error that that file is missing. When I do 
dpkg --configure -a  I get the same message.
In order to solve a problem with the screen not blanking  I removed gdm3 and 
lightdm then reinstalled gdm3, that's when the error showed up. gdm3.

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

Title:
  package xcursor-themes 1.0.6-0ubuntu1 failed to install/upgrade:
  installed xcursor-themes package post-installation script subprocess
  returned error exit status 2

Status in xcursor-themes package in Ubuntu:
  Incomplete

Bug description:
  none

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: xcursor-themes 1.0.6-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  455.38  Thu Oct 22 06:06:59 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.13
  AptOrdering:
   gdm3:amd64: Install
   ubuntu-desktop-minimal:amd64: Install
   ubuntu-desktop:amd64: Install
   xcursor-themes:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Nov 30 17:47:16 2020
  Dependencies:
   
  DistUpgraded: 2020-11-09 22:11:21,286 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 455.38, 5.4.0-54-generic, x86_64: installed
   nvidia, 455.38, 5.4.0-56-generic, x86_64: installed
  ErrorMessage: installed xcursor-themes package post-installation script 
subprocess returned error exit status 2
  GraphicsCard:
   NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GK208B [GeForce GT 
710] [1462:8c93]
  InstallationDate: Installed on 2017-04-02 (1338 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 002 Device 002: ID 050d:705c Belkin Components F5D7050 Wireless G 
Adapter v4000 [Zydas ZD1211B]
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/10p, 12M
   |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=zd1211rw, 
12M
   |__ Port 7: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
   |__ Port 7: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/10p, 480M
  MachineType: System manufacturer System Product Name
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=UUID=2cde2844-40c1-4e06-85a5-9ee53a38864a ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: xcursor-themes
  Title: package xcursor-themes 1.0.6-0ubuntu1 failed to install/upgrade: 
installed xcursor-themes package post-installation script subprocess returned 
error exit status 2
  UpgradeStatus: Upgraded to focal on 2020-11-10 (20 days ago)
  dmi.bios.date: 01/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0702
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4N68T-M-V2
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0702:bd01/26/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N68T-M-V2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  

[Desktop-packages] [Bug 1902044] Re: SRU the current 42.6 stable update

2020-12-01 Thread Sebastien Bacher
** Summary changed:

- SRU the current 42.5 stable update 
+ SRU the current 42.6 stable update

** Changed in: deja-dup (Ubuntu Groovy)
   Importance: Undecided => Low

** Changed in: deja-dup (Ubuntu Groovy)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

** Changed in: deja-dup (Ubuntu Groovy)
   Status: New => In Progress

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

Title:
  SRU the current 42.6 stable update

Status in deja-dup package in Ubuntu:
  Fix Released
Status in deja-dup source package in Groovy:
  In Progress

Bug description:
  * Impact
  That's the current stable update, including some fixes and translation updates
  https://gitlab.gnome.org/World/deja-dup/-/releases/42.5

  The update should help with bug #1901340 and backup on removable
  drives

  * Test case

  Check that local and remote backups and restore are working.

  * Regression potential

  The update has some fixes for backup on removable and encrypted media
  so that's probably something to give some testing to

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

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


[Desktop-packages] [Bug 1905422] Re: CoinMP Solver not Available, option requires coinmp to be promoted

2020-12-01 Thread Heather Ellsworth
** Changed in: libreoffice (Ubuntu)
 Assignee: (unassigned) => Heather Ellsworth (hellsworth)

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

Title:
  CoinMP Solver not Available, option requires coinmp to be promoted

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Hi! LibreOffice Calc supports the CoinMP Linear Solver, which is an
  excellent solver to be used in spreadsheets and makes LO Calc superior
  to other office suites in that regard.

  However, the build provided by this PPA does not come with CoinMP
  Solver enabled (see Tools > Solver > Options). I posted a question at
  Ask LibreOffice and I was informed that CoinMP is enabled by default
  during build and maybe the PPA maintainers chose to disable it.

  https://ask.libreoffice.org/en/question/240836/coinmp-solver-on-
  libreoffice-calc/

  In fact, I built LibreOffice from source and CoinMP was there.
  However, building from source is not convenient and I'd like to use
  the PPA.

  Is it possible that CoinMP Solver be included in future builds of
  LibreOffice provided by this PPA?

  I am currently using LibreOffice 7.0.3.1 on Ubuntu 20.04.

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

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


  1   2   >