date:20210420

[Expired for lightdm (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  No matter how i write the lightdm.conf file, it makes the whole thing
  crash and i can't login. I'm trying to change the greeter to webkit2

Status in lightdm package in Ubuntu:
  Expired

Bug description:
  I installed lightdm and then rebooted. It worked fine but i wanted to
  change how it looks. I tried installing the web-greeter using whither
  as instructed here: https://askubuntu.com/questions/960334/how-can-i
  -install-lightdm-webkit2-greeter

  and the PC wouldn't open. It would be loading forever. So then i
  deleted the conf file and it reverted to the default. I've tried
  placing the same conf file at /etc/lightdm/lightdm.conf with the same
  results

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: lightdm 1.30.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Feb 19 14:49:25 2021
  InstallationDate: Installed on 2020-10-14 (127 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to groovy on 2020-11-26 (84 days ago)

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

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

[Desktop-packages] [Bug 1921991] Re: [SRU] Support isdv4-aes stylus group and multiple AES stylus definitions

2021-04-20 Thread Chris Halse Rogers

Thanks for that. @Bin - thanks for checking that these fixes are in
hirsute. Are they also in groovy? If they're not in groovy's libwacom
we'll also need an upload to groovy, so people who update from focal to
groovy don't lose this fix.

** Also affects: libwacom (Ubuntu Groovy)
   Importance: Undecided
   Status: New

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

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

Title:
  [SRU] Support isdv4-aes stylus group and multiple AES stylus
  definitions

Status in OEM Priority Project:
  Triaged
Status in libwacom package in Ubuntu:
  Fix Released
Status in libwacom source package in Focal:
  Fix Committed
Status in libwacom source package in Groovy:
  Incomplete

Bug description:
  [Impact]

   * There are lots of stylus couldn't be used on Lenovo's platform, our
  OEM customer request to support ThinkPad P15 Gen 1, ThinkPad X1 Yoga
  Gen5, ThinkPad P1 G3.

   * I reviewed and tested the below patches from upstream. It could
  support the stylus very well on P15, P1 or X1 Yoga.

   * a864679 - Add multiple AES stylus definitions 
     I applied into libwacom2 1.3-2ubuntu1, no errors.

   * 8652aa3 - Add isdv4-aes stylus group to all AES sensors
    I tried to apply this patch, but there are not 'data/isdv4-48ca.tablet' and 
'data/isdv4-48ce.tablet', it failed for these two files.

   * ba02abf - Add ISDv4 51e9 (Lenovo ThinkPad P15 Gen 1) (#325)

  [Test Plan]

   * Need your laptop have AES stylus, check the pen setting at gnome-
  control-center when the pen touch the screen. It could not
  set/customize the stylus, such as the second button as right click.

   * After updated the new packages with these patches, you could
  customize the stylus at gnome-control-center.

  [Where problems could occur]

   * It only changes the data/ parts to support more stylus from
  upstream, so it's low risk.

  [Other Info]

   * Related bug:
  https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1869059

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

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

[Desktop-packages] [Bug 1921991] Re: [SRU] Support isdv4-aes stylus group and multiple AES stylus definitions

2021-04-20 Thread Chris Halse Rogers

Hello Bin, or anyone else affected,

Accepted libwacom into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/libwacom/1.3-2ubuntu2
in a few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: libwacom (Ubuntu Focal)
   Status: New => Fix Committed

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

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

Title:
  [SRU] Support isdv4-aes stylus group and multiple AES stylus
  definitions

Status in OEM Priority Project:
  Triaged
Status in libwacom package in Ubuntu:
  Fix Released
Status in libwacom source package in Focal:
  Fix Committed
Status in libwacom source package in Groovy:
  Incomplete

Bug description:
  [Impact]

   * There are lots of stylus couldn't be used on Lenovo's platform, our
  OEM customer request to support ThinkPad P15 Gen 1, ThinkPad X1 Yoga
  Gen5, ThinkPad P1 G3.

   * I reviewed and tested the below patches from upstream. It could
  support the stylus very well on P15, P1 or X1 Yoga.

   * a864679 - Add multiple AES stylus definitions 
     I applied into libwacom2 1.3-2ubuntu1, no errors.

   * 8652aa3 - Add isdv4-aes stylus group to all AES sensors
    I tried to apply this patch, but there are not 'data/isdv4-48ca.tablet' and 
'data/isdv4-48ce.tablet', it failed for these two files.

   * ba02abf - Add ISDv4 51e9 (Lenovo ThinkPad P15 Gen 1) (#325)

  [Test Plan]

   * Need your laptop have AES stylus, check the pen setting at gnome-
  control-center when the pen touch the screen. It could not
  set/customize the stylus, such as the second button as right click.

   * After updated the new packages with these patches, you could
  customize the stylus at gnome-control-center.

  [Where problems could occur]

   * It only changes the data/ parts to support more stylus from
  upstream, so it's low risk.

  [Other Info]

   * Related bug:
  https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1869059

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

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

[Desktop-packages] [Bug 1923389] Re: Screenshot different colours

2021-04-20 Thread Murilo Zilli

Seems similar to that bug

** Also affects: gnome-screenshot (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: gnome-screenshot (Ubuntu)

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

Title:
  Screenshot different colours

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu version 18.04.5 LTS.

  gnome-screenshot:
    Installed: 3.25.0-0ubuntu2
    Candidate: 3.25.0-0ubuntu2
    Version table:
   *** 3.25.0-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Expected: Both colors on the image and the web page are the same hex code.
  Happened instead: Diffent colour hex.

  Taking a screenshot from a webpage changes the colors slighlty.

  I have attached a video of what is happening, its a slighlt different
  colour but still different altogether.

  From a HTML page it is #11283C but when I place the screenshot on top of a 
background with that color, its clearly different.
  On image the hex is #0D253D.

  I have attached a video of the process

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

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

[Desktop-packages] [Bug 1916488] Re: SRU 1.64.5 to focal

This bug was fixed in the package gjs - 1.64.5-0ubuntu0.20.04.01

---
gjs (1.64.5-0ubuntu0.20.04.01) focal; urgency=medium

  * New upstream release (LP: #1916488):
- Fix Error in function "_init()" in module "modules/overrides/GObject.js"
- gi/wrapperutils: Move gjs_get_string_id() into resolve() implementations
- overrides/Gtk: Set BuilderScope in class init
- fix readline build on certain systems

 -- Marco Trevisan (Treviño)   Mon, 22 Feb 2021
14:56:22 +0100

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

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

Title:
  SRU 1.64.5 to focal

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

Bug description:
  [ Impact ]

  That's the current GNOME stable update, including some performance 
improvements and crash fixes backported from the development branch.
  https://gitlab.gnome.org/GNOME/gjs/-/tags/1.64.5

  [ Test case ]

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

  GNOME Shell and its components should continue working with no
  javascript related errors, as well other gjs based apps like polari

  [ Regression potential ]

  GJS based GTK4 should work properly, resolution of GI types was
  changed and so exported GI types should continue working.

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

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

[Desktop-packages] [Bug 1916488] Update Released

2021-04-20 Thread Chris Halse Rogers

The verification of the Stable Release Update for gjs has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  SRU 1.64.5 to focal

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

Bug description:
  [ Impact ]

  That's the current GNOME stable update, including some performance 
improvements and crash fixes backported from the development branch.
  https://gitlab.gnome.org/GNOME/gjs/-/tags/1.64.5

  [ Test case ]

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

  GNOME Shell and its components should continue working with no
  javascript related errors, as well other gjs based apps like polari

  [ Regression potential ]

  GJS based GTK4 should work properly, resolution of GI types was
  changed and so exported GI types should continue working.

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

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

[Desktop-packages] [Bug 1925057] Re: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound

2021-04-20 Thread Hui Wang

So if only run below commands, does the audio become good or not?
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x08
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x4ab7


Or could you do a test to find the minimal group of commands to make the audio 
change normal?

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

Title:
  [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or
  crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello,

  I'm using Ubuntu together with Windows on my laptop.

  If I boot in Ubuntu after Windows sound doesn't work well (instead of
  system sounds I can hear only shot noise). To fix the issue I need to
  completely shut down the system (call Power Off via Ubuntu GUI) and
  then boot again in Ubuntu. Please note, that reboot (called via Ubuntu
  GUI) doesn't help to fix the issue.

  Expected result: sound works well regardless of boot history.
  Actual result: every time I boot in Ubuntu after Windows sound doesn't work.

  Issue occurrence: 100%.

  Environment:
  $ lsb_release -rd
  Description: Ubuntu Hirsute Hippo (development branch)
  Release: 21.04
  $ uname -a
  Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 
x86_64 x86_64 x86_64 GNU/Linux

  Thank you in advance!

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gluttton   1640 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 19 19:37:56 2021
  InstallationDate: Installed on 2021-03-06 (43 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Smart Sound Technology Audio Controller - sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   кві 19 19:37:21 tiptop pulseaudio[958]: After module unload, module 
'module-null-sink' was still loaded!
   кві 19 19:37:21 tiptop systemd[944]: pulseaudio.service: Succeeded.
   кві 19 19:37:40 tiptop systemd[944]: pulseaudio.service: Succeeded.
   кві 19 19:37:50 tiptop systemd[944]: pulseaudio.socket: Succeeded.
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or 
crackling sound
  UpgradeStatus: Upgraded to hirsute on 2021-03-06 (43 days ago)
  dmi.bios.date: 01/14/2021
  dmi.bios.release: 1.31
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DHCN31WW
  dmi.board.asset.tag: ���
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN
  dmi.chassis.asset.tag: ���
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga Slim 7 14IIL05
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05:
  dmi.product.family: Yoga Slim 7 14IIL05
  dmi.product.name: 82A1
  dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05
  dmi.product.version: Yoga Slim 7 14IIL05
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1793410] Re: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working

2021-04-20 Thread Hazem Alabiad

Same issue here Acer Swift SF315-52G 
Both internal and external microphones don't work.

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

Title:
  [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal
  microphone not working

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Recently bought a new Acer Swift 3 laptop and installed Ubuntu 18.04
  on it. Everything works except the internal microphone. I have also
  tested with an external microphone and this didn't work either.

  I have worked my way through all the suggested solutions I could find,
  including trying to reconfigure the pins using hdajacketask. In
  pavucontrol I have options for Internal Microphone and Microphone
  (unplugged) but the internal mic only captures static noise.

  The latest HD-Audio Codec-Specific Models has configurations for
  alc255-acer and alc256 for some other models, but setting options snd-
  hda-intel model=MODEL in /etc/modprobe.d/alsa-base.conf does not solve
  the issue with any of these.

  Some info -

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-
  LP HD Audio (rev 21)

  
  cat /proc/asound/cards:

   0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xdf1a8000 irq 127

  
  dmesg | grep snd:

  [3.944593] snd_hda_core: loading out-of-tree module taints kernel.
  [3.956337] snd_soc_skl: Unknown symbol snd_hdac_display_power (err 0)
  [3.956422] snd_soc_skl: Unknown symbol snd_hdac_i915_exit (err 0)
  [4.000880] snd_hda_intel :00:1f.3: Probing card using HDA DKMS, 
version 0.201808050301~ubuntu18.04.1
  [4.000895] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [4.013061] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC256: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [4.013063] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [4.013065] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [4.013066] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [4.013066] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [4.013068] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x18
  [4.013069] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12

  
  info on node 12 from cat /proc/asound/card*/codec\#*:

  Node 0x12 [Pin Complex] wcaps 0x40040b: Stereo Amp-In
Control: name="Internal Mic Boost Volume", index=0, device=0
  ControlAmp: chs=3, dir=In, idx=0, ofs=0
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals:  [0x02 0x02]
Pincap 0x0020: IN
Pin Default 0x4000: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0x0, Sequence = 0x0
Pin-ctls: 0x20: IN
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0

  Let me know if you need any other information.

  James

  ---

  Tags:  bionic
  Uname: Linux 4.15.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  _MarkForUpload: True
  dmi.bios.date: 06/22/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Default string
  dmi.board.name: Erdinger_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd06/22/2018:svnAcer:pnSwiftSF315-52:pvrV1.04:rvnKBL:rnErdinger_KL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF315-52
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1925141] Re: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1)

2021-04-20 Thread Bug Watch Updater

** Changed in: kbd-chooser
   Status: Unknown => New

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

Title:
  There is no CapsLock indication of CapsLock key using Caps Lock LED on
  the keyboard while using plain TTY (such as Ctrl+Alt+F1)

Status in kbd-chooser:
  New
Status in kbd package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have minimal Ubuntu 20.04 LTS installed with all default settings and 
minimal set of packages on the laptop or desktop with physical CapsLock / Caps 
Lock LED indicator on the case or keyboard.
  2. Boot the system using default settings
  3. Login to the system
  4. Press `` key, enter some letters in CAPITALS (while CapsLock 
LED is on)
  5. Press `` key again, enter some letters in lowercase (while 
CapsLock LED is off)

  Expected results:
  * CapsLock key toggles CapsLock LED, the LED state indicates current CapsLock 
key function

  Actual results:
  * CapsLock LED is always off

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd-sysv 245.4-4ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  Uname: Linux 5.4.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Apr 20 11:31:53 2021
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kbd-chooser/+bug/1925141/+subscriptions

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

[Desktop-packages] [Bug 1925265] Re: Fresh install of hirsute-preinstalled-desktop-arm64+raspi has packages to autoremove

2021-04-20 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1925265

** Tags added: iso-testing

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

Title:
  Fresh install of hirsute-preinstalled-desktop-arm64+raspi has packages
  to autoremove

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Immediately after installing hirsute-preinstalled-desktop-arm64+raspi
  on a Raspberry Pi I noticed that there were packages available for
  autoremoval.

  bdmurray@bdmurray-desktop:~$ sudo apt autoremove
  [sudo] password for bdmurray:
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages will be REMOVED:
cryptsetup-bin dctrl-tools dmeventd dmraid dpkg-repack efibootmgr 
gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 grub-common grub-efi-arm64
grub-efi-arm64-bin grub-efi-arm64-signed grub2-common kpartx kpartx-boot 
libdebian-installer4 libdevmapper-event1.02.1
libdmraid1.0.0.rc16 liblvm2cmd2.03 libtimezonemap-data libtimezonemap1 lvm2 
os-prober python3-icu python3-pam rdate
thin-provisioning-tools
  0 upgraded, 0 newly installed, 27 to remove and 0 not upgraded.
  After this operation, 45.5 MB disk space will be freed.
  Do you want to continue? [Y/n] n
  Abort.

  It seems to me the installation process should run an autoremove at
  the end.

  bdmurray@bdmurray-desktop:~$ cat /var/log/installer/version 
  ubiquity 21.04.19

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

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

[Desktop-packages] [Bug 1925266] [NEW] Ubuntu should have two web browsers installed by default.

2021-04-20 Thread Clinton H

Public bug reported:

Users should be encouraged to use one web browser for general web
browsing. Another secure web browser with private mode enabled by
default, should be used for sensitive(accessing financial accounts and
accessing an email address used exclusively for financial accounts)
browsing. Addons and plug-ins should be blocked, because they can
contain security flaws which would weaken the secure browser. Cookie
files should be erased when the tab or browser is closed to prevent bad
actor from stealing cookie files.

A user might not know the danger of using a single web browser for
everything. There are undiscovered security flaws in web browsers. If a
user visits a webpage that is infected with JavaScript malware, a user’s
web browser will become infected with malware. If the user uses that
same browser to access sensitive accounts, sensitive data can be stolen.
Webpage content might be modified.

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

** Description changed:

  Users should be encouraged to use one web browser for general web
  browsing. Another secure web browser with private mode enabled by
  default, should be used for sensitive(accessing financial accounts and
  accessing an email address used exclusively for financial accounts)
  browsing. Addons and plug-ins should be blocked, because they can
- contain security flaws which would weaken the secure browser.
+ contain security flaws which would weaken the secure browser. Cookie
+ files should be erased when the tab or browser is closed to prevent bad
+ actor from stealing cookie files.
  
  A user might not know the danger of using a single web browser for
  everything. There are undiscovered security flaws in web browsers. If a
  user visits a webpage that is infected with JavaScript malware, a user’s
  web browser will become infected with malware. If the user uses that
  same browser to access sensitive accounts, sensitive data can be stolen.
  Webpage content might be modified.

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

Title:
  Ubuntu should have two web browsers installed by default.

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Users should be encouraged to use one web browser for general web
  browsing. Another secure web browser with private mode enabled by
  default, should be used for sensitive(accessing financial accounts and
  accessing an email address used exclusively for financial accounts)
  browsing. Addons and plug-ins should be blocked, because they can
  contain security flaws which would weaken the secure browser. Cookie
  files should be erased when the tab or browser is closed to prevent
  bad actor from stealing cookie files.

  A user might not know the danger of using a single web browser for
  everything. There are undiscovered security flaws in web browsers. If
  a user visits a webpage that is infected with JavaScript malware, a
  user’s web browser will become infected with malware. If the user uses
  that same browser to access sensitive accounts, sensitive data can be
  stolen. Webpage content might be modified.

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

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

[Desktop-packages] [Bug 1925265] [NEW] Fresh install of hirsute-preinstalled-desktop-arm64+raspi has packages to autoremove

2021-04-20 Thread Brian Murray

Public bug reported:

Immediately after installing hirsute-preinstalled-desktop-arm64+raspi on
a Raspberry Pi I noticed that there were packages available for
autoremoval.

bdmurray@bdmurray-desktop:~$ sudo apt autoremove
[sudo] password for bdmurray:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  cryptsetup-bin dctrl-tools dmeventd dmraid dpkg-repack efibootmgr 
gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 grub-common grub-efi-arm64
  grub-efi-arm64-bin grub-efi-arm64-signed grub2-common kpartx kpartx-boot 
libdebian-installer4 libdevmapper-event1.02.1
  libdmraid1.0.0.rc16 liblvm2cmd2.03 libtimezonemap-data libtimezonemap1 lvm2 
os-prober python3-icu python3-pam rdate
  thin-provisioning-tools
0 upgraded, 0 newly installed, 27 to remove and 0 not upgraded.
After this operation, 45.5 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.

It seems to me the installation process should run an autoremove at the
end.

bdmurray@bdmurray-desktop:~$ cat /var/log/installer/version 
ubiquity 21.04.19

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: hirsute raspi-image

** Tags added: raspi-image

** Tags added: hirsute

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

Title:
  Fresh install of hirsute-preinstalled-desktop-arm64+raspi has packages
  to autoremove

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Immediately after installing hirsute-preinstalled-desktop-arm64+raspi
  on a Raspberry Pi I noticed that there were packages available for
  autoremoval.

  bdmurray@bdmurray-desktop:~$ sudo apt autoremove
  [sudo] password for bdmurray:
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages will be REMOVED:
cryptsetup-bin dctrl-tools dmeventd dmraid dpkg-repack efibootmgr 
gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 grub-common grub-efi-arm64
grub-efi-arm64-bin grub-efi-arm64-signed grub2-common kpartx kpartx-boot 
libdebian-installer4 libdevmapper-event1.02.1
libdmraid1.0.0.rc16 liblvm2cmd2.03 libtimezonemap-data libtimezonemap1 lvm2 
os-prober python3-icu python3-pam rdate
thin-provisioning-tools
  0 upgraded, 0 newly installed, 27 to remove and 0 not upgraded.
  After this operation, 45.5 MB disk space will be freed.
  Do you want to continue? [Y/n] n
  Abort.

  It seems to me the installation process should run an autoremove at
  the end.

  bdmurray@bdmurray-desktop:~$ cat /var/log/installer/version 
  ubiquity 21.04.19

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

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

[Desktop-packages] [Bug 1925264] [NEW] Create a gnome applet that would display Ubuntu security news, data breaches, scams, etc.

2021-04-20 Thread Clinton H

Public bug reported:

Could you create a gnome applet for Ubuntu that would display security
news from:

www.threatpost.com
www.securelist.com
usa.kaspersky.com/blog/

Ubuntu should be focused on security and privacy. The applet could be
bundled with Ubuntu.

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

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

Title:
  Create a gnome applet that would display Ubuntu security news, data
  breaches, scams, etc.

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Could you create a gnome applet for Ubuntu that would display security
  news from:

  www.threatpost.com
  www.securelist.com
  usa.kaspersky.com/blog/

  Ubuntu should be focused on security and privacy. The applet could be
  bundled with Ubuntu.

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

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

[Desktop-packages] [Bug 1925141] Re: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1)

Ok, let's do this in steps:
1. boot machine - CapsLock function and LED are off
2. login and press CapsLock button - now  user can enter CAPITALS and CapsLock 
LED should be on
3. press CapsLock button again - now user can enter lowercase letters and 
CapsLock LED is off

What else should I explain to you, Dan Streetman (ddstreet) ?


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

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Confirmed

** Description changed:

  Steps to reproduce:
  1. Have minimal Ubuntu 20.04 LTS installed with all default settings and 
minimal set of packages on the laptop or desktop with physical CapsLock / Caps 
Lock LED indicator on the case or keyboard.
  2. Boot the system using default settings
  3. Login to the system
- 4. Press  key, enter some letters in capitals
- 5. Press  key again, enter some letters in lowercase
+ 4. Press `` key, enter some letters in CAPITALS (while CapsLock 
LED is on)
+ 5. Press `` key again, enter some letters in lowercase (while 
CapsLock LED is off)
  
  Expected results:
  * CapsLock key switches on CapsLock LED, the LED state indicates current 
CapsLock key function
  
  Actual results:
  * CapsLock LED is always off
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd-sysv 245.4-4ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  Uname: Linux 5.4.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Apr 20 11:31:53 2021
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago)

** Description changed:

  Steps to reproduce:
  1. Have minimal Ubuntu 20.04 LTS installed with all default settings and 
minimal set of packages on the laptop or desktop with physical CapsLock / Caps 
Lock LED indicator on the case or keyboard.
  2. Boot the system using default settings
  3. Login to the system
  4. Press `` key, enter some letters in CAPITALS (while CapsLock 
LED is on)
  5. Press `` key again, enter some letters in lowercase (while 
CapsLock LED is off)
  
  Expected results:
- * CapsLock key switches on CapsLock LED, the LED state indicates current 
CapsLock key function
+ * CapsLock key toggles CapsLock LED, the LED state indicates current CapsLock 
key function
  
  Actual results:
  * CapsLock LED is always off
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd-sysv 245.4-4ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  Uname: Linux 5.4.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Apr 20 11:31:53 2021
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago)

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

Title:
  There is no CapsLock indication of CapsLock key using Caps Lock LED on
  the keyboard while using plain TTY (such as Ctrl+Alt+F1)

Status in kbd-chooser:
  Unknown
Status in kbd package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have minimal Ubuntu 20.04 LTS installed with all default settings and 
minimal set of packages on the laptop or desktop with physical CapsLock / Caps 
Lock LED indicator on the case or keyboard.
  2. Boot the system using default settings
  3. Login to the system
  4. Press `` key, enter some letters in CAPITALS (while CapsLock 
LED is on)
  5. Press `` key again, enter some letters in lowercase (while 
CapsLock LED is off)

  Expected results:
  * CapsLock key toggles CapsLock LED, the LED state indicates current CapsLock 
key function

  Actual results:
  * CapsLock LED is always off

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd-sysv 245.4-4ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  Uname: Linux 5.4.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Apr 20 11:31:53 2021
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kbd-chooser/+bug/1925141/+subscriptions

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

[Desktop-packages] [Bug 1925141] Re: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1)

CapsLock LED should react on  CapsLock key, is not it?

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

Title:
  There is no CapsLock indication of CapsLock key using Caps Lock LED on
  the keyboard while using plain TTY (such as Ctrl+Alt+F1)

Status in kbd-chooser:
  Unknown
Status in kbd package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have minimal Ubuntu 20.04 LTS installed with all default settings and 
minimal set of packages on the laptop or desktop with physical CapsLock / Caps 
Lock LED indicator on the case or keyboard.
  2. Boot the system using default settings
  3. Login to the system
  4. Press `` key, enter some letters in CAPITALS (while CapsLock 
LED is on)
  5. Press `` key again, enter some letters in lowercase (while 
CapsLock LED is off)

  Expected results:
  * CapsLock key toggles CapsLock LED, the LED state indicates current CapsLock 
key function

  Actual results:
  * CapsLock LED is always off

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd-sysv 245.4-4ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  Uname: Linux 5.4.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Apr 20 11:31:53 2021
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kbd-chooser/+bug/1925141/+subscriptions

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

[Desktop-packages] [Bug 1925141] Re: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1)

Was a copy-paste problem. Thank you for your comment, dear developer!

** Description changed:

  Steps to reproduce:
  1. Have minimal Ubuntu 20.04 LTS installed with all default settings and 
minimal set of packages on the laptop or desktop with physical CapsLock / Caps 
Lock LED indicator on the case or keyboard.
  2. Boot the system using default settings
  3. Login to the system
  4. Press  key, enter some letters in capitals
  5. Press  key again, enter some letters in lowercase
  
- Actual results:
+ Expected results:
  * CapsLock key switches on CapsLock LED, the LED state indicates current 
CapsLock key function
  
- Expected results:
+ Actual results:
  * CapsLock LED is always off
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd-sysv 245.4-4ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  Uname: Linux 5.4.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Apr 20 11:31:53 2021
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago)

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

