[Desktop-packages] [Bug 2016400] Re: System program problem detected

2023-04-15 Thread Apport retracing service
*** This bug is a duplicate of bug 2012287 ***
https://bugs.launchpad.net/bugs/2012287

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #2012287, so 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.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/2016400/+attachment/5664354/+files/CoreDump.gz

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/2016400/+attachment/5664356/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/2016400/+attachment/5664357/+files/ProcStatus.txt

** This bug has been marked a duplicate of bug 2012287
   gjs-console crashed with signal 6 in g_assertion_message("assertion failed: 
(!priv->is_realized)") from g_assertion_message_expr() from 
gsk_renderer_dispose() from gsk_renderer_dispose() from g_object_unref()

** Information type changed from Private Security to Public Security

** Tags removed: need-amd64-retrace

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

Title:
  System program problem detected

Status in gjs package in Ubuntu:
  New

Bug description:
  System program problem detected always pop-up

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: gjs 1.75.90-1
  Uname: Linux 6.2.0-18-generic x86_64
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 16 04:22:13 2023
  ExecutablePath: /usr/bin/gjs-console
  ExecutableTimestamp: 1678210639
  ProcCmdline: /usr/bin/gjs-console /usr/bin/gnome-characters 
--gapplication-service
  ProcCwd: /home/ubuntu
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: gjs
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users

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


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


[Desktop-packages] [Bug 2012100] Re: gnome-shell crashed with SIGSEGV in meta_wayland_compositor_get_context() from display_from_offer() from data_offer_receive() from ffi_call_unix64()

2023-04-15 Thread Bug Watch Updater
** Changed in: mutter
   Status: New => Fix Released

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

Title:
  gnome-shell crashed with SIGSEGV in
  meta_wayland_compositor_get_context() from display_from_offer() from
  data_offer_receive() from ffi_call_unix64()

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/d525586b43c9aeae86d5c9c7bb28ba925afb

  I have this error when I'm connecting to nym-connect (nymtech.net)

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44~beta-1ubuntu1
  Uname: Linux 5.19.0-21-generic x86_64
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 17 18:10:09 2023
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1677216555
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/judemont
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 11
  SourcePackage: gnome-shell
  UserGroups: adm cdrom dip lpadmin plugdev sudo users

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


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


[Desktop-packages] [Bug 915080]

2023-04-15 Thread Qa-admin-q
Dear Vadim Rutkovsky,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time, it's possible that the bug has
been fixed, or the details of the problem have changed. We'd really
appreciate your help in getting confirmation that the bug is still
present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of
LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information 
from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to 
RESOLVED-WORKSFORME and leave a comment that includes the information from Help 
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular 
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a 
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your 
bug pertains to a feature added after 3.3) from 
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: 
https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

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

Title:
  [Upstream] Column formatting not honored saving to .doc

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

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 11.10
  Release:  11.10

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:3.4.4-0ubuntu1
Candidate: 1:3.4.4-0ubuntu1
Version table:
   *** 1:3.4.4-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.4.3-3ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages

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

  cd ~/Desktop && wget -c
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/915080/+attachment/2685315/+files/Blocco%20schizzi%20botanico.doc
  -O example.doc && lowriter -nologo example.doc

  Click Format -> Sections... -> highlight Section1 -> click button
  Remove -> highlight Section3 -> click button Remove -> button OK ->
  Format -> Columns... -> change combobox Columns to 2 -> button OK ->
  Save, close, reopen and the column formatting remains as in the
  screenshot
  
https://launchpadlibrarian.net/91366200/Schermata-L%27arte%20del%20disegno%20botanico.doc2%20-%20LibreOffice%20Writer.png
  .

  4) What happens instead is the column formatting changes back to the
  way it was before making the above changes. A screenshot of this
  
