[Desktop-packages] [Bug 1999320] Re: Font alignment issue in search bar when using scaling factor > 1

2024-02-01 Thread Bug Watch Updater
** Changed in: yaru
   Status: Unknown => New

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

Title:
  Font alignment issue in search bar when using scaling factor > 1

Status in Yaru Theme:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in yaru-theme package in Ubuntu:
  New

Bug description:
  When I use a desktop interface text scaling factor of 1.5, the
  alignment text in the applications menu search bar is not set properly

  I have attached a screenshot showing the issue.

  1)
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04
  2) xorg:
Installed: 1:7.7+23ubuntu2
Candidate: 1:7.7+23ubuntu2
Version table:
   *** 1:7.7+23ubuntu2 500
  500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  3) text was centered
  4) it is not centered

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


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


[Desktop-packages] [Bug 1958019]

2024-02-01 Thread j4cobgarby
(In reply to Lukas from comment #814)
> (In reply to Jacob Garby from comment #813)
> > I have a "Lenovo Legion Slim 7i 16", and several days ago, out of nowhere,
> > the speaker started working. I have no idea how -- I did not change
> anything
> > manually. I suspect it's a new kernel version that did it.
> > 
> > I'm on Arch Linux, and I can't remember which kernel version I have
> > installed (but I can update when I get home later today).
> > 
> > Anyway, good news!
> 
> Amazing
> 
> I would like to reproduce this. You can find out your current kernel version
> with the command "uname -r". The installed sound packages/libs would also be
> interesting. What I know of would be to look at the alsa version. 
> Someone else surely has more information on what to specificly look for and
> how.

Okay, so my kernel version is 6.7.2-arch1-1

These are some (maybe all) of the audio related packages I have installed:
kpipewire 5.27.10-1
libpipewire 1:1.0.1-2
pipewire 1:1.0.1-2
pipewire-alsa 1:1.0.1-2
pipewire-audio 1:1.0.1-2
pipewire-jack 1:1.0.1-2
pipewire-pulse 1:1.0.1-2
libpulse 17.0-3
pipewire-pulse 1:1.0.1-2
projectm-pulseaudio 3.1.12-4

But I can verify that my speaker did also work _before_ I switched from
Pulseaudio to Pipewire, seems both should work.

The result of running alsa-info is here: http://alsa-
project.org/db/?f=07a1fdaf34a424adc27dbb6be3f417995df6994f

Good luck!

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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


[Desktop-packages] [Bug 1945063] Re: Ubuntu Dock Bug with window minimize when having Dock at the bottom

2024-02-01 Thread Daniel van Vugt
** Tags removed: impish
** Tags added: mantic

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

Title:
  Ubuntu Dock Bug with window minimize when having Dock at the bottom

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

Bug description:
  Running Ubuntu 21.10 (I know it is still not released, but wanted to test 
it). I noticed that there a bug where when you have the Dock at the bottom and 
you launch an app, which minimizing it it won’t minimize to the bottom as it 
still thinks the Dock is off to the left. Once you change work spaces then only 
does the app realize that the dock is at the bottom of the screen. Please see 
attached video.
  https://imgur.com/a/mgLJ3xp

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 25 12:14:42 2021
  InstallationDate: Installed on 2021-04-28 (149 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1945063/+subscriptions


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


[Desktop-packages] [Bug 2047363] Re: bottom dock animation issue

2024-02-01 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1945063 ***
https://bugs.launchpad.net/bugs/1945063

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 1945063, 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.


** This bug has been marked a duplicate of bug 1945063
   Ubuntu Dock Bug with window minimize when having Dock at the bottom

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

Title:
  bottom dock animation issue

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

Bug description:
  I noticed that there a bug where when you have the Dock at the bottom
  and you launch an app, which minimizing it it won’t minimize to the
  bottom as it still thinks the Dock is off to the left. Once you change
  work spaces then only does the app realize that the dock is at the
  bottom of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell-extension-ubuntu-dock 87ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 25 21:38:53 2023
  InstallationDate: Installed on 2023-12-02 (23 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1999320] Re: Font alignment issue in search bar when using scaling factor > 1

2024-02-01 Thread Daniel van Vugt
** Also affects: yaru-theme (Ubuntu)
   Importance: Undecided
   Status: New

** Bug watch added: github.com/ubuntu/yaru/issues #4023
   https://github.com/ubuntu/yaru/issues/4023

** Also affects: yaru via
   https://github.com/ubuntu/yaru/issues/4023
   Importance: Unknown
   Status: Unknown

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

Title:
  Font alignment issue in search bar when using scaling factor > 1

Status in Yaru Theme:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in yaru-theme package in Ubuntu:
  New

Bug description:
  When I use a desktop interface text scaling factor of 1.5, the
  alignment text in the applications menu search bar is not set properly

  I have attached a screenshot showing the issue.

  1)
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04
  2) xorg:
Installed: 1:7.7+23ubuntu2
Candidate: 1:7.7+23ubuntu2
Version table:
   *** 1:7.7+23ubuntu2 500
  500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  3) text was centered
  4) it is not centered

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


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


[Desktop-packages] [Bug 1813937] Re: How to get back my favorite dialog after screenshot?