Title:
  There is no CapsLock indication of CapsLock key using Caps Lock LED on
  the keyboard while using plain TTY (such as Ctrl+Alt+F1)

Status in kbd-chooser:
  Unknown
Status in kbd package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have minimal Ubuntu 20.04 LTS installed with all default settings and 
minimal set of packages on the laptop or desktop with physical CapsLock / Caps 
Lock LED indicator on the case or keyboard.
  2. Boot the system using default settings
  3. Login to the system
  4. Press `` key, enter some letters in CAPITALS (while CapsLock 
LED is on)
  5. Press `` key again, enter some letters in lowercase (while 
CapsLock LED is off)

  Expected results:
  * CapsLock key toggles CapsLock LED, the LED state indicates current CapsLock 
key function

  Actual results:
  * CapsLock LED is always off

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd-sysv 245.4-4ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  Uname: Linux 5.4.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Apr 20 11:31:53 2021
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kbd-chooser/+bug/1925141/+subscriptions

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

[Desktop-packages] [Bug 1925141] Re: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1)

2021-04-20 Thread Dan Streetman

> Actual results:
> * CapsLock key switches on CapsLock LED, the LED state indicates current 
> CapsLock key function
>
> Expected results:
> * CapsLock LED is always off

the 'actual results' sounds like correct behavior to me...?

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