https://launchpadlibrarian.net/91366199/Schermata-L%27arte%20del%20disegno%20botanico.doc1%20-%20LibreOffice%20Writer.png
  .

  WORKAROUND: Save as .odt as the column formatting is preserved.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: libreoffice-core 1:3.3.4-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-13.53-generic 2.6.38.8
  Uname: Linux 2.6.38-13-generic i686
  Architecture: i386
  Date: Wed Jan 11 23:50:02 2012
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=it_IT:en
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to natty on 2011-10-17 (86 days ago)

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


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


[Desktop-packages] [Bug 2016395] [NEW] control-center sound using audio devices without consent

2023-04-15 Thread Ken Anderson
Public bug reported:

(Reporting for blind user ken)

gnome-control-center sound is forcing the selection of an input device
you do not have consent to use.The only option listed is CM108
microphone.   None is not an option; it needs to be.  Motherboard audio
is also missing.

Just because an audio device exists does not mean you have consent to
use it for desktop audio purposes.  NONE must always be an option.
Audio output device also lacks none, though in this case it isn't
causing an issue because there is another audio output device.  However,
using this audio output device without permission is a federal crime.
Unauthorized radio transmissions are not allowed.

Reproduce:
* 
* Plug in  digirig mobile which contains a USB hub, CM108 audio, and CP210 
serial and ham radio rig interface circuitry.   
* Enable pipewire as described here: 
https://gist.github.com/the-spyke/2de98b22ff4f978ebf0650c90e82027e?permalink_comment_id=4116017
* Open control-center sound.
* Try to set output device to none.

Ubuntu 22.04.2 LTS Linux ken-OptiPlex-760 5.15.0-69-generic #76-Ubuntu
SMP Fri Mar 17 17:19:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux


This is by no means the only audio device that is not yours to use 
indiscriminately.  There are many uses for audio devices that are not for user 
interaction.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6
ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87
Uname: Linux 5.15.0-69-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 15 18:17:39 2023
InstallationDate: Installed on 2018-05-05 (1806 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to jammy on 2022-12-05 (131 days ago)

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


** Tags: amd64 apport-bug jammy

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

Title:
  control-center sound using audio devices without consent

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

Bug description:
  (Reporting for blind user ken)

  gnome-control-center sound is forcing the selection of an input device
  you do not have consent to use.The only option listed is CM108
  microphone.   None is not an option; it needs to be.  Motherboard
  audio is also missing.

  Just because an audio device exists does not mean you have consent to
  use it for desktop audio purposes.  NONE must always be an option.
  Audio output device also lacks none, though in this case it isn't
  causing an issue because there is another audio output device.
  However, using this audio output device without permission is a
  federal crime.   Unauthorized radio transmissions are not allowed.

  Reproduce:
  * 
  * Plug in  digirig mobile which contains a USB hub, CM108 audio, and CP210 
serial and ham radio rig interface circuitry.   
  * Enable pipewire as described here: 
https://gist.github.com/the-spyke/2de98b22ff4f978ebf0650c90e82027e?permalink_comment_id=4116017
  * Open control-center sound.
  * Try to set output device to none.

  Ubuntu 22.04.2 LTS Linux ken-OptiPlex-760 5.15.0-69-generic #76-Ubuntu
  SMP Fri Mar 17 17:19:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  
  This is by no means the only audio device that is not yours to use 
indiscriminately.  There are many uses for audio devices that are not for user 
interaction.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6
  ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87
  Uname: Linux 5.15.0-69-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 15 18:17:39 2023
  InstallationDate: Installed on 2018-05-05 (1806 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to jammy on 2022-12-05 (131 days ago)

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


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


[Desktop-packages] [Bug 2014986] Re: gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial xxxx error_code 8 request_code 131 (XInputExtension) m

2023-04-15 Thread Launchpad Bug Tracker
This bug was fixed in the package mutter - 44.0-2ubuntu4

---
mutter (44.0-2ubuntu4) lunar; urgency=medium

  [ Daniel van Vugt ]
  * Add proposed patch to treat XIChangeProperty errors as warnings,
fixes crash on login or resume from suspend with Nvidia graphics drivers
(LP: #2014986)

 -- Jeremy Bícha   Fri, 14 Apr 2023 14:32:30 -0400

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

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

Title:
  gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid
  parameter attributes)'. (Details: serial  error_code 8
  request_code 131 (XInputExtension) minor_code 57)]

Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/53564230b4b22425c80ba6615ecceab429c477e4

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Apr  2 01:49:43 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2023-03-30 (2 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 44.0-2ubuntu2
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /lib/x86_64-linux-gnu/libX11.so.6
   g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: Upgraded to lunar on 2023-04-01 (0 days ago)
  UserGroups: N/A
  separator:

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


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


[Desktop-packages] [Bug 2016387] [NEW] After updating to 23.04, none of the integrated shell extensions work

2023-04-15 Thread Nicolás Abel Carbone
Public bug reported:

After updating to 23.04, none of the integrated shell extensions work.
This includes the dock, desktop icons and appindicators, for example.

Also, and I think related to this, the Desktop tab on the settings app
doesn't work either.

See attached screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell-extension-ubuntu-dock 79ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 15 12:38:49 2023
InstallationDate: Installed on 2022-02-02 (436 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: Upgraded to lunar on 2023-04-15 (0 days ago)

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


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

** Attachment added: "Captura desde 2023-04-15 12-40-13.png"
   
https://bugs.launchpad.net/bugs/2016387/+attachment/5664246/+files/Captura%20desde%202023-04-15%2012-40-13.png

** Description changed:

- After updating to 23.04, none of the integrated shell extensions work. 
+ After updating to 23.04, none of the integrated shell extensions work.
  This includes the dock and desktop icons, for example.
  
- Also, and I think related to this, the Appearance on the settings
+ Also, and I think related to this, the Desktop tab on the settings app
  doesn't work either.
  
  See attached screenshot.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell-extension-ubuntu-dock 79ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 15 12:38:49 2023
  InstallationDate: Installed on 2022-02-02 (436 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to lunar on 2023-04-15 (0 days ago)

** Description changed:

  After updating to 23.04, none of the integrated shell extensions work.
- This includes the dock and desktop icons, for example.
+ This includes the dock, desktop icons and appindicators, for example.
  
  Also, and I think related to this, the Desktop tab on the settings app
  doesn't work either.
  
  See attached screenshot.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell-extension-ubuntu-dock 79ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 15 12:38:49 2023
  InstallationDate: Installed on 2022-02-02 (436 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to lunar on 2023-04-15 (0 days ago)

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

Title:
  After updating to 23.04, none of the integrated shell extensions work

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

Bug description:
  After updating to 23.04, none of the integrated shell extensions work.
  This includes the dock, desktop icons and appindicators, for example.

  Also, and I think related to this, the Desktop tab on the settings app
  doesn't work either.

  See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell-extension-ubuntu-dock 79ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 15 12:38:49 2023
  InstallationDate: Installed on 2022-02-02 (436 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to lunar on 2023-04-15 (0 days ago)

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


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


[Desktop-packages] [Bug 2016386] [NEW] message erreur non conforme

2023-04-15 Thread Roland Lemp
Public bug reported:

Le clic en haut a droite pour enregistrer fonctionne parfaitemant, mais
provoque toujours un message d'erreur "impossible d'enregistrer"...en
fait le scan est parfaitement enregistre a l'emplacement voulu (par
exemple le Bureau)

Pour quitter simple-scan on est oblige de cliquer sur "ne pas
enregistrer".

Ce message erratique est apparu apres mise a jour vers ubuntu 22.04.
Le bug persiste en desinstallant simple-scan et en le reinstallant avec snap 
(Document Scanner).

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: simple-scan 42.0-1
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-38-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 15 17:26:49 2023
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
 Bus 001 Device 002: ID 046d:c505 Logitech, Inc. Cordless Mouse+Keyboard 
Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. PN41
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic 
root=UUID=f815be65-dc90-4f87-8b1d-41835dc9b32b ro quiet splash vt.handoff=7
SourcePackage: simple-scan
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/02/2021
dmi.bios.release: 5.19
dmi.bios.vendor: ASUSTeK COMPUTER INC.
dmi.bios.version: 0802
dmi.board.asset.tag: Default string
dmi.board.name: PN41
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: ASSET-1234567890
dmi.chassis.type: 35
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnASUSTeKCOMPUTERINC.:bvr0802:bd08/02/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnPN41:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnPN41:rvrTobefilledbyO.E.M.:cvnChassisManufacture:ct35:cvrChassisVersion:sku:
dmi.product.family: Vivo PC
dmi.product.name: PN41
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Affects: simple-scan (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  message erreur non conforme

Status in simple-scan package in Ubuntu:
  New

Bug description:
  Le clic en haut a droite pour enregistrer fonctionne parfaitemant,
  mais provoque toujours un message d'erreur "impossible
  d'enregistrer"...en fait le scan est parfaitement enregistre a
  l'emplacement voulu (par exemple le Bureau)

  Pour quitter simple-scan on est oblige de cliquer sur "ne pas
  enregistrer".

  Ce message erratique est apparu apres mise a jour vers ubuntu 22.04.
  Le bug persiste en desinstallant simple-scan et en le reinstallant avec snap 
(Document Scanner).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: simple-scan 42.0-1
  ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 15 17:26:49 2023
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 002: ID 046d:c505 Logitech, Inc. Cordless Mouse+Keyboard 
Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. PN41
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic 
root=UUID=f815be65-dc90-4f87-8b1d-41835dc9b32b ro quiet splash vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: ASUSTeK COMPUTER INC.
  dmi.bios.version: 0802
  dmi.board.asset.tag: Default string
  dmi.board.name: PN41
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: ASSET-1234567890
  dmi.chassis.type: 35
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnASUSTeKCOMPUTERINC.:bvr0802:bd08/02/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnPN41:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnPN41:rvrTobefilledbyO.E.M.:cvnChassisManufacture:ct35:cvrChassisVersion:sku:
  dmi.product.family: Vivo PC
  dmi.product.name: PN41
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Desktop-packages] [Bug 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_obje

2023-04-15 Thread Bug Watch Updater
** Changed in: accountsservice
   Status: New => Fix Released

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

Title:
  indicator-messages-service crashed with SIGSEGV in
  g_type_check_instance() from g_signal_handlers_disconnect_matched()
  from act_user_manager_finalize() from g_object_unref() from
  im_accounts_service_dispose()

Status in accountsservice:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Released
Status in indicator-messages package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
indicator-messages.  This problem was most recently seen with package version 
13.10.1+18.10.20180918-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 
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/accountsservice/+bug/2015962/+subscriptions


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


[Desktop-packages] [Bug 2016045] Re: Screen sometimes freezes [modeset(0): Present-flip: queue async flip during flip on CRTC 0 failed: Invalid argument]

2023-04-15 Thread Spiridon
Related issue fix ( MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 on /etc/environment
) did not fix the issue.

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

Title:
  Screen sometimes freezes [modeset(0): Present-flip: queue async flip
  during flip on CRTC 0 failed: Invalid argument]

Status in xorg-server package in Ubuntu:
  New

Bug description:
  1/3 times I tab in / out of a app/game, that is running using the nvidia 
dedicated gpu, the screen freezes forcing me to restart my laptop. The cursor 
is still "usable" and reboot using SysRq REISUB is possible.
  This is not tied only to steam games, other apps/games like minecraft also 
cause this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.105.17  Tue Mar 28 
18:02:59 UTC 2023
   GCC version:  gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04)
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 13 00:58:23 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: nvidia/525.105.17, 5.19.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] 
[103c:84c1]
 Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:84c1]
  InstallationDate: Installed on 2023-02-06 (65 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0408:5300 Quanta Computer, Inc. HP Wide Vision HD 
Camera
   Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek 
Bluetooth 4.2 Adapter
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Laptop 15-cs2xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic 
root=UUID=bd5e3449-4d4f-4ebd-afef-1e4da7b9ec69 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2020
  dmi.bios.release: 15.23
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.23
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 84C1
  dmi.board.vendor: HP
  dmi.board.version: 15.32
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 15.32
  dmi.modalias: 
dmi:bvnInsyde:bvrF.23:bd12/25/2020:br15.23:efr15.32:svnHP:pnHPPavilionLaptop15-cs2xxx:pvrType1ProductConfigId:rvnHP:rn84C1:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku7EF01EA#AB7:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cs2xxx
  dmi.product.sku: 7EF01EA#AB7
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Desktop-packages] [Bug 2016045] Re: Screen sometimes freezes [modeset(0): Present-flip: queue async flip during flip on CRTC 0 failed: Invalid argument]

2023-04-15 Thread Spiridon
Hello, sorry for the wait. Added the kernel parameter and reproduced the
bug. Here is the new log ( full log was over 75mb so I tailed the last
1 lines ). If older lines are needed, I can provide more.

** Attachment added: "pd-tail.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2016045/+attachment/5664158/+files/pd-tail.txt

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

Title:
  Screen sometimes freezes [modeset(0): Present-flip: queue async flip
  during flip on CRTC 0 failed: Invalid argument]

Status in xorg-server package in Ubuntu:
  New

Bug description:
  1/3 times I tab in / out of a app/game, that is running using the nvidia 
dedicated gpu, the screen freezes forcing me to restart my laptop. The cursor 
is still "usable" and reboot using SysRq REISUB is possible.
  This is not tied only to steam games, other apps/games like minecraft also 
cause this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.105.17  Tue Mar 28 
18:02:59 UTC 2023
   GCC version:  gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04)
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 13 00:58:23 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: nvidia/525.105.17, 5.19.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] 
[103c:84c1]
 Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:84c1]
  InstallationDate: Installed on 2023-02-06 (65 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0408:5300 Quanta Computer, Inc. HP Wide Vision HD 
Camera
   Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek 
Bluetooth 4.2 Adapter
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Laptop 15-cs2xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic 
root=UUID=bd5e3449-4d4f-4ebd-afef-1e4da7b9ec69 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2020
  dmi.bios.release: 15.23
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.23
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 84C1
  dmi.board.vendor: HP
  dmi.board.version: 15.32
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 15.32
  dmi.modalias: 
dmi:bvnInsyde:bvrF.23:bd12/25/2020:br15.23:efr15.32:svnHP:pnHPPavilionLaptop15-cs2xxx:pvrType1ProductConfigId:rvnHP:rn84C1:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku7EF01EA#AB7:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cs2xxx
  dmi.product.sku: 7EF01EA#AB7
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


-- 
Mailing list: https://launchpad.net/~desktop-package

[Desktop-packages] [Bug 2016364] [NEW] The GDM3 login welcome message is not showing after editing "/etc/gdm3/greeter.dconf-defaults" and setting the option banner-message-enable to true.

2023-04-15 Thread maruf
Public bug reported:

GDM3 version: GDM 42.0
OS: Ubuntu 22.04.2 LTS
Kernel: 5.15.0-69-generic
Windowing System: X11

The 'disable-user-list' option is not working even though I have enabled
'disable-user-list=true' in the '/etc/gdm3/greeter.dconf-defaults' file.

I have also reinstalled 'ubuntu-desktop', but it is still not working."

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

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

Title:
  The GDM3 login welcome message is not showing after editing
  "/etc/gdm3/greeter.dconf-defaults" and setting the option banner-
  message-enable to true.

Status in gdm3 package in Ubuntu:
  New

Bug description:
  GDM3 version: GDM 42.0
  OS: Ubuntu 22.04.2 LTS
  Kernel: 5.15.0-69-generic
  Windowing System: X11

  The 'disable-user-list' option is not working even though I have
  enabled 'disable-user-list=true' in the '/etc/gdm3/greeter.dconf-
  defaults' file.

  I have also reinstalled 'ubuntu-desktop', but it is still not
  working."

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


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


[Desktop-packages] [Bug 1987979]

2023-04-15 Thread Nathan Teodosio
For your information, if trying this in a snap, make sure to supply a
correct XDG_RUNTIME_DIR as that seems to be modified by snapcraft or
snapd.

Namely, in a `snap run --shell {snap-name-with-spd}`, this fails:

```
$ spd-say bye
Failed to connect to Speech Dispatcher:
Error: Can't connect to unix socket 
/run/user/1000/snap.geheim/speech-dispatcher/speechd.sock: No such file or 
directory. Autospawn: Autospawn failed. Spawn error 8: Failed to execute child 
process “/usr/bin/speech-dispatcher” (No such file or directory)
```

but this works:

```
$ XDG_RUNTIME_DIR=/run/user/1000 spd-say bye
```

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

Title:
  [snap] Firefox Narrator stopped working after upgrade from 20.04 to
  22.04

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  In Progress

Bug description:
  I just noticed that the narrator feature, which reads articles out
  load with TTS in Firefox reading view stopped working after upgrading
  to 22.04. Another user reported the same problem on ask Ubuntu:

  https://askubuntu.com/questions/1418391/no-tts-voices-on-
  firefox-v102-0-after-upgrading-to-ubuntu-22-04-lts

  Also, if you have no clue what this is about:
  https://askubuntu.com/questions/953509/how-can-i-change-the-voice-
  used-by-firefox-reader-view-narrator-in-ubuntu

  ---

  1)

  $   lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  2) Firefox is a snap now, but I guess for the feature to work it needs
  to detect TTS which is packaged as deb.

  $  snap list firefox
  Name Version  Rev   Tracking   Publisher  Notes
  firefox  104.0-3  1749  latest/stable  mozilla✓   -

  $  apt-cache policy espeak speech-dispatcher-espeak-ng firefox
  espeak:
    Installed: 1.48.15+dfsg-3
    Candidate: 1.48.15+dfsg-3
    Version table:
   *** 1.48.15+dfsg-3 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status
  speech-dispatcher-espeak-ng:
    Installed: 0.11.1-1ubuntu1
    Candidate: 0.11.1-1ubuntu1
    Version table:
   *** 0.11.1-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.11.1-1 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  firefox:
    Installed: (none)
    Candidate: 1:1snap1-0ubuntu2
    Version table:
   1:1snap1-0ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  3) open a website, enter reader mode, click the icon with sound waves
  and hear the text being read with TTS

  4) the icon is missing

  ---

  Edit: I tested Firefox Flatpak and it is also affected, my best guess
  is that Firefox is not at fault.

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


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