2024-02-01 Thread Jason Bodnar
I was able to install the Mint version from
https://ftp5.gwdg.de/pub/linux/debian/mint/packages/pool/upstream/g/gnome-
screenshot/gnome-screenshot_41.0+mint2+vanessa_amd64.deb and it replaced
the existing version and does what I want. I guess I need to lock the
version.

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

Title:
  How to get back my favorite dialog after screenshot?

Status in gnome-screenshot package in Ubuntu:
  Triaged

Bug description:
  In earlier versions of that package I just pressed Shift+PrScr, select
  an area and see a dialog after it whether I want to save it or not.

  Now Shift+PrScr saves screenshot implicitly and I have to press
  Shift+Alt+PrScr

  Could you provide me a solution (Not gnome-screenshot -a -i because it has 
extra dialog after executing it)?
  If it's as designed, please tell me latest version with older behaviour I 
could hold from updates

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


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


[Desktop-packages] [Bug 1813937] Re: How to get back my favorite dialog after screenshot?

2024-02-01 Thread Jason Bodnar
I just switched from Linux Mint Virginia. It's version of gnome-
screenshot allows you to decide whether to save the file, copy it to the
clipboard or abandon it. Any way to get the behavior in ubuntu?

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

Title:
  How to get back my favorite dialog after screenshot?

Status in gnome-screenshot package in Ubuntu:
  Triaged

Bug description:
  In earlier versions of that package I just pressed Shift+PrScr, select
  an area and see a dialog after it whether I want to save it or not.

  Now Shift+PrScr saves screenshot implicitly and I have to press
  Shift+Alt+PrScr

  Could you provide me a solution (Not gnome-screenshot -a -i because it has 
extra dialog after executing it)?
  If it's as designed, please tell me latest version with older behaviour I 
could hold from updates

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


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


[Desktop-packages] [Bug 2039021] Re: NO-GUI headless convert-to function error in 7.6.1.2 60(Build:2)

2024-02-01 Thread Bug Watch Updater
** Changed in: df-libreoffice
   Status: Confirmed => Fix Released

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

Title:
  NO-GUI headless convert-to function error in 7.6.1.2 60(Build:2)

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

Bug description:
  Original bug report to LibreOffice team:
  https://bugs.documentfoundation.org/show_bug.cgi?id=157424

  7.6.1.2 60(Build:2) no-gui version, Ubuntu Server  20.04 LTS gives
  error.

  soffice --headless --convert-to pdf path/to/file --> Error: source
  file could not be loaded

  Ubuntu 20.04 LTS Desktop version has no error with the same version,
  only on Server. The installation difference is libreoffice vs
  libreoffice-nogui. Previous version doesent produces this error:
  7.5.6.2 50(Build:2) work perfect.

  Lots of no-gui version fails in Ubuntu Server 20.04 LTS with "Error:
  source file could not be loaded" message.

  Specific examples:

  - LibreOffice 6.4.7.2 40(Build:2)  --> Same error with xlsx with --convert-to 
html
  - LibreOffice 7.5.3.2 50(Build:2)  --> Same error with xlsx with --convert-to 
html

  !!! Only LibreOffice 7.5.6.2 50(Build:2) works perfectly in both case.
  !!! Example outputs:

  soffice --headless --convert-to pdf teszt.docx
  convert /home/zsolt/teszt.docx -> /home/zsolt/teszt.pdf using filter : 
writer_pdf_Export

  soffice --headless --convert-to html teszt.xlsx
  convert /home/zsolt/teszt.xlsx -> /home/zsolt/teszt.html using filter : HTML 
(StarCalc)

  Fortunately *ppa:libreoffice/libreoffice-still* contains the good
  version so i had to change the repos in all servers

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


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


[Desktop-packages] [Bug 2039021]

2024-02-01 Thread Libreoffice-commits
Noel Grandin committed a patch related to this issue.
It has been pushed to "libreoffice-24-2":

https://git.libreoffice.org/core/commit/61371bf3b19441d2c30a51153fcc675eafdd49b8

tdf#158695 convert-to bogusly needs libcui (--disable-gui build)

It will be available in 24.2.1.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

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

Title:
  NO-GUI headless convert-to function error in 7.6.1.2 60(Build:2)

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

Bug description:
  Original bug report to LibreOffice team:
  https://bugs.documentfoundation.org/show_bug.cgi?id=157424

  7.6.1.2 60(Build:2) no-gui version, Ubuntu Server  20.04 LTS gives
  error.

  soffice --headless --convert-to pdf path/to/file --> Error: source
  file could not be loaded

  Ubuntu 20.04 LTS Desktop version has no error with the same version,
  only on Server. The installation difference is libreoffice vs
  libreoffice-nogui. Previous version doesent produces this error:
  7.5.6.2 50(Build:2) work perfect.

  Lots of no-gui version fails in Ubuntu Server 20.04 LTS with "Error:
  source file could not be loaded" message.

  Specific examples:

  - LibreOffice 6.4.7.2 40(Build:2)  --> Same error with xlsx with --convert-to 
html
  - LibreOffice 7.5.3.2 50(Build:2)  --> Same error with xlsx with --convert-to 