Title:
  There is no CapsLock indication of CapsLock key using Caps Lock LED on
  the keyboard while using plain TTY (such as Ctrl+Alt+F1)

Status in kbd-chooser:
  Unknown
Status in kbd package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have minimal Ubuntu 20.04 LTS installed with all default settings and 
minimal set of packages on the laptop or desktop with physical CapsLock / Caps 
Lock LED indicator on the case or keyboard.
  2. Boot the system using default settings
  3. Login to the system
  4. Press  key, enter some letters in capitals
  5. Press  key again, enter some letters in lowercase

  Actual results:
  * CapsLock key switches on CapsLock LED, the LED state indicates current 
CapsLock key function

  Expected results:
  * CapsLock LED is always off

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd-sysv 245.4-4ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  Uname: Linux 5.4.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Apr 20 11:31:53 2021
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kbd-chooser/+bug/1925141/+subscriptions

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

[Desktop-packages] [Bug 1923358] Re: Other servers doesn't display server list (Software Updater)

great, it was probably the same as the mentioned issue, closing

** Changed in: software-properties (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  Other servers doesn't display server list (Software Updater)

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  Using Settings and then trying to choose other server doesn't do
  anything. It should display the list of available other servers.

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

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

[Desktop-packages] [Bug 1925057] Re: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound

Please, see below testing results.

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x78
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x003e
// bad
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x77
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x0015
// bad
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x67
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0xf000
// bad
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x3b
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x60d9
// bad
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x33
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x8580
// bad
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x1b
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x0a6b
// bad
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x1a
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x8003
// bad
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x0f
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x02a2
// bad
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x0e
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x65c0
// bad
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x08
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x4ab7
// good, at this line sound works well and lines below are not necessary
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x06
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x6115

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

Title:
  [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or
  crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello,

  I'm using Ubuntu together with Windows on my laptop.

  If I boot in Ubuntu after Windows sound doesn't work well (instead of
  system sounds I can hear only shot noise). To fix the issue I need to
  completely shut down the system (call Power Off via Ubuntu GUI) and
  then boot again in Ubuntu. Please note, that reboot (called via Ubuntu
  GUI) doesn't help to fix the issue.

  Expected result: sound works well regardless of boot history.
  Actual result: every time I boot in Ubuntu after Windows sound doesn't work.

  Issue occurrence: 100%.

  Environment:
  $ lsb_release -rd
  Description: Ubuntu Hirsute Hippo (development branch)
  Release: 21.04
  $ uname -a
  Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 
x86_64 x86_64 x86_64 GNU/Linux

  Thank you in advance!

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gluttton   1640 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 19 19:37:56 2021
  InstallationDate: Installed on 2021-03-06 (43 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Smart Sound Technology Audio Controller - sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   кві 19 19:37:21 tiptop pulseaudio[958]: After module unload, module 
'module-null-sink' was still loaded!
   кві 19 19:37:21 tiptop systemd[944]: pulseaudio.service: Succeeded.
   кві 19 19:37:40 tiptop systemd[944]: pulseaudio.service: Succeeded.
   кві 19 19:37:50 tiptop systemd[944]: pulseaudio.socket: Succeeded.
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or 
crackling sound
  UpgradeStatus: Upgraded to hirsute on 2021-03-06 (43 days ago)
  dmi.bios.date: 01/14/2021
  dmi.bios.release: 1.31
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DHCN31WW
  dmi.board.asset.tag: ���
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN
  dmi.chassis.asset.tag: ���
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga Slim 7 14IIL05
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05:
  dmi.product.family: Yoga Slim 7 14IIL05
  dmi.product.name: 82A1
  dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05
  dmi.product.version: Yoga Slim 7 14IIL05
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1923479] Re: out of buffer access and Integer overflow in Exiv2

2021-04-20 Thread Leonidas S. Barbosa

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-29457

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

Title:
  out of buffer access and Integer overflow in Exiv2

Status in exiv2 package in Ubuntu:
  In Progress

Bug description:
  An out of buffer access: 
https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d
  and a Integer overflow : 
https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0

  affects Exiv2 in ubuntu releases

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

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

[Desktop-packages] [Bug 1925141] Re: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1)

The bug is actually in `kdb` package. Forcibly purging it using `sudo
dpkg -P --force-all kbd` fixes the issue. But this package is useful.
Please fix this bug.

** Bug watch added: github.com/legionus/kbd/issues #55
   https://github.com/legionus/kbd/issues/55

** Also affects: ubuntu-seeds via
   https://github.com/legionus/kbd/issues/55
   Importance: Unknown
   Status: Unknown

** No longer affects: ubuntu-seeds

** Also affects: kbd-chooser via
   https://github.com/legionus/kbd/issues/55
   Importance: Unknown
   Status: Unknown

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

Title:
  There is no CapsLock indication of CapsLock key using Caps Lock LED on
  the keyboard while using plain TTY (such as Ctrl+Alt+F1)

Status in kbd-chooser:
  Unknown
Status in kbd package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have minimal Ubuntu 20.04 LTS installed with all default settings and 
minimal set of packages on the laptop or desktop with physical CapsLock / Caps 
Lock LED indicator on the case or keyboard.
  2. Boot the system using default settings
  3. Login to the system
  4. Press  key, enter some letters in capitals
  5. Press  key again, enter some letters in lowercase

  Actual results:
  * CapsLock key switches on CapsLock LED, the LED state indicates current 