[Desktop-packages] [Bug 1987979]

2023-04-15 Thread Nathan Teodosio
I tried
https://github.com/brailcom/speechd/commit/4fc86d73a87c9e120489b89b43d4e9423b68df4f
and that seems to have solved the problem here!

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

Title:
  [snap] Firefox Narrator stopped working after upgrade from 20.04 to
  22.04

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  In Progress

Bug description:
  I just noticed that the narrator feature, which reads articles out
  load with TTS in Firefox reading view stopped working after upgrading
  to 22.04. Another user reported the same problem on ask Ubuntu:

  https://askubuntu.com/questions/1418391/no-tts-voices-on-
  firefox-v102-0-after-upgrading-to-ubuntu-22-04-lts

  Also, if you have no clue what this is about:
  https://askubuntu.com/questions/953509/how-can-i-change-the-voice-
  used-by-firefox-reader-view-narrator-in-ubuntu

  ---

  1)

  $   lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  2) Firefox is a snap now, but I guess for the feature to work it needs
  to detect TTS which is packaged as deb.

  $  snap list firefox
  Name Version  Rev   Tracking   Publisher  Notes
  firefox  104.0-3  1749  latest/stable  mozilla✓   -

  $  apt-cache policy espeak speech-dispatcher-espeak-ng firefox
  espeak:
    Installed: 1.48.15+dfsg-3
    Candidate: 1.48.15+dfsg-3
    Version table:
   *** 1.48.15+dfsg-3 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status
  speech-dispatcher-espeak-ng:
    Installed: 0.11.1-1ubuntu1
    Candidate: 0.11.1-1ubuntu1
    Version table:
   *** 0.11.1-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.11.1-1 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  firefox:
    Installed: (none)
    Candidate: 1:1snap1-0ubuntu2
    Version table:
   1:1snap1-0ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  3) open a website, enter reader mode, click the icon with sound waves
  and hear the text being read with TTS

  4) the icon is missing

  ---

  Edit: I tested Firefox Flatpak and it is also affected, my best guess
  is that Firefox is not at fault.

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


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