html

  !!! Only LibreOffice 7.5.6.2 50(Build:2) works perfectly in both case.
  !!! Example outputs:

  soffice --headless --convert-to pdf teszt.docx
  convert /home/zsolt/teszt.docx -> /home/zsolt/teszt.pdf using filter : 
writer_pdf_Export

  soffice --headless --convert-to html teszt.xlsx
  convert /home/zsolt/teszt.xlsx -> /home/zsolt/teszt.html using filter : HTML 
(StarCalc)

  Fortunately *ppa:libreoffice/libreoffice-still* contains the good
  version so i had to change the repos in all servers

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


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


[Desktop-packages] [Bug 2039021]

2024-02-01 Thread Rene Engelhard
sorry, works. setting to FIXED again

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

Title:
  NO-GUI headless convert-to function error in 7.6.1.2 60(Build:2)

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

Bug description:
  Original bug report to LibreOffice team:
  https://bugs.documentfoundation.org/show_bug.cgi?id=157424

  7.6.1.2 60(Build:2) no-gui version, Ubuntu Server  20.04 LTS gives
  error.

  soffice --headless --convert-to pdf path/to/file --> Error: source
  file could not be loaded

  Ubuntu 20.04 LTS Desktop version has no error with the same version,
  only on Server. The installation difference is libreoffice vs
  libreoffice-nogui. Previous version doesent produces this error:
  7.5.6.2 50(Build:2) work perfect.

  Lots of no-gui version fails in Ubuntu Server 20.04 LTS with "Error:
  source file could not be loaded" message.

  Specific examples:

  - LibreOffice 6.4.7.2 40(Build:2)  --> Same error with xlsx with --convert-to 
html
  - LibreOffice 7.5.3.2 50(Build:2)  --> Same error with xlsx with --convert-to 
html

  !!! Only LibreOffice 7.5.6.2 50(Build:2) works perfectly in both case.
  !!! Example outputs:

  soffice --headless --convert-to pdf teszt.docx
  convert /home/zsolt/teszt.docx -> /home/zsolt/teszt.pdf using filter : 
writer_pdf_Export

  soffice --headless --convert-to html teszt.xlsx
  convert /home/zsolt/teszt.xlsx -> /home/zsolt/teszt.html using filter : HTML 
(StarCalc)

  Fortunately *ppa:libreoffice/libreoffice-still* contains the good
  version so i had to change the repos in all servers

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


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


[Desktop-packages] [Bug 1950703] Re: Keyboard input does't work in several apps with iBus running

2024-02-01 Thread Anna
we have still the problem with firefox and app store with snap 2.61.

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

Title:
  Keyboard input does't work in several apps with iBus running

Status in snapd:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  If installed through Snap and with iBus running the keyboard doesn't work in 
Standard Notes, XMind and Chromium apps on Manjaro 21.1. Killing iBus fixes the 
issue.
  The keyboard works in Visual Studio, however
  

  
  snap 2.51.3-2
  snapd 2.51.3-2
  series 16
  manjaro -
  kernel 5.10.70-1-MANJARO
  
  
  
   sudo snap connections chromium

  Interface PlugSlot
 Notes
  audio-playbackchromium:audio-playback 
:audio-playback  -
  audio-record  chromium:audio-record   
:audio-record-
  bluez chromium:bluez  :bluez  
 -
  browser-support   chromium:browser-sandbox
:browser-support -
  camerachromium:camera :camera 
 -
  content[gnome-3-28-1804]  chromium:gnome-3-28-1804
gnome-3-28-1804:gnome-3-28-1804  -
  content[gtk-3-themes] chromium:gtk-3-themes   
gtk-common-themes:gtk-3-themes   -
  content[icon-themes]  chromium:icon-themes
gtk-common-themes:icon-themes-
  content[sound-themes] chromium:sound-themes   
gtk-common-themes:sound-themes   -
  cups-control  chromium:cups-control   
:cups-control-
  desktop   chromium:desktop:desktop
 -
  desktop-legacychromium:desktop-legacy 
:desktop-legacy  -
  gsettings chromium:gsettings  :gsettings  
 -
  home  chromium:home   :home   
 -
  joystick  chromium:joystick   :joystick   
 -
  mount-observe chromium:mount-observe  -   
 -
  mpris -   
chromium:mpris   -
  network   chromium:network:network
 -
  network-bind  chromium:network-bind   
:network-bind-
  network-manager   chromium:network-manager-   
 -
  openglchromium:opengl :opengl 
 -
  password-manager-service  chromium:password-manager-service   -   
 -
  personal-fileschromium:chromium-config
:personal-files  -
  pulseaudiochromium:pulseaudio -   
 -
  raw-usb   chromium:raw-usb-   
 -
  removable-media   chromium:removable-media
:removable-media -
  screen-inhibit-controlchromium:screen-inhibit-control 
:screen-inhibit-control  -
  system-files  chromium:etc-chromium-browser-policies  
:system-files-
  system-packages-doc   chromium:system-packages-doc
:system-packages-doc -
  u2f-devices   chromium:u2f-devices
:u2f-devices -
  unity7chromium:unity7 :unity7 
 -
  upower-observechromium:upower-observe 
:upower-observe  -
  wayland   chromium:wayland:wayland
 -
  x11   chromium:x11:x11
 -


  
  sudo snap connections standard-notes

  Interface Plug Slot   
  Notes
  audio-playbackstandard-notes:audio-playback