CapsLock key function

  Expected results:
  * CapsLock LED is always off

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd-sysv 245.4-4ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  Uname: Linux 5.4.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Apr 20 11:31:53 2021
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kbd-chooser/+bug/1925141/+subscriptions

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

[Desktop-packages] [Bug 1925141] Re: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1)

Running `sudo chmod a-x $(dpkg -L kbd | grep bin/)` also fix the issue.

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

Title:
  There is no CapsLock indication of CapsLock key using Caps Lock LED on
  the keyboard while using plain TTY (such as Ctrl+Alt+F1)

Status in kbd-chooser:
  Unknown
Status in kbd package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have minimal Ubuntu 20.04 LTS installed with all default settings and 
minimal set of packages on the laptop or desktop with physical CapsLock / Caps 
Lock LED indicator on the case or keyboard.
  2. Boot the system using default settings
  3. Login to the system
  4. Press  key, enter some letters in capitals
  5. Press  key again, enter some letters in lowercase

  Actual results:
  * CapsLock key switches on CapsLock LED, the LED state indicates current 
CapsLock key function

  Expected results:
  * CapsLock LED is always off

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd-sysv 245.4-4ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  Uname: Linux 5.4.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Apr 20 11:31:53 2021
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kbd-chooser/+bug/1925141/+subscriptions

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

[Desktop-packages] [Bug 1925141] Re: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1)

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

** Also affects: console-setup (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: shadow (Ubuntu)

** No longer affects: systemd (Ubuntu)

** No longer affects: console-setup (Ubuntu)

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

Title:
  There is no CapsLock indication of CapsLock key using Caps Lock LED on
  the keyboard while using plain TTY (such as Ctrl+Alt+F1)

Status in kbd package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have minimal Ubuntu 20.04 LTS installed with all default settings and 
minimal set of packages on the laptop or desktop with physical CapsLock / Caps 
Lock LED indicator on the case or keyboard.
  2. Boot the system using default settings
  3. Login to the system
  4. Press  key, enter some letters in capitals
  5. Press  key again, enter some letters in lowercase

  Actual results:
  * CapsLock key switches on CapsLock LED, the LED state indicates current 
CapsLock key function

  Expected results:
  * CapsLock LED is always off

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd-sysv 245.4-4ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  Uname: Linux 5.4.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Apr 20 11:31:53 2021
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago)

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

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

[Desktop-packages] [Bug 1707611] Re: Sound does not automatically switch to HDMI when connected

2021-04-20 Thread Marius Gedminas

My laptop with Ubuntu 20.10 automatically switches to the HDMI output
when I plug in my monitor (via a USB C cable connected to a dock station
connected to the monitor via a HDMI cable).

And then, a second later, it switches to the USB dock's audio output
(which has nothing plugged in), but that's a different bug.