[Desktop-packages] [Bug 1811724] Re: libbd_mdraid.so.2: cannot open shared object file

2023-04-15 Thread Bug Watch Updater
** Changed in: udisks2 (Debian)
   Status: Unknown => New

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

Title:
  libbd_mdraid.so.2: cannot open shared object file

Status in udisks2 package in Ubuntu:
  Confirmed
Status in udisks2 package in Debian:
  New

Bug description:
  Had some (probably unrelated?) trouble typing input into login console, and 
went looking through /var/log/syslog : 
  found

  Jan 14 21:10:21 vps39184 udisksd[611]: udisks daemon version 2.8.1 starting
  Jan 14 21:10:22 vps39184 udisksd[611]: failed to load module mdraid: 
libbd_mdraid.so.2: cannot open shared object file: No such file or directory
  Jan 14 21:10:22 vps39184 udisksd[611]: Failed to load the 'mdraid' 
libblockdev plugin

  Seems to give this warning every time I boot.

  udisks2:
Installed: 2.8.1-3
Candidate: 2.8.1-3

  ubuntu: 19.04 disco

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: udisks2 2.8.1-3
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu18
  Architecture: amd64
  CustomUdevRuleFiles: 80-net-setup-link.rules
  Date: Mon Jan 14 21:31:52 2019
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Red Hat KVM
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=/dev/vda1 ro vga16fb.modeset=0 quiet splash
  SourcePackage: udisks2
  UpgradeStatus: Upgraded to disco on 2018-11-23 (52 days ago)
  dmi.bios.date: 01/01/2007
  dmi.bios.vendor: Seabios
  dmi.bios.version: 0.5.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: Red Hat
  dmi.modalias: 
dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.6.0PC:cvnRedHat:ct1:cvr:
  dmi.product.family: Red Hat Enterprise Linux
  dmi.product.name: KVM
  dmi.product.version: RHEL 6.6.0 PC
  dmi.sys.vendor: Red Hat

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


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


[Desktop-packages] [Bug 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual

2023-04-15 Thread Ludovic Rousseau
The problem MAY be related to Debian issue #1034209 "pcscd:
dh_installsystemd doesn't handle files in /usr/lib/systemd/system"
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034209

** Bug watch added: Debian Bug tracker #1034209
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034209

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

Title:
  pcscd 1.9.5-3 do not start automatically, only manual

Status in pcsc-lite package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Mate 22.04 with the latest updates.
  Problem is present with internal smart-card reader and also external usb 
smart-card reader.

  eid-viewer sees no card reader,but When i do:

  sudo pcscd -f

  it is working, also following the tips of Ludovic:
  
https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html

  sudo systemctl stop pcscd.socket
  sudo systemctl start pcscd.socket

  It is working until next restart.

  libacsccid1  version: 1.1.8-1
  libccid version: 1.5.0-2
  pcscd version: 1.9.5-3
  eid-archive version: 2022.3
  eid-mw version: 5.0.28v5.0.28-0u2204-1
  eid-viewer version: 5.0.28v5.0.28-0u2204-1

  In Firefox, my eid card is then also recognized, but only in the ESR
  version, but this is a know Mozilla bug.

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


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