:audio-playback  -
  browser-support   standard-notes:browser-support   
:browser-support -
  content[gnome-3-28-1804]  standard-notes:gnome-3-28-1804   
gnome-3-28-1804:gnome-3-28-1804  -
  content[gtk-3-themes] standard-notes:gtk-3-themes  
gtk-common-themes:gtk-3-themes   -
  

[Desktop-packages] [Bug 2050743] Re: plymouthd crashed with SIGSEGV in ply_input_device_get_keymap()

2024-02-01 Thread Launchpad Bug Tracker
This bug was fixed in the package plymouth - 23.360.11-0ubuntu3

---
plymouth (23.360.11-0ubuntu3) noble; urgency=medium

  * Add renderers-Do-not-assume-all-keyboards-have-LEDs.patch to avoid
plymouthd from segfaulting on some systems, resulting in missing
splash screens. (LP: #2050743)

 -- Daniel van Vugt   Thu, 01 Feb 2024
11:18:08 +0800

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

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

Title:
  plymouthd crashed with SIGSEGV in ply_input_device_get_keymap()

Status in Plymouth:
  Fix Released
Status in plymouth package in Ubuntu:
  Fix Released

Bug description:
  Unsure

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: plymouth 23.360.11-0ubuntu2
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Mon Jan 22 18:15:26 2024
  DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
  ExecutablePath: /usr/sbin/plymouthd
  InstallationDate: Installed on 2024-01-22 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240122)
  JournalErrors: -- No entries --
  Lspci:
   
  Lspci-vt:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.0-14-generic 
root=UUID=be8601a9-912c-475f-a790-c973864eb61f ro quiet splash vt.handoff=7
  ProcCmdline: /usr/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid 
--attach-to-session
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.0-14-generic 
root=UUID=be8601a9-912c-475f-a790-c973864eb61f ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x766b66f5aeab :   
mov0x40(%rdi),%rdi
   PC (0x766b66f5aeab) ok
   source "0x40(%rdi)" (0x0040) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: plymouth
  StacktraceTop:
   ply_input_device_get_keymap () from 
/lib/x86_64-linux-gnu/libply-splash-core.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/plymouth/renderers/frame-buffer.so
   ply_keymap_icon_new () from /lib/x86_64-linux-gnu/libply-splash-graphics.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/plymouth/two-step.so
   ?? () from /lib/x86_64-linux-gnu/libply-splash-core.so.5
  TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  Title: plymouthd crashed with SIGSEGV in ply_input_device_get_keymap()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  dmi.bios.date: 04/06/2022
  dmi.bios.release: 4.1
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.1
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.1
  dmi.chassis.asset.tag: 4565-7867-8475-0140-6079-1274-47
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.1
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.1:bd04/06/2022:br4.1:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.1:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.1:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.1:skuNone:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.1
  dmi.sys.vendor: Microsoft Corporation
  separator:

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


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


[Desktop-packages] [Bug 1949291]

2024-02-01 Thread regisperdreau
Problem is this could/should be personalised according language/country/local 
community or specific users. High potential to create a white elephant, 
impossible to maintain. "But there's no such word as can't" 
In the opposite point of view , I would propose to create another bar for local 
community marketing.

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

Title:
  LibreOffice has started displaying a donation nag

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

Bug description:
  I just opened up a spreadsheet (technically a CSV file, but who's
  counting), to discover LibreOffice displaying an eye-catching blue
  "Your donations support our worldwide community." banner just below
  the toolbars and about a toolbar and a half tall.

  This irritating nag is apparently supposed to display every 90 to 180
  days with no in-application means to disable it permanently, and
  there's apparently also a "Help us make LibreOffice even better!"
  banner that can appear too.

  According to this blog post...

  https://www.remembertheusers.com/2019/11/0580-libreoffice-nag-
  notices.html

  ...it is not responsive to configuration overrides within the user
  profile and the only apparent solution that doesn't require patching
  the source and rebuilding is to create a file containing the following
  markup in `$BASEDIR/share/registry`
  (`/usr/lib/libreoffice/share/registry` as installed by the Ubuntu
  package):

  
  http://www.w3.org/2001/XMLSchema; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xmlns:oor="http://openoffice.org/2001/registry;>

http://openoffice.org/2004/installation; oor:name="Setup" 
oor:package="org.openoffice">
  

  0


  0

  

  

  Regardless of how it's achieved, I think it's tasteless, irritating,
  and probably doesn't give a very good image to any office customers
  Ubuntu may have downstream for random employees to be receiving nag
  banners like that in IT-installed software.

  Please consider patching it out or otherwise ensuring it never
  triggers in distro-provided builds of LibreOffice.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice 1:6.4.7-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sun Oct 31 04:32:03 2021
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1949291]

2024-02-01 Thread Jeff Fortin Tam
With my marketing hat on:

I believe the solution is not to try to make infobars thinner or try to
space out the nags, but rather to combine those calls-to-action into one
infobar (that is deferred if needed, to not be shown at the same time as
the read-only document infobar).

