date:20200709

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

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

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in linux package in Ubuntu:
  New

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP

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

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

[Desktop-packages] [Bug 1887107] [NEW] Missing entry for timezone database when setting timezone via the text search

2020-07-09 Thread Adrien L.

Public bug reported:

I can't find Montreal in the timezone search box, even though it is
present in the /usr/share/zoneinfo database.

What I did:
Settings > Time & Date > Time Zone > Click in the search box and start typing 
Mont...
What I expected:
Autocompletion.
What happened:
No completion found.

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

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.1-1ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul  9 23:59:01 2020
ExecutablePath: /usr/bin/gnome-control-center
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Missing entry for timezone database when setting timezone via the text
  search

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

Bug description:
  I can't find Montreal in the timezone search box, even though it is
  present in the /usr/share/zoneinfo database.

  What I did:
  Settings > Time & Date > Time Zone > Click in the search box and start typing 
Mont...
  What I expected:
  Autocompletion.
  What happened:
  No completion found.

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  9 23:59:01 2020
  ExecutablePath: /usr/bin/gnome-control-center
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)

Which graphics does the HDMI connect to? Intel or Nvidia?

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

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works",
  but it blinks, the image showed via HDMI on the second monitor blinks.
  So is impossible to work with it. Since all this time I was searching
  about this and I'm almost sure this is a problem of the GPU's Intel.
  But I saw this problem on askubuntu just with laptops with hybrid
  graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not
  sure if they have the same problem here).

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

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

[Desktop-packages] [Bug 1882161] Re: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority

@sil2100

hello Lukasz,

I just update the bug's description, would you please check if it is ok
for you to proceed SRU.

Thanks!

** Description changed:

  [Impact]
  
   * On the Dell machines with multi function audio jack, the
     headphone/headset can't output sound automatically, which is different
     from ubuntu 18.04. The headphone/headset should be able to  output
     sound automatically after plugging in the audio jack.
  
  [Test Case]
  
   * On Tiger Lake platform
-Reproduce step:
+    Reproduce step:
     1. plug headphone/headset
     2. open g-c-c sound to check
  
     Expect result: The output device should switch to headphone or headset,
    since headphone's priority is higher in ucm2 config.
     Actual result: The output device is still internal speaker.
  
  [Regression Potential]
  
-  * Low, just do a small change to store the ucm devices by their priority.
-    and upstream just merged this patch.
+  * The change insert the ucm device by its priority, the potential
+regression is low, since if the change is not working properly, the 
+side effect is that the order of ucm devices are wrong, and it won't 
+switch to the correct output device as expect, but user can still
+config it manually.
  
  [Other]
  
   * This bug originates from an OEM private bug #1875597, then ubuntu users
     reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329
     and the 1st issue of #1881659 have the same root cause as #1875597
  
   * The root cause is the ucm2 conf defines 2 input devices: the Mic2 and
     Headset MIC, and the pulseaudio parse the input device Headset MIC
     first then Mic2, finally the audio jack is set to Mic2 mode, this make
     the audio jack can't output sound anymore. To fix it, let the audio
     jack set to Headset MIC mode by default (Headset MIC has higher
     priority than Mic2 in the ucm2 conf), to do so, let pulseaudio send the
     device event to module-switch-on-port-available by the order of
     priority in the umc2.

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

Title:
  module-switch-on-port-avaiable: switch the port on ucm devices based
  on the priority

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * On the Dell machines with multi function audio jack, the
     headphone/headset can't output sound automatically, which is different
     from ubuntu 18.04. The headphone/headset should be able to  output
     sound automatically after plugging in the audio jack.

  [Test Case]

   * On Tiger Lake platform
     Reproduce step:
     1. plug headphone/headset
     2. open g-c-c sound to check

     Expect result: The output device should switch to headphone or headset,
    since headphone's priority is higher in ucm2 config.
     Actual result: The output device is still internal speaker.

  [Regression Potential]

   * The change insert the ucm device by its priority, the potential
 regression is low, since if the change is not working properly, the 
 side effect is that the order of ucm devices are wrong, and it won't 
 switch to the correct output device as expect, but user can still
 config it manually.

  [Other]

   * This bug originates from an OEM private bug #1875597, then ubuntu users
     reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329
     and the 1st issue of #1881659 have the same root cause as #1875597

   * The root cause is the ucm2 conf defines 2 input devices: the Mic2 and
     Headset MIC, and the pulseaudio parse the input device Headset MIC
     first then Mic2, finally the audio jack is set to Mic2 mode, this make
     the audio jack can't output sound anymore. To fix it, let the audio
     jack set to Headset MIC mode by default (Headset MIC has higher
     priority than Mic2 in the ucm2 conf), to do so, let pulseaudio send the
     device event to module-switch-on-port-available by the order of
     priority in the umc2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1882161/+subscriptions

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

[Desktop-packages] [Bug 1882161] Re: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority

** Description changed:

- This bug originates from an OEM private bug #1875597, then ubuntu users
- reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329
- and the 1st issue of #1881659 have the same root cause as #1875597
+ [Impact]
  
- [Impact]
- On the Dell machines with multi function audio jack, after installing the 
ubuntu 20.04 and if the audio driver is sof instead of legacy hda, the 
headphone/headset can't output sound automatically after users plug in a 
headphone/headset. This is different from ubuntu 18.04, on the 18.04, the 
headphone/headset could output sound automatically after plugging in the audio 
jack.
- 
- [Fix]
- The root cause is the ucm2 conf defines 2 input devices: the Mic2 and Headset 
MIC, and the pulseaudio parse the input device Headset MIC first then Mic2, 
finally the audio jack is set to Mic2 mode, this make the audio jack can't 
output sound anymore. To fix it, let the audio jack set to Headset MIC mode by 
default (Headset MIC has higher priority than Mic2 in the ucm2 conf), to do so, 
let pulseaudio send the device event to module-switch-on-port-available by the 
order of priority in the umc2.
+  * On the Dell machines with multi function audio jack, the 
+headphone/headset can't output sound automatically, which is different 
+from ubuntu 18.04. The headphone/headset should be able to  output 
+sound automatically after plugging in the audio jack.
  
  [Test Case]
- applying the fix patch to pulseaudio, plug a headset/headphone to the multi 
function audio jack, play sound from headset/headphone, the sound could be 
heard from headset/headphone.
  
- [Regression Risk]
- Low, just do a small change to store the ucm devices by their priority. and 
upstream just merged this patch.
+  * Reproduce step:
+1. plug headphone/headset
+2. open g-c-c sound to check
+ 
+Expect result: The output device should switch to headphone or headset, 
+   since headphone's priority is higher in ucm2 config.
+Actual result: The output device is still internal speaker.
+
+ [Regression Potential]
+ 
+  * Low, just do a small change to store the ucm devices by their priority. 
+and upstream just merged this patch.
+ 
+ [Other]
+ 
+  * This bug originates from an OEM private bug #1875597, then ubuntu users 
+reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329 
+and the 1st issue of #1881659 have the same root cause as #1875597
+ 
+  * The root cause is the ucm2 conf defines 2 input devices: the Mic2 and 
+Headset MIC, and the pulseaudio parse the input device Headset MIC 
+first then Mic2, finally the audio jack is set to Mic2 mode, this make 
+the audio jack can't output sound anymore. To fix it, let the audio 
+jack set to Headset MIC mode by default (Headset MIC has higher 
+priority than Mic2 in the ucm2 conf), to do so, let pulseaudio send the 
+device event to module-switch-on-port-available by the order of 
+priority in the umc2.

** Description changed:

  [Impact]
  
-  * On the Dell machines with multi function audio jack, the 
-headphone/headset can't output sound automatically, which is different 
-from ubuntu 18.04. The headphone/headset should be able to  output 
-sound automatically after plugging in the audio jack.
+  * On the Dell machines with multi function audio jack, the
+    headphone/headset can't output sound automatically, which is different
+    from ubuntu 18.04. The headphone/headset should be able to  output
+    sound automatically after plugging in the audio jack.
  
  [Test Case]
  
-  * Reproduce step:
-1. plug headphone/headset
-2. open g-c-c sound to check
+  * On Tiger Lake platform
+Reproduce step:
+    1. plug headphone/headset
+    2. open g-c-c sound to check
  
-Expect result: The output device should switch to headphone or headset, 
-   since headphone's priority is higher in ucm2 config.
-Actual result: The output device is still internal speaker.
-
+    Expect result: The output device should switch to headphone or headset,
+   since headphone's priority is higher in ucm2 config.
+    Actual result: The output device is still internal speaker.
+ 
  [Regression Potential]
  
-  * Low, just do a small change to store the ucm devices by their priority. 
-and upstream just merged this patch.
+  * Low, just do a small change to store the ucm devices by their priority.
+    and upstream just merged this patch.
  
  [Other]
  
-  * This bug originates from an OEM private bug #1875597, then ubuntu users 
-reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329 
-and the 1st issue of #1881659 have the same root cause as #1875597
+  * This bug originates from an OEM private bug #1875597, then ubuntu users
+    reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329
+    and the 1st issue of #1881659 have the same root cause

[Desktop-packages] [Bug 1791761] Re: No mail retrieving from a local popa3d server with thunderbird 1.52.9.1

2020-07-09 Thread D. Hugh Redelmeier

I had a problem much like this.

- in 2020 January.

- Ubuntu 18.04

- broke when I updated Thunderbird from 1:52.7.0+build1-0ubuntu1

- fixed when I rolled it back and pinned it.

With recent updates, even 1:52.7.0+build1-0ubuntu1 failed in a way that
seems the same.

I then updated to the latest version and it still fails.

I have a POP server on my LAN.  Thunderbird accesses it using TLS.

tcpdump shows that Thunderbird opens a TCP/IP connection and does
nothing with it.

I seem to remember (from 2020 January) that someone said that the bug is
actually in a library.  Unfortunately I don't remember which one.  ldd
applied to thunderbird doesn't show any likely candidates.

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

Title:
  No mail retrieving from a local popa3d server with thunderbird
  1.52.9.1

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Software version : Thunderbird 1.52.9.1+buid3-Ounbuntu0.14.04.1

  From the update to this version no mail retrieve from my local pop3 server 
(popa3d) 
  Message: connection refused
  try with Claws : no problem
  try with old Thunderbird version (1.24.4.0) : no problem
  I've blocked this old version until the problem could be solved.

  PS: No SSL connection and Pass transmitted in Clear

  Best regards

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: thunderbird 1:24.4.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-135.161~14.04.1-generic 4.4.140
  Uname: Linux 4.4.0-135-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  BuildID: 20140318000702
  Channel: Unavailable
  CurrentDesktop: X-Cinnamon
  Date: Mon Sep 10 18:51:36 2018
  ForcedLayersAccel: False
  InstallationDate: Installed on 2015-12-13 (1002 days ago)
  InstallationMedia: Cubuntu 14.04.3.201c - Release amd64
  IpRoute:
   default via 192.168.1.1 dev eth0 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.2 
   192.168.5.0/24 dev eth1  proto kernel  scope link  src 192.168.5.1
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=24.4.0/20140318000702 (In use)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   freshplayerplugin 0.3.3+git20151209~webupd8~trusty
   icedtea-7-plugin  1.5.3-0ubuntu0.14.04.1
   rhythmbox-mozilla 3.0.2-0ubuntu2
   totem-mozilla 3.10.1-1ubuntu4
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 05/22/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0402
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5KPL-AM EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 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.:bvr0402:bd05/22/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-AMEPU:rvrx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  http_proxy: http://192.168.5.1:8080

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

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

[Desktop-packages] [Bug 1887018] [NEW] Xorg crash when I was using Visual Studio code, throwing me back to the login screen

2020-07-09 Thread Seija Kijin

Public bug reported:

Sometimes, when this happens, the computer goes to sleep too.

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
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Thu Jul  9 17:47:23 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 620 [1028:0810]
InstallationDate: Installed on 2020-07-06 (3 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
 Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 5570
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=b7d02d55-0b33-48b4-8eb2-5217925c5f81 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/20/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.5
dmi.board.name: 09YTN7
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5570
dmi.product.sku: 0810
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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

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


** Tags: amd64 apport-bug crash focal ubuntu

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

Title:
  Xorg crash when I was using Visual Studio code, throwing me back to
  the login screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes, when this happens, the computer goes to sleep too.

  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
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Thu Jul  9 17:47:23 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2020-07-06 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=b7d02d55-0b33-48b4-8eb2-5217925c5f81 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz

[Desktop-packages] [Bug 1886729] Re: Dell displayport YJ3Y6 adapter doesn't drive 4K screen properly

2020-07-09 Thread Robert Collins

It is super snappy but doesn't work any better: one of the external
monitors, or the other but not both.

I'm unfamiliar with Wayland, and Googling around has not found any
equivalent tools to xrandr to let me interrogate what the system thinks
is going on, so I've included a screenshot of the displays control
panel.

What further diagnostics would you like me to perform?

** Attachment added: "displays failure"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1886729/+attachment/5391134/+files/display-failure.png

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

Title:
  Dell displayport YJ3Y6 adapter doesn't drive 4K screen properly

Status in mutter package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have some early dell 4k 60hz screens - the ones which report 2
  panels internally for DP 60Hz - horrid hack I know; I recently got a
  new XPS laptop and put Ubuntu on it.

  That XPS laptop has two USB-C/thunderbolt ports, so to drive the
  screens I bought two slightly different DP adapters - one with power
  passthrough, and a cheaper one that only does DP.

  The more expensive one 'USB-C to HDMI/DP' drives the monitor happily
  over DP, though sadly only at 30Hz - can't have everything :/. It
  reports one monitor as one output: DP-1 in the attached information:

  DP-1 connected 3840x2160+0+0 (normal left inverted right x axis y axis) 527mm 
x 296mm
 3840x2160 29.98*+  30.0029.97  
 1920x1200 59.88  
  ...

  
  The cheaper one reports the single monitor as two distinct outputs, at 60hz 
interestingly - 

  DP-3-8 connected (normal left inverted right x axis y axis)
 1920x2160 59.99 +
  DP-3-9 connected 1920x2160+7680+0 (normal left inverted right x axis y axis) 
527mm x 296mm
 1920x2160 59.99*+
 1920x1200 59.88  

   which in theory if summed together would be one whole screen. But
  attempting to configure the output results in an error:

  xrandr --output DP-1 --auto --left-of eDP-1 --output DP-3-9 --auto --right-of 
DP-3-8 --output DP-3-8 --auto --right-of eDP-1
  xrandr: cannot find crtc for output DP-3-8

  I'm not sure if this is an intrinsic limitation of the USB-C->DP
  dongle, or whether there is something that can be done in the software
  to deal with this 10 year old hardware hack I have sitting on my
  desktop.

  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
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  8 11:20:17 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
 Subsystem: Dell Iris Plus Graphics G7 [1028:096d]
  InstallationDate: Installed on 2020-07-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. XPS 13 9300
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.11
  dmi.board.name: 0WX9VX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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/ubuntu/+source/mutter/+bug/1886729/+subscriptions

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

[Desktop-packages] [Bug 1883886] Re: Print dialogue's height in Libreoffice Writer is too high to see and click buttons.

2020-07-09 Thread Bug Watch Updater

** Bug watch added: Document Foundation Bugzilla #134679
   https://bugs.documentfoundation.org/show_bug.cgi?id=134679

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

Title:
   Print dialogue's height in Libreoffice Writer is too high to see and
  click buttons.

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

Bug description:
  Hello,

  I have the bug that is denoted here
  https://ask.libreoffice.org/en/question/240651/print-dialogue-too-
  large-to-select-ok-to-print/ and here
  https://bugs.documentfoundation.org/show_bug.cgi?id=127782#c67.

  Essentially, the libreoffice writer print's dialog box is too high for
  me to view and press the buttons with the mouse. A workaround is to
  just press ENTER to print.

  Please see the following screenshot for an example:
  https://snipboard.io/vc1X0f.jpg

  My information is as follows:

  Results of lsb_release -rd

  Description: Ubuntu 20.04 LTS
  Release: 20.04

  Results of apt-cache policy libreoffice-writer

  libreoffice-writer:
Installed: 1:6.4.3-0ubuntu0.20.04.1
Candidate: 1:6.4.3-0ubuntu0.20.04.1
Version table:
   *** 1:6.4.3-0ubuntu0.20.04.1 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1:6.4.2-0ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  Just FYI in case it is necessary: I am using Lubuntu 20.04 LTS with LXQt. 

  Best regards,

  
  Owen Charles

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-writer 1:6.4.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Wed Jun 17 12:47:56 2020
  InstallationDate: Installed on 2020-06-05 (11 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1883886]

2020-07-09 Thread Pmenzel+bugs-documentfoundation-org

I confirm, that on the Dell Latitude E7250 with Debian Sid/unstable with
GNOME 3.36.3 and LibreOffice 1:7.0.0~rc1-5, the issue is fixed.

There is a small glitch though, and I created bug #134679.

[1]: https://bugs.documentfoundation.org/show_bug.cgi?id=134679

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

Title:
   Print dialogue's height in Libreoffice Writer is too high to see and
  click buttons.

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

Bug description:
  Hello,

  I have the bug that is denoted here
  https://ask.libreoffice.org/en/question/240651/print-dialogue-too-
  large-to-select-ok-to-print/ and here
  https://bugs.documentfoundation.org/show_bug.cgi?id=127782#c67.

  Essentially, the libreoffice writer print's dialog box is too high for
  me to view and press the buttons with the mouse. A workaround is to
  just press ENTER to print.

  Please see the following screenshot for an example:
  https://snipboard.io/vc1X0f.jpg

  My information is as follows:

  Results of lsb_release -rd

  Description: Ubuntu 20.04 LTS
  Release: 20.04

  Results of apt-cache policy libreoffice-writer

  libreoffice-writer:
Installed: 1:6.4.3-0ubuntu0.20.04.1
Candidate: 1:6.4.3-0ubuntu0.20.04.1
Version table:
   *** 1:6.4.3-0ubuntu0.20.04.1 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1:6.4.2-0ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  Just FYI in case it is necessary: I am using Lubuntu 20.04 LTS with LXQt. 

  Best regards,

  
  Owen Charles

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-writer 1:6.4.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Wed Jun 17 12:47:56 2020
  InstallationDate: Installed on 2020-06-05 (11 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1887005] Re: Untranslatable "Ratio:" in compact view

2020-07-09 Thread Ubuntu Foundations Team Bug Bot

The attachment "translate-ratio.patch" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Untranslatable "Ratio:" in compact view

Status in transmission package in Ubuntu:
  New

Bug description:
  It is impossible now to translate "Ratio:" string in compact torrent
  list. Please apply the patch to fix the issue.

  https://git.launchpad.net/ubuntu/+source/transmission/tree/gtk
  /torrent-cell-
  renderer.c?id=3a7bff14283a3962b181bd1a9dc870cc356eaffe#n219

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

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

[Desktop-packages] [Bug 1887010] [NEW] problème de démarrage ordinateur lenovo G50

2020-07-09 Thread BEDECARRAX

Public bug reported:

Bonjour,

En marche, l'ordinateur avec ubuntu 18.04 fonctionne très bien. Il s'éteint 
facilement. Pour le re démarrer, l'écran reste noir très longtemps, parfois 
pendant une heure avant de retrouver le bureau et re fonctionner normalement. 
Le disque dur fonctionne normalement, la barette mémoire aussi que j'ai testé 
en la remplaçant par une neuve: le problème reste. Je ne comprends pas la cause 
de ce problème.
Pouvez vous m'aider? Merci

Hello,

When running, the computer with ubuntu 18.04 works very well. It goes out 
easily. To restart it, the screen remains black for a very long time, sometimes 
for an hour before finding the office and re-operating normally. The hard drive 
works normally, the memory module also that I tested by replacing it with a new 
one: the problem remains. I do not understand the cause of this problem.
Can you help me? Thank you
(I do not understand English)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-106.107-generic 4.15.18
Uname: Linux 4.15.0-106-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Jul  9 21:48:34 2020
DistUpgraded: 2019-08-20 08:07:14,386 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 5500 [17aa:390c]
   Subsystem: Lenovo Radeon R5 M330 [17aa:390c]
InstallationDate: Installed on 2019-08-14 (330 days ago)
InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227)
MachineType: LENOVO 80E5
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-106-generic 
root=UUID=5732a78d-7e74-4071-9c56-b93ae51ffae3 ro quiet splash
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2019-08-20 (324 days ago)
dmi.bios.date: 07/23/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: B0CN93WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Lenovo G50-80
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G50-80
dmi.modalias: 
dmi:bvnLENOVO:bvrB0CN93WW:bd07/23/2015:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoG50-80:
dmi.product.family: IDEAPAD
dmi.product.name: 80E5
dmi.product.version: Lenovo G50-80
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Wed Jun 24 22:12:46 2020
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.3
xserver.video_driver: modeset

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


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

Title:
  problème de démarrage ordinateur lenovo G50

Status in xorg package in Ubuntu:
  New

Bug description:
  Bonjour,

  En marche, l'ordinateur avec ubuntu 18.04 fonctionne très bien. Il s'éteint 
facilement. Pour le re démarrer, l'écran reste noir très longtemps, parfois 
pendant une heure avant de retrouver le bureau et re fonctionner normalement. 
Le disque dur fonctionne normalement, la barette mémoire aussi que j'ai testé 
en la remplaçant par une neuve: le problème reste. Je ne comprends pas la cause 
de ce problème.
  Pouvez vous m'aider? Merci

  Hello,

  When running, the computer with ubuntu 18.04 works very well. It goes out 
easily. To restart it, the screen remains black for a very long time, sometimes 
for an hour before finding the office and re-operating normally. The hard drive 
works normally, the memory module also that I tested by replacing it with a new 
one: the problem remains. I do not understand the cause of this problem.
  Can you help me? Thank you
  (I do not understand English)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1

[Desktop-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)

2020-07-09 Thread Noctis Bennington

Same result Kai-Heng. :(

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

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works",
  but it blinks, the image showed via HDMI on the second monitor blinks.
  So is impossible to work with it. Since all this time I was searching
  about this and I'm almost sure this is a problem of the GPU's Intel.
  But I saw this problem on askubuntu just with laptops with hybrid
  graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not
  sure if they have the same problem here).

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

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

[Desktop-packages] [Bug 1887005] [NEW] Untranslatable "Ratio:" in compact view

2020-07-09 Thread Nicholas Guriev

Public bug reported:

It is impossible now to translate "Ratio:" string in compact torrent
list. Please apply the patch to fix the issue.

https://git.launchpad.net/ubuntu/+source/transmission/tree/gtk/torrent-
cell-renderer.c?id=3a7bff14283a3962b181bd1a9dc870cc356eaffe#n219

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

** Patch added: "translate-ratio.patch"
   
https://bugs.launchpad.net/bugs/1887005/+attachment/5391110/+files/translate-ratio.patch

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

Title:
  Untranslatable "Ratio:" in compact view

Status in transmission package in Ubuntu:
  New

Bug description:
  It is impossible now to translate "Ratio:" string in compact torrent
  list. Please apply the patch to fix the issue.

  https://git.launchpad.net/ubuntu/+source/transmission/tree/gtk
  /torrent-cell-
  renderer.c?id=3a7bff14283a3962b181bd1a9dc870cc356eaffe#n219

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

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

[Desktop-packages] [Bug 1887001] [NEW] Mouse suddenly stopped working

2020-07-09 Thread Mubarak SULAYMAN

Public bug reported:

Mouse suddenly stopped working and didn't fix even after a reboot.

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
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: Thu Jul  9 19:40:16 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:146a]
InstallationDate: Installed on 2019-05-02 (434 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: Hewlett-Packard HP Pavilion dm4 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=a3b4ba1a-5361-47c5-9d78-b04d395d28b8 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/21/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.23
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 146A
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 58.27
dmi.chassis.asset.tag: CNU0483ZXV
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.23:bd10/21/2010:svnHewlett-Packard:pnHPPaviliondm4NotebookPC:pvr058B11242B1020100:rvnHewlett-Packard:rn146A:rvr58.27:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
dmi.product.name: HP Pavilion dm4 Notebook PC
dmi.product.sku: XH124UA#ABA
dmi.product.version: 058B11242B1020100
dmi.sys.vendor: Hewlett-Packard
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.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
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 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/1887001

Title:
  Mouse suddenly stopped working

Status in xorg package in Ubuntu:
  New

Bug description:
  Mouse suddenly stopped working and didn't fix even after a reboot.

  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
  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: Thu Jul  9 19:40:16 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:146a]
  InstallationDate: Installed on 2019-05-02 (434 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Hewlett-Packard HP Pavilion dm4 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=a3b4ba1a-5361-47c5-9d78-b04d395d28b8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.23
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 146A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 58.27
  dmi.chassis.asset.tag: CNU0483ZXV
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.23:bd10/21/2010:svnHewlett-Packard:pnHPPaviliondm4NotebookPC:pvr058B11242B1020100:rvnHewlett-Packard:rn146A:rvr58.27:cvnHewlett-Packard:ct10:cvrChassisVersion:

[Desktop-packages] [Bug 1886996] Re: Restore previous configuration after turning off fractional scaling does not work

2020-07-09 Thread Treviño

** Also affects: mutter (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: mutter (Ubuntu Focal)
   Status: New => In Progress

** Changed in: mutter (Ubuntu Focal)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: mutter (Ubuntu Focal)
   Importance: Undecided => Medium

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

Title:
  Restore previous configuration after turning off fractional scaling
  does not work

Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Focal:
  In Progress

Bug description:
  1. From control center, display panel, enable fractional scaling
  2. Set scaling to some fractional value and apply and confirm it.
  3. Turn off the fractional scaling switch and apply it
  4. Fractional scaling should be reverted to the selected integer scaling.
  5. When gnome-shell shows the confirmation dialog, click "Revert Settings"
  6. Expect the fractional scaling to be re-enabled and applied as it used to be

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

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

[Desktop-packages] [Bug 1886996] [NEW] Restore previous configuration after turning off fractional scaling does not work

2020-07-09 Thread Treviño

Public bug reported:

1. From control center, display panel, enable fractional scaling
2. Set scaling to some fractional value and apply and confirm it.
3. Turn off the fractional scaling switch and apply it
4. Fractional scaling should be reverted to the selected integer scaling.
5. When gnome-shell shows the confirmation dialog, click "Revert Settings"
6. Expect the fractional scaling to be re-enabled and applied as it used to be

** Affects: mutter (Ubuntu)
 Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: In Progress

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

Title:
  Restore previous configuration after turning off fractional scaling
  does not work

Status in mutter package in Ubuntu:
  In Progress

Bug description:
  1. From control center, display panel, enable fractional scaling
  2. Set scaling to some fractional value and apply and confirm it.
  3. Turn off the fractional scaling switch and apply it
  4. Fractional scaling should be reverted to the selected integer scaling.
  5. When gnome-shell shows the confirmation dialog, click "Revert Settings"
  6. Expect the fractional scaling to be re-enabled and applied as it used to be

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

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

[Desktop-packages] [Bug 1879053] Re: Fractional Upscaling is descaling Certain Apps

2020-07-09 Thread Treviño

This is not something that we can fix at mutter level, does the scaling
work properly when using 200%?

Otherwise this is a not-fixing for mutter, while the toolkits should be
fixed to handle the X11 scaling.

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

Title:
  Fractional Upscaling is descaling Certain Apps

Status in mutter package in Ubuntu:
  New
Status in wine package in Ubuntu:
  New

Bug description:
  1) Description:   Ubuntu 20.04 LTS
  Release:  20.04
  2) wine-development:
    Installed: 5.5-3ubuntu1
    Candidate: 5.5-3ubuntu1
  Same goes for wine stable 5.0.
  Other Packages foxit 2.4.4.xx, Notepad v7.8.6

  3) I'm using a relatively small QHD Display. The Fractional Scaling
  Feature is really something I've looked forward to and I'm super
  grateful that it has been implemented. With my setup my life gets
  easier when having a little zoom but still have a good amount of
  pixels and nice sharpness on my workspace :D

  4) With some apps the fractional scaling has an opposite effect. For
  example wine apps and foxit reader appear tiny with fractional scaling
  turned on (I'm using 125%) and the apps shrink compared to 100%.

  Is this the right place to report the bug or do i need to make a
  bugreport for every specific app?

  Kind regards,
  Tobi

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

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

[Desktop-packages] [Bug 1876219] Re: iris driver for old cpu

2020-07-09 Thread arno

This bug disappears if I go back from intel x driver to standard
modesetting driver. I didn't to that intenionally. I haven't been aware
of that, but to get xbacklight working (to change screen brightness) I
activated that. After removing that change in /etc/X11 mpv/celluloid
works without this variable.

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

Title:
  iris driver for old cpu

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  I am not completely sure where I should file the bug. I am using
  Lubuntu 20.04 with lxqt, and since the upgrade to 20.04 iris is the
  default graphics driver, which results in crashes in multiple apps
  including guvcview and calibre. Setting
  MESA_LOADER_DRIVER_OVERRIDE=i965 fixed the problem. I am not sure but
  is it true that iris does not support older generations of Intel CPUs?
  If it is the case would it be possible to revert to i965 in those
  circumstances? Thanks!

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

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

[Desktop-packages] [Bug 1886948] Re: Can't calibrate monitor

Thank you for your bug report, that sounds like an issue upstream, could
you report it upstream on

https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues ?

it seems similar to https://gitlab.gnome.org/GNOME/gnome-control-
center/-/issues/951

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #951
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/951

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Can't calibrate monitor

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

Bug description:
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  Tried to calibrate my monitor with an external device (x-rite huey
  pro). Process seems to go fine and starts working on the calibration.
  At about 80% of the progress bar  I receive the message (in basque,
  not sure where to search it in english):

  Kalibrazioak huts egin du
  Kalibratzeko behar diren tresnak ez daude instalatuta
  Kalibrazioaren gailua ken dezakezu

  Which translates to (free non-official translation)

  Calibration has failed.
  The tools needed for calibration are not installed
  You can remove the calibration device

  Launching the tool from the command line, I receive these messages:

  (gnome-control-center:3471): color-cc-panel-WARNING **: 13:28:57.868: 
calibration failed with code 4: failed to get filename for colprof
  (gnome-control-center:3471): color-cc-panel-WARNING **: 13:33:46.435: Failed 
to send Cancel: GDBus.Error:org.freedesktop.ColorHelper.Internal: cannot cancel 
as status is idle
  (gnome-control-center:3471): color-cc-panel-WARNING **: 13:33:46.436: failed 
to start calibrate: failed to calibrate

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  9 13:38:26 2020
  InstallationDate: Installed on 2020-06-25 (14 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=eu_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1886986] [NEW] Two-finger scrolling stops working after resume from suspend

2020-07-09 Thread Eric Floehr

Public bug reported:

Two-finger scrolling works fine on boot, but on my Thinkpad T440s after
I resume from suspend, two-finger scrolling no longer works. Touchpad
still works to move the mouse and click, but two-finger scrolling does
not.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-input-synaptics (not installed)
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul  9 13:19:48 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
InstallationDate: Installed on 2020-07-08 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324)
MachineType: LENOVO 20AQCTO1WW
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=73c278e2-f6ac-4e7d-b045-af3f1fe950bd ro quiet splash vt.handoff=7
SourcePackage: xserver-xorg-input-synaptics
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/10/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET71WW (2.21 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AQCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: 0B98405 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T440s
dmi.product.name: 20AQCTO1WW
dmi.product.sku: LENOVO_MT_20AQ_BU_Think_FM_ThinkPad T440s
dmi.product.version: ThinkPad T440s
dmi.sys.vendor: LENOVO
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.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

** Affects: xserver-xorg-input-synaptics (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Two-finger scrolling stops working after resume from suspend

Status in xserver-xorg-input-synaptics package in Ubuntu:
  New

Bug description:
  Two-finger scrolling works fine on boot, but on my Thinkpad T440s
  after I resume from suspend, two-finger scrolling no longer works.
  Touchpad still works to move the mouse and click, but two-finger
  scrolling does not.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-input-synaptics (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  9 13:19:48 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  InstallationDate: Installed on 2020-07-08 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324)
  MachineType: LENOVO 20AQCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=73c278e2-f6ac-4e7d-b045-af3f1fe950bd ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/10/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET71WW (2.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20AQCTO1WW
  dmi.product.sku: LENOVO_MT_20AQ_BU_Think_FM_ThinkPad T440s
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri:

[Desktop-packages] [Bug 1876894] Re: Scaling is not reverted properly (appears shrunk) when disabling fractional scaling

Testing 1:3.36.3-0ubuntu1 there is no scaling to a tiny ration, marking
as verified

** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-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/1876894

Title:
  Scaling is not reverted properly (appears shrunk) when disabling
  fractional scaling

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

Bug description:
  * Impact

  Scaling is not reverted properly (appears shrunk) when disabling
  fractional scaling

  
  * Test Case

  Do this in an Ubuntu/Xorg session:

  0. Be on a "clean" system wrt. fractional scaling, i.e. disabled & scaling at 
100%
  1. Open gnome-control-center → displays
  2. Turn on fractional scaling
  3. Select 125%
  4. Press apply (the scaling should correctly change now)
  5. Turn off fractional scaling by changing the toggle

  Now everything is shrunk - it's not been returned to 100% properly.
  See the attached screenshot where the text is tiny instead of regular
  100% size. If you do this instead of step 5:

  5. Select 100% scaling
  7. Press apply
  8. Turn off fractional scaling by changing the toggle

  Then everything returns to the normal size.

  I'm on nvidia(-440), but Séb said that he saw this on his Intel
  machine too.

  
  * Regression potential

  Verify that scaling changes are correctly applied on different setup

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.1-3ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Tue May  5 10:57:40 2020
  InstallationDate: Installed on 2012-10-07 (2766 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to focal on 2020-01-16 (109 days ago)

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

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

[Desktop-packages] [Bug 1876891] Re: The fractional scaling toggle applies instantly and not when "Apply" is pressed

Testing 1:3.36.3-0ubuntu1 the toggle doesn't trigger the action and the
user needs to press apply as expected, marked as verified

** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-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/1876891

Title:
  The fractional scaling toggle applies instantly and not when "Apply"
  is pressed

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

Bug description:
  * Impact

  The fractional scaling toggle applies instantly and not when "Apply"
  is pressed

  * Test Case

  Do this when in an Xorg/Ubuntu session:

  0. Have fractional scaling disabled and set to 100%
  1. Go to gnome-control-center -> displays
  2. Turn on the fractional scaling toggle
  3. Select 125%
  4. Press apply (the scaling should apply correctly)
  5. Turn off the toggle
  6. Turn the toggle back on

  At 5 and 6, the scaling changes. It shouldn't - this should only
  happen when you press 'Apply'. The toggle needs to not be directly
  connected to GSettings.

  * Regression potential

  Check that screen settings changed are correctly applied and only when
  clicking the corresponding button

  

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Tue May  5 10:35:48 2020
  InstallationDate: Installed on 2012-10-07 (2766 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2020-01-16 (109 days ago)

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

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

[Desktop-packages] [Bug 1886024] Re: Removal of dropped arch: Groovy - arm64, riscv64 and s390x

2020-07-09 Thread Steve Langasek

This was handled via #ubuntu-release IRC (the preferred mechanism for
requesting binary removals).

** Changed in: bbswitch (Ubuntu Groovy)
   Status: New => Fix Released

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

Title:
  Removal of dropped arch: Groovy - arm64, riscv64 and s390x

Status in bbswitch package in Ubuntu:
  Fix Released
Status in bbswitch source package in Groovy:
  Fix Released

Bug description:
  https://people.canonical.com/~ubuntu-archive/proposed-
  migration/groovy/update_excuses.html

  bbswitch 0.8-9 is stuck[*] in groovy-proposed/universe, since it
  dropped arm64, riscv64 and s390x - can we get those removed from the
  archive?

  *:
  
https://wiki.ubuntu.com/ProposedMigration#My_package_is_stalled_because_it.27s_out_of_date_on_some_architecture.__What_do_I_do.3F

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

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

[Desktop-packages] [Bug 1877774] Re: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_chang

2020-07-09 Thread Brendan_P

Via dup: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1886672

For me, the issue is fixed when unlocking the screen.

However NOT when resuming laptop after a suspend.

Laptop, using laptop display only > Suspend > Plugin additional monitor
> Resume. Only laptop screen is active.

Login > Restart Gnome-shell, second screen resumes.

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

Title:
  gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()
  from st_theme_node_paint_equal() from st_widget_recompute_style() from
  st_widget_style_changed() [when locking the screen] [usually due to
  dash-to-panel]

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  GNOME shell crashes on extensions loading / updates

  [ Test case ]
   - No clear test case, normally may happen during screen locking/unlocking
   - But crashes should be monitored at
 https://errors.ubuntu.com/problem/4127e7e714fd28c090da0220de2ff06e71274eda

  [ Regression potential ]

  Stylesheet memory could be leaked

  ---

  Seems to be reproducible
  Suspend the computer
  Start the computer from suspend
  Start chrome gmail.
  Has happened two times

  ProblemType: CrashDistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.36.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu33
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  9 20:00:47 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-04-16 (23 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415.2)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fe1b40c4252 <_st_theme_node_ensure_background+226>: 
mov(%rax),%r12
   PC (0x7fe1b40c4252) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%r12" ok
  SegvReason: reading NULL VMA
  Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
   _st_theme_node_ensure_background () from /usr/lib/gnome-shell/libst-1.0.so
   st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   st_widget_style_changed () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1886977] [NEW] Grid-like cursor movement on touchpad

2020-07-09 Thread Mladen Jablanovic

Public bug reported:

Moving cursor using touchpad goes in zigzag pattern, when moving diagonally.
The laptop is Toshiba Portege R830

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libinput10 1.10.4-1ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-62-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CurrentDesktop: MATE
Date: Thu Jul  9 17:35:34 2020
SourcePackage: libinput
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Description changed:

- Moving cursor using touchpad goes in zigzag pattern, when moving
- diagonally.
+ Moving cursor using touchpad goes in zigzag pattern, when moving diagonally.
+ The laptop is Toshiba Portege R830
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libinput10 1.10.4-1ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-62-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Jul  9 17:35:34 2020
  SourcePackage: libinput
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Grid-like cursor movement on touchpad

Status in libinput package in Ubuntu:
  New

Bug description:
  Moving cursor using touchpad goes in zigzag pattern, when moving diagonally.
  The laptop is Toshiba Portege R830

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libinput10 1.10.4-1ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-62-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Jul  9 17:35:34 2020
  SourcePackage: libinput
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1886869] Re: Double dock after screen lock.

2020-07-09 Thread Amir Alcocer May

Thank you for your reply, apparently i have 2 docks, disabling
extensions solves this problem, but after disabling all extensions and
locking the screen now i see the dock on the blocked screen.

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

Title:
  Double dock after screen lock.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After locking my screen and unlocking, i see a double dock. The first
  one have the trash can icon and the main one doesn't.

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Es un directorio: 
'/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  440.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/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: Wed Jul  8 15:27:41 2020
  DistUpgraded: 2020-04-24 12:10:19,615 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso 
hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.100, 5.4.0-39-generic, x86_64: installed
   nvidia, 440.100, 5.4.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] 
[1002:9874] (rev e6) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon R7 Graphics [1458:d000]
   NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GK208B [GeForce GT 710] [1458:375a]
  InstallationDate: Installed on 2020-04-04 (94 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   LANGUAGE=es_MX:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_MX.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=acb80b2e-decc-41c3-b1b0-daa06a3b7465 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-24 (75 days ago)
  dmi.bios.date: 10/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FD
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A68HM-H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFD:bd10/09/2018:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A68HM-H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 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.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/ubuntu/+source/gnome-shell/+bug/1886869/+subscriptions

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

[Desktop-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones

2020-07-09 Thread animesh garg

same issue on hp pavillion au620tx
# 17 works

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

Title:
  Crackling and popping sound when using headphones

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Arch Linux:
  New
Status in Fedora:
  New

Bug description:
  Laptop is  HP Pavilion - 15-au118tx. The laptop has B and O play and
  the output from speakers are just fine, when using headphones there is
  some kind of crackling and popping sound in both ears but prominently
  in the left ear.

  The issue happens only when the sound is played, if i reduce the PCM
  way low using alsamixer, the effect is minimized but the volume is
  also reduced. Increasing the volume in the panel increases the PCM as
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antony 1719 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Dec  7 23:30:05 2016
  InstallationDate: Installed on 2016-11-20 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] 
Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689

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

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

[Desktop-packages] [Bug 1882161] Re: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority

2020-07-09 Thread Łukasz Zemczak

The test case seems very vague sadly, could we get it a bit better
clarified. What I mean is: what are the preliminary requirements for the
test case to be valid? Does it have to be performed on specific
hardware? What kind of hardware should it be? The regression potential
field also doesn't say much about the regression potential, e.g. where
possible regressions could be seen. I would appreciate if someone could
update it with some regression analysis: what else can this break? Can
different devices stop working by this? Which code paths are being
touched by this change?

Thanks!

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

Title:
  module-switch-on-port-avaiable: switch the port on ucm devices based
  on the priority

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  This bug originates from an OEM private bug #1875597, then ubuntu
  users reported 2 public bugs #1871329 and #1881659. The 2nd issue of
  #1871329 and the 1st issue of #1881659 have the same root cause as
  #1875597

  [Impact]
  On the Dell machines with multi function audio jack, after installing the 
ubuntu 20.04 and if the audio driver is sof instead of legacy hda, the 
headphone/headset can't output sound automatically after users plug in a 
headphone/headset. This is different from ubuntu 18.04, on the 18.04, the 
headphone/headset could output sound automatically after plugging in the audio 
jack.

  [Fix]
  The root cause is the ucm2 conf defines 2 input devices: the Mic2 and Headset 
MIC, and the pulseaudio parse the input device Headset MIC first then Mic2, 
finally the audio jack is set to Mic2 mode, this make the audio jack can't 
output sound anymore. To fix it, let the audio jack set to Headset MIC mode by 
default (Headset MIC has higher priority than Mic2 in the ucm2 conf), to do so, 
let pulseaudio send the device event to module-switch-on-port-available by the 
order of priority in the umc2.

  [Test Case]
  applying the fix patch to pulseaudio, plug a headset/headphone to the multi 
function audio jack, play sound from headset/headphone, the sound could be 
heard from headset/headphone.

  [Regression Risk]
  Low, just do a small change to store the ucm devices by their priority. and 
upstream just merged this patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1882161/+subscriptions

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

[Desktop-packages] [Bug 1885673] Re: won't auto-select input when headset is plugged and selected in pop-up window

@Yuan, yes, it's fine to do but the SRU team usually create those when
accepting the upload

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

Title:
  won't auto-select input when headset is plugged and selected in pop-up
  window

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

Bug description:
  [Impact]

   * audio input won't auto select and no pop-up dialog when headset is
  plugged

   * backporting fix gitlab_ucm_mixer_control_select.patch in groovy to
  focal.

  [Test Case]

   * Using Tiger Lake platform
   * Step to reproduce:
     1. plug-in headset
     2. check g-c-c

     Expected result:
       audio input switch to headset mic.

     Actual result:
       audio input is not changed.

  [Regression Potential]

   * the change corrupt the audio device selection, the audio
  input/output is not as expect

  [Other Info]

   * a patch is there waiting for upstream review :
  https://gitlab.gnome.org/GNOME/libgnome-volume-
  control/-/merge_requests/10

   * Test pass after 'do-release-upgrade -d' on the Tiger Lake platform
  to groovy with gnome-control-center_1:3.36.4-1ubuntu1.

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

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

[Desktop-packages] [Bug 1857252] Re: chromium 79 remote display broken

2020-07-09 Thread Bug Watch Updater

** Changed in: chromium (Debian)
   Status: New => Fix Released

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

Title:
  chromium 79 remote display broken

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in chromium package in Debian:
  Fix Released
Status in chromium package in Fedora:
  Unknown

Bug description:
  Chromium 78 worked and things broke in version 79.

  With chromium 79 when using the remote display (ssh for x forward) I
  get the display forward but only a blank (white) window. Chromiumn
  does not render anything into the window.

  If I am at the console then every thing work normal. Also Firefox does
  work for remote display. It just chromium 79 that has this problem.

  Every thing worked with version 78.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.36
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: GNOME
  Date: Sun Dec 22 14:57:30 2019
  InstallationDate: Installed on 2016-07-24 (1246 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to bionic on 2018-09-03 (475 days ago)
  VarLogDistupgradeTermlog:

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

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

[Desktop-packages] [Bug 1886812] Re: Mysterious image on first boot lock screen

Found it with the help of AskUbuntu guys:

https://askubuntu.com/questions/1257334/mysterious-image-on-first-boot-
lock-screen

Seems that is a "bug" on the theme I was using, not an Ubuntu one. But
we can use this for reference. :-)

That beach was driving me mad! :-)

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

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

Title:
  Mysterious image on first boot lock screen

Status in gnome-shell package in Ubuntu:
  Opinion

Bug description:
  I'm using Ubuntu 20.04 and noticed a weird behavior. When I define the
  wallpaper image, ok, now is the same image for the lock screen and
  wallpaper, but on every first boot I get a mysterious image I don't
  know where is coming from. Is a beach or something. I already checked
  my images on home and even removed the wallpaper images from /usr, but
  the mysterious image is still there. Any tips how can I change it?
  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  8 08:41:59 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-05 (855 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-05-09 (60 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2018-03-12T07:12:03.188751

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

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

[Desktop-packages] [Bug 1885673] Re: won't auto-select input when headset is plugged and selected in pop-up window

2020-07-09 Thread Yuan-Chen Cheng

If we still need to land in focal, shall we affect focal series for
g-c-c?

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

Title:
  won't auto-select input when headset is plugged and selected in pop-up
  window

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

Bug description:
  [Impact]

   * audio input won't auto select and no pop-up dialog when headset is
  plugged

   * backporting fix gitlab_ucm_mixer_control_select.patch in groovy to
  focal.

  [Test Case]

   * Using Tiger Lake platform
   * Step to reproduce:
     1. plug-in headset
     2. check g-c-c

     Expected result:
       audio input switch to headset mic.

     Actual result:
       audio input is not changed.

  [Regression Potential]

   * the change corrupt the audio device selection, the audio
  input/output is not as expect

  [Other Info]

   * a patch is there waiting for upstream review :
  https://gitlab.gnome.org/GNOME/libgnome-volume-
  control/-/merge_requests/10

   * Test pass after 'do-release-upgrade -d' on the Tiger Lake platform
  to groovy with gnome-control-center_1:3.36.4-1ubuntu1.

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

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

[Desktop-packages] [Bug 1878507] Re: No HDMI audio in ubuntu 20.04

Can you please temporarily remove "~/.config/pulse/* " and attach `pactl
list cards` here? Thanks!

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

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

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

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

Title:
  No HDMI audio in ubuntu 20.04

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

Bug description:
  Sound settings does not offer hdmi audio in 20.04, but was there in 16 and 18 
LTSs.
  New HDMI monitor is fine but no audio. Reboot to Ubuntu 16.04.1 LTS (16.04) 
{linux /boot/vmlinuz-4.4.0-24-generic} and all is well.

  ALSA Information Script v 0.4.65 ran giving result at:
  http://alsa-project.org/db/?f=84926788cff2eb5d8d305d6a896608514495ce2f

  Deleting ~/.config/pulse/* broke all the sound but ok again when
  restored

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paul   1715 F pulseaudio
   /dev/snd/controlC1:  paul   1715 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 01:06:50 2020
  HibernationDevice: RESUME=UUID=6ee76bfb-393c-47bf-807f-6d0d8929c120
  InstallationDate: Installed on 2016-06-15 (1428 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=a0ad560d-ee6e-4f49-b40f-d239ecfcf167 ro persistent quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-06 (7 days ago)
  dmi.bios.date: 12/22/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0915
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A785TD-M EVO
  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.:bvr0915:bd12/22/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-MEVO: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.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers w

2020-07-09 Thread Prajwal Manandhar

Hello, I am having the same issues in my hp envy y013cl laptop.I tried
the above steps but could not get the audio from speakers working.Please
help me fix this issue.Will provide all the necessary logs.

Aplay-l
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: CX8200 Analog [CX8200 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

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

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP

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

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

[Desktop-packages] [Bug 1886812] Re: Mysterious image on first boot lock screen

This is the image I don't know where come from.

** Attachment added: "screenshot2.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886812/+attachment/5391046/+files/screenshot2.png

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

Title:
  Mysterious image on first boot lock screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I'm using Ubuntu 20.04 and noticed a weird behavior. When I define the
  wallpaper image, ok, now is the same image for the lock screen and
  wallpaper, but on every first boot I get a mysterious image I don't
  know where is coming from. Is a beach or something. I already checked
  my images on home and even removed the wallpaper images from /usr, but
  the mysterious image is still there. Any tips how can I change it?
  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  8 08:41:59 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-05 (855 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-05-09 (60 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2018-03-12T07:12:03.188751

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

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

[Desktop-packages] [Bug 1760399] Re: New On-screen keyboard does not appear automatically when selecting some text fields

2020-07-09 Thread Mario Vukelic

@michel.ekimia, please see bug #1880596

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

Title:
  New On-screen keyboard does not appear automatically when selecting
  some text fields

Status in OEM Priority Project:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Bionic:
  Fix Released
Status in gnome-shell source package in Bionic:
  Fix Released
Status in gnome-settings-daemon source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  on-screen keyboard cannot be reliably opened when running under xorg.

  [Test Case]
  1. Login into an xorg session
  1. Open an application with text-entries (e.g. Firefox)
  2. Try to enter text in a text entry using the new OSK

  Expected results:
  The on-screen keyboard should appear.

  [Regression Potential]
  The proposed fix requires a change in the way gnome-settings-daemon decides 
to enable or disable ibus. Please make sure that ibus correctly works when
  using a keyboard layout that requires it (e.g. chinese).

  [Original Report]
  I have always used an on-screen keyboard as a virtual keyboard for entering 
text in a different layout than my physical keyboard. This time I cannot, since 
I cannot manually trigger the new OSK.

  Steps:

  1. Open Firefox
  2. Try to enter text in a different layout using the new OSK
  3. You cannot make the OSK appear

  When enabled, the new OSK appears automatically in Activities, but I
  cannot trigger it outside GNOME apps. You have to enable the new OSK
  first from Universal Access in Settings.

  I consider this a regression from 16.04 LTS, where On-board is easily
  triggered.

  Workaround:

  sudo apt install onboard

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  1 11:31:16 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-02 (180 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (4 days ago)

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

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

[Desktop-packages] [Bug 1886812] Re: Mysterious image on first boot lock screen

This is what happens after I log in again. Seems that is something
related with user session.

** Attachment added: "screenshot3.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886812/+attachment/5391047/+files/screenshot3.png

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

Title:
  Mysterious image on first boot lock screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I'm using Ubuntu 20.04 and noticed a weird behavior. When I define the
  wallpaper image, ok, now is the same image for the lock screen and
  wallpaper, but on every first boot I get a mysterious image I don't
  know where is coming from. Is a beach or something. I already checked
  my images on home and even removed the wallpaper images from /usr, but
  the mysterious image is still there. Any tips how can I change it?
  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  8 08:41:59 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-05 (855 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-05-09 (60 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2018-03-12T07:12:03.188751

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

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

[Desktop-packages] [Bug 1886812] Re: Mysterious image on first boot lock screen

Guys, just noticed that *after* the first boot, if I click on the user
icon on the bottom right (screenshot1.png), I also get the mysterious
background (screenshot2.png) and after log in again, I get a delay
(screenshot3.png).

** Attachment added: "screenshot1.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886812/+attachment/5391045/+files/screenshot1.png

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

Title:
  Mysterious image on first boot lock screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I'm using Ubuntu 20.04 and noticed a weird behavior. When I define the
  wallpaper image, ok, now is the same image for the lock screen and
  wallpaper, but on every first boot I get a mysterious image I don't
  know where is coming from. Is a beach or something. I already checked
  my images on home and even removed the wallpaper images from /usr, but
  the mysterious image is still there. Any tips how can I change it?
  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  8 08:41:59 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-05 (855 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-05-09 (60 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2018-03-12T07:12:03.188751

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

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

[Desktop-packages] [Bug 1886812] Re: Mysterious image on first boot lock screen

I'm running some scripts here to try to find all the images with more
than 800px on all over the system. As soon as I get and check the
results, I came back here with some news. :-)

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

Title:
  Mysterious image on first boot lock screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I'm using Ubuntu 20.04 and noticed a weird behavior. When I define the
  wallpaper image, ok, now is the same image for the lock screen and
  wallpaper, but on every first boot I get a mysterious image I don't
  know where is coming from. Is a beach or something. I already checked
  my images on home and even removed the wallpaper images from /usr, but
  the mysterious image is still there. Any tips how can I change it?
  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  8 08:41:59 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-05 (855 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-05-09 (60 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2018-03-12T07:12:03.188751

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

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

[Desktop-packages] [Bug 1886279] Re: simple-scan pdf compression

2020-07-09 Thread Degrange Thomas

As a user I like to know what happens inside things.

I would like a combo-box in "preferences" giving the following choices for 
saving to pdf:
1) Jpeg or zlib (smallest one chosen for each image) -> default
2) Jpeg only (lossy)
3) Zlib only (lossless)

Your proposition is much simpler, however it remains opaque to users.

It depends on the audience you target.

Note: I just installed everything to disable jpeg compression in a local
build (quick hack) and debug the program. It is my first time with Vala
+ Gtk. So we may have more technical discussion now.

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

Title:
  simple-scan pdf compression

Status in simple-scan package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  PDF compression cannot appropriately be configured.

  Having taken a look at the latest source code of simple-scan:
  1) simple-scan compresses each image in ZLIB or JPEG depending on the 
compressed size (it keeps the ZLIB version if it is smaller than the JPEG)
  2) the "quality" setting only applies to JPEG

  With this in mind, I think it is impossible to use simple-scan to
  create a PDF full of lossless ZLIB images for archiving documents
  where we want to keep quality at the expense of the size.

  Best regards

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

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

[Desktop-packages] [Bug 1760399] Re: New On-screen keyboard does not appear automatically when selecting some text fields

2020-07-09 Thread Michel-Ekimia

@vita-cell : Same here on 20.04 , no OSK in oem-config :-( , did you
open a new bug ?

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

Title:
  New On-screen keyboard does not appear automatically when selecting
  some text fields

Status in OEM Priority Project:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Bionic:
  Fix Released
Status in gnome-shell source package in Bionic:
  Fix Released
Status in gnome-settings-daemon source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  on-screen keyboard cannot be reliably opened when running under xorg.

  [Test Case]
  1. Login into an xorg session
  1. Open an application with text-entries (e.g. Firefox)
  2. Try to enter text in a text entry using the new OSK

  Expected results:
  The on-screen keyboard should appear.

  [Regression Potential]
  The proposed fix requires a change in the way gnome-settings-daemon decides 
to enable or disable ibus. Please make sure that ibus correctly works when
  using a keyboard layout that requires it (e.g. chinese).

  [Original Report]
  I have always used an on-screen keyboard as a virtual keyboard for entering 
text in a different layout than my physical keyboard. This time I cannot, since 
I cannot manually trigger the new OSK.

  Steps:

  1. Open Firefox
  2. Try to enter text in a different layout using the new OSK
  3. You cannot make the OSK appear

  When enabled, the new OSK appears automatically in Activities, but I
  cannot trigger it outside GNOME apps. You have to enable the new OSK
  first from Universal Access in Settings.

  I consider this a regression from 16.04 LTS, where On-board is easily
  triggered.

  Workaround:

  sudo apt install onboard

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  1 11:31:16 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-02 (180 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (4 days ago)

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

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

[Desktop-packages] [Bug 1867402] Re: [snap] Icons in file picker are corrupted

2020-07-09 Thread Chris Williamson

I have this same problem. I'm running Kubuntu 20.04 with Chromium snap
revision 1213.

** Attachment added: "Screenshot_20200709_073623.png"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1867402/+attachment/5391040/+files/Screenshot_20200709_073623.png

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

Title:
  [snap] Icons in file picker are corrupted

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  See the attached picture. This happens in bionic.

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

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

[Desktop-packages] [Bug 1864365] Re: [snap] Dialog font missing

2020-07-09 Thread Olivier Tilloy

Thanks for the feedback Chris. The garbled icons problem is a different
one indeed, tracked by bug #1867402.

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

Title:
  [snap] Dialog font missing

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  $ lsb_release -rb
  Description:  Ubuntu 19.10
  Release:  19.10

  $ snap info chromium
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: Canonical✓
  store-url: https://snapcraft.io/chromium
  contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
  license:   unset
  description: |
    An open-source browser project that aims to build a safer, faster, and more 
stable way for all
    Internet users to experience the web.
  commands:
    - chromium.chromedriver
    - chromium
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: latest/stable
  refresh-date: 3 days ago, at 01:56 CET
  channels:
    stable:80.0.3987.116 2020-02-19 (1036) 160MB -
    candidate: 80.0.3987.116 2020-02-19 (1036) 160MB -
    beta:  81.0.4044.17  2020-02-17 (1028) 161MB -
    edge:  81.0.4044.17  2020-02-14 (1028) 161MB -
  installed:   80.0.3987.116(1036) 160MB -

  Basic Ubuntu 19.10 installation using "factory default" font settings.

  Expected :
  When opening any file dialog (to open or upload a file, for example) from 
Chromium snap application, the file dialog renders normally.

  What happened instead:
  When opening any file dialog (to open or upload a file, for example) from 
Chromium snap application, all characters in the dialog box are empty squares 
(see attached screenshot).

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

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

[Desktop-packages] [Bug 1864365] Re: [snap] Dialog font missing

2020-07-09 Thread Chris Williamson

Olivier:

I am running revision 1213 on Kubuntu 20.04. Removing
~/snap/chromium/common/.cache fixed this issue for me, and it has not
returned after multiple restarts nor after I installed the font as
described in comment #11.

Before I removed the .cache directory, my file dialogs did look very
much like the screenshot Steven posted in comment #1, with rectangles
instead of letters. But now that the letters are back, I notice that
many of the icons are garbled, which is different from Steven's
screenshot. So for sure at least the icon part is a different issue, and
I will look to see if anyone else has posted it, or else I'll post it as
a new bug.

I am now assuming that my font problem was a different issue as well, so
I'm going to stick with the revision I have, unless it would help you
for me to try revision 1221 too, in which case please let me know. :-)

** Attachment added: "Screenshot_20200709_073623.png"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864365/+attachment/5391039/+files/Screenshot_20200709_073623.png

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

Title:
  [snap] Dialog font missing

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  $ lsb_release -rb
  Description:  Ubuntu 19.10
  Release:  19.10

  $ snap info chromium
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: Canonical✓
  store-url: https://snapcraft.io/chromium
  contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
  license:   unset
  description: |
    An open-source browser project that aims to build a safer, faster, and more 
stable way for all
    Internet users to experience the web.
  commands:
    - chromium.chromedriver
    - chromium
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: latest/stable
  refresh-date: 3 days ago, at 01:56 CET
  channels:
    stable:80.0.3987.116 2020-02-19 (1036) 160MB -
    candidate: 80.0.3987.116 2020-02-19 (1036) 160MB -
    beta:  81.0.4044.17  2020-02-17 (1028) 161MB -
    edge:  81.0.4044.17  2020-02-14 (1028) 161MB -
  installed:   80.0.3987.116(1036) 160MB -

  Basic Ubuntu 19.10 installation using "factory default" font settings.

  Expected :
  When opening any file dialog (to open or upload a file, for example) from 
Chromium snap application, the file dialog renders normally.

  What happened instead:
  When opening any file dialog (to open or upload a file, for example) from 
Chromium snap application, all characters in the dialog box are empty squares 
(see attached screenshot).

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

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

[Desktop-packages] [Bug 1886279] Re: simple-scan pdf compression

2020-07-09 Thread Bartosz Kosiorek

The code responsible for encoding pdf is available here:
https://gitlab.gnome.org/GNOME/simple-scan/-/blob/master/src/book.vala#L348

It is comparing jpeg with zlib:
https://gitlab.gnome.org/GNOME/simple-scan/-/blob/master/src/book.vala#L479

How would you like to change it?
What do you think about setting quality to maximum, force zlib compression?

** Changed in: simple-scan (Ubuntu)
   Status: New => Incomplete

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

Title:
  simple-scan pdf compression

Status in simple-scan package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  PDF compression cannot appropriately be configured.

  Having taken a look at the latest source code of simple-scan:
  1) simple-scan compresses each image in ZLIB or JPEG depending on the 
compressed size (it keeps the ZLIB version if it is smaller than the JPEG)
  2) the "quality" setting only applies to JPEG

  With this in mind, I think it is impossible to use simple-scan to
  create a PDF full of lossless ZLIB images for archiving documents
  where we want to keep quality at the expense of the size.

  Best regards

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

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

[Desktop-packages] [Bug 1886948] [NEW] Can't calibrate monitor

2020-07-09 Thread Gari Araolaza

Public bug reported:

Description:Ubuntu 20.04 LTS
Release:20.04

Tried to calibrate my monitor with an external device (x-rite huey pro).
Process seems to go fine and starts working on the calibration. At about
80% of the progress bar  I receive the message (in basque, not sure
where to search it in english):

Kalibrazioak huts egin du
Kalibratzeko behar diren tresnak ez daude instalatuta
Kalibrazioaren gailua ken dezakezu

Which translates to (free non-official translation)

Calibration has failed.
The tools needed for calibration are not installed
You can remove the calibration device

Launching the tool from the command line, I receive these messages:

(gnome-control-center:3471): color-cc-panel-WARNING **: 13:28:57.868: 
calibration failed with code 4: failed to get filename for colprof
(gnome-control-center:3471): color-cc-panel-WARNING **: 13:33:46.435: Failed to 
send Cancel: GDBus.Error:org.freedesktop.ColorHelper.Internal: cannot cancel as 
status is idle
(gnome-control-center:3471): color-cc-panel-WARNING **: 13:33:46.436: failed to 
start calibrate: failed to calibrate

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul  9 13:38:26 2020
InstallationDate: Installed on 2020-06-25 (14 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=eu_ES.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Can't calibrate monitor

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

Bug description:
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  Tried to calibrate my monitor with an external device (x-rite huey
  pro). Process seems to go fine and starts working on the calibration.
  At about 80% of the progress bar  I receive the message (in basque,
  not sure where to search it in english):

  Kalibrazioak huts egin du
  Kalibratzeko behar diren tresnak ez daude instalatuta
  Kalibrazioaren gailua ken dezakezu

  Which translates to (free non-official translation)

  Calibration has failed.
  The tools needed for calibration are not installed
  You can remove the calibration device

  Launching the tool from the command line, I receive these messages:

  (gnome-control-center:3471): color-cc-panel-WARNING **: 13:28:57.868: 
calibration failed with code 4: failed to get filename for colprof
  (gnome-control-center:3471): color-cc-panel-WARNING **: 13:33:46.435: Failed 
to send Cancel: GDBus.Error:org.freedesktop.ColorHelper.Internal: cannot cancel 
as status is idle
  (gnome-control-center:3471): color-cc-panel-WARNING **: 13:33:46.436: failed 
to start calibrate: failed to calibrate

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  9 13:38:26 2020
  InstallationDate: Installed on 2020-06-25 (14 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=eu_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1873298] Re: No way to enroll multiple fingers for identification

** Description changed:

* Impact

This is the continuation of bug #1865845.

In g-c-c user panel, it is not possible to enroll more than one finger
for authentication.

* Test Case

1. enroll fingerprint in gnome-control-center
2. close the dialog
3. click it again to enroll another finger
4. it shows a dialog requiring you to delete your fingerprints

* Impact

As per this, GNOME design has produced some artwork that we want to implement
to fix all these issues:
- https://gitlab.gnome.org/Teams/Design/settings-mockups/-/issues/18

There will be few new strings, although most of the action events are
already covered by the fprintd translations.

UI will change quite a lot, but the current documentation [1] should not
be affected by the change, being quite generic, but in case it might be
updated to be clearer. The change are important improvements and oem
request so believe it's right to carry over as a SRU and considered as
hardware enablement

+ The new strings are already translatable on launchpad and the
+ translators mailing list has been notified, hopefully we can get some
+ coverage for the new UI in time for the LTS .1 langpack refresh
+
[1] https://help.ubuntu.com/19.10/ubuntu-help/session-fingerprint.html

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

Title:
No way to enroll multiple fingers for identification

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

Bug description:
* Impact

This is the continuation of bug #1865845.

In g-c-c user panel, it is not possible to enroll more than one finger
for authentication.

* Test Case

1. enroll fingerprint in gnome-control-center
2. close the dialog
3. click it again to enroll another finger
4. it shows a dialog requiring you to delete your fingerprints

* Impact

As per this, GNOME design has produced some artwork that we want to implement
to fix all these issues:
- https://gitlab.gnome.org/Teams/Design/settings-mockups/-/issues/18

There will be few new strings, although most of the action events are
already covered by the fprintd translations.

UI will change quite a lot, but the current documentation [1] should
not be affected by the change, being quite generic, but in case it
might be updated to be clearer. The change are important improvements
and oem request so believe it's right to carry over as a SRU and
considered as hardware enablement

The new strings are already translatable on launchpad and the
translators mailing list has been notified, hopefully we can get some
coverage for the new UI in time for the LTS .1 langpack refresh

[1] https://help.ubuntu.com/19.10/ubuntu-help/session-fingerprint.html

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

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

[Desktop-packages] [Bug 1873298] Re: No way to enroll multiple fingers for identification

** Description changed:

+ * Impact
+
This is the continuation of bug #1865845.

In g-c-c user panel, it is not possible to enroll more than one finger
for authentication.

- steps:
+ * Test Case
+
1. enroll fingerprint in gnome-control-center
2. close the dialog
3. click it again to enroll another finger
4. it shows a dialog requiring you to delete your fingerprints
+
+ * Impact

As per this, GNOME design has produced some artwork that we want to implement
to fix all these issues:
- https://gitlab.gnome.org/Teams/Design/settings-mockups/-/issues/18

There will be few new strings, although most of the action events are
already covered by the fprintd translations.

UI will change quite a lot, but the current documentation [1] should not
be affected by the change, being quite generic, but in case it might be
- updated to be clearer.
+ updated to be clearer. The change are important improvements and oem
+ request so believe it's right to carry over as a SRU and considered as
+ hardware enablement

[1] https://help.ubuntu.com/19.10/ubuntu-help/session-fingerprint.html

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

Title:
No way to enroll multiple fingers for identification

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

Bug description:
* Impact

This is the continuation of bug #1865845.

In g-c-c user panel, it is not possible to enroll more than one finger
for authentication.

* Test Case

1. enroll fingerprint in gnome-control-center
2. close the dialog
3. click it again to enroll another finger
4. it shows a dialog requiring you to delete your fingerprints

* Impact

As per this, GNOME design has produced some artwork that we want to implement
to fix all these issues:
- https://gitlab.gnome.org/Teams/Design/settings-mockups/-/issues/18

There will be few new strings, although most of the action events are
already covered by the fprintd translations.

UI will change quite a lot, but the current documentation [1] should
not be affected by the change, being quite generic, but in case it
might be updated to be clearer. The change are important improvements
and oem request so believe it's right to carry over as a SRU and
considered as hardware enablement

[1] https://help.ubuntu.com/19.10/ubuntu-help/session-fingerprint.html

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

[Desktop-packages] [Bug 1676763] Re: usb_modeswitch_dispatcher crashed with SIGSEGV in strrchr()

2020-07-09 Thread Jakub Vaněk

Thank you, I've tested the fix and it mostly works. However, a minor
fixup is needed for flawless switching of this particular modem, see
https://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=2=2915#p19606

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

Title:
  usb_modeswitch_dispatcher crashed with SIGSEGV in strrchr()

Status in usb-modeswitch package in Ubuntu:
  Fix Released

Bug description:
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  usb-modeswitch:
Instalados: 2.4.0+repack0-1ubuntu1
Candidato:  2.4.0+repack0-1ubuntu1
Tabla de versión:
   *** 2.4.0+repack0-1ubuntu1 500
  500 http://es.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  
  This error appears just after login.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: usb-modeswitch 2.4.0+repack0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Mar 28 09:40:09 2017
  ExecutablePath: /usr/sbin/usb_modeswitch_dispatcher
  InstallationDate: Installed on 2017-03-24 (3 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  ProcCmdline: /usr/sbin/usb_modeswitch_dispatcher --switch-systemd 1-6
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
  Signal: 11
  SourcePackage: usb-modeswitch
  StacktraceTop:
   strrchr () at ../sysdeps/x86_64/strrchr.S:32
   ?? ()
   __libc_start_main (main=0x555ed4e5f970, argc=3, argv=0x7ffd50b28338, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffd50b28328) at ../csu/libc-start.c:291
   ?? ()
  Title: usb_modeswitch_dispatcher crashed with SIGSEGV in strrchr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1884759] Re: U2f yubikey stopped working in chromium snap

2020-07-09 Thread Alexey Bazhin

Log attached. Relevant line probably

[92777:92906:0709/115647.054273:ERROR:udev_watcher.cc(96)] Failed to
begin udev enumeration.

** Attachment added: "chrom3.log"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+attachment/5390970/+files/chrom3.log

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

Title:
  U2f yubikey stopped working in chromium snap

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I was previously using u2f from yubikey in chromium snap, but now it doesn't 
work.
  No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced.
  U2f still works in firefox installed as deb.

  # snap connections chromium | grep u2f
  u2f-devices   chromium:u2f-devices   :u2f-devices 
   manual

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

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

[Desktop-packages] [Bug 1886021] Re: Nautilus slow after upgrade 20.04

2020-07-09 Thread Cristina Franzolini

Thanks for your help :-)

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

Title:
  Nautilus slow after upgrade 20.04

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  After I upgraded to 20.04, nautilus is very slow to open (open folder
  from applications, also, when I need open a file or save it)

  time nautilus:
  real  0m54,410s
  user  0m2,962s
  sys   0m0,483s

  Error:
  Error creating proxy: Errore nel chiamare StartServiceByName per 
org.gtk.vfs.AfcVolumeMonitor: È stato raggiunto il timeout (g-io-error-quark, 
24)
  RuntimeError: object at 0x7f203826c910 of type ColumnExtension is not 
initialized

  Nautilus version 1:3.36.3-0ubuntu1

  I tried this solution:
  
https://askubuntu.com/questions/1161928/nautilus-files-app-takes-long-time-to-start-on-ubuntu-18-04

  But it doesn't work.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2015-11-20 (1690 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: nautilus 1:3.36.3-0ubuntu1
  PackageArchitecture: amd64
  Tags: third-party-packages focal
  Uname: Linux 5.7.1-050701-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-09 (58 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1863282] Re: libreoffice menu bar disappeared

2020-07-09 Thread Darko Veberic

(ubuntu 20.04 xfce)
after removing all of the 
libreoffice-{gnome,gtk2,gtk3,gtk,kde4,kde5,kde,plasma,qt5} packages (with 
subsequent apt --purge autoremove) and then tried to install them individually, 
solo only. the result is appearance of a tiny menubar (at least with a 4k 
resolution) when any of the aforementioned packages is installed, EXCEPT for 
libreoffice-gnome and libreoffice-gtk3, for which no menu is present.

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

Title:
  libreoffice  menu bar disappeared

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Last kde neon 18.04 update Libreoffice menu bar disappeared. Uninstall 
libreoffice-kde & libreoffice-kde4 resolve problem, but need to install 
libreoffice-gtk3.
  KDE neon User Edition 5.18 18.04
  libreoffice-kde 1:6.0.7-0ubuntu0.18.04.10
  libreoffice-kde4 1:6.0.7-0ubuntu0.18.04.10

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

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

[Desktop-packages] [Bug 1886021] Re: Nautilus slow after upgrade 20.04

closing the bug as invalid then, thanks for providing the details and
better to avoid 'make install' local hacks next time to avoid such
issues :-)

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Nautilus slow after upgrade 20.04

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  After I upgraded to 20.04, nautilus is very slow to open (open folder
  from applications, also, when I need open a file or save it)

  time nautilus:
  real  0m54,410s
  user  0m2,962s
  sys   0m0,483s

  Error:
  Error creating proxy: Errore nel chiamare StartServiceByName per 
org.gtk.vfs.AfcVolumeMonitor: È stato raggiunto il timeout (g-io-error-quark, 
24)
  RuntimeError: object at 0x7f203826c910 of type ColumnExtension is not 
initialized

  Nautilus version 1:3.36.3-0ubuntu1

  I tried this solution:
  
https://askubuntu.com/questions/1161928/nautilus-files-app-takes-long-time-to-start-on-ubuntu-18-04

  But it doesn't work.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2015-11-20 (1690 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: nautilus 1:3.36.3-0ubuntu1
  PackageArchitecture: amd64
  Tags: third-party-packages focal
  Uname: Linux 5.7.1-050701-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-09 (58 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1886021] Re: Nautilus slow after upgrade 20.04

2020-07-09 Thread Cristina Franzolini

libimobiledevice.so.6.0.0

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

Title:
  Nautilus slow after upgrade 20.04

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  After I upgraded to 20.04, nautilus is very slow to open (open folder
  from applications, also, when I need open a file or save it)

  time nautilus:
  real  0m54,410s
  user  0m2,962s
  sys   0m0,483s

  Error:
  Error creating proxy: Errore nel chiamare StartServiceByName per 
org.gtk.vfs.AfcVolumeMonitor: È stato raggiunto il timeout (g-io-error-quark, 
24)
  RuntimeError: object at 0x7f203826c910 of type ColumnExtension is not 
initialized

  Nautilus version 1:3.36.3-0ubuntu1

  I tried this solution:
  
https://askubuntu.com/questions/1161928/nautilus-files-app-takes-long-time-to-start-on-ubuntu-18-04

  But it doesn't work.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2015-11-20 (1690 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: nautilus 1:3.36.3-0ubuntu1
  PackageArchitecture: amd64
  Tags: third-party-packages focal
  Uname: Linux 5.7.1-050701-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-09 (58 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1882248] Re: plug headset won't proper reconfig ouput to it on machine with default output

2020-07-09 Thread Hui Wang

This is the debdiff for pulseaudio bionic. And because the patch is
already in the eoan, focal,..., only bionic need this patch.


** Patch added: "pulseaudio_11.1-1ubuntu7.10.debdiff"
   
https://bugs.launchpad.net/oem-priority/+bug/1882248/+attachment/5390950/+files/pulseaudio_11.1-1ubuntu7.10.debdiff

** Description changed:

+ This is for pulseaudio bionic:
+ 
+ [Impact]
+ On a Dell machine without internal spk and internal mic, after freshly
+ install the bionic on it, the active profile is Off, after users plug a
+ headset to it and users select the headset from the pop-up dialogue,
+ users expect the profile changes to analog-stereo (headset is on it),
+ but the active_profile is still Off.
+ 
+ [Fix]
+ Upstream already has a patch to fix it, cherrypiack that patch to bionic.
+ And that patch is already in the eoan, focal, ...
+ 
+ [Test Case]
+ freshly install the bionic with this patch on that dell machine,
+ plug headset and select the headset from UI, the profile changes to
+ analog-stereo, and play some sound, we could hear it from the headset
+ 
+ [Regression Risk]
+ Low, this patch is already in the upstream for a long time, and it is
+ already in the eoan and focal.
+ 
+ 
+ 
  For linux kernel (oem-b):
  
  [Impact]
  On a Dell machine without internal spk and internal mic, after freshly
  install the bionic on it, and users plug a headset, the sound couldn't
  output from headset.
  
  [Fix]
  reverse the order of headset mic and headphone mic
  
  [Test Case]
  freshly install the bionic with this patch on that dell machine,
  plug headset and play sound, we could hear the sound from headset.
  
  [Regression Risk]
  Low, this patch only affects the machine without internal mic and
  internal spk, and I already tested this patch on the machine without
  internal mic and internal spk, it worked well.
  
- 
- 
- target machine does not have built-in speaker, and the monitor does not have 
an audio output (like d-sub VGA)
+ target machine does not have built-in speaker, and the monitor does not
+ have an audio output (like d-sub VGA)
  
  As first boot, there will be a "dummy output" in g-c-c.
  
  After plug-in headset, there will be a headset appear in g-c-c, but it
  won't be automatically selected even it's chosen in the pop-up window.

** Summary changed:

- plug headset won't proper reconfig ouput to it on machine with default output
+ [SRU] plug headset won't proper reconfig ouput to it on machine with default 
output

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

Title:
  [SRU] plug headset won't proper reconfig ouput to it on machine with
  default output

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in linux-oem package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in linux-oem source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Bionic:
  New

Bug description:
  This is for pulseaudio bionic:

  [Impact]
  On a Dell machine without internal spk and internal mic, after freshly
  install the bionic on it, the active profile is Off, after users plug a
  headset to it and users select the headset from the pop-up dialogue,
  users expect the profile changes to analog-stereo (headset is on it),
  but the active_profile is still Off.

  [Fix]
  Upstream already has a patch to fix it, cherrypiack that patch to bionic.
  And that patch is already in the eoan, focal, ...

  [Test Case]
  freshly install the bionic with this patch on that dell machine,
  plug headset and select the headset from UI, the profile changes to
  analog-stereo, and play some sound, we could hear it from the headset

  [Regression Risk]
  Low, this patch is already in the upstream for a long time, and it is
  already in the eoan and focal.


  
  For linux kernel (oem-b):

  [Impact]
  On a Dell machine without internal spk and internal mic, after freshly
  install the bionic on it, and users plug a headset, the sound couldn't
  output from headset.

  [Fix]
  reverse the order of headset mic and headphone mic

  [Test Case]
  freshly install the bionic with this patch on that dell machine,
  plug headset and play sound, we could hear the sound from headset.

  [Regression Risk]
  Low, this patch only affects the machine without internal mic and
  internal spk, and I already tested this patch on the machine without
  internal mic and internal spk, it worked well.

  target machine does not have built-in speaker, and the monitor does
  not have an audio output (like d-sub VGA)

  As first boot, there will be a "dummy output" in g-c-c.

  After plug-in headset, there will be a headset appear in g-c-c, but it
  won't be automatically selected even it's chosen in the pop-up window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1882248/+subscriptions

-- 
Mailing list:

[Desktop-packages] [Bug 1886021] Re: Nautilus slow after upgrade 20.04

Great, so which one worked, removing the lib or the nautilus one?

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

Title:
  Nautilus slow after upgrade 20.04

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  After I upgraded to 20.04, nautilus is very slow to open (open folder
  from applications, also, when I need open a file or save it)

  time nautilus:
  real  0m54,410s
  user  0m2,962s
  sys   0m0,483s

  Error:
  Error creating proxy: Errore nel chiamare StartServiceByName per 
org.gtk.vfs.AfcVolumeMonitor: È stato raggiunto il timeout (g-io-error-quark, 
24)
  RuntimeError: object at 0x7f203826c910 of type ColumnExtension is not 
initialized

  Nautilus version 1:3.36.3-0ubuntu1

  I tried this solution:
  
https://askubuntu.com/questions/1161928/nautilus-files-app-takes-long-time-to-start-on-ubuntu-18-04

  But it doesn't work.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2015-11-20 (1690 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: nautilus 1:3.36.3-0ubuntu1
  PackageArchitecture: amd64
  Tags: third-party-packages focal
  Uname: Linux 5.7.1-050701-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-09 (58 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1886732] Re: Shotwell fails to import and wrongly reports "photo library folder was not writable"

Thanks!

** Changed in: shotwell (Ubuntu)
   Status: Confirmed => Triaged

** Also affects: ubuntuone-shotwell-plugin via
   https://gitlab.gnome.org/GNOME/shotwell/-/issues/267
   Importance: Unknown
   Status: Unknown

** Summary changed:

- Shotwell fails to import and wrongly reports "photo library folder was not 
writable"
+ Shotwell reports read permission as "photo library folder was not writable"

** Summary changed:

- Shotwell reports read permission as "photo library folder was not writable"
+ reports read permission as "photo library folder was not writable"

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

Title:
  reports read permission as "photo library folder was not writable"

Status in ubuntuone-shotwell-plugin:
  Unknown
Status in shotwell package in Ubuntu:
  Triaged

Bug description:
  1) Ubuntu version: Ubuntu 20.04 LTS

  2) shotwell package version: 0.30.10-0ubuntu0.1

  3) 
   a. I'm performing "Import from folder" from an external drive. 
   b. This external drive is formatted as HFS+, comes from a Mac, and by 
default it's mounted as read-only, which is OK.
   c. As result of the import, some files (both photos and videos) are imported 
ok, while some others don't.
   d. For those which are not imported, the error reported in the UI is "953 
photos/videos failed to import because the photo library folder was not 
writable", which doesn't make sense, as some others were imported.

  Looking further, I came to found in ~/.cache/shotwell/shotwell.log the
  following pattern:

  L 3733 2020-07-07 20:47:09 [WRN] BatchImport.vala:1840: Unable to perform MD5 
checksum on file : Error opening file : Permission 
denied
  L 3733 2020-07-07 20:47:09 [WRN] BatchImport.vala:1405: Import failure 
: File write error

  By checking the code, I see convert_error method maps several different error 
codes to ImportResult.FILE_WRITE_ERROR
  In particular, lines 124 and 125 map IOError.PERMISSION_DENIED to 
ImportResult.FILE_WRITE_ERROR

  else if (ioerr is IOError.PERMISSION_DENIED)
  return ImportResult.FILE_WRITE_ERROR;

  But in this case, the permission denied came from the read, and not from the 
write.
  BTW: Permission denied has to do with different permissions for those files, 
so it's ok to not have been imported.

  4) It's ok for Shotwell to fail importing files without read
  permission, but the error message confuses the user, which may
  understand Shotwell library got corrupted (as on same operation some
  files were imported and some others don't). A better error message
  could be "953 photos/videos failed to import because permission was
  denied to read the source files"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntuone-shotwell-plugin/+bug/1886732/+subscriptions

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

[Desktop-packages] [Bug 1882248] Re: plug headset won't proper reconfig ouput to it on machine with default output

2020-07-09 Thread Hui Wang

** Changed in: pulseaudio (Ubuntu Bionic)
   Importance: Undecided => Critical

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

Title:
  plug headset won't proper reconfig ouput to it on machine with default
  output

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in linux-oem package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in linux-oem source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Bionic:
  New

Bug description:
  For linux kernel (oem-b):

  [Impact]
  On a Dell machine without internal spk and internal mic, after freshly
  install the bionic on it, and users plug a headset, the sound couldn't
  output from headset.

  [Fix]
  reverse the order of headset mic and headphone mic

  [Test Case]
  freshly install the bionic with this patch on that dell machine,
  plug headset and play sound, we could hear the sound from headset.

  [Regression Risk]
  Low, this patch only affects the machine without internal mic and
  internal spk, and I already tested this patch on the machine without
  internal mic and internal spk, it worked well.


  
  target machine does not have built-in speaker, and the monitor does not have 
an audio output (like d-sub VGA)

  As first boot, there will be a "dummy output" in g-c-c.

  After plug-in headset, there will be a headset appear in g-c-c, but it
  won't be automatically selected even it's chosen in the pop-up window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1882248/+subscriptions

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

[Desktop-packages] [Bug 1886021] Re: Nautilus slow after upgrade 20.04

2020-07-09 Thread Cristina Franzolini

Yesss, it's work.
Now I haven't delays more.
Thanks :)

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

Title:
  Nautilus slow after upgrade 20.04

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  After I upgraded to 20.04, nautilus is very slow to open (open folder
  from applications, also, when I need open a file or save it)

  time nautilus:
  real  0m54,410s
  user  0m2,962s
  sys   0m0,483s

  Error:
  Error creating proxy: Errore nel chiamare StartServiceByName per 
org.gtk.vfs.AfcVolumeMonitor: È stato raggiunto il timeout (g-io-error-quark, 
24)
  RuntimeError: object at 0x7f203826c910 of type ColumnExtension is not 
initialized

  Nautilus version 1:3.36.3-0ubuntu1

  I tried this solution:
  
https://askubuntu.com/questions/1161928/nautilus-files-app-takes-long-time-to-start-on-ubuntu-18-04

  But it doesn't work.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2015-11-20 (1690 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: nautilus 1:3.36.3-0ubuntu1
  PackageArchitecture: amd64
  Tags: third-party-packages focal
  Uname: Linux 5.7.1-050701-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-09 (58 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1720364] Re: Unable to use shortcuts with keyboard layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS

2020-07-09 Thread Evgeny

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

Same with Kubuntu 20.

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

Title:
  Unable to use  shortcuts with  keyboard
  layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS

Status in MATE Desktop:
  New
Status in Ubuntu MATE:
  New
Status in X.Org X server:
  Confirmed
Status in marco package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed
Status in xorg-hwe-16.04 package in Ubuntu:
  Confirmed
Status in xorg package in Debian:
  New

Bug description:
  Steps to reproduce:
  1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 
17.10 or 18.04 LTS.
  2. Set-up two keyboard layouts - English and Russian
  3. Set  as keyboard layout switcher
  4. Try to use shortcuts starting from :
  4.1. Open Firefox, open new tab, go to some site in it, close tab, try to 
click  to restore closed tab.
  4.2. Open mate-terminal, try to open new tab with , or copy 
(), or paste ().
  4.3. Open pluma, write some text, try to navigate in it with 
.

  Expected results:
   switches keyboard layout, shortcuts starting from 
 work normally.

  Actual results:
   switches keyboard layout, shortcuts starting from 
 do not work.

  Notes:
  1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with 
 keyboard layout switcher.
  2. This problem was discovered before on 13.10, 14.04 and other modern 
versions with GNOME desktop (Metacity and Compiz) - see bug 1245473.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: marco 1.18.1-3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic i686
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: i386
  CurrentDesktop: MATE
  Date: Fri Sep 29 16:18:02 2017
  InstallationDate: Installed on 2017-08-26 (33 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  SourcePackage: marco
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mate-desktop/+bug/1720364/+subscriptions

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

[Desktop-packages] [Bug 1811219] Re: High precision touchpad scrolling doesn't work in Wayland sessions (but does in Xorg)

2020-07-09 Thread Olivier Tilloy

Thanks for confirming the fix Daniel!

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

Title:
  High precision touchpad scrolling doesn't work in Wayland sessions
  (but does in Xorg)

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  High precision touchpad scrolling doesn't work in Wayland sessions
  (but does in Xorg).

  I guess it's probably Xwayland failing to support the more advanced
  XInput stuff?

  Note: This bug report is about high precision (and thus low latency)
  touchpad scrolling. It is not about "Smooth Scrolling" simply because
  "Smooth Scrolling" actually means something quite different in
  Chromium. :P

  Test case:

  1. In chrome://flags, set Smooth Scrolling to Disabled and restart the 
browser.
  2. Use your touchpad (usually two fingers) to scroll a web page.

  Observed:

  In an Ubuntu session (pure Xorg), the scrolling is noticeably high
  precision like a Macbook or Chromebook. In a Wayland session however,
  the scrolling stutters badly like it's still using old-style mouse
  wheel emulation.

  Note also: If you have "Smooth Scrolling" enabled then Chromium
  replaces the stutter with smoother scrolling but you can still tell
  it's broken in Wayland sessions because the latency is much higher.
  It's having to fake the smoothness by delaying and extrapolating from
  mouse wheel-style tick events.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: chromium-browser 71.0.3578.98-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-2:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAQrEbwTEoxQQUZAQS1NCB4Oh31rk81syUNUFSlSwCBgKlA0QBxTwEBAQEBAQEBKDyAoHCwI0AwIDYABkQhAAAa/wBZQ00wRjUxUkExSkwK/ABERUxMIFUyNDEzCiAg/QA4TB5REQAKICAgICAgAUICAx3xUJAFBAMCBxYBHxITFCAVEQYjCR8HgwEAAAI6gBhxOC1AWCxFAAZEIQAAHgEdgBhxHBYgWCwlAAZEIQAAngEdAHJR0B4gbihVAAZEIQAAHowK0Iog4C0QED6WAAZEIQAAGAAA
   modes: 1920x1200 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 
1920x1080i 1920x1080 1920x1080i 1920x1080 1920x1080 1600x1200 1280x1024 
1280x1024 1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 
800x600 800x600 720x576 720x576 720x480 720x480 720x480 720x480 720x480 640x480 
640x480 640x480 640x480 720x400
  DRM.card0-DP-3:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  Date: Thu Jan 10 17:11:06 2019
  Desktop-Session:
   'None'
   'None'
   '/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:

  Env:
   'None'
   'None'
  InstallationDate: Installed on 2018-12-04 (37 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)
  InstalledPlugins:
   /usr/lib/mozilla/plugins:
     => libgnome-shell-browser-plugin.so
   (size: 22496 bytes, mtime: Wed Dec  5 20:53:32 2018)
  Load-Avg-1min: 2.33
  Load-Processes-Running-Percent:   0.1%
  MachineType: LENOVO 10M7CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=052b7096-9b82-4712-b596-7629d5f6498c ro quiet splash vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M16KT47A
  dmi.board.name: 3102
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN 3259627060530
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: ThinkCentre M710s
  dmi.product.name: 10M7CTO1WW
  dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s
  dmi.product.version: ThinkCentre M710s
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1844775] Re: HDR support for Ubuntu

2020-07-09 Thread U. Artie Eoff

FWIW, There is also HDR10 tone map support in gstreamer-vaapi
https://gitlab.freedesktop.org/gstreamer/gstreamer-
vaapi/-/merge_requests/270

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

Title:
  HDR support for Ubuntu

Status in ffmpeg package in Ubuntu:
  Fix Released
Status in intel-media-driver package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Triaged
Status in weston package in Ubuntu:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  i915:
  - 5.3 (Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/
  - gen4+ needs https://patchwork.freedesktop.org/series/63373/
  - so anything beyond initial Ice Lake support will not be in 5.4

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

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

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

[Desktop-packages] [Bug 1885363] Re: [amdgpu] Screen flickers after waking up from suspend

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc4/

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

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

Title:
  [amdgpu] Screen flickers after waking up from suspend

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I upgraded my Ubuntu 20.04 system with a new graphics card a few days ago. 
Everything seems fine when running the system normally, however whenever I 
suspend the machine and then wake it back up, severe problems occur.
  The first time, the machine froze completely. Switching to a different TTY 
didn't work anymore and the keyboard LEDs didn't respond to caps and num lock 
anymore, so I had to force shutdown. The second time, it came back OK but the 
screen has been flickering heavily since. Restarting Gnome and unplugging and 
plugging monitors back in hasn't helped.

  Relevant specs:
  CPU: AMD® Ryzen 9 3900x 12-core processor × 24 
  GPU: AMD® Radeon rx 5600 xt (MSI RADEON RX 5600 XT MECH OC)
  Monitors: 1x Acer running at 3840x2160 60Hz, 2x Medion (showing up as 
"Messeltronik Dresden GmbH") both running at 1920x1080 60Hz.
  Gnome: 3.36.2
  X11
  Apt doesn't report any updates.

  The flickering is most pronounced on the Acer. On the Medions, it
  seems to only happen when something changes on the screen. I have
  tried to capture this on video: https://youtu.be/HWT1J76-x94

  
  This bug seem quite similar to this one 
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874588). I can also stop 
the flickering by switching the Acer to 1080p but when switching back to 4k, 
the problem reappears.

  I hope that ubuntu-bug has included all the necessary details. Let me
  know if you need anything else.

  Thank you very much for your help!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  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: GNOME
  Date: Sat Jun 27 10:44:32 2020
  DistUpgraded: 2020-04-30 20:17:33,403 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.100, 5.4.0-37-generic, x86_64: installed
   nvidia, 440.100, 5.4.0-39-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev ca) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 10 [Radeon RX 
5600 OEM/5600 XT / 5700/5700 XT] [1462:381e]
  InstallationDate: Installed on 2019-03-26 (458 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-30 (57 days ago)
  dmi.bios.date: 04/08/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.60
  dmi.board.name: X570 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd04/08/2020:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  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/ubuntu/+source/linux/+bug/1885363/+subscriptions

-- 
Mailing list:

[Desktop-packages] [Bug 1881699] Re: No analog output

Seems to share the same root cause on lp: #1875199.

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

Title:
  No analog output

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After a fresh boot and login, there is no analog output. Only HDMI and 
bluetooth are available.
  It becomes available when I kill pulseaudio with 'pulseaudio -k' but the 
sound indicator only shows 'dummy' output and I cannot control the output from 
the sound settings or the sound indicator.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu36
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  j-lallement  184080 F pulseaudio
   /dev/snd/controlC1:  j-lallement  184080 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  2 06:32:09 2020
  InstallationDate: Installed on 2020-05-31 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: FNCML357.0032.2019.1021.1624
  dmi.board.asset.tag: Default string
  dmi.board.name: NUC10i7FNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K61360-302
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: FN
  dmi.product.name: NUC10i7FNH
  dmi.product.sku: BXNUC10i7FNH
  dmi.product.version: K61081-302
  dmi.sys.vendor: Intel(R) Client Systems
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu36
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  j-lallement   3669 F pulseaudio
   /dev/snd/controlC0:  j-lallement   3669 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-05-31 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527)
  MachineType: Intel(R) Client Systems NUC10i7FNH
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_huyn9u@/vmlinuz-5.4.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_huyn9u ro snd-intel-dspcfg.dsp_driver=1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  groovy
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/21/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: FNCML357.0032.2019.1021.1624
  dmi.board.asset.tag: Default string
  dmi.board.name: NUC10i7FNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K61360-302
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: FN
  dmi.product.name: NUC10i7FNH
  dmi.product.sku: BXNUC10i7FNH
  dmi.product.version: K61081-302
  dmi.sys.vendor: Intel(R) Client Systems

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

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

[Desktop-packages] [Bug 1885673] Re: won't auto-select input when headset is plugged and selected in pop-up window

** Description changed:

  [Impact]
  
   * audio input won't auto select and no pop-up dialog when headset is
  plugged
  
   * backporting fix gitlab_ucm_mixer_control_select.patch in groovy to
  focal.
  
  [Test Case]
  
   * Using Tiger Lake platform
   * Step to reproduce:
     1. plug-in headset
     2. check g-c-c
  
     Expected result:
       audio input switch to headset mic.
  
     Actual result:
       audio input is not changed.
  
  [Regression Potential]
  
   * the change corrupt the audio device selection, the audio input/output
  is not as expect
  
  [Other Info]
  
   * a patch is there waiting for upstream review :
  https://gitlab.gnome.org/GNOME/libgnome-volume-
  control/-/merge_requests/10
  
   * Test pass after 'do-release-upgrade -d' on the Tiger Lake platform to
- groovy
+ groovy with gnome-control-center_1:3.36.4-1ubuntu1.

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

Title:
  won't auto-select input when headset is plugged and selected in pop-up
  window

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

Bug description:
  [Impact]

   * audio input won't auto select and no pop-up dialog when headset is
  plugged

   * backporting fix gitlab_ucm_mixer_control_select.patch in groovy to
  focal.

  [Test Case]

   * Using Tiger Lake platform
   * Step to reproduce:
     1. plug-in headset
     2. check g-c-c

     Expected result:
       audio input switch to headset mic.

     Actual result:
       audio input is not changed.

  [Regression Potential]

   * the change corrupt the audio device selection, the audio
  input/output is not as expect

  [Other Info]

   * a patch is there waiting for upstream review :
  https://gitlab.gnome.org/GNOME/libgnome-volume-
  control/-/merge_requests/10

   * Test pass after 'do-release-upgrade -d' on the Tiger Lake platform
  to groovy with gnome-control-center_1:3.36.4-1ubuntu1.

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

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

[Desktop-packages] [Bug 1885673] Re: won't auto-select input when headset is plugged and selected in pop-up window