Incidentally, module-switch-on-connect in PulseAudio 14 (and also Ubuntu 
20.10's 13.99.2) has a blacklist of sink names that should not be switched to.  
The default value of this blacklist is a regexp matching "hdmi".  The blacklist 
doesn't appear to work (which is also a different bug).
If it does start to work at some point, you may have to edit 
/etc/pulse/default.pa and change

load-module module-switch-on-connect

to say

load-module module-switch-on-connect blacklist=""

if you want HDMI outputs to be switched to.

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

Title:
  Sound does not automatically switch to HDMI when connected

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When connecting a HDMI cable or other audio device, the user must
  manually click on the "sound volume" in the top-right and switch to
  the newly connected device.

  Example: you connect a HDMI cable to the television, but then you must
  manually choose the HDMI sound option; it does not get selected
  automatically.

  Often times e.g. when the HDMI cable is disconnected, the user must
  then manually click on the "speakers" or "line out" setting - EVEN IF
  IT'S ALREADY SELECTED, it must be clicked on again for the sound to
  work through the computer's speakers.

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

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

[Desktop-packages] [Bug 1914053] Re: US intl. Deadkeys not working in some programs

2021-04-20 Thread Arbiel Perlacremaz

I'm experimenting a very analog trouble.

I designed my own keyboard layout and my own .XCompose file to produce
ancien greek characters such as α ά ὰ ὰ ᾴ ᾳ ἁ ᾁ ἀ ᾀ, … (I'm using 18.04
to type the present text). Ι've been using these keyboard and .XCompose
file for several years now and they worked fine until I installed Ubuntu
20.04 on a new PC a few weaks ago.

When I hit a dead key, a little circle may get displayed on the screen,
however not systematically. This little circle disappears when I hit the
desired key, and the cursor returns to its previous location.

I'm very disapointed and ready to return to Ubuntu 18.04.

Arbiel

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

Title:
US intl. Deadkeys not working in some programs

Status in xorg-server package in Ubuntu:
Confirmed

Bug description:
Kubuntu 20.04
KDE Plasma 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
xorg:
Installed: 1:7.7+19ubuntu14
Candidate: 1:7.7+19ubuntu14
Version table:
*** 1:7.7+19ubuntu14 500
500 http://no.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

The keyboard layout is set as English (US, intl., with dead keys) to deal
with European lettering. This worked fine for a long time, but suddenly, the
dead keys are not working in several programs. As in, when typing the dead key
nothing happens. E.g. they don't work in browsers (checked in Firefox and
Chrome) and in the Matrix Element program. However, they do work in other
programs, such as Kate and LibreOffice.
Normally one can type an apostrophe (') by hitting that key and typing a
space, but now the only way to get that character in those few programs is by
pressing Alt Gr+' . The same thing for letters like é. Normally pressing '+e
would work, now only Alt Gr+e works.

Apport bug report (aka ubuntu-bug xorg) did not work for the xorg
package.

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

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

[Desktop-packages] [Bug 1921585] Re: Screen contents visible when switching between logged in users using CTrl + Alt + Fx

2021-04-20 Thread Steve Beattie

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

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

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

Title:
  Screen contents visible when switching between logged in users using
  CTrl + Alt + Fx

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The screen contents is briefly visible when switching between logged
  in user accounts using Ctrl + Alt + Fx shortcuts.

  To reproduce, 
  1. Create two user accounts.
  2. Log in to the first user account.
  3. Switch to the login window using Ctrl + Alt + F1
  4. Log in to the second user account.
  5. Wait until the screen lock enables on the first account.
  6. Switch to the first account using Ctrl + Alt + F2.

  The screen contents on the first account will be visible for about a
  second before the screen lock login prompt is displayed.

  This bug may be related to 
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1532508

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

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

[Desktop-packages] [Bug 1914053] Re: US intl. Deadkeys not working in some programs

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

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

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

Title:
  US intl. Deadkeys not working in some programs

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 20.04
  KDE Plasma 5.18.5
  KDE Frameworks Version: 5.68.0
  Qt Version: 5.12.8
  xorg: 
  Installed: 1:7.7+19ubuntu14 
  Candidate: 1:7.7+19ubuntu14 
  Version table:
  *** 1:7.7+19ubuntu14 500
  500 http://no.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  The keyboard layout is set as English (US, intl., with dead keys) to deal 
with European lettering. This worked fine for a long time, but suddenly, the 
dead keys are not working in several programs. As in, when typing the dead key 
nothing happens. E.g. they don't work in browsers (checked in Firefox and 
Chrome) and in the Matrix Element program. However, they do work in other 
programs, such as Kate and LibreOffice.
  Normally one can type an apostrophe (') by hitting that key and typing a 
space, but now the only way to get that character in those few programs is by 
pressing Alt Gr+' . The same thing for letters like é. Normally pressing '+e 
would work, now only Alt Gr+e works.

  Apport bug report (aka ubuntu-bug xorg) did not work for the xorg
  package.

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

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

[Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session

2021-04-20 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1925238

** Tags added: iso-testing

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

Title:
  [nvidia-prime] switches between xorg and wayland session

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

Bug description:
  I have noticed this on a hirsute install from today's RC media
  (20210420) with ubuntu-drivers-common 1:0.8.9.1.

  The first boot is always xorg, and nvidia mode is selected.

  After that reboots are *usually* wayland, but sometimes they are xorg
  too. When it's wayland then ondemand mode is selected.

  What is the default meant to be - probably ondemand?

  Seems like it's somehow nondeterministic. Attaching some logs.

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

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

[Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session

>From the second boot

** Attachment added: "gpu-manager-wayland.log"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+attachment/5490359/+files/gpu-manager-wayland.log

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

Title:
  [nvidia-prime] switches between xorg and wayland session

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

Bug description:
  I have noticed this on a hirsute install from today's RC media
  (20210420) with ubuntu-drivers-common 1:0.8.9.1.

  The first boot is always xorg, and nvidia mode is selected.

  After that reboots are *usually* wayland, but sometimes they are xorg
  too. When it's wayland then ondemand mode is selected.

  What is the default meant to be - probably ondemand?

  Seems like it's somehow nondeterministic. Attaching some logs.

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

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

[Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session

>From the first boot

** Attachment added: "gpu-manager-xorg.log"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+attachment/5490357/+files/gpu-manager-xorg.log

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

Title:
  [nvidia-prime] switches between xorg and wayland session

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

Bug description:
  I have noticed this on a hirsute install from today's RC media
  (20210420) with ubuntu-drivers-common 1:0.8.9.1.

  The first boot is always xorg, and nvidia mode is selected.

  After that reboots are *usually* wayland, but sometimes they are xorg
  too. When it's wayland then ondemand mode is selected.

  What is the default meant to be - probably ondemand?

  Seems like it's somehow nondeterministic. Attaching some logs.

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

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

[Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session

>From the second boot

** Attachment added: "lsmod-wayland.log"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+attachment/5490358/+files/lsmod-wayland.log

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

Title:
  [nvidia-prime] switches between xorg and wayland session

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

Bug description:
  I have noticed this on a hirsute install from today's RC media
  (20210420) with ubuntu-drivers-common 1:0.8.9.1.

  The first boot is always xorg, and nvidia mode is selected.

  After that reboots are *usually* wayland, but sometimes they are xorg
  too. When it's wayland then ondemand mode is selected.

  What is the default meant to be - probably ondemand?

  Seems like it's somehow nondeterministic. Attaching some logs.

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

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

[Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session

>From the first boot

** Attachment added: "lsmod-xorg.log"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+attachment/5490356/+files/lsmod-xorg.log

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

Title:
  [nvidia-prime] switches between xorg and wayland session

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

Bug description:
  I have noticed this on a hirsute install from today's RC media
  (20210420) with ubuntu-drivers-common 1:0.8.9.1.

  The first boot is always xorg, and nvidia mode is selected.

  After that reboots are *usually* wayland, but sometimes they are xorg
  too. When it's wayland then ondemand mode is selected.

  What is the default meant to be - probably ondemand?

  Seems like it's somehow nondeterministic. Attaching some logs.

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

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

[Desktop-packages] [Bug 1925238] [NEW] [nvidia-prime] switches between xorg and wayland session

Public bug reported:

I have noticed this on a hirsute install from today's RC media
(20210420) with ubuntu-drivers-common 1:0.8.9.1.

The first boot is always xorg, and nvidia mode is selected.

After that reboots are *usually* wayland, but sometimes they are xorg
too. When it's wayland then ondemand mode is selected.

What is the default meant to be - probably ondemand?

Seems like it's somehow nondeterministic. Attaching some logs.

** Affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New

** Attachment added: "modinfo-nvidia-drm.log"

https://bugs.launchpad.net/bugs/1925238/+attachment/5490355/+files/modinfo-nvidia-drm.log

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

Title:
[nvidia-prime] switches between xorg and wayland session

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

Bug description:
I have noticed this on a hirsute install from today's RC media
(20210420) with ubuntu-drivers-common 1:0.8.9.1.

The first boot is always xorg, and nvidia mode is selected.

After that reboots are *usually* wayland, but sometimes they are xorg
too. When it's wayland then ondemand mode is selected.

What is the default meant to be - probably ondemand?

Seems like it's somehow nondeterministic. Attaching some logs.

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

[Desktop-packages] [Bug 1900068] Re: Upgrade to zeitgeist-1.0.3

2021-04-20 Thread Hans Joachim Desserud

https://bugs.launchpad.net/ubuntu/+source/zeitgeist/1.0.3-4ubuntu1

Looks like the new version is in place in Hirsute now.

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

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

Title:
  Upgrade to zeitgeist-1.0.3

Status in zeitgeist package in Ubuntu:
  Fix Released
Status in zeitgeist package in Debian:
  Fix Released

Bug description:
  Please do upgrade zeitgeist from current 1.0.2 to 1.0.3.

  It is required for GNOME Activity Journal to work. GNOME Activity Journal has
  been ported to GTK3. It will be available in GNOME repos shortly.

  For more details:

  https://discourse.gnome.org/t/zeitgeist-gnome-activity-
  journal-1-0/4521

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

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

[Desktop-packages] [Bug 1925217] Re: package python3-uno 1:6.4.6-0ubuntu0.20.04.1 failed to install/upgrade: new python3-uno package pre-removal script subprocess returned error exit status 1

2021-04-20 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package python3-uno 1:6.4.6-0ubuntu0.20.04.1 failed to
  install/upgrade: new python3-uno package pre-removal script subprocess
  returned error exit status 1

Status in libreoffice package in Ubuntu:
  New

Bug description:
  It shows that debpython module is not there but it is not installable
  as well.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python3-uno 1:6.4.6-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Apr 18 12:50:16 2021
  ErrorMessage: new python3-uno package pre-removal script subprocess returned 
error exit status 1
  InstallationDate: Installed on 2021-04-02 (17 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.5
  SourcePackage: libreoffice
  Title: package python3-uno 1:6.4.6-0ubuntu0.20.04.1 failed to 
install/upgrade: new python3-uno package pre-removal script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1925217] [NEW] package python3-uno 1:6.4.6-0ubuntu0.20.04.1 failed to install/upgrade: new python3-uno package pre-removal script subprocess returned error exit status 1

2021-04-20 Thread Bhaskar Saivinay Jeebula

Public bug reported:

It shows that debpython module is not there but it is not installable as
well.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: python3-uno 1:6.4.6-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Apr 18 12:50:16 2021
ErrorMessage: new python3-uno package pre-removal script subprocess returned 
error exit status 1
InstallationDate: Installed on 2021-04-02 (17 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.5
SourcePackage: libreoffice
Title: package python3-uno 1:6.4.6-0ubuntu0.20.04.1 failed to install/upgrade: 
new python3-uno package pre-removal script subprocess returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package python3-uno 1:6.4.6-0ubuntu0.20.04.1 failed to
  install/upgrade: new python3-uno package pre-removal script subprocess
  returned error exit status 1

Status in libreoffice package in Ubuntu:
  New

Bug description:
  It shows that debpython module is not there but it is not installable
  as well.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python3-uno 1:6.4.6-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Apr 18 12:50:16 2021
  ErrorMessage: new python3-uno package pre-removal script subprocess returned 
error exit status 1
  InstallationDate: Installed on 2021-04-02 (17 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.5
  SourcePackage: libreoffice
  Title: package python3-uno 1:6.4.6-0ubuntu0.20.04.1 failed to 
install/upgrade: new python3-uno package pre-removal script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1924851] Re: intel display drivers not working

2021-04-20 Thread Daniel Letzeisen

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

** This bug is no longer a duplicate of bug 1924889
   i915 graphics driver not loading for Rocket Lake i7-11700K [8086:4c8a]
** This bug has been marked a duplicate of bug 1905466
   drm/i915: Drop force_probe requirement for Rocket Lake

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

Title:
  intel display drivers not working

Status in xorg package in Ubuntu:
  New

Bug description:
  Getting llvmpipe (LLVM 11.0.0, 256 bits) as display instead of intel
  drivers. Only available Resolution 1024X768

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 17 18:35:34 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  DkmsStatus: rtl8821ce, 5.5.2.1, 5.8.0-50-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2021-04-17 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: Gigabyte Technology Co., Ltd. B560M DS3H AC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=f0b245ca-169e-4fdc-80d3-14f66691147b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F1
  dmi.board.asset.tag: Default string
  dmi.board.name: B560M DS3H AC
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF1:bd01/11/2021:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnB560MDS3HAC:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560MDS3HAC:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B560 MB
  dmi.product.name: B560M DS3H AC
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1820859] Re: nautilus --version segfaults in g_application_impl_get_dbus_object_path

2021-04-20 Thread Treviño

** Tags removed: needs-packaging

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

Title:
  nautilus --version segfaults in
  g_application_impl_get_dbus_object_path

Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
nautilus.  This problem was most recently seen with package version 
1:3.31.90-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/8a8c9fc62039a8bb83a7ee530ac4140a9b8c29d9 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1908999] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1

Are you aware that the PPA that you're using is abandoned, so you won't
be getting security updates to your browser? See the notice at the top
of https://launchpad.net/~xalt7x/+archive/ubuntu/chromium-deb-vaapi.

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  package chromium-browser (not installed) failed to install/upgrade:
  new chromium-browser package pre-installation script subprocess
  returned error exit status 1

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  I uninstalled the chromium snap because it was downloading an upgrade
  and failing daily. After I did it I tried to install it again (with
  apt) and it tried to install a snap and failed, sending me here.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  AptOrdering:
   chromium-browser:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Dec 22 11:50:14 2020
  ErrorMessage: new chromium-browser package pre-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2017-12-11 (1106 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.2
  SourcePackage: chromium-browser
  Title: package chromium-browser (not installed) failed to install/upgrade: 
new chromium-browser package pre-installation script subprocess returned error 
exit status 1
  UpgradeStatus: Upgraded to focal on 2020-10-10 (72 days ago)

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

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

[Desktop-packages] [Bug 1925188] Re: Mozilla Firefox Multiple Vulnerabilities

** Changed in: firefox (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: firefox (Ubuntu)
   Importance: Undecided => High

** Changed in: firefox (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Mozilla Firefox Multiple Vulnerabilities

Status in firefox package in Ubuntu:
  In Progress

Bug description:
  CVE Numbers

  CVE‑2021‑24002  , CVE‑2021‑23998
   ,
  CVE‑2021‑29946  , CVE‑2021‑29944
   ,
  CVE‑2021‑23994  , CVE‑2021‑24000
   ,
  CVE‑2021‑29947  , CVE‑2021‑23997
   ,
  CVE‑2021‑23999  , CVE‑2021‑23996
  

  Description

  Multiple vulnerabilities have been reported in Mozilla Firefox, which
  can be exploited by malicious people to conduct spoofing attacks,
  disclose sensitive information, bypass certain security restrictions,
  and compromise a vulnerable system.

  The vulnerabilities are reported in versions prior to 88

  Affected Software

  The following software is affected by the described vulnerability.
  Please check the vendor links below to see if exactly your version is
  affected.

  Mozilla Firefox 87.x

  Solution

  Upgrade to version 88.

  References

  1. https://www.mozilla.org/en-US/security/advisories/mfsa2021-16
  

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

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

[Desktop-packages] [Bug 1820859] Re: nautilus --version segfaults in g_application_impl_get_dbus_object_path

2021-04-20 Thread Treviño

** Tags added: needs-packaging

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

Title:
  nautilus --version segfaults in
  g_application_impl_get_dbus_object_path

Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
nautilus.  This problem was most recently seen with package version 
1:3.31.90-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/8a8c9fc62039a8bb83a7ee530ac4140a9b8c29d9 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1925188] Re: Mozilla Firefox Multiple Vulnerabilities

2021-04-20 Thread Eduardo Barretto

** Information type changed from Private Security to Public Security

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

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

Title:
  Mozilla Firefox Multiple Vulnerabilities

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  CVE Numbers

  CVE‑2021‑24002  , CVE‑2021‑23998
   ,
  CVE‑2021‑29946  , CVE‑2021‑29944
   ,
  CVE‑2021‑23994  , CVE‑2021‑24000
   ,
  CVE‑2021‑29947  , CVE‑2021‑23997
   ,
  CVE‑2021‑23999  , CVE‑2021‑23996
  

  Description

  Multiple vulnerabilities have been reported in Mozilla Firefox, which
  can be exploited by malicious people to conduct spoofing attacks,
  disclose sensitive information, bypass certain security restrictions,
  and compromise a vulnerable system.

  The vulnerabilities are reported in versions prior to 88

  Affected Software

  The following software is affected by the described vulnerability.
  Please check the vendor links below to see if exactly your version is
  affected.

  Mozilla Firefox 87.x

  Solution

  Upgrade to version 88.

  References

  1. https://www.mozilla.org/en-US/security/advisories/mfsa2021-16
  

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

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

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

2021-04-20 Thread Luis Alberto Pabón

I haven't got any pulseaudio updates on 21.04, to which version of
ubuntu was the fix released to?

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1925057] Re: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound

2021-04-20 Thread Hui Wang

When problem happens, please run each group of SET_COEF_INDEX and 
SET_PROC_COEF, then test if the audio changes normal or not:
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x78
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x003e
// test if audio changes normal or not
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x77
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x0015
// test if audio changes normal or not
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x67
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0xf000
//...
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x3b
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x60d9

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x33
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x8580

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x1b
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x0a6b

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x1a
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x8003

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x0f
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x02a2

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x0e
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x65c0

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x08
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x4ab7

sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x06
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x6115

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

Title:
  [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or
  crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello,

  I'm using Ubuntu together with Windows on my laptop.

  If I boot in Ubuntu after Windows sound doesn't work well (instead of
  system sounds I can hear only shot noise). To fix the issue I need to
  completely shut down the system (call Power Off via Ubuntu GUI) and
  then boot again in Ubuntu. Please note, that reboot (called via Ubuntu
  GUI) doesn't help to fix the issue.

  Expected result: sound works well regardless of boot history.
  Actual result: every time I boot in Ubuntu after Windows sound doesn't work.

  Issue occurrence: 100%.

  Environment:
  $ lsb_release -rd
  Description: Ubuntu Hirsute Hippo (development branch)
  Release: 21.04
  $ uname -a
  Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 
x86_64 x86_64 x86_64 GNU/Linux

  Thank you in advance!

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gluttton   1640 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 19 19:37:56 2021
  InstallationDate: Installed on 2021-03-06 (43 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Smart Sound Technology Audio Controller - sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   кві 19 19:37:21 tiptop pulseaudio[958]: After module unload, module 
'module-null-sink' was still loaded!
   кві 19 19:37:21 tiptop systemd[944]: pulseaudio.service: Succeeded.
   кві 19 19:37:40 tiptop systemd[944]: pulseaudio.service: Succeeded.
   кві 19 19:37:50 tiptop systemd[944]: pulseaudio.socket: Succeeded.
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or 
crackling sound
  UpgradeStatus: Upgraded to hirsute on 2021-03-06 (43 days ago)
  dmi.bios.date: 01/14/2021
  dmi.bios.release: 1.31
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DHCN31WW
  dmi.board.asset.tag: ���
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN
  dmi.chassis.asset.tag: ���
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga Slim 7 14IIL05
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05:
  dmi.product.family: Yoga Slim 7 14IIL05
  dmi.product.name: 82A1
  dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05
  dmi.product.version: Yoga Slim 7 14IIL05
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list:

[Desktop-packages] [Bug 1908999] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1

2021-04-20 Thread Santiago Gala

Not at the time. I found a way to have a proper apt package installed
and I want to live without snaps as much as possible, so now I have

$ apt policy chromium-browser
chromium-browser:
  Installed: 87.0.4280.88-0ubuntu0.20.04.1.1~vaapi
  Candidate: 87.0.4280.88-0ubuntu0.20.04.1.1~vaapi
  Version table:
 1:85.0.4183.83-0ubuntu0.20.04.2 500
500 http://es.archive.ubuntu.com/ubuntu focal-updates/universe amd64 
Packages
 *** 87.0.4280.88-0ubuntu0.20.04.1.1~vaapi 1337
   1337 http://ppa.launchpad.net/xalt7x/chromium-deb-vaapi/ubuntu 
focal/main amd64 Packages
100 /var/lib/dpkg/status
 80.0.3987.163-0ubuntu1 500
500 http://es.archive.ubuntu.com/ubuntu focal/universe amd64 Packages


instead of the fake package that installs a snap

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

Title:
  package chromium-browser (not installed) failed to install/upgrade:
  new chromium-browser package pre-installation script subprocess
  returned error exit status 1

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I uninstalled the chromium snap because it was downloading an upgrade
  and failing daily. After I did it I tried to install it again (with
  apt) and it tried to install a snap and failed, sending me here.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  AptOrdering:
   chromium-browser:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Dec 22 11:50:14 2020
  ErrorMessage: new chromium-browser package pre-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2017-12-11 (1106 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.2
  SourcePackage: chromium-browser
  Title: package chromium-browser (not installed) failed to install/upgrade: 
new chromium-browser package pre-installation script subprocess returned error 
exit status 1
  UpgradeStatus: Upgraded to focal on 2020-10-10 (72 days ago)

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

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

[Desktop-packages] [Bug 1925057] Re: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound

** Attachment added: "alsa-info-good.txt.yy9imLvHvj"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1925057/+attachment/5490137/+files/alsa-info-good.txt.yy9imLvHvj

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

Title:
  [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or
  crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello,

  I'm using Ubuntu together with Windows on my laptop.

  If I boot in Ubuntu after Windows sound doesn't work well (instead of
  system sounds I can hear only shot noise). To fix the issue I need to
  completely shut down the system (call Power Off via Ubuntu GUI) and
  then boot again in Ubuntu. Please note, that reboot (called via Ubuntu
  GUI) doesn't help to fix the issue.

  Expected result: sound works well regardless of boot history.
  Actual result: every time I boot in Ubuntu after Windows sound doesn't work.

  Issue occurrence: 100%.

  Environment:
  $ lsb_release -rd
  Description: Ubuntu Hirsute Hippo (development branch)
  Release: 21.04
  $ uname -a
  Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 
x86_64 x86_64 x86_64 GNU/Linux

  Thank you in advance!

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gluttton   1640 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 19 19:37:56 2021
  InstallationDate: Installed on 2021-03-06 (43 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Smart Sound Technology Audio Controller - sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   кві 19 19:37:21 tiptop pulseaudio[958]: After module unload, module 
'module-null-sink' was still loaded!
   кві 19 19:37:21 tiptop systemd[944]: pulseaudio.service: Succeeded.
   кві 19 19:37:40 tiptop systemd[944]: pulseaudio.service: Succeeded.
   кві 19 19:37:50 tiptop systemd[944]: pulseaudio.socket: Succeeded.
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or 
crackling sound
  UpgradeStatus: Upgraded to hirsute on 2021-03-06 (43 days ago)
  dmi.bios.date: 01/14/2021
  dmi.bios.release: 1.31
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DHCN31WW
  dmi.board.asset.tag: ���
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN
  dmi.chassis.asset.tag: ���
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga Slim 7 14IIL05
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05:
  dmi.product.family: Yoga Slim 7 14IIL05
  dmi.product.name: 82A1
  dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05
  dmi.product.version: Yoga Slim 7 14IIL05
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1925057] Re: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound

** Attachment added: "alsa-info-bad.txt.k4EOeiWnvC"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1925057/+attachment/5490136/+files/alsa-info-bad.txt.k4EOeiWnvC

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

Title:
  [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or
  crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello,

  I'm using Ubuntu together with Windows on my laptop.

  If I boot in Ubuntu after Windows sound doesn't work well (instead of
  system sounds I can hear only shot noise). To fix the issue I need to
  completely shut down the system (call Power Off via Ubuntu GUI) and
  then boot again in Ubuntu. Please note, that reboot (called via Ubuntu
  GUI) doesn't help to fix the issue.

  Expected result: sound works well regardless of boot history.
  Actual result: every time I boot in Ubuntu after Windows sound doesn't work.

  Issue occurrence: 100%.

  Environment:
  $ lsb_release -rd
  Description: Ubuntu Hirsute Hippo (development branch)
  Release: 21.04
  $ uname -a
  Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 
x86_64 x86_64 x86_64 GNU/Linux

  Thank you in advance!

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gluttton   1640 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 19 19:37:56 2021
  InstallationDate: Installed on 2021-03-06 (43 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Smart Sound Technology Audio Controller - sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   кві 19 19:37:21 tiptop pulseaudio[958]: After module unload, module 
'module-null-sink' was still loaded!
   кві 19 19:37:21 tiptop systemd[944]: pulseaudio.service: Succeeded.
   кві 19 19:37:40 tiptop systemd[944]: pulseaudio.service: Succeeded.
   кві 19 19:37:50 tiptop systemd[944]: pulseaudio.socket: Succeeded.
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or 
crackling sound
  UpgradeStatus: Upgraded to hirsute on 2021-03-06 (43 days ago)
  dmi.bios.date: 01/14/2021
  dmi.bios.release: 1.31
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DHCN31WW
  dmi.board.asset.tag: ���
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN
  dmi.chassis.asset.tag: ���
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga Slim 7 14IIL05
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05:
  dmi.product.family: Yoga Slim 7 14IIL05
  dmi.product.name: 82A1
  dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05
  dmi.product.version: Yoga Slim 7 14IIL05
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1925057] Re: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound

Please find the requested output attached.

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

Title:
  [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or
  crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello,

  I'm using Ubuntu together with Windows on my laptop.

  If I boot in Ubuntu after Windows sound doesn't work well (instead of
  system sounds I can hear only shot noise). To fix the issue I need to
  completely shut down the system (call Power Off via Ubuntu GUI) and
  then boot again in Ubuntu. Please note, that reboot (called via Ubuntu
  GUI) doesn't help to fix the issue.

  Expected result: sound works well regardless of boot history.
  Actual result: every time I boot in Ubuntu after Windows sound doesn't work.

  Issue occurrence: 100%.

  Environment:
  $ lsb_release -rd
  Description: Ubuntu Hirsute Hippo (development branch)
  Release: 21.04
  $ uname -a
  Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 
x86_64 x86_64 x86_64 GNU/Linux

  Thank you in advance!

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gluttton   1640 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 19 19:37:56 2021
  InstallationDate: Installed on 2021-03-06 (43 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Smart Sound Technology Audio Controller - sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   кві 19 19:37:21 tiptop pulseaudio[958]: After module unload, module 
'module-null-sink' was still loaded!
   кві 19 19:37:21 tiptop systemd[944]: pulseaudio.service: Succeeded.
   кві 19 19:37:40 tiptop systemd[944]: pulseaudio.service: Succeeded.
   кві 19 19:37:50 tiptop systemd[944]: pulseaudio.socket: Succeeded.
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or 
crackling sound
  UpgradeStatus: Upgraded to hirsute on 2021-03-06 (43 days ago)
  dmi.bios.date: 01/14/2021
  dmi.bios.release: 1.31
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DHCN31WW
  dmi.board.asset.tag: ���
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN
  dmi.chassis.asset.tag: ���
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga Slim 7 14IIL05
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05:
  dmi.product.family: Yoga Slim 7 14IIL05
  dmi.product.name: 82A1
  dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05
  dmi.product.version: Yoga Slim 7 14IIL05
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1923358] Re: Other servers doesn't display server list (Software Updater)

2021-04-20 Thread Julian Andres Klode

** Package changed: update-manager (Ubuntu) => software-properties
(Ubuntu)

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

Title:
  Other servers doesn't display server list (Software Updater)

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  Using Settings and then trying to choose other server doesn't do
  anything. It should display the list of available other servers.

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

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

[Desktop-packages] [Bug 1923358] [NEW] Other servers doesn't display server list (Software Updater)

You have been subscribed to a public bug:

Using Settings and then trying to choose other server doesn't do
anything. It should display the list of available other servers.

** Affects: software-properties (Ubuntu)
 Importance: Low
 Status: Incomplete

-- 
Other servers doesn't display server list (Software Updater)
https://bugs.launchpad.net/bugs/1923358
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to software-properties in Ubuntu.

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

[Desktop-packages] [Bug 1925067] Re: Power Statistics has bad colors for dark color scheme

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

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

** Changed in: gnome-power-manager (Ubuntu)
   Importance: Undecided => Low

** This bug has been marked a duplicate of bug 1852172
   Battery history and statistics graphs markings are unreadable on a dark theme

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

Title:
  Power Statistics has bad colors for dark color scheme

Status in gnome-power-manager package in Ubuntu:
  New

Bug description:
  When viewing graphs; the X and Y axis numbers are barely visible with the 
Dark color scheme.
  Screenshot attached.

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

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

[Desktop-packages] [Bug 1925095] Re: GNOME Desktop selection is misallinged with the mouse on 21.04-dev

** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-
desktop-icons-ng (Ubuntu)

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

Title:
  GNOME Desktop selection is misallinged with the mouse on 21.04-dev

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

Bug description:
  When dragging the mouse while selected on the Desktop, the selection
  box is misaligned with the mouse pointer. The issue only started
  happening on 21.04 after upgrading from 20.04 to the dev version of
  the OS.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
  Uname: Linux 5.11.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 19 22:00:22 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-12-28 (112 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   LANG=pt_BR.UTF-8
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-04-13 (6 days ago)

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

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

[Desktop-packages] [Bug 1923389] Re: Screenshot different colours 18.04

Thank you for the bug report, it seems similar to
https://gitlab.gnome.org/GNOME/gnome-screenshot/-/issues/113

** Bug watch added: gitlab.gnome.org/GNOME/gnome-screenshot/-/issues #113
   https://gitlab.gnome.org/GNOME/gnome-screenshot/-/issues/113

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

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

** Summary changed:

- Screenshot different colours 18.04
+ Screenshot different colours

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

Title:
  Screenshot different colours

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu version 18.04.5 LTS.

  gnome-screenshot:
    Installed: 3.25.0-0ubuntu2
    Candidate: 3.25.0-0ubuntu2
    Version table:
   *** 3.25.0-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Expected: Both colors on the image and the web page are the same hex code.
  Happened instead: Diffent colour hex.

  Taking a screenshot from a webpage changes the colors slighlty.

  I have attached a video of what is happening, its a slighlt different
  colour but still different altogether.

  From a HTML page it is #11283C but when I place the screenshot on top of a 
background with that color, its clearly different.
  On image the hex is #0D253D.

  I have attached a video of the process

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

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

[Desktop-packages] [Bug 1925088] Re: Headphones don't work when speakers work

2021-04-20 Thread Robert

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

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

Title:
  Headphones don't work when speakers work

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Hi!

  I have problem with front panel audio output connector. Speakers still
  work after my headphones is connected. Everything correctly works on
  windows 10.

  I selected headphones in Settings -> Sound -> Output, but speakers
  were continuing working.

  PulseAudio Volume Control didn't help too. I've tried to change
  configuration and select headphones as output devices.

  When i disconnected speakers, headphones weren't still working.

  I've done all list from
  https://help.ubuntu.com/community/SoundTroubleshooting and haven't
  found any problems.

  pacmd - https://pastebin.com/Jkfqt4ft
  aplay - https://pastebin.com/NGq37fVb
  snd   - https://pastebin.com/7bS0GKzc
  lspci - https://pastebin.com/Z6CYmRU2
  alsa  - http://alsa-project.org/db/?f=b5701e36e1510cb211fd3047c36598da27fef2d9

  My hardware:

  CPU - Intel i9 10900k
  Mobo - Asus z590-e with the latest bios.
  GPU - Nvidia RTX 3070

  If you need some additional information, I will provide it.

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

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

[Desktop-packages] [Bug 1703377] Re: Gnome online account login prevents paste or autotype

** Changed in: gnome-online-accounts (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-online-accounts (Ubuntu)
   Status: Confirmed => Triaged

** Also affects: gnome-online-accounts via
   https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/17
   Importance: Unknown
   Status: Unknown

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

Title:
  Gnome online account login prevents paste or autotype

Status in gnome-online-accounts:
  Unknown
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  On entering Login data to an online account such as google.

  Using keepass as password manager I now can not enter my password via
  paste nor via autotype. Trying any of them results in an invalid
  password.

  Ubuntu 16.10 - GNOME Shell 3.20.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1703377/+subscriptions

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

[Desktop-packages] [Bug 1925088] [NEW] Headphones don't work when speakers work

You have been subscribed to a public bug:

Hi!

I have problem with front panel audio output connector. Speakers still
work after my headphones is connected. Everything correctly works on
windows 10.

I selected headphones in Settings -> Sound -> Output, but speakers were
continuing working.

PulseAudio Volume Control didn't help too. I've tried to change
configuration and select headphones as output devices.

When i disconnected speakers, headphones weren't still working.

I've done all list from
https://help.ubuntu.com/community/SoundTroubleshooting and haven't found
any problems.

pacmd - https://pastebin.com/Jkfqt4ft
aplay - https://pastebin.com/NGq37fVb
snd   - https://pastebin.com/7bS0GKzc
lspci - https://pastebin.com/Z6CYmRU2
alsa  - http://alsa-project.org/db/?f=b5701e36e1510cb211fd3047c36598da27fef2d9

My hardware:

CPU - Intel i9 10900k
Mobo - Asus z590-e with the latest bios.
GPU - Nvidia RTX 3070

If you need some additional information, I will provide it.

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


** Tags: bot-comment
-- 
Headphones don't work when speakers work
https://bugs.launchpad.net/bugs/1925088
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to pulseaudio in Ubuntu.

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

[Desktop-packages] [Bug 1925152] [NEW] firefox not responsive when typing in address bar or web based search box

2021-04-20 Thread Bevan

Public bug reported:

Firefox 87 by Ubuntu in plasma Wayland 21.04 is not responsive when
typing in the address bar or text boxes.

I am trying to type a URL in the address bar or text for searching. I
will only let me type 2 or 3 characters of text then it seems to lock
up. Can't even select text with a mouse.

I think it is doing this in the background but doesn't display on screen
as me doing anything.

I don't have this issue with the Firefox which I downloaded directly
from Mozilla. Furthermore, I just unzip the file and run the Firefox bin
file.

If I run Ubuntu Firefox in x11 I don't have these issues.

Running firefox from terminal gives them message
(firefox:74754): Gdk-CRITICAL **: 21:15:01.027: 
gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 
'GDK_IS_WAYLAND_WINDOW (window)' failed

I get the same message even in safemode and the same issues.

cpu is between 5% and 30% with firefox

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: firefox 87.0+build3-0ubuntu4
ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
Uname: Linux 5.11.0-14-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  kiwilinux  51325 F pulseaudio
 /dev/snd/controlC0:  kiwilinux  51325 F pulseaudio
BuildID: 20210318103112
CasperMD5CheckResult: unknown
Channel: Unavailable
CurrentDesktop: KDE
Date: Tue Apr 20 20:16:44 2021
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
DefaultProfilePrefSources:
 /usr/lib/firefox/defaults/pref/all-ubuntumate.js
 prefs.js
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
InstallationDate: Installed on 2019-09-30 (567 days ago)
InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
Profile0Extensions: extensions.sqlite corrupt or missing
Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile0Locales: extensions.sqlite corrupt or missing
Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
Profile0PrefSources:
 /usr/lib/firefox/defaults/pref/all-ubuntumate.js
 prefs.js
Profile0Themes: extensions.sqlite corrupt or missing
Profile2Extensions: extensions.sqlite corrupt or missing
Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile2Locales: extensions.sqlite corrupt or missing
Profile2PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
Profile2PrefSources:
 /usr/lib/firefox/defaults/pref/all-ubuntumate.js
 prefs.js
Profile2Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile1 (Default) - LastVersion=75.0/20200403170909 (Out of date)
 Profile0 - LastVersion=87.0/20210318103112
 Profile2 - LastVersion=88.0/20210415204500 (Out of date)
RebootRequiredPkgs:
 linux-image-5.11.0-16-generic
 linux-base
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: Upgraded to hirsute on 2021-04-17 (2 days ago)
dmi.bios.date: 09/22/2020
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FX505DV.311
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: FX505DV
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No  Asset  Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 15.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFX505DV.311:bd09/22/2020:br5.14:efr15.0:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505DV_FX505DV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505DV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: TUF Gaming
dmi.product.name: TUF Gaming FX505DV_FX505DV
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2019-10-22T20:48:03.215408

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


** Tags: amd64 apport-bug hirsute wayland-session

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

Title:
  firefox not responsive when typing in address bar or web based search
  box

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox 87 by Ubuntu in plasma Wayland 21.04 is not responsive when
  typing in the address

[Desktop-packages] [Bug 1924184] Re: drive not showing

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Please also ensure that you include the release and flavour of Ubuntu
that you are using.

Thank you!

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

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

Title:
  drive not showing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  i coudnt find graphic drive

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 15 03:35:34 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0844]
 Subsystem: Dell Jet PRO [Radeon R5 M230 / R7 M260DX / Radeon 520 Mobile] 
[1028:0844]
  InstallationDate: Installed on 2021-04-13 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Vostro 3578
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic 
root=UUID=7cf915de-bb29-49e2-a9cc-0079efc75ed1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2020
  dmi.bios.release: 1.10
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 01Y7V4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd01/09/2020:br1.10:svnDellInc.:pnVostro3578:pvr:rvnDellInc.:rn01Y7V4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3578
  dmi.product.sku: 0844
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1924832] Re: evince output displays wrong in Adobe Reader

Thank you for your bug report, could you perhaps also report it upstream
on https://gitlab.gnome.org/GNOME/evince/-/issues ?

** Changed in: evince (Ubuntu)
   Importance: Undecided => Low

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

Title:
  evince output displays wrong in Adobe Reader

Status in evince package in Ubuntu:
  New

Bug description:
  wget https://www.irs.gov/pub/irs-pdf/f1040s2.pdf
  launch evince
  open f1040s2.pdf
  Fill in example numbers in lines 4 and 10.
  Save As... test-1040s2.pdf

  On the same Ubuntu-18.04 machine, in both xpdf and evince, all of
  test-1040s2.pdf displays as expected, specifically including the form
  entries.

  Copied f1040s2.pdf to a (virtual) machine running MS-Windows-10, and opened 
in Adobe Reader DC 2021.001.20142 .
  Expected: display correctly, specifically the form entries in lines 4 and 10.
  Actual: no form entries show up in line 4 or 10, as seen in 
tax-pdf-adobe-reader-w10.png file from screenshot (lines 4 & 10 circled in red 
with the gimp).

  Ubuntu-18.04.5-LTS, evince-3.28.4-0ubuntu1.2

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pdfshuffler 0.6.0-8
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Apr 16 21:16:52 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-11-21 (878 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: pdfshuffler
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1860551] Re: package chromium-browser 78.0.3904.70-0ubuntu0.19.04.4 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error ex

According to DpkgTerminalLog.txt, installation of the chromium snap
completed successfully. Not sure what happened there.

In any case, Ubuntu 19.10 has reached end-of-life and is not supported
any longer, if you're still using it I strongly recommend upgrading to a
supported version (e.g. 20.04).

** Changed in: chromium-browser (Ubuntu)
   Status: New => Incomplete

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  package chromium-browser 78.0.3904.70-0ubuntu0.19.04.4 failed to
  install/upgrade: new chromium-browser package pre-installation script
  subprocess returned error exit status 128

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  During a routine update, the installation of this package got stuck
  for several minutes with process pk-debconf-help taking 100% CPU. I
  then killed that process and run apt -f install, and it went without
  problem.

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser 78.0.3904.70-0ubuntu0.19.04.4
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  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///wAebX5YAQEBAQEVAQOAMx146l6lolVNoCYRUFQhCACzAIGAgUBxQAEBAQEBAQEBAjqAGHE4LUBYLEUA/iIRAAAe/QA4PR5TDwAKICAgICAg/ABJUFMyMzUKICAgICAg/wBTZXJpYWwgTnVtYmVyAUkCAx3xSpAEAwEUEgUfEBMjCQcHgwEAAGUDDAAQAAI6gBhxOC1AWCxFAP4iEQAAHgEdgBhxHBYgWCwlAP4iEQAAngEdAHJR0B4gbihVAP4iEQAAHowK0Iog4C0QED6WAP4iEQAAGAAA5g==
   modes: 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080i 
1920x1080 1920x1080i 1680x1050 1280x1024 1280x960 1152x864 1280x720 1280x720 
1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 720x480 720x480 
640x480 640x480 640x480
  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:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAw5KcFAAAbAQSlHxF44kQVoVJGoCkPUFQBAQEBAQEBAQEBAQEBAQEBaV4AoKCgKVAwIKUANa4QAAAaiEsAoKCgKVAwIKUANa4QAAAa/gBMRyBEaXNwbGF5CiAg/gBMUDE0MFFIMi1TUEExAHw=
   modes: 2560x1440 2560x1440
  Date: Wed Jan 22 10:24:02 2020
  Desktop-Session:
   'None'
   'None'
   'None'
  Env:
   'None'
   'None'
  ErrorMessage: new chromium-browser package pre-installation script subprocess 
returned error exit status 128
  InstallationDate: Installed on 2018-12-14 (404 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Load-Avg-1min: 3.18
  Load-Processes-Running-Percent:   0.1%
  MachineType: LENOVO 20LDCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=f3170b45-30d1-4b61-89eb-954adc8f5363 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
  SourcePackage: chromium-browser
  Title: package chromium-browser 78.0.3904.70-0ubuntu0.19.04.4 failed to 
install/upgrade: new chromium-browser package pre-installation script 
subprocess returned error exit status 128
  UpgradeStatus: Upgraded to eoan on 2019-11-11 (71 days ago)
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N25ET51W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN25ET51W(1.37):bd10/30/2019:svnLENOVO:pn20LDCTO1WW:pvrThinkPadX1Yoga3rd:rvnLENOVO:rn20LDCTO1WW:rvrNotDefined:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 3rd
  dmi.product.name: 20LDCTO1WW
  dmi.product.sku: LENOVO_MT_20LD_BU_Think_FM_ThinkPad X1 Yoga 3rd
  dmi.product.version: ThinkPad X1 Yoga 3rd
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver

The issue was fixed in hirsute I believe but it referenced the wrong
launchpad bug so didn't get closed, right?

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

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

Title:
  Cursor bleeds on the platform with Mali armsoc driver

Status in OEM Priority Project:
  New
Status in OEM Priority Project focal series:
  New
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  The cursor bleeds because of the bug in xorg which does not refresh the 
sprite background. (LP: #1911479)
  The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu).

  [Test Case]

  Check if cursor is still bleeding with the patched xorg-server

  [ Regression potential ]

  The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver.
  It won't impact other platforms.

  ---
  Xilinx is trying to upstream the patch. It's still under review.
  https://lists.x.org/archives/xorg-devel/2021-March/058672.html

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

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

[Desktop-packages] [Bug 1908999] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1

It looks like the gnome-platform snap wasn't installed, or was disconnected.
Can you share the output of the following commands?

snap list

snap connections

Does retrying work?

sudo apt reinstall chromium-browser

** Changed in: chromium-browser (Ubuntu)
   Status: New => Incomplete

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

Title:
  package chromium-browser (not installed) failed to install/upgrade:
  new chromium-browser package pre-installation script subprocess
  returned error exit status 1

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I uninstalled the chromium snap because it was downloading an upgrade
  and failing daily. After I did it I tried to install it again (with
  apt) and it tried to install a snap and failed, sending me here.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  AptOrdering:
   chromium-browser:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Dec 22 11:50:14 2020
  ErrorMessage: new chromium-browser package pre-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2017-12-11 (1106 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.2
  SourcePackage: chromium-browser
  Title: package chromium-browser (not installed) failed to install/upgrade: 
new chromium-browser package pre-installation script subprocess returned error 
exit status 1
  UpgradeStatus: Upgraded to focal on 2020-10-10 (72 days ago)

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

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

[Desktop-packages] [Bug 1914885] Re: Botted up, logged in, then error: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subproce

DpkgHistoryLog.txt contains this:

Start-Date: 2021-02-06  10:13:12
Commandline: apt install chromium-browser
Requested-By: rpgrbroadcaster1 (1000)
Install: chromium-browser:amd64 (1:85.0.4183.83-0ubuntu0.20.04.2)

So it looks like you did request to install chromium-browser.

As for the error itself, from DpkgTerminalLog.txt:

==> Installing the chromium snap
2021-02-06T10:13:51-08:00 INFO Waiting for conflicting change in progress: 
conflicting plug snap chromium, task "connect"

It looks like a transient failure, if you're interested in installing
chromium-browser I'd suggest retrying:

sudo apt reinstall chromium-browser

Otherwise, you can safely remove it:

sudo apt purge chromium-browser

** Changed in: chromium-browser (Ubuntu)
   Status: New => Incomplete

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

Title:
  Botted up, logged in, then error: package chromium-browser (not
  installed) failed to install/upgrade: new chromium-browser package
  pre-installation script subprocess returned error exit status 1 - Did
  not install this. Nor did I try to install this. This is fresh OS
  install.

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Botted up, logged in, then error: package chromium-browser (not
  installed) failed to install/upgrade: new chromium-browser package
  pre-installation script subprocess returned error exit status 1 - Did
  not install this. Nor did I try to install this. This is fresh OS
  install.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.16
  AptOrdering:
   chromium-browser:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Feb  6 10:14:09 2021
  ErrorMessage: new chromium-browser package pre-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2021-02-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: chromium-browser
  Title: package chromium-browser (not installed) failed to install/upgrade: 
new chromium-browser package pre-installation script subprocess returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1914772] Re: package chromium-browser 1:85.0.4183.83-0ubuntu2 failed to install/upgrade: 新的 chromium-browser 软件包 pre-installation 脚本子进程返回错误状态 10

>From DpkgTerminalLog.txt:

准备解压 .../chromium-browser_1%3a85.0.4183.83-0ubuntu2_arm64.deb  ...
=> Installing the chromium snap
==> Checking connectivity with the snap store
Your system is unable to reach the snap store, please make sure you're
connected to the Internet and update any firewall or proxy settings as
needed so that you can reach the snap store.
You can manually check for connectivity by running "snap info chromium"
Aborting will cause the upgrade to fail and will require it to be
re-attempted  once snapd is functional on the system.
Skipping will let the package upgrade continue but chromium will not be
functional until the chromium snap is installed.


What is the output of the following command?

snap info chromium

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  package chromium-browser 1:85.0.4183.83-0ubuntu2 failed to
  install/upgrade: 新的 chromium-browser 软件包 pre-installation 脚本 子进程返回错误状态
  10

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I cannot install chromium.

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: chromium-browser 1:85.0.4183.83-0ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-1013.16-raspi 5.8.18
  Uname: Linux 5.8.0-1013-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu50.5
  AptOrdering:
   chromium-browser:arm64: Install
   NULL: ConfigurePending
  Architecture: arm64
  CasperMD5CheckResult: skip
  Date: Fri Feb  5 22:09:05 2021
  Dependencies:
   
  ErrorMessage: 新的 chromium-browser 软件包 pre-installation 脚本 子进程返回错误状态 10
  ImageMediaBuild: 20201022
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.5ubuntu2
   apt  2.1.10ubuntu0.2
  SourcePackage: chromium-browser
  Title: package chromium-browser 1:85.0.4183.83-0ubuntu2 failed to 
install/upgrade: 新的 chromium-browser 软件包 pre-installation 脚本 子进程返回错误状态 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1923675] Re: package chromium-browser 1:85.0.4183.83-0ubuntu2 failed to install/upgrade: el subproceso nuevo paquete chromium-browser script pre-installation devolvió el código

This looks like a temporary problem:

==> Installing the chromium snap
error: snap "chromium" has "install-snap" change in progress

Can you try re-installing chromium-browser, and let us know if it
succeeds?

sudo apt reinstall chromium-browser

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

Title:
  package chromium-browser 1:85.0.4183.83-0ubuntu2 failed to
  install/upgrade: el subproceso nuevo paquete chromium-browser script
  pre-installation devolvió el código de salida de error 10

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  soy un novato en ubuntu, pero me guio mucho de tutoriales, he
  instalado ya varias paquetescon exito y es mi primera vez con un
  problema

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: chromium-browser 1:85.0.4183.83-0ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  AptOrdering:
   chromium-browser:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Apr 13 19:20:52 2021
  Dependencies:
   
  ErrorMessage: el subproceso nuevo paquete chromium-browser script 
pre-installation devolvió el código de salida de error 10
  InstallationDate: Installed on 2021-03-27 (17 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.5ubuntu2
   apt  2.1.10ubuntu0.1
  SourcePackage: chromium-browser
  Title: package chromium-browser 1:85.0.4183.83-0ubuntu2 failed to 
install/upgrade: el subproceso nuevo paquete chromium-browser script 
pre-installation devolvió el código de salida de error 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2021-04-20 Thread Bug Watch Updater

** Changed in: pulseaudio
   Status: New => Fix Released

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1922438] Re: Firefox unusable on Kubuntu 21.04 Wayland session