Infobars (at least in GTK) can have multiple action buttons, and the
"Get involved" and "Donate" actions should be only one thing:
"Contribute", pointing to a unified web landing page that takes care
both of the "contribute by donating money" and "contribute by
volunteering" scenarios. No need to make those separate messages.

As such, if you're going to nag every user on every new release, then my
recommendation would be a single nag infobar like this:

> Welcome to LibreOffice XYZ! Discover what's new in this version, and
help us future versions!   [ Read the Release Notes] [ Contribute ] [X]

Clicking the buttons other than X would not close the infobar, that way
they can click both buttons.


If you show three nags one after another (even on separate startups) instead, 
then you're just frustration-conditioning the user to close/dismiss anything 
shown there, and your nags lose their effectiveness.

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

Title:
  LibreOffice has started displaying a donation nag

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

Bug description:
  I just opened up a spreadsheet (technically a CSV file, but who's
  counting), to discover LibreOffice displaying an eye-catching blue
  "Your donations support our worldwide community." banner just below
  the toolbars and about a toolbar and a half tall.

  This irritating nag is apparently supposed to display every 90 to 180
  days with no in-application means to disable it permanently, and
  there's apparently also a "Help us make LibreOffice even better!"
  banner that can appear too.

  According to this blog post...

  https://www.remembertheusers.com/2019/11/0580-libreoffice-nag-
  notices.html

  ...it is not responsive to configuration overrides within the user
  profile and the only apparent solution that doesn't require patching
  the source and rebuilding is to create a file containing the following
  markup in `$BASEDIR/share/registry`
  (`/usr/lib/libreoffice/share/registry` as installed by the Ubuntu
  package):

  
  http://www.w3.org/2001/XMLSchema; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xmlns:oor="http://openoffice.org/2001/registry;>

http://openoffice.org/2004/installation; oor:name="Setup" 
oor:package="org.openoffice">
  

  0


  0

  

  

  Regardless of how it's achieved, I think it's tasteless, irritating,
  and probably doesn't give a very good image to any office customers
  Ubuntu may have downstream for random employees to be receiving nag
  banners like that in IT-installed software.

  Please consider patching it out or otherwise ensuring it never
  triggers in distro-provided builds of LibreOffice.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice 1:6.4.7-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sun Oct 31 04:32:03 2021
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 2037604] Re: Backport packages for 22.04.4 HWE stack

2024-02-01 Thread Andreas Hasenack
** Tags removed: verification-done-jammy
** Tags added: verification-needed-jammy

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

Title:
  Backport packages for 22.04.4 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in rust-bindgen package in Ubuntu:
  Invalid
Status in rust-clang-sys package in Ubuntu:
  Invalid
Status in directx-headers source package in Jammy:
  Fix Committed
Status in mesa source package in Jammy:
  Fix Committed
Status in rust-bindgen source package in Jammy:
  Invalid
Status in rust-clang-sys source package in Jammy:
  Invalid

Bug description:
  [Impact]
  The graphics HWE stack from mantic needs to be backported for 22.04.4

  directx-headers
  - build-dep of the new Mesa

  mesa
  - new major release (23.2.x)
  - new HW support, Meteor Lake..

  [Test case]
  We want to cover at least 2-3 different, widely used and already previously 
supported GPU generations from both AMD and Intel which are supported by this 
release, as those are the ones that cover most bases; nouveau users tend to 
switch to the NVIDIA blob after installation. No need to test ancient GPU's 
supported by mesa-amber. And best to focus on the newer generations (~5y and 
newer) as the older ones are less likely to break at this point.
  - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*)
  - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 
(TGL/ADL/RKL/RPL/DG2)

  Install the new packages and run some tests:
  - check that the desktop is still using hw acceleration and hasn't fallen 
back to swrast/llvmpipe
  - run freely available benchmarks that torture the GPU (Unigine 
Heaven/Valley/Superposition)
  - run some games from Steam if possible

  and in each case check that there is no gfx corruption happening or
  worse.

  Note that upstream releases have already been tested for OpenGL and
  Vulkan conformance by their CI.

  [Where things could go wrong]
  This is a major update of Mesa, there could be regressions but we'll try to 
catch any with testing. And since it shares bugs with mantic, we'd already know 
if there are serious issues. We will backport the final 23.2.x at a later 
stage, the first backport is needed for enabling Intel Meteor Lake.

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


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


[Desktop-packages] [Bug 2051945] Re: Gnome-control-center: many entries missing in 'Notification' section

2024-02-01 Thread Sebastien Bacher
Thank you for your bug report, that's a wanted change upstream to stop
listing system components, see https://gitlab.gnome.org/GNOME/gnome-
control-center/-/merge_requests/1592

If applications are missing it probably means their .desktop Categories
need to be updated

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

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  Gnome-control-center: many entries missing in 'Notification' section

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

Bug description:
  In the section 'Notifications' many entries are missing.
  see attached image: on left the screenshot from Noble, on right from Mantic.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-control-center 1:46~alpha-2ubuntu2
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 15:12:21 2024
  InstallationDate: Installed on 2024-02-01 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240201)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 2051945] [NEW] Gnome-control-center: many entries missing in 'Notification' section

2024-02-01 Thread corrado venturini
Public bug reported:

In the section 'Notifications' many entries are missing.
see attached image: on left the screenshot from Noble, on right from Mantic.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-control-center 1:46~alpha-2ubuntu2
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb  1 15:12:21 2024
InstallationDate: Installed on 2024-02-01 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240201)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Attachment added: "Screenshot from 2024-02-01 15-09-53.png"
   
https://bugs.launchpad.net/bugs/2051945/+attachment/5744114/+files/Screenshot%20from%202024-02-01%2015-09-53.png

** Summary changed:

- Many entries missing in 'Notification' section
+ Gnome-control-center: many entries missing in 'Notification' section

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

Title:
  Gnome-control-center: many entries missing in 'Notification' section

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

Bug description:
  In the section 'Notifications' many entries are missing.
  see attached image: on left the screenshot from Noble, on right from Mantic.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-control-center 1:46~alpha-2ubuntu2
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 15:12:21 2024
  InstallationDate: Installed on 2024-02-01 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240201)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 2037604] Re: Backport packages for 22.04.4 HWE stack

2024-02-01 Thread Andreas Hasenack
Technically, the verification from prior comments was performed on
23.2.1-1ubuntu3.1~22.04.1, not 23.2.1-1ubuntu3.1~22.04.2. I think they
need to be done on the mesa package that is in proposed now, which is
.2.

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

Title:
  Backport packages for 22.04.4 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in rust-bindgen package in Ubuntu:
  Invalid
Status in rust-clang-sys package in Ubuntu:
  Invalid
Status in directx-headers source package in Jammy:
  Fix Committed
Status in mesa source package in Jammy:
  Fix Committed
Status in rust-bindgen source package in Jammy:
  Invalid
Status in rust-clang-sys source package in Jammy:
  Invalid

Bug description:
  [Impact]
  The graphics HWE stack from mantic needs to be backported for 22.04.4

  directx-headers
  - build-dep of the new Mesa

  mesa
  - new major release (23.2.x)
  - new HW support, Meteor Lake..

  [Test case]
  We want to cover at least 2-3 different, widely used and already previously 
supported GPU generations from both AMD and Intel which are supported by this 
release, as those are the ones that cover most bases; nouveau users tend to 
switch to the NVIDIA blob after installation. No need to test ancient GPU's 
supported by mesa-amber. And best to focus on the newer generations (~5y and 
newer) as the older ones are less likely to break at this point.
  - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*)
  - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 
(TGL/ADL/RKL/RPL/DG2)

  Install the new packages and run some tests:
  - check that the desktop is still using hw acceleration and hasn't fallen 
back to swrast/llvmpipe
  - run freely available benchmarks that torture the GPU (Unigine 
Heaven/Valley/Superposition)
  - run some games from Steam if possible

  and in each case check that there is no gfx corruption happening or
  worse.

  Note that upstream releases have already been tested for OpenGL and
  Vulkan conformance by their CI.

  [Where things could go wrong]
  This is a major update of Mesa, there could be regressions but we'll try to 
catch any with testing. And since it shares bugs with mantic, we'd already know 
if there are serious issues. We will backport the final 23.2.x at a later 
stage, the first backport is needed for enabling Intel Meteor Lake.

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


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


[Desktop-packages] [Bug 2018439] Re: Apparmor crashes GPU acceleration

2024-02-01 Thread Georgia Garcia
Hi Daniel!
Thanks for testing and making sure. As you were able to figure out, the 
AppArmor parser accepts both include and #includes, although we are deprecating 
the latter. 

Since the AppArmor policy is distributed by the Mozilla Team's firefox,
they need to add this permission to their AppArmor profile in the
package.

** Changed in: apparmor (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Apparmor crashes GPU acceleration

Status in apparmor package in Ubuntu:
  Invalid
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Apparmor crashes GPU acceleration

  Firefox GPU acceleration started crashing after updating from Ubuntu
  22.10 to 23.04.

  $ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.04
  Release:23.04

  $ apt-cache policy firefox
  firefox:
Installed: 113.0+build1-0ubuntu0.23.04.1~mt1
Candidate: 113.0+build1-0ubuntu0.23.04.1~mt1
Version table:
   1:1snap1-0ubuntu3 500
  500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu lunar/main 
amd64 Packages
   *** 113.0+build1-0ubuntu0.23.04.1~mt1 999
  500 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
lunar/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy libglx-mesa0 
  libglx-mesa0:
Installed: 23.0.3~kisak1~k
Candidate: 23.0.3~kisak1~k
Version table:
   *** 23.0.3~kisak1~k 500
  500 https://ppa.launchpadcontent.net/kisak/kisak-mesa/ubuntu 
kinetic/main amd64 Packages
  100 /var/lib/dpkg/status
   23.0.2-1ubuntu1 500
  500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu lunar/main 
amd64 Packages

  $ apt-cache policy apparmor
  apparmor:
Installed: 3.0.8-1ubuntu2
Candidate: 3.0.8-1ubuntu2
Version table:
   *** 3.0.8-1ubuntu2 500
  500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu lunar/main 
amd64 Packages
  100 /var/lib/dpkg/status

  # Expected behavior

  Firefox should not crash in WebGL aquarium and continue to work
  properly like on 22.10. It should successfully use my GPU to make
  scrolling smooths and save battery when watching videos.

  # Actual behavior

  1. Startup takes a second or two longer than usual
  2. Typing in the address bar is slow
  3. Scrolling takes 400% CPU usage
  4. Scrolling stutters
  5. VAAPI on https://www.w3schools.com/html/html5_video.asp is no longer used 
as shown in intel_gpu_top
  6. Fans start spinning and battery goes down fast
  7. glxtest failures had to be manually deleted in about:config
  8. Only a few fish in WebGL aquarium 
(https://webglsamples.org/aquarium/aquarium.html) load before Firefox 
force-closes with the message: "Mozilla Crash Reporter Firefox had a problem 
and crashed. Unfortunately, the crash reporter is unable to submit a crash 
report. Details: The application did not leave a crash dump file. Close"
  9. The following lines are relevant in dmesg after clearing it:

  [22157.695580] kauditd_printk_skb: 6 callbacks suppressed
  [22157.695582] audit: type=1400 audit(1683153440.994:2583): apparmor="DENIED" 
operation="capable" class="cap" profile="firefox" pid=15898 comm="firefox" 
capability=21  capname="sys_admin"
  [22157.739641] audit: type=1400 audit(1683153441.038:2584): apparmor="DENIED" 
operation="open" class="file" profile="firefox" 
name="/sys/devices/pci:00/:00:02.0/revision" pid=15901 comm="firefox" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [22157.739647] audit: type=1400 audit(1683153441.038:2585): apparmor="DENIED" 
operation="open" class="file" profile="firefox" 
name="/sys/devices/pci:00/:00:02.0/config" pid=15901 comm="firefox" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [22157.739719] audit: type=1400 audit(1683153441.038:2586): apparmor="DENIED" 
operation="open" class="file" profile="firefox" 
name="/sys/devices/pci:00/:00:02.0/revision" pid=15901 comm="firefox" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [22157.739729] audit: type=1400 audit(1683153441.038:2587): apparmor="DENIED" 
operation="open" class="file" profile="firefox" 
name="/sys/devices/pci:00/:00:02.0/config" pid=15901 comm="firefox" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [22157.769407] audit: type=1400 audit(1683153441.070:2588): apparmor="DENIED" 
operation="open" class="file" profile="firefox" 
name="/proc/15898/oom_score_adj" pid=15898 comm="firefox" requested_mask="w" 
denied_mask="w" fsuid=1000 ouid=1000
  [22157.773042] audit: type=1400 audit(1683153441.074:2589): apparmor="DENIED" 
operation="file_mmap" class="file" profile="firefox//lsb_release" 
name="/usr/bin/dash" pid=15934 comm="lsb_release" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=0
  [22157.974718] audit: type=1400 audit(1683153441.274:2590): apparmor="DENIED" 

[Desktop-packages] [Bug 1370013] Re: backport request for precise

2024-02-01 Thread Jeremy Bícha
Ubuntu 12.04 LTS "Precise" has reached end of life.

** Changed in: docbook-xsl (Ubuntu)
   Status: In Progress => Won't Fix

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

Title:
  backport request for precise

Status in docbook-xsl package in Ubuntu:
  Won't Fix

Bug description:
  I would like to request a backport of the 1.78.1+dfsg-1 Version to
  precise.

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


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


[Desktop-packages] [Bug 1586678] Re: Should have better support for GNOME Online Accounts

2024-02-01 Thread Bug Watch Updater
** Changed in: thunderbird
   Status: New => Confirmed

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

Title:
  Should have better support for GNOME Online Accounts

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

Bug description:
  I think that it would be really good if Thunderbird had proper support
  for GNOME Online Accounts.

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


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


[Desktop-packages] [Bug 1586678]

2024-02-01 Thread Thatoo
(In reply to Wayne Mery (:wsmwk) from comment #10)
> The entire staff focus for the last 12 months has been Supernvova version 115 
> (which brings improvements for **all** platforms) and will continue to be so 
> through September.  This bug will be evaluated after September, if no 
> statement has been posted by then.

Hello,
Any news on the evaluation that happen in last September?

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

Title:
  Should have better support for GNOME Online Accounts

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

Bug description:
  I think that it would be really good if Thunderbird had proper support
  for GNOME Online Accounts.

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


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


[Desktop-packages] [Bug 1586678]

2024-02-01 Thread Vseerror-i
Thanks for asking.

gnome accounts is a feature that the core team will not develop, but
we’re happy to take patches from contributors.

More generally, better OS integration in general is something we will
review around the end of the year but we need to scope it and be
methodical on what we want to support.

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

Title:
  Should have better support for GNOME Online Accounts

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

Bug description:
  I think that it would be really good if Thunderbird had proper support
  for GNOME Online Accounts.

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


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


[Desktop-packages] [Bug 1864215] Re: Please add webp loader to gdk-pixbuf

2024-02-01 Thread Mantas Kriaučiūnas
webp-pixbuf-loader package is added to ppa:baltix and to ubuntu-
defaults-baltix metapackage recommends, see commit:

https://salsa.debian.org/baltix-team/baltix-defaults-
metapackages/ubuntu-defaults-
baltix/-/commit/45d2bdff366a8125a079d3ec10a274df22d00d36#5c28d8ddb90b37ffdfa1108948fbd9ff73f845a1

** Changed in: webp-pixbuf-loader (Baltix)
   Status: In Progress => Fix Released

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

Title:
  Please add webp loader to gdk-pixbuf

Status in gdk-pixbuf:
  Fix Released
Status in webp-pixbuf-loader package in Ubuntu:
  Fix Released
Status in gdk-pixbuf package in Baltix:
  Fix Committed
Status in webp-pixbuf-loader package in Baltix:
  Fix Released
Status in webp-pixbuf-loader package in Debian:
  Fix Released

Bug description:
  Attempting to load a webp image -- for instance, 

https://images.theweek.com/sites/default/files/styles/tw_image_9_4/public/FKK78W.jpg.webp
  or

https://cdn.vox-cdn.com/thumbor/2YtWB5zH7sPycyc0FYv3JSB6SFw=/60x0:1140x720/920x613/filters:focal(60x0:1140x720):format(webp)/cdn.vox-cdn.com/uploads/chorus_image/image/49663815/timburton.0.0.jpg
  -- in a gdk-pixbuf app results in a "Couldn’t recognize the image file 
format" error.

  Bug 1318327 covers this issue in eye of gnome, and bug 1407644 in
  libwebp, but isn't this really a gdk-pixbuf issue? If it really does
  belong to libwebp, my apologies, please dup this bug to 1407644 (I'm
  confident it doesn't belong to eog since I don't use that program; I
  have other programs that use libgdk-pixbuf).

  You can probably use eog to test this, or run
  /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders | grep -i 
webp
  (I assume the loader would mention webp if there was a loader for it).

  I have these packages installed in addition to libgdk-pixbuf2.0-0:
  libwebp-dev libwebp6 libwebpdemux2 libwebpmux3 webp. file recognizes
  the format:

  $ file /tmp/FKK78W.jpg.webp
  /tmp/FKK78W.jpg.webp: RIFF (little-endian) data, Web/P image, VP8 encoding, 
1200x533, Scaling: [none]x[none], YUV color, decoders should clamp

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-1build1
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  Date: Fri Feb 21 08:48:36 2020
  InstallationDate: Installed on 2019-10-10 (133 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1864215/+subscriptions


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


[Desktop-packages] [Bug 1879330] Re: Copy of .xcf thumbnails does not work

2024-02-01 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/1879330

** Tags added: iso-testing

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

Title:
  Copy of .xcf thumbnails does not work

Status in nautilus package in Ubuntu:
  New

Bug description:
  I have a folder with an .xcf (GIMP) image, the image has a correct thumbnail 
in the nautilus window. When I copy (cut+paste) the image in the same folder 
the thumbnail is empty.
  If I copy the image from a different folder the thumbnail shows the logo of 
GIMP.
  In both cases the thumbnail is WRONG.
  Doing the same with a .jpg or .png image the thumbnails are correct. 
  The same problem happens in Ubuntu 20.04 and 20.10 
  See the attached image

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: nautilus 1:3.37.1.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu34
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 15:21:24 2020
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'initial-size' b'(653, 418)'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
  InstallationDate: Installed on 2020-05-11 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200511)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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


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


[Desktop-packages] [Bug 2050743] Re: plymouthd crashed with SIGSEGV in ply_input_device_get_keymap()

2024-02-01 Thread Bug Watch Updater
** Changed in: plymouth
   Status: New => Fix Released

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

Title:
  plymouthd crashed with SIGSEGV in ply_input_device_get_keymap()

Status in Plymouth:
  Fix Released
Status in plymouth package in Ubuntu:
  Fix Committed

Bug description:
  Unsure

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: plymouth 23.360.11-0ubuntu2
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Mon Jan 22 18:15:26 2024
  DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
  ExecutablePath: /usr/sbin/plymouthd
  InstallationDate: Installed on 2024-01-22 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240122)
  JournalErrors: -- No entries --
  Lspci:
   
  Lspci-vt:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.0-14-generic 
root=UUID=be8601a9-912c-475f-a790-c973864eb61f ro quiet splash vt.handoff=7
  ProcCmdline: /usr/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid 
--attach-to-session
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.0-14-generic 
root=UUID=be8601a9-912c-475f-a790-c973864eb61f ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x766b66f5aeab :   
mov0x40(%rdi),%rdi
   PC (0x766b66f5aeab) ok
   source "0x40(%rdi)" (0x0040) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: plymouth
  StacktraceTop:
   ply_input_device_get_keymap () from 
/lib/x86_64-linux-gnu/libply-splash-core.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/plymouth/renderers/frame-buffer.so
   ply_keymap_icon_new () from /lib/x86_64-linux-gnu/libply-splash-graphics.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/plymouth/two-step.so
   ?? () from /lib/x86_64-linux-gnu/libply-splash-core.so.5
  TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  Title: plymouthd crashed with SIGSEGV in ply_input_device_get_keymap()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  dmi.bios.date: 04/06/2022
  dmi.bios.release: 4.1
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.1
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.1
  dmi.chassis.asset.tag: 4565-7867-8475-0140-6079-1274-47
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.1
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.1:bd04/06/2022:br4.1:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.1:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.1:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.1:skuNone:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.1
  dmi.sys.vendor: Microsoft Corporation
  separator:

